According to the standards of project management, each project should     pass through certain phases for its successful realization.

Web development also has number of phases which are thought to be the good practice of development.

All starts with your quote’s handling. Your quote is analyzed and either the rough estimate is sent back to you, or some additional questions are asked to define the initial requirements.

The rough estimate provides the information of project’s duration (in hours) and cost. It may be changed during the requirements’ definition – or stay idem.

After we agree on estimate – the project is started.

So we come to the phase called system modeling. During the modeling you’ll get the prototype of your future site (interlinked html pages which will reflect all elements of the website) as well as functional specification with the scrupulous description of the site – starting with its scope and purpose and up to the browsers’ choice and detailed portrayal of each page.

You’ll check both prototype and specification, and after they’re approved the final estimate is created with detailed information of all functionality decomposed into modules.

So we come to the next phase – development.

After the site is ready – we move toward the quality assurance. It is normally accomplished in two iterations – first, when the project is ready, it’s tested locally. After the local testing is finished – the site is set up on client’s host and there starts the second iteration of testing.

Only after we make sure the projects’ functionality works fine and no bugs are left – we ask you to check the site up.

After you declare the web site being conformed to the requirement – we close the project.