Activity: Promote Baselines
Purpose
- The purposes of this activity is to ensure that
baselines (individually tested components from various implementers, and
development teams, combined together to work together as a product) are
'tagged' to reflect the level of software maturity, stability and
quality they may have achieved. The appropriately tagged baselined
version is then available for release or further development in
subsequent iterations
|
Role:
Integrator
|
Frequency: On-going as part of the Iterative Development Process |
Steps
|
Input Artifacts:
|
Resulting Artifacts:
|
Baselines help to keep the project team synchronized. They provide a view to
the most current version of the project assets. As such, baselines need to
created on a regular basis in accordance with the project's CM policies.
Baselines could be named after the phase and iteration in which they area
created. In this instance the name of a baseline could be BL-Product-X-c2,
implying that it is the baseline created at the end of the second iteration in
the Construction Phase.
However, the other labeling conventions for baselines could be commensurate
with the level of testing, and quality, a product baseline may have achieved. In
this case, the baseline could, for example, be tagged as:
- Integration Tested,
- System Tested,
- Acceptance Tested, and
- Production.
The labeling convention described above suggests that the once a baseline has
been tested, and verified, to have achieved a certain quality level it is
promoted and tagged with higher order label.
| |
|