In the implementation phase, the team builds the components either from scratch or by composition. Given the architecture document from the design phase and the requirement document from the analysis phase, the team should build exactly what has been requested, though there is still room for innovation and flexibility. For example, a component may be narrowly designed for this particular system, or the component may be made more general to satisfy a reusability guideline. 2.2 The architecture document should give guidance. Sometimes, this guidance is found in the requirement document. The implementation phase is summarized in Table 2.3 on page .
The implementation phase deals with issues of quality, performance, baselines, libraries, and debugging. The end deliverable is the product itself.
There are already many established techniques associated with implementation. This thesis does not depend on which technique is followed.