UCM design overview
Now that we understand the basic UCM objects, there are more questions:
What is the best way to put the objects together into a usage model?
How many components should I use and at what level should they be defined?
How many projects should I have?
We can answer these questions quickly and all at once: it depends.
In this section we break down the variables that factor into UCM design decisions by taking a closer look at the objects that most determine your usage model:
Components— Decomposing an application into configuration objects
Projects— Organizing the development and release efforts
Streams— Organizing the workflow within a project
Components, project, and streams define the structure of the configuration and how, at ...
Get Software Configuration Management: A Clear Case for IBM Rational ClearCase and ClearQuest UCM now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
