The Word template can be bought through a template package. Case studies and reports are freely available in the table below.
The purpose of the Implementation Model Document is to define the order in which the components and subsystems should be implemented, which builds to create when integrating the system, and how they are to be assessed.
The following people will use the Implementation Model Document:
- Implementers, to plan the order in which to implement classes, and what and when to deliver to system integration
- Integrator, as a planning tool
- Test designer, to define the tests for the iteration
As soon as it has been decided which use cases are to be implemented, the Implementation Model Document is planned in the current iteration. It is modified as needed during the iteration.
An integrator is responsible for authoring the Implementation Model Document, and keeping it up-to-date. For each build, the test designer will contribute descriptions of the test cases, test procedures and test scripts to be used to assess the build. These may be supplied as references to material contained in other test artifacts.
You should adjust the outline of the Implementation Model Document to suit the nature of your project. For example, if the system is large, there may be a case for having subsidiary plans for each subsystem. The formality and extent of the test material contained or referenced from the Implementation Model Document will vary depending on the significance of the build. Obviously the final build of an iteration will be formally assessed against all the evaluation criteria described in the Iteration Plan.