|
Process
Requirement gathering
Our team essence all the user needs and related details to the design. The purpose of this discipline is to engineer
the requirements for your project, including the identification, modeling, and documentation of those requirements.
The main deliverable of this discipline is the Software Requirements Specification (SRS), also referred to as the Requirements Model,
which encompasses the captured requirements.
Design Draft
The purpose of this discipline is to evolve a robust architecture for your system based on your requirements, to transform the requirements into a first design
draft, and to ensure that implementation environment issues are reflected in your design.
The initial view of website's design draft is presented to the client. The actual improvement process starts after the feedbacks are
provided from the client to OCS team.
Reconsideration
If the project cannot pass the milestone, there is still time for it to be cancelled or redesigned by our team.
Final Design Draft
In this phase the main focus goes to the development of components and other features of the system being designed. This is the phase when the bulk of the
coding takes place. In larger projects,
several construction iterations may be developed in an effort to divide the use cases into manageable segments that produce demonstrable prototypes.
This phase produces the final external release of the software.
Website launch
In this phase the website demo has moved from the development of OCS to the end user.
If all objectives are met, the website is launched and the development cycle ends.
|