Mastering UML: When to Use Sequence, Component, and State Diagrams

1. Review of the Previous Chapter

The previous article introduced the standard modeling language UML, covering use‑case and class diagrams and basic modeling techniques. An error in the aggregation relationship diagram was identified and corrected, as shown in the images below.

2. Abstract

The article summarizes the author’s experience with system‑architecture modeling, aiming to help readers unfamiliar with UML tools or the process of building abstract models from requirements. It introduces the core UML structural and behavioral diagrams that will be covered.

3. Chapter Outline

Review of the previous chapter

Abstract

Chapter content

Abstract model diagrams

Chapter summary

Series progress

References

Preview of the next article

4. Abstract Model Diagrams in UML

4.1 Sequence Diagram

Introduction

A sequence diagram (also called a communication diagram) describes the detailed steps of a process by showing the interaction order among objects. It complements use‑case diagrams by visualizing how a system function is implemented.

Details

Key elements include objects (lifelines), activation bars, and messages. An example of an IC‑card bus‑fare transaction illustrates object creation, activation, synchronous and asynchronous messages, and object destruction (shown by an X on the lifeline).

The diagram also demonstrates synchronous vs. asynchronous calls, interaction frames for flow control, and the use of callbacks.

Summary

Interaction frames can be nested but increase complexity, so it is advisable to split complex flows into separate sequence diagrams.

4.2 Component Diagram

Introduction

Component diagrams describe the relationships among system components. UML’s definition of a component has evolved from a simple file or executable to an independent, encapsulated unit that provides services.

Details

Elements include components, containers, packages, constraints, and notes. Relationships such as dependency and generalization are modeled similarly to class diagrams.

Components expose interfaces (e.g., a "Person" component offering "Thinking" and "Sleep" interfaces) and can be packaged, containerized, or constrained.

Summary

Component diagrams help architects partition system functionality, enabling reuse and clear service contracts.

4.3 State Diagram

Introduction

State diagrams model the behavior of a single object (or component) by showing how it changes state in response to events. They are useful when an object’s lifecycle is driven by state transitions.

Details

Applicable to use cases, classes, subsystems, or entire systems. Elements include states, initial/final markers, transitions, decision points, synchronization bars, and composite (nested) states.

Examples illustrate decision points, parallel synchronization, and composite states for complex workflows such as ordering and payment processes.

Summary

To create a state diagram: identify the object, list all possible states and triggering events, mark start and end states, and decide whether composite states are needed for clarity.

5. Chapter Summary

The chapter covered UML sequence, component, and state diagrams, explaining their purposes, key elements, and when to use each. It also outlined a step‑by‑step approach for modeling with these diagrams.

6. References

http://www.uml.org – Official UML website.

http://www.rational.com/uml/resources/documentation/index.jsp – UML specifications.

http://www.rational.com/rose – IBM Rational Rose tool.

http://www.rational.com/xde – IBM Rational XDE tool.

http://argouml.tigris.org – ArgoUML open‑source tool.

http://uml.sourceforge.net/index.php – Umbrello UML Modeller.

7. Preview of the Next Article

The next installment will complete the discussion with activity and deployment diagrams, as well as other less‑common UML diagram types.