|
|
| Development Process |
|
| |
| Quality control is based on the principle that all deliverables from the application shall be independently reviewed, so that defects are identified and corrected as soon as possible. |
|
| |
|
 |
|
| A strategy for testing may be viewed in the context of a spiral. Unit testing begins at the vortex of the spiral, and concentrates on each unit/component of the software as implemented in the source code. Using the component level design description as a guide, important control paths are tested to uncover errors within the boundary of the module. Testing progresses outwards along the spiral to integration testing, where the focus is on design and the construction of software architecture. Integration testing is a systematic technique for constructing the program structure, while at the same time conducting tests to uncover errors associated with interfacing. As we move outwards on the spiral, we encounter validation testing where requirements established as part of requirement analysis are validated against the software that has been constructed. Finally, we arrive at system testing, where the software and other system elements are tested as a whole. |
|
| Deployment |
|
| After the entire product is completely tested and approved, the deployment team deploys the product in the target environment as specified in the deployment document. The deployment diagram given by the systems architect during the architecture phase is used to deploy various components of the product in their target environments. |
|
| |
 |
|
|
|
|
|
|
|
