Mastering UML: From Project Kickoff to System Design with Real-World Cases

Project Initiation Phase

This stage corresponds to problem definition and feasibility research, focusing on interviews to confirm what the system should do, assess project scope, essential business processes, technical constraints, and key success factors.

Requirement Analysis Phase

Requirement analysis involves gathering and documenting needs via use‑case diagrams. Business process design uses the Eriksson‑Penker Business Extension Model to capture high‑level workflows, followed by activity diagrams that illustrate the "big picture" without excessive detail.

From the activity diagram of the electronic procurement system, specific use cases are extracted by questioning participants about actors, required services, and system interactions.

Use‑case diagrams are then created to visualise functional requirements.

System Design Phase

Design builds on the use‑case model, identifying Control Objects, Entity Objects, and Boundary Objects. Each use case is mapped to a control object with defined responsibilities, inputs, and outputs.

Example: the "Generate Purchase Request (RFP)" use case yields a control object with two private functions.

Two‑stage sequence diagrams validate interactions: first treat the system as a black box, then replace it with concrete control objects.

Establishing the Domain Model

Domain models capture the essential concepts of the problem space using class diagrams. The case of the hospital discharge system demonstrates how control objects, entity objects (e.g., bed, patient, doctor), and boundary objects are identified and organized.

Package diagrams group classes into namespaces to control access.

Expressing Object Interaction

Sequence diagrams depict the flow of messages between objects for a given use case, serving as a blueprint for developers.

Communication diagrams complement sequence diagrams by showing structural relationships alongside interactions.

Micro‑Design Artifacts

Object diagrams capture a snapshot of all objects at a specific moment, aiding verification of class diagrams.

State‑machine diagrams consolidate state transitions of key entities (e.g., hospital bed) derived from multiple use cases.

When timing is critical, time diagrams highlight temporal constraints, such as automatic bed status changes after a timeout.

Conclusion

The article has covered the essential UML diagrams used during requirement analysis and system design, illustrated with two real‑world case studies, and points to additional UML diagram types for further study.