Development Case: Implementation
For a high level overview of the activities done in the Implementation Discipline, see the Implementation Workflow Detail diagram in the organizational Development Case.
Topics
Artifacts used 
Here is a list of artifacts this project will produce for the Implementation Discipline. The Review details indicate the formality in the review procedure for a particular artifact. To see the corresponding artifact list for the organizational process, follow this link.
| Artifacts |
Deliverables |
Review Details | Tools used | |||
| Incep | Elab | Const | Trans | |||
| Implementation Model | X | X | Formal-Internal | Rational Rose | ||
| Integration Build Plan | X | X | Formal-External | Microsoft Word | ||
| Test Drivers, stubs | X | X | Informal | |||
| Architectural Prototype Software Baseline | X | Formal-External | ||||
| R1.0 Software Baseline | X | Formal-External | ||||
| R2.0 Software Baseline | X | Formal-External | ||||
Notes on the Artifacts
The project plans to release two versions of the software, to ensure customer satisfaction and to be able to correct any major issues raised by the user community from trying out the first release. The Architectural Prototype will be demonstrated in the development environment. It requires formal approval from the project owners.
The Architectural parts of the Implementation Model is captured in the Implementation View section of the Software Architecture Document (see Analysis & Design Discipline Configuration).
Reports
None.
Additional Review Procedures
None.
Other Issues
None.