Chapter 10. Diagram Reference

Table of Contents

1. Structural Diagrams
2. Class Diagram
2.1. Diagram Elements
2.2. Toolbar
3. Object Diagram
3.1. Diagram Elements
3.2. Toolbar
4. Component Diagrams
4.1. Diagram Elements
4.2. Toolbar
5. Deployment Diagrams
5.1. Diagram Elements
5.2. Toolbar
6. Behavioral Diagrams
7. Use Case Diagrams
7.1. Diagram Elements
7.2. Toolbar
8. Sequence Diagrams
8.1. Diagram Elements
8.2. Toolbar
9. Collaboration Diagrams
9.1. Diagram Elements
9.2. Toolbar
10. State Machine Diagrams
10.1. States
10.2. Creating Diagrams
10.3. Editing Diagrams
10.4. Diagram Elements
10.5. Toolbar
11. Activity Diagrams
11.1. Creating Activity Diagrams
11.1.1. Using the Spacer Feature
11.2. Actions
11.2.1. Call Action
11.2.2. Send Signal Action
11.2.3. Accept Event Action
11.3. Nodes
11.3.1. Input and Output Pins
11.3.2. Object Node
11.3.3. Initial, Final Activity, and Final Flow Nodes
11.3.4. Fork and Join Nodes
11.3.5. Decision and Merge Nodes
11.3.6. Activity Parameter Node
11.4. Flow
11.4.1. Object and Control Flow
11.4.2. Exception Handler
11.5. Activity Groups
11.5.1. Activity Partitions
11.5.2. Interruptable Activity Regions
11.5.3. Expansion Regions
11.5.4. Conditional Nodes
11.5.5. Loop Node
11.6. Diagram Elements
11.7. Toolbar

There is a lot to say about when to use which diagram type when developing a design, and what the role of it should be. The different answers to this are referred to as the design process or design method. This document is not intended to describe a concrete design process. Poseidon for UML can be used for any such process. Instead, in this chapter we will look at the various diagram types and how the corresponding model elements are created or edited in Poseidon. For many of these diagrams, a short example has already been given in the default model Stattauto, which we looked at in Chapter 4.