UML Diagrams Overview – Class Diagram, Sequence Diagram, Activity Diagram & Use Case

This post is a term explanation of the UML diagram overview – including exam questions and tags.

In a Nutshell

UML diagrams (Unified Modeling Language) are standardized, graphical representations for modeling software systems. They help visualize structure, behavior, and processes and are an integral part of software development and IHK exams.

Compact Technical Description

UML comprises 14 different diagram types, divided into structure and behavior diagrams. Structure diagrams (e.g., class diagram, object diagram, component diagram) describe static aspects of a system. Behavior diagrams (e.g., activity diagram, state diagram, sequence diagram) represent dynamic processes and interactions. UML is independent of programming languages and serves communication within the development team and with clients. Class diagrams, use case diagrams, activity diagrams, and sequence diagrams are particularly relevant for exams.

Exam-Relevant Key Points

• UML is a standardized notation for software models
• Distinction between structure vs. behavior 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 IHK project presentations and 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, decisions)
5. State diagram (states of an object 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 of large systems)
10. Deployment diagram (distribution of software on 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 understanding within the team and in documentation
• Supports communication with non-technical stakeholders

Disadvantages

• Creation effort for complex systems
• Risk of over-documentation
• Not every diagram type is intuitively understandable

Typical Exam Questions (with Short Answer)

1. Class diagram shows? Classes, their attributes, methods, and relationships with each other.
2. Use activity diagram? To represent processes, workflows, or algorithm flows.
3. UML stands for? Unified Modeling Language – a standardized modeling language.
4. Behavior diagrams include? Activity, sequence, state, use case, and communication diagrams.
5. Use case diagram is? Shows interactions of users (actors) with the system.
6. Inheritance in class diagram represented? Arrow with white, triangular tip from subclass to superclass.
7. Sequence vs. activity diagrams? Sequence diagrams show temporal object communication, activity diagrams show control flows.
8. UML in IHK project documentation? Helps visualize and describe software architecture.

Most Important Sources

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