Capability Pattern: Environment
This capability pattern covers the activities and workflow for the Environment discipline.
DescriptionWork Breakdown StructureTeam AllocationWork Product Usage
Purpose
The purpose of the environment activities is to provide the software development organization with the software development environment, both processes and tools, that support the development team.
Relationships
Context
Description
During the early iterations of the project, the project-specific environment is prepared. The project-specific environment is then refined during each iteration, as needed.
Properties
Event Driven
Multiple Occurrences
Ongoing
Optional
Planned
Repeatable
Illustrations
Examples
Usage
Usage Notes

Decide How to Perform the Workflow

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

  • Decide how to perform the workflow by looking at the activities in this workflow. Study the diagram with its guard conditions and the guidelines. Decide which activities to perform and in which order. 
  • Decide what parts of the Environment activities 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 User Support Material.
  • Decide when, during the project lifecycle, to introduce each part of the workflow. The Development Process is always introduced in the beginning of a project.  Optionally, the Development Case may be used to document the detailed, project-specific tailoring decisions. A customized Delivery Process may be imported into Rational Portfolio Manager to aid in assigning work and tracking progress of the project. The other artifacts are introduced when they are needed.
More Information
Guidelines
Concepts

©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.