The top-level Package Diagram (PD) in each UML model includes four packages, one for each of the views in the model. One of these packages, called processors, may be decomposed through one or more further levels of PD to a set of Deployment Diagrams (DPDs).
DPDs are UML’s attempt to recognise that there is a world outside software. That is, these diagrams attempt to show the physical processors in the system (called nodes in DPDs), the processes that are allocated to them, and, to a limited extent, how these processors are interconnected.
These diagrams are intended to show the allocation of processes to nodes, by listing the processes that may run on a processor underneath the node symbol for the processor. Cradle will support this mapping in a different way, by providing a frame called PROCESSES in the node’s component specification, in which the names of the processes allocated to the node can be listed.
By being defined by component specifications, the descriptions of nodes will be cross referenceable.
DPDs do not show data exchanges between nodes. For a more complete representation of architectures, consider Architecture Interconnect Diagrams (AIDs) and Process Architecture Diagrams (PADs).
DPDs are not hierarchical. Their connectivity is:
DPDs are only available in models in the Implementation Domain.
DPDs take their name and number from the package from which they are an expansion. They contain nodes and links. The nodes are defined by specifications. The number of the specification is the dot concatenation of the DPD number and the node number, its name is the same as the node name.
An example DPD is:
The symbols available in DPDs are:
Symbol | Name | Description | Definition | Expansion |
---|---|---|---|---|
Comment | Makes a note anywhere in the diagram. Are always surrounded by * characters. Note: If you do not want Cradle to automatically add an * go to the Graphics Settings section of Project Setup and turn off the Automatically add asterisks to diagram's comment symbols option. | None | None | |
Processor Node | A runtime physical object that represents a processing resource, generally having at least a memory and often processing capability as well. | Equipment specification | None | |
Picture | Allows you to choose the location of a GIF or JPEG image to be displayed as a diagram symbol or to be embedded in an existing diagram symbol. | None | None | |
Node Dependency | A communication association. | None | None | |
Item | Represents a requirement or system note in the diagram. | None | None | |
Context Item | Represents a requirement or system note in a diagram and is a container within which other object symbols can be drawn or attached. | None | None | |
Cross Reference Link | Represents a cross reference that exists between a pair of system notes/requirements. It can also represent a cross reference between a system note/requirement and a specification or data definition or system that describes the objects symbols that it connects. | None | None |