Analysis and design diagrams¶
Analysis collaboration¶
One per use case: the actor, the boundary used, the control that coordinates and the entities touched, with numbered messages. Boundaries talk only to controls; entities never call upward.
Design classes¶
Packages by layer or feature, as recorded in a decision, with the operations each class exposes. Interfaces appear where a dependency must be inverted.
Design sequence¶
Messages between concrete design elements, including the failure path as an alt block and the transaction boundary as a note. It must follow the same paths as the specification.
Data model¶
Tables or collections with keys, relations and constraints, mapped from the entities and listed with that mapping. Lines are drawn for foreign keys only.
Components¶
Components grouped by layer, the interfaces they provide and require, and which component implements each interface. Dependencies point at interfaces, not at implementations.
Deployment¶
Nodes, containers, external systems and the protocols on the links.