Artifacts > Environment Artifact Set > Development Case > Guidelines > Important Decisions in Environment

Topics

Decide How to Perform the Workflow To top of page

The following decisions should be made regarding the Environment discipline's workflow:

  • Decide how to perform the workflow by looking at the Environment: Workflow. Study the diagram with its guard conditions and the guidelines. Decide which workflow details to perform and in which order. 
  • Decide what parts of the Environment workflow details to perform. In general, the artifacts in the Environment discipline 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. 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 To top of page

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 Purpose

Tailoring (Optional, Recommended)

Guidelines

 Project specific guidelines are appropriate whenever there are project-specific standards that must be followed, or good practices that need to be communicated.

Recommended as applicable to project activities.

Many projects will reuse guidelines rather than create their own. Small teams with experienced members and a shared philosophy may decide not to formally document some guidelines. The risk in this case is that standards and quality may drift over time.
Development Case Documents the development process to be followed on the project.

Recommended for most projects.
Development Infrastructure (including Tools) This is the hardware and software tools used as part of development. All projects will have a Development Infrastructure. Many projects will reuse an existing development infrastructure, rather than create their own.
Development-Organization Assessment Used to guide the process engineer in tailoring a process for an organization.

Optional.

In large organizations, an assessment is usually critical to making good process-related decisions.
  Ensures consistent style and quality of end-user support material.

Recommended for most projects with end-user support material.

Many projects will reuse an existing styleguide rather than create their own.
Project-Specific Templates  

Optional.

Associated with more formal processes.

Tailor each artifact by performing the steps described in Activity: Develop Development Case, under the heading "Tailor Artifacts per Discipline".



Copyright  © 1987 - 2001 Rational Software Corporation


Display Rational Unified Process using frames

Rational Unified Process