In the design phase, many issues must be dealt with, many dilemmas solved and users’ needs defined in order to reach an actual technical solution. It is crucial in developing the solution to adhere to the theoretically defined and experience-based and confirmed methodology, which consists of the following phases:

  • comprehensive analysis of the existing state and potential technical limitations and particularities;
  • In case of a completely new system, careful analysis of the needs that the solution must meet and fulfil;
  • outlining the solution proposal, with all its architecture and technical specificities that might influence the existing system or future functioning. Thorough elaboration of the solution proposed and all the details of its implementation guarantee to the user, preferably before all interested services, that the solution will be suitable in entirety and not just in one part of its structure;
  • steps necessary to define the solution commercially as well as all the phases necessary to choose the solution and the provider are the precondition for continuation;
  • the continuation implies that the consensus on solution acceptability has been reached, which means that the design of project solution can commence, encompassing not only technical elaboration but also temporal dimension of the solution as well as its interactions with the existing system and the work process, that most frequently must not be disturbed;
  • an integral part of the solution set up in such a way must also be the analysis of potential difficulties and risks, and their mitigation. It is thereby ensured that the solution will be implemented in the scope that guarantees that functional specifications and the deadline are met, in other words, that “the thing bought” will be implemented in the arranged period of time.

Design procedure conducted in this way provides the user with assurance that proposed solutions are functional, developed according to best practice principles, and financially optimal.