Guidelines: Important Decisions in Environment
Topics
Decide How to Perform the
Workflow 
The following decisions should be made regarding the Environment workflow:
- Decide how to perform the workflow by looking at the Environment: Workflow Details. Study the diagram with its guard conditions, and the guidelines. Decide which workflow details to perform and in which order.
- Decide which parts of the Environment workflow to perform. In general the artifacts in the Environment workflow are introduced as they are needed. For example, a Manual Styleguide is developed, only if the project will develop End-User Support Material.
- Decide when, during the project lifecycle, to introduce each part of the workflow. More information look at Environment: Workflow Details. The Artifact: Development Case is always introduced in the beginning of a project. the other artifacts are introduced when they are needed. For example, the Artifact: Programming Guidelines should be ready when you start implementing.
Decide How to Use Artifacts
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) |
| Business Modeling Guidelines | Should have. If you do business modeling, this is mainly used to determine the scope and level of detail. |
| Design Guidelines | Must have. If you design, you'll always need design guidelines. The main issue is to determine the scope and level of detail. |
| Development Case | Must have. The main issue is to determine the scope of the development case. |
| Development Infrastructure | Must have. |
| Development-Organization Assessment | Could have. |
| Manual Styleguide | Must have. If you develop end-user support material, you'll always need a manual styleguide. The main issue is to determine its scope and level of detail. The simplest solution is to use an existing styleguide. |
| Project-Specific Templates | Must have. There will be a template for each document artifact and each report. |
| Programming Guidelines | Must
have. If you develop code, you'll always need programming guidelines. The
main issue is to determine its scope and level of detail. The simplest
solution is to use existing programming guidelines.
See Artifact: Programming Guidelines for some ready-to-use programming guidelines delivered with the Rational Unified Process. |
| Test Guidelines | Should have. If you test, you will always need Test Guidelines. The main issue is to determine its scope and level of detail. |
| Tools | Must have. The issue here is to select and acquire the supporting tools you'll use. |
| Use-Case Modeling Guidelines | Must have. You will always need use-case modeling guidelines. The main issue is to determine its scope and level of detail. |
| User-Interface Guidelines | Could have. If you model the user interface, you will need User-Interface Guidelines. |
Tailor each artifact by performing the steps described in Activity:
Develop Development Case, under the heading "Tailor Artifacts per
Workflow".
