UML Architecture Diagrams: Types, Usage, and Timing in the Software Development Lifecycle

For many developers, architecture diagrams are essential tools for understanding, planning, and building software systems. This article, featuring senior architect Li Zhihui (Tencent Cloud TVP) and author of the bestseller "High‑Concurrency Architecture Practice", introduces common UML architecture diagrams, explains their selection principles, and describes when and how to use them during software design.

1. Introduction

Architecture diagrams serve as a bridge between architects, product managers, developers, and testers. A single diagram can convey complex system structures more effectively than words.

2. Common UML Architecture Diagrams

Class Diagram : Shows classes, their attributes, methods, and static relationships (association, dependency, composition, aggregation, inheritance, generalization). Example image included.

Sequence Diagram : Describes dynamic interaction among participants (objects, components, servers) using vertical lifelines and activation bars.

Component Diagram : Depicts physical components (JAR, DLL, etc.) and their static dependencies. Often used for module design.

Deployment Diagram : Illustrates the final physical deployment of the system, including servers and key components.

Use‑Case Diagram : Shows actors (people or other systems) and the system’s functional requirements.

State Diagram : Presents the lifecycle states of a single object (e.g., order, user) and transitions between them.

Activity Diagram : Describes process logic and business flow, similar to a flowchart, and introduces swimlanes to separate responsibilities.

3. Application Scenarios and Timing in the Software Development Cycle

Requirement Analysis : Use case diagrams for functional description, activity diagrams for key business processes, sequence diagrams for integration scenarios, simplified class diagrams for domain modeling, and state diagrams for objects with complex state changes.

High‑Level Design : Deployment diagrams for the physical blueprint, component diagrams (and component sequence diagrams) for module relationships, and component activity diagrams for inter‑component workflows.

Detailed Design : Class diagrams and class‑level sequence diagrams guide code implementation; activity diagrams can detail complex method logic.

4. Conclusion

UML is a language for thinking and communication. When designing software architecture, draw diagrams to clarify your ideas and to help others understand them. The focus should be on accurate expression rather than aesthetic perfection.

Recommended online tool: https://app.diagrams.net/

Author: Li Zhihui, senior architect at Tongcheng Travel, Tencent Cloud TVP, former Alibaba technical expert, Intel Asia‑Pacific architect, CTO of ZhaiMi and WiFi万能钥匙, Apache Spark contributor, author of "High‑Concurrency Architecture Practice" and "Large‑Scale Website Architecture".

Note: The article also contains promotional content for community activities, giveaways, and QR‑code images.