The top-level Package Diagram (PD) in each UML model includes four packages: one for each of the views in the model. Two of these packages, called components and processes may be decomposed through one or more further levels of PD to a set of Component Diagrams (CPDs).
In the Component View, CPDs show dependencies between compilation units, typically including source files, and the runtime components of the final system. In the Process View, the CPDs show the dependencies between processes (scheduleable units that may be selected for execution on the host machine’s processor) in terms of runtime components. Runtime components typically include:
These diagrams are intended to show the allocation of classes to compilation units and processes, respectively, although UML does not define how this is to occur. Cradle will support this mapping by providing a frame called CLASSES in which the names of the classes contained within the component or task can be listed.
By being defined in component specifications, the components and tasks are cross referenceable.
CPDs are not hierarchical. Their connectivity is:
CPDs are only available for models in the Implementation Domain.
CPDs take their name and number from the package from which they are an expansion. They contain components and tasks, each of which is defined by a specification.
An example CPD is:
Here is a description of the symbols available: