Task: Create Baselines
This task defines what a Baseline is and when Baselines should be created.
Purpose
  • To ensure that all developed work products are captured and archived, at given points in time, as a basis for further product development. 
Relationships
RolesMain: Additional: Assisting:
InputsMandatory: Optional: External:
  • None
Outputs
Main Description

Good candidates for a baseline are the sets of files and directories under version control that are developed, integrated and released together. A baseline identifies one and only one version of a element. Composite baselines are groupings of baselines delivered by teams working on separate subsystems of the overall project.

Part of the iterative development methodology is to constantly build an executable product. A baseline should be seen as the moving front of development which contains the necessary work products for subsequent development. So baselines should be created certainly at the end of each iteration.

Project baselining practices are followed in accordance with the configuration identification, baselining and archiving step defined in Task: Establish CM Policies.



Properties
Multiple Occurrences
Event Driven
Ongoing
Optional
Planned
Repeatable
More Information