Chapter 10. Diagram Reference

Table of Contents
10.1. Structural Diagrams
10.2. Class Diagram
10.2.1. Diagram Elements
10.2.2. Toolbar
10.3. Object Diagram
10.3.1. Diagram Elements
10.3.2. Toolbar
10.4. Component Diagrams
10.4.1. Diagram Elements
10.4.2. Toolbar
10.5. Deployment Diagrams
10.5.1. Diagram Elements
10.5.2. Toolbar
10.6. Behavioral Diagrams
10.7. Use Case Diagrams
10.7.1. Diagram Elements
10.7.2. Toolbar
10.8. Sequence Diagrams
10.8.1. Diagram Elements
10.8.2. Toolbar
10.9. Collaboration Diagrams
10.9.1. Diagram Elements
10.9.2. Toolbar
10.10. State Machine Diagrams
10.10.1. States
10.10.2. Creating Diagrams
10.10.3. Editing Diagrams
10.10.4. Diagram Elements
10.10.5. Toolbar
10.11. Activity Diagrams
10.11.1. Creating Activity Diagrams
10.11.2. Actions
10.11.2.1. Call Action
10.11.2.2. Send Signal Action
10.11.2.3. Accept Event Action
10.11.3. Nodes
10.11.3.1. Input and Output Pins
10.11.3.2. Object Node
10.11.3.3. Initial, Final Activity, and Final Flow Nodes
10.11.3.4. Fork and Join Nodes
10.11.3.5. Decision and Merge Nodes
10.11.3.6. Activity Parameter Node
10.11.4. Flow
10.11.4.1. Object and Control Flow
10.11.4.2. Exception Handler
10.11.5. Activity Groups
10.11.5.1. Activity Partitions
10.11.5.2. Interruptable Activity Regions
10.11.5.3. Expansion Regions
10.11.5.4. Conditional Nodes
10.11.5.5. Loop Node
10.11.6. Diagram Elements
10.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.

10.1. Structural Diagrams

Structural diagrams are used to show the organization of the system and include Class, Component, Deployment, and Object diagrams.