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.