Artifacts >
Environment Artifact Set >
Development Case >
Guidelines >
Important Decisions in Deployment
Guidelines:
|
Part of workflow |
Comments |
Developing end-user materials | This includes Role: Technical Writer, Activity: Develop Support Materials, and Artifact: End-User Support Material. |
Developing training materials | This includes Role: Course Developer, Activity: Develop Training Materials, and Artifact: Training Materials. |
Beta testing | Only introduce Workflow Detail: Beta Test Product if you do beta testing. |
Document the decisions in the Development Case, under the headings Disciplines, Deployment, Workflow.
Decide which artifacts to use and how to use each of them. The table below describes those artifacts you must have and those used in some cases. For more detailed information on how to tailor each artifact, and a discussion of the advantages and disadvantages of that specific artifact, read the section titled "Tailoring" for each artifact.
For each artifact, decide how the artifact should be used: Must have, Should have, Could have or Won't have. For more details, see Guidelines: Classifying Artifacts.
Artifact | Brief Tailoring Comments (see the artifact for details) |
Bill of Materials | Must have. |
Deployment Plan | Must have. The question is how comprehensive to make this, which depends on the complexity of the deployment. |
Deployment Unit | Must have. It contains everything that make up a product. |
End-User Support Material | Must have. End-user support material are always developed. The question is how the end-user support material is designed. |
Installation Artifacts | Must have. |
Product | Must have. |
Release Notes | Must have. |
Training Materials | Should have. Use this if end-users need to be trained. |
Tailor each artifact by performing the steps described in Activity:
Develop Development Case, under the heading "Tailor Artifacts per
Discipline".
Rational Unified
Process
|