After deliberation of the general concept of the project, along with a considerable amount of details on the specifications, the project is
officially launched to production.

A time table is made based on the requirements, estimated difficulty of
the tasks involved, and the approximate length of time required for each
task. The allocation of manpower will also refer to this time table.

A detailed list of specifications and a step by step description of every
input and output is made to ensure a clear understanding of the
processes involved in the project. If necessary, a translation for the
specifications and scenarios is also made during this period.

A sample is made which shows the basic appearance and functionality
of the project based on the specifications. The sample is made for
approval and as a primary basis on how the requirements are
implemented in the project as well as determine other possible options
to improve the project. At this point it is possible that the specifications
and scenario is modified to optimize the capabilities and create
workarounds on the limitations of the project based on the sample.

A partial version of the project is released which has all functionalities
active but all the modules may or may not be complete yet. The design
and layout are complete at this point.

Tests are done locally and by the client based on the Alpha version.
Bug reports are made both locally and by the client on both the physical
appearance and also on the functionalities of the project. All bugs will
be fixed and questionable issues will be further discussed with the
client and will be resolved during this phase.

A complete version of the project is released. All functionalities are
active and all modules are complete. The design and layout are
complete and may be final in this phase.

Another round of tests are performed both locally and by the client
based on the Beta version. Bug reports are made along with other
issues and requests by the client. Bugs will be fixed and all issues
will be further discussed and a final resolution is made and addressed.
Another version and debugging phase will be done if necessary and
if the schedule permits.

A final version is then made which is exactly how the final copy of the
project will be released. If the distribution will be on CDs then the final
version will be released as a CD in order to simulate its actual
performance. This release is considered final and contains all the
necessary installers and utilities as will be expected in the distribution
copy of the project.

Local testers and client's testers will give this final version several
rounds of thorough testing and detailed check. Bug reports will be
made both locally and by the client and a final request on changes on
questionable issues will also made. All bugs will be fixed and verified
and all issues will be resolved and verified.

A master copy is created and sent to the client from the fixed and verified version after the final testing process. The master copy is an exact version of how the project will be distributed.