<Project Name>
Implementation Model Document
Version <1.0>
[Note: The following template is provided for use with the
Unified Process for EDUcation. Text enclosed in square brackets and displayed
in blue italics (style=InfoBlue) is included to provide guidance to the author
and should be deleted before publishing the document. A paragraph entered
following this style will automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which
display a gray background when selected), select File>Properties and replace
the Title, Subject and Company fields with the appropriate information for this
document. After closing the dialog, automatic fields may be updated throughout
the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or
simply click on the field and press F9. This must be done separately for
Headers and Footers. Alt-F9 will toggle between displaying the field names and
the field contents. See Word help for more information on working with fields.]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3 Definitions, Acronyms, and Abbreviations
2. Implementation Model
Overview
3.1.1 Components and subsystems to be
implemented
3.1.2 Implementation model related
diagrams
Implementation Model
Document
[The introduction of the Implementation Model Document provides
an overview of the entire document. It includes the purpose, scope,
definitions, acronyms, abbreviations, references, and overview of this Implementation
Model Document.]
[Specify the purpose of this Implementation Model Document.]
[A brief description of the scope of this Implementation
Model Document; what model(s) it is associated with and anything else that
is affected or influenced by this document.]
[This subsection provides the definitions of all terms,
acronyms, and abbreviations required to properly interpret the Implementation
Model Document. This information may be provided by reference to the
project’s Glossary.]
[This subsection provides a complete list of all documents
referenced elsewhere in the Implementation Model Document. Identify each
document by title, report number (if applicable), date, and publishing
organization. Specify the sources from which the references can be obtained.
This information may be provided by reference to an appendix or to another
document.]
[This subsection describes what the rest of the Implementation
Model Document contains and explains how the document is organized.]
[Include Global Implementation Model Diagram and Packages to
provide an overview of the multiple components to be implemented. In the early iterations, it is possible that
this model is not complete, but its content is ought to change to the project
evolution.]
[State which components and subsystems to implement in this
iteration. Also state the preferred order in which the subsystems will be
implemented to be ready in time for integration. Include Implementation model
packages/sections to picture the subsystems to be implemented]
[The integration, in the iteration, is divided into a number
of increments, each resulting in a build, which is integration-tested. This
section specifies which builds to create and which subsystems will be part of
each build. For each build, this section needs to specify how the build is
constructed, the criteria for its assessment and how it is to be tested, in
particular:
·
Construction
Build scripts
and any other instructions that describe how the build is constructed.
Baseline records that define the
versions of the configuration items used to construct the build.
·
Evaluation and Test
Evaluation criteria—a description of the capabilities
against which the build will be judged. This may contain a subset of the
evaluation criteria in the corresponding Iteration Plan and other build
specific evaluation criteria (particularly when, for example, the build is an
architecture build which does not deliver much, if any capability that is visible
to the end-user.
Installation and setup instructions to execute and test the
build.
Test cases,
test procedures, test scripts, and test results.
Note: In all cases, there is no requirement to replicate
material in this plan—references will suffice if the material exists in other
artifacts; for example, the Artifact: Test Plan.]