Artifact: Project-Specific Templates
| These are the templates for document artifacts and reports used in the project. There can also be templates for models and modeling elements, such as the design model. | |
| Other Relationships: | Part Of Development Process |
| Role: | Process Engineer |
| Optionality/Occurrence: | Early in the project and revisited for every iteration. |
| Templates and Reports: | |
| Examples: | |
| UML Representation: | Not applicable. |
| More Information: | - Guideline: Alternative Representations of Document Artifacts |
| Input to Activities: - Launch Development Process - Prepare Templates for the Project | Output from Activities: - Prepare Templates for the Project |
Purpose
The Project-Specific Templates are produced to support the production of artifacts and reports.
Timing
The selection and tailoring of already existing templates is usually done in the early days of the project, and revisited for every iteration, based on the needs faced by the project for the upcoming iteration. The development of new templates may be performed in any iteration as needed.
Responsibility
The Process Engineer role is primarily responsible for this artifact. Those responsibilities include:
- Selecting appropriate templates for the project.
- Preparing these templates by doing project-specific adjustments to make them more usable.
- Working with the artifact producers to incorporate suggestions for improvements.
- Initiating the development of new templates needed by the project.
- Promoting any templates developed or modified by the project to the process group responsible for harvesting and producing assets for reuse.
Tailoring
Which templates to select varies from project to project. Each template should be tailored to fit the needs of the project. Tailoring can range from inserting the project’s look and feel and meta information, to more extensive tailoring of the content of the templates.