Master UML Modeling: From Basics to Use Case & Class Diagrams

Abstract

This article starts from system architecture modeling, sharing the author’s work and study experience, and aims to help readers unfamiliar with modeling processes, tools, or requirement‑driven model creation understand how to analyze requirements and build abstract models—an essential skill for architects.

Chapter Contents

1. Abstract 2. Chapter contents 3. Modeling tool introduction and usage 4. Abstract model diagrams 5. Summary 6. Series progress 7. Next chapter preview

Modeling Tool Introduction

Before introducing tools, the article defines a modeling language as a rule‑based graphical or textual language used to describe the structure and behavior of a model and to convey knowledge to those familiar with the language.

Among many modeling languages, UML (Unified Modeling Language) is the most popular and widely adopted standard.

UML originated in 1997 when the Object Management Group (OMG) released it to provide a common design language for development teams. By 2003 UML had become industry‑accepted, though many professionals still lack deep understanding.

Abstract Model in Modeling

The series will use UML exclusively for modeling, and subsequent chapters will continue to rely on UML diagrams for design.

UML diagrams are divided into structural and behavioral types.

Behavioral Diagrams

Use‑Case Diagram

A use‑case diagram shows system functions, actors (users, external systems, etc.), and their interactions.

Key elements: system, actors, use cases, relationships.

Typical relationships include include, extend, and generalization, plus association lines for direct actor‑use‑case links.

Steps to create a use‑case diagram:

Divide the system into functional modules.

Abstract functional requirements to achieve high cohesion and low coupling, identifying actors for each module.

Refine modules into specific use cases.

Analyze relationships among actors and use cases.

Iterate the above steps if any part remains unclear.

Class Diagram

A class diagram is the most common structural diagram, depicting static system structure, entities, their attributes, and operations.

It consists of a rectangle divided into three compartments: name, attributes, and operations.

Attributes include visibility (public, protected, private), name, type, default value, and multiplicity. Operations include visibility, name, parameter list, and return type.

Relationships between classes:

Association : a line indicating a direct relationship; includes aggregation (has‑a, hollow diamond) and composition (stronger has‑a, filled diamond).

Generalization : inheritance shown by a line with a hollow triangle pointing to the parent.

Dependency : a dashed line with an arrow indicating one class depends on another.

Examples of each relationship are illustrated with images.

Chapter Summary

The chapter provides a brief introduction to UML and detailed guidance on building use‑case and class diagrams, two essential diagram types for modeling. It emphasizes that UML helps analyze problems from multiple angles, improve design, and clearly express functional separation and composition.

Next Chapter Preview

The next article will cover other commonly used UML diagrams such as sequence diagrams, component diagrams, and state diagrams.