Master UML Modeling: From Use Cases to Class Diagrams for System Architecture

Abstract

This article starts from system architecture modeling, sharing the author’s experience and summarizing how to analyze requirements, create abstract models, and use UML diagrams to communicate design ideas.

Chapter Contents

Abstract

Chapter contents

Modeling tool introduction and usage

Abstract model diagrams

Essential summary

Series progress

Next chapter preview

Modeling Tool Introduction

Before introducing tools, the article defines a modeling language as a graphical or textual language based on rules, symbols, diagrams, and keywords that describe the structure and behavior of a model and convey knowledge to those familiar with the language.

The most widely used modeling language is UML (Unified Modeling Language), which has become an industry‑standard.

UML originated in 1997 when the Object Management Group (OMG) released it to provide a common design language for development teams, enabling them to read and discuss system architecture similarly to architectural blueprints.

By 2003 UML gained broad industry acceptance, yet many professionals still lack a deep understanding of its concepts.

Abstract Models in Modeling

The series will use UML exclusively for modeling, and subsequent chapters will build designs based on UML diagrams.

UML diagrams are divided into structural and behavioral types.

Behavioral Diagrams

Use‑case diagram

A use‑case diagram shows system functions, actors, and their interactions, helping teams visualize functional requirements.

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 each module to achieve high cohesion and low coupling, identifying participants (users, roles, databases, etc.).

Refine modules into specific use cases.

Analyze relationships among actors and use cases.

Iterate the above steps if any part remains unclear.

Class Diagram

Class diagrams depict the static structure of a system, showing entities, their attributes, and relationships.

They consist of a rectangle divided into three compartments (name, attributes, operations) and can include namespaces (packages).

Modifiers indicate visibility (public, protected, private). Static members are underlined; virtual members are italic.

Class diagrams also support parameterized (generic) types.

Elements of a class diagram:

Attributes: visibility, name, type, default value, multiplicity.

Operations: visibility, name, parameter list, return type, parameter direction.

Relationships between classes include:

Association (including aggregation and composition).

Generalization (inheritance).

Dependency (e.g., constructor injection).

Aggregation represents a “has‑a” relationship with a hollow diamond, while composition uses a solid diamond to indicate stronger ownership.

Chapter Summary

The chapter provides a concise introduction to UML, focusing on use‑case and class diagrams, which are essential modeling artifacts for system design.

Understanding UML enables analysts to view problems from multiple angles, improve designs, and clearly express functional separation and composition.

Next Chapter Preview

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