UML and Object-Oriented Design

4.

Behavioral UML Diagrams

4.1.

Use Case Diagram

4.1.1.

Purpose and Applications

4.1.2.

4.1.2.1.

4.1.2.1.1.

4.1.2.1.2.

Secondary Actors

4.1.2.1.3.

4.1.2.1.4.

Actor Generalization

4.1.2.2.

4.1.2.2.1.

Use Case Notation

4.1.2.2.2.

Use Case Naming

4.1.2.2.3.

Use Case Descriptions

4.1.2.2.4.

Use Case Specifications

4.1.2.3.

System Boundary

4.1.2.3.1.

System Boundary Box

4.1.2.3.2.

Subject Classification

4.1.3.

4.1.3.1.

4.1.3.1.1.

Actor to Use Case Association

4.1.3.1.2.

Communication Association

4.1.3.2.

4.1.3.2.1.

Use Case Inclusion

4.1.3.2.2.

Include Semantics

4.1.3.3.

4.1.3.3.1.

Use Case Extension

4.1.3.3.2.

Extension Points

4.1.3.3.3.

Extend Conditions

4.1.3.4.

4.1.3.4.1.

Actor Generalization

4.1.3.4.2.

Use Case Generalization

4.1.4.

Use Case Documentation

4.1.4.1.

Preconditions and Postconditions

4.1.4.2.

Main Success Scenarios

4.1.4.3.

Alternative Flows

4.1.4.4.

Exception Flows

4.2.

Activity Diagram

4.2.1.

Purpose and Applications

4.2.2.

4.2.2.1.

4.2.2.1.1.

Action Notation

4.2.2.1.2.

4.2.2.2.

4.2.2.2.1.

Activity Notation

4.2.2.2.2.

Activity Parameters

4.2.2.3.

4.2.2.3.1.

4.2.2.3.2.

Activity Final Node

4.2.2.3.3.

Flow Final Node

4.2.2.4.

4.2.2.4.1.

Control Flow Arrows

4.2.2.4.2.

4.2.2.5.

4.2.2.5.1.

4.2.2.5.2.

4.2.2.5.3.

4.2.2.6.

Decision and Merge Nodes

4.2.2.6.1.

Decision Node Notation

4.2.2.6.2.

Guard Conditions

4.2.2.6.3.

Merge Node Notation

4.2.2.7.

Fork and Join Nodes

4.2.2.7.1.

Fork Node Notation

4.2.2.7.2.

Join Node Notation

4.2.2.7.3.

Parallel Execution

4.2.2.8.

4.2.2.8.1.

Activity Partitions

4.2.2.8.2.

Responsibility Assignment

4.2.3.

Advanced Concepts

4.2.3.1.

Exception Handling

4.2.3.2.

Interruptible Activity Regions

4.2.3.3.

Expansion Regions

4.3.

Sequence Diagram

4.3.1.

Purpose and Applications

4.3.2.

4.3.2.1.

4.3.2.1.1.

Object Lifelines

4.3.2.1.2.

Actor Lifelines

4.3.2.1.3.

Lifeline Notation

4.3.2.2.

4.3.2.2.1.

Execution Specification

4.3.2.2.2.

Focus of Control

4.3.2.3.

4.3.2.3.1.

Synchronous Messages

4.3.2.3.2.

Asynchronous Messages

4.3.2.3.3.

Return Messages

4.3.2.3.4.

4.3.2.3.5.

Create Messages

4.3.2.3.6.

Destroy Messages

4.3.2.4.

Object Creation and Destruction

4.3.2.4.1.

Creation Notation

4.3.2.4.2.

Destruction Notation

4.3.2.4.3.

Object Lifecycle

4.3.3.

Interaction Fragments

4.3.3.1.

Combined Fragments

4.3.3.2.

4.3.3.3.

Alternative Fragment

4.3.3.4.

Optional Fragment

4.3.3.5.

Parallel Fragment

4.3.3.6.

Critical Region Fragment

4.3.3.7.

Negative Fragment

4.3.3.8.

Assertion Fragment

4.3.4.

Time and Duration Constraints

4.3.5.

Interaction Occurrences

4.4.

State Machine Diagram

4.4.1.

Purpose and Applications

4.4.2.

4.4.2.1.

4.4.2.1.1.

4.4.2.1.2.

4.4.2.1.3.

Internal Activities

4.4.2.1.3.1.

4.4.2.1.3.2.

4.4.2.1.3.3.

4.4.2.2.

4.4.2.3.

4.4.2.4.

4.4.2.4.1.

Transition Notation

4.4.2.4.2.

4.4.2.4.3.

Guard Conditions

4.4.2.4.4.

Actions and Effects

4.4.2.5.

Self-Transition

4.4.3.

Advanced Concepts

4.4.3.1.

Composite States

4.4.3.1.1.

4.4.3.1.2.

Hierarchical States

4.4.3.2.

Orthogonal Regions

4.4.3.2.1.

Concurrent States

4.4.3.2.2.

Parallel Regions

4.4.3.3.

4.4.3.3.1.

Shallow History

4.4.3.3.2.

4.4.3.4.

Junction and Choice Points

4.5.

Communication Diagram

4.5.1.

Purpose and Applications

4.5.2.

4.5.2.1.

Lifelines as Nodes

4.5.2.2.

Messages as Links

4.5.2.3.

Sequence Numbering

4.5.2.4.

4.5.3.

Relationship to Sequence Diagrams

4.5.4.

Structural Emphasis

4.6.

Interaction Overview Diagram

4.6.1.

Purpose and Applications

4.6.2.

Combining Activity and Sequence Elements

4.6.3.

Interaction Occurrences

4.6.4.

Control Flow Between Interactions

4.6.5.

High-Level Interaction Modeling

4.7.

4.7.1.

Purpose and Applications

4.7.2.

Lifelines with Timelines

4.7.3.

State Changes over Time

4.7.4.

Condition Changes

4.7.5.

Time and Duration Constraints

4.7.6.

4.7.7.

Message Exchanges

Previous

3. Structural UML Diagrams

Go to top

Next

5. Object-Oriented Design Principles