Labels versus Baselines
January 7, 2010A common question from new Configuration Managers is, “What is the difference between a label and a baseline”.
A label is exactly what it sounds like, a name assigned to one or more things (whatever they are). Generally no further qualification is needed.
A baseline, in configuration management circles, has much more significance.
A baseline is an immutable set of items, including all the information that specifies those items and records of how those items where derived. Baselines are subject to audit to confirm their integrity. The precise nature of these audits varies according to lifecycle phase and the environment (safety critical, commercial, defence and so on). Apart from situation specific requirements baseline audits typically aim to establish, as a minimum:
- The baseline contains all relevant items.
- The baseline is correctly identified.
- The records (change records and so on) associated with the baseline are secure, accurate and reflect the true nature of the baseline.
- The baseline is secure; that is, the baseline items are held in a fashion that ensures their availability.
- The baseline has been established through the approved process. For example, that all appropriate development, change and testing has be performed according to the established development methodology.
I would add that even though labels are at a simpler functional level than baselines, labels can be used in the same manner. That is, most tools that provide the label function, give the CM user a way to access all CIs that have a specific label (i.e., a baseline) for reporting or building purposes. I used this extensively with PVCS Version Manager and passed several audits successfully. Further, I have used the baseline functionality provided by Serena Dimensions CM with the equivalent success. Given the opportunity to choose between the two, I prefer using labels because of the flexibility.
Thanks for your articles.
Regards.