Overview
The following section outlines the fundamental concepts of baselines within the CDCM system and the process of creating a “closed baseline.” A baseline represents an unchangeable snapshot of a configuration. While a configuration can grow and evolve over time, a baseline captures it in a precisely defined, finalized state. However, since a configuration in CDCM references other configurations or external work products (such as streams/baselines in Codebeamer), closing a baseline is not straightforward. Only once all referenced objects are also locked and cannot be altered can the baseline be formally “closed.” This multi-step process ensures that the baseline consolidates all information in a definitive state, providing a stable reference point for future audits, comparisons, and traceability.
Creating a New Baseline
When starting the baseline creation process in CDCM, you begin by converting a stream (your initial, flexible configuration) into a baseline. At this stage, the baseline remains open and can still change, but it establishes the core foundation for eventually creating a stable, closed baseline. You can choose to baseline all configuration items or only those tagged with specific baseline types, ensuring that the resulting baseline best fits your project’s needs.
Prerequisites
Permissions:
To create or modify a baseline, you must have the
maintain-concept with typefor the type of the configuration where you want to create a baseline in the current configuration area
Workflow
On the configuration use the sub-menu and click the “create a baseline” button
Create the Baseline:
Choose the scope of the baseline:
Full Baseline: Select all configuration items (CIs) in the configuration.
Partial Baseline: Choose one or more baseline types, only CIs with these baseline types will be in the new baseline
Confirm and save the new baseline.
Closing a Baseline
This section outlines the process of transitioning an open baseline to a fully closed, unchangeable state. It describes each step, from ensuring all referenced configurations and external items are stabilized, to systematically locking down every changeable aspect. The final action is to set the configuration’s state to a “closed baseline” state (see The State Model for more details about state changes). Once this status is successfully applied, the baseline becomes an immutable reference point, capturing the exact state of the configuration and all its associated data at that moment.
Before a configuration can be set to the “closed baseline” state, all referenced configuration items must be stabilized and put into a “closed baseline” state. If a configuration item can be put into a “closed baseline” state depend on the type of referenced item:
Internal configuration item (CDCM configuration): The referenced configuration must be in a “closed baseline” state.
External work product (OSLC-based storage location): The referenced work product must itself be a baseline.
External work product (non-OSLC storage location): Currently, there are no stabilization requirements.
Once all configuration items are in a “closed baseline” state the configuration itself can be put into a “closed baseline” state.
Putting a configuration item and a configuration into a “baseline closed” state cannot be reverted
5. Deriving a Stream from a Baseline
Deriving a stream from a baseline involves taking an existing baseline—regardless of whether it is open or closed—and using it as a starting point for a new stream. This new stream inherits the baseline’s configuration items and settings but reverts them to a flexible, modifiable state, enabling further development and updates.
Steps:
Select a baseline (e.g., Release 1.0).
Click Derive Stream.
Write the title of the new stream into the input field
Confirm to create a new configuration in the Initial state.
Appendices
Glossary
Configuration: A structured collection of items representing a product or system state.
Baseline: A snapshot of a configuration serving as a reference point.
Superstate: A higher-level classification that dictates allowed state transitions.
Known Limitations
Deletion of baseline types is not supported.
Modifications to state model associations are restricted post-creation.
0 Comments