Designing a UML 1.5 Activity Diagram
From RAD Studio
Go Up to UML 1.5 Diagram Procedures Index
Use the following tips and techniques when you design a UML 1.5 Activity Diagram.
To design a UML 1.5 Activity Diagram, follow this general procedure:
- Create one or more swimlanes. You can place several swimlanes on a single diagram, or create a separate diagram for each.
Warning: You cannot create nested swimlanes.
- Create one or more activities. You can place several activities on a single swimlane, or create a separate swimlane for each.
Warning: You cannot create nested activities.
- For convenient browsing, first model the main flow. Next, cover branching, concurrent flows, and object flows.
Tip: Use separate diagrams as needed and then hyperlink them.
- Create Start, End, Signal Receipt, and Signal Sending elements for your swimlanes.If your activity has several Start points, they can be used simultaneously.
- Create object nodes. You do not link object nodes to classes on your Class Diagrams. However, you can use hyperlinks for better understanding of your diagrams.
- Create state nodes for your swimlanes.
Tip: You can create nested states.
- Optionally, create a History node.
- Connect nodes by links.
- You can optionally create shortcuts to related elements of other diagrams.