UML Diagrams Overview – Class Diagrams, Sequence Diagrams, Activity Diagrams & Use Cases

This article is a concept overview of UML diagrams, including exam questions and tags.

In a Nutshell

UML diagrams (Unified Modeling Language) are standardized graphical representations used to model software systems. They help visualize structure, behavior, and workflows, making them essential to software development and professional certification exams.

Technical Definition

UML comprises 14 different diagram types, divided into structural and behavioral diagrams. Structural diagrams (such as class diagrams, object diagrams, and component diagrams) describe the static aspects of a system. Behavioral diagrams (such as activity diagrams, state diagrams, and sequence diagrams) represent dynamic processes and interactions. UML is programming language-agnostic and serves as a communication tool within development teams and with stakeholders. Class diagrams, use case diagrams, activity diagrams, and sequence diagrams are especially relevant for certification.

Exam-Relevant Key Points

• UML is a standardized notation for software models
• Distinction between structural and behavioral diagrams
• Class diagrams show attributes, methods, and relationships
• Sequence diagrams visualize message flow between objects
• Activity diagrams describe process and workflow logic
• Use case diagrams show user interactions with the system
• Diagrams must be created correctly, legibly, and in compliance with standards
• UML is part of professional certification project documentation

Core Components

1. Class Diagram (structural model with classes, attributes, methods)
2. Object Diagram (concrete instances of a class diagram)
3. Component Diagram (modules and their dependencies)
4. Activity Diagram (control flow, loops, decision points)
5. State Diagram (object states and their transitions)
6. Use Case Diagram (use cases, actors, system boundaries)
7. Sequence Diagram (temporal message flow)
8. Communication Diagram (object interactions, structural)
9. Package Diagram (structuring large systems)
10. Deployment Diagram (distribution of software across hardware)

Practical Example

// Example: excerpt from a class diagram
- User
    - username: String
    - password: String
    - login(): boolean
    - logout(): void

Explanation: A "User" class with attributes and methods for login. The notation shows visibility (+ public, - private).

Advantages and Disadvantages

Advantages

• Structured and standardized representation of complex systems
• Promotes team understanding and documentation
• Supports communication with non-technical stakeholders

Disadvantages

• Creation effort increases with system complexity
• Risk of over-documentation
• Not all diagram types are immediately intuitive

Typical Exam Questions (with Brief Answers)

1. What does a class diagram show? Classes, their attributes, methods, and relationships to one another.
2. When do you use an activity diagram? To represent processes, workflows, or algorithm execution.
3. What does UML stand for? Unified Modeling Language – a standardized modeling notation.
4. Which are behavioral diagrams? Activity, sequence, state, use case, and communication diagrams.
5. What is a use case diagram? Shows interactions between users (actors) and the system.
6. How is inheritance represented in a class diagram? An arrow with a white triangular head pointing from subclass to superclass.
7. Difference between sequence and activity diagrams? Sequence diagrams show temporal object communication; activity diagrams show control flows.
8. Why use UML in professional certification project documentation? It helps visualize and describe software architecture.

Next in the UML Learning Path

The next article in the UML learning path covers UML Fundamentals: Diagram Types and Notation — a detailed introduction to different UML diagram types and their notation.

Key Resources

1. https://plantuml.com/de
2. https://www.uml-diagrams.org
3. https://www.draw.io