How does it happen?
Usually it begins with understanding your needs. It might be just an idea or already defined requirements for an IT system. If it’s the first case, we discuss the idea and think of possible ways for implementing the idea. In the second case we clarify the defined requirements. As a result we get something we call business requirement description. We make a cost estimate based on this description and prepare you an offer. This service is free of charge.
In this step we develop a system while specifying business processes and system functionality, describe data bases and develop on-screen forms. This step is taken by our systems analyst who interviews you. The drawn up document is called SRS (software requirement specification), which typically conforms to LVS 68:1996 standard. In most cases it is sufficient for the client to understand that the system would function and for our programmers to understand how to program the system.
In case there is a necessity for a detailed technical solution description of the system, a document we call SDD (software design description) is drawn up that typically corresponds to LV 72:1996. standard. It is done by our system architects.
In sophisticated projects other documents are drawn up, too – system concept, project organization plan, risk assessment plan, testing concept plan etc.
Often the cost estimate is made after this phase – it allows making more precise cost estimate and set more precise deadlines.
The design phase consists of two parts: design concept and technical design.
Design concept is drawn by conceptual designer whose task is to create the visual concept of the system (especially the public part). The second part is done by a technical designer who draws other parts of the system in the coordinated half-finished visual concept. Technical designer mainly focuses on what we call usability or the convenience of system usage.
In this phase a group of programmers develop a system according to the specification and design. Project manager meets you on an agreed date (typically once a week to once a month) and shows the progress as well as agrees with you what will be done in the next period. Thus you can efficiently follow the progress and direct the project development.
This phase is project specific and can include various means of testing: unit testing, functional testing, integration testing etc. Typically the testing necessary for the project is agreed upon before the project when discussing the business requirements. In any case this phase contains a testing we call accept testing.
In the specification end phase or programming phase a document is drawn up that we call accept testing plan. It describes what particular tests should you carry out to ensure that we have developed a system that corresponds to the specification. After the programming phase our project manager together with your representative carries out these tests. In case of positive test results the system is considered to be developed.
In this phase the system documentation agreed upon before the project development is drawn up. It might be a user manual, an administrator manual etc.
Sometimes manuals are not necessary for simple systems; however, training is necessary for each project. After this phase the people who will use and administrate the system are ready to start working with it.
In this phase your or our system administrators install and configure the server software and the developed system. If there is data that needs to be transferred from other systems, this should be the next implementation step. In sophisticated cases a document we call migration plan is drawn up before this step. This document contains information about the step by step migration from the old system to the new one. After this step the system is considered to be implemented.
9Warranty maintenance and support
During the warranty maintenance period after implementing the system, system errors are fixed free of charge. During this period we also offer system administration and support services. System administrator looks after the server activity. Support service deals with user problems. One can also order simple system changes by using our support system Qtask.