Each project manager or project leader will be responsible for making sure teams members conform to the CM policies concerning these artifacts. In terms of software configuration management, configuration identification means being able to find and identify the correct version of any project artifact quickly and easily. The negative impact of having an ineffective configuration identification system is measured in terms of lost time and quality. 3.1.1 Identification Methods Labels identify specific versions of artifacts. The set of artifacts that constitute a version of a subsystem are, collectively and individually, identifiable by a particular version and label.
Labels are therefore useful in re-use or referencing original sets of versioned artifacts.
The following is a the product artifact labeling convention to be used for labeling paths and artifacts in the product directory structure. During the lifecycle of SHS software projects, baselines based on milestone reviews will be established at the end of each Inception iteration, each Elaboration iteration, each Construction iteration as marked by the review process milestone. This will be accomplished by labeling the entire project directory structure according to the identification methods described above. For example, Project X is up for the Objectives review at the end of the first iteration of the Inception phase. The project manager or project leader makes sure all artifacts for that review period are checked in and creates a label of the project directory structure.