About using composite baselines

A composite baseline selects baselines in other components. You create a composite baseline by creating dependency relationships between the component that stores the composite baseline and the components whose baselines are selected by the composite baseline.

If your project team works on multiple components, you may want to use a composite baseline to represent the project baseline.

Like all baselines, a composite baseline must belong to a component. However, that component does not need to contain any of its own elements. You first create a component without creating a root directory in a VOB. Such a component can never contain any elements of its own. It contains only the composite baseline that selects the recommended baselines of the project components. By using a composite baseline in this manner, you can identify one baseline to represent the entire project. This is easier than keeping track of a set of baselines, one for each component.

In creating the composite baseline using the component without a VOB root directory, you select the latest baseline from each component that the project uses.

A composite baseline can select other composite baselines. For example, if your system is so large that it consists of multiple projects, you may want to use a composite baseline to represent the system baseline. You can use multiple composite baselines within the same project.