Activity Diagram (UML) – Process Modeling, Workflow, Synchronization, Signal & Join
This article is a definition of terms for the activity diagram – including exam questions and tags.
In a Nutshell
An activity diagram models the flow of a process or workflow with a focus on the activities and their flow control within a system or application.
Compact Technical Description
An activity diagram is a behavioral diagram of the UML (Unified Modeling Language) that describes the flow of activities in a system. It graphically represents control and data flows and helps visualize processes both within software processes and between actors and systems. Typical elements are start and end nodes, activities, decisions, and synchronizations. The diagram is ideal for requirements analysis, process modeling, and documentation of business logic. It can represent both sequential and parallel flows.
Exam-Relevant Key Points
- Belongs to the UML diagram family (behavioral diagrams)
- Models business processes and system flows
- Uses symbols such as activity, decision, start and end nodes
- Relevance in IHK for analysis, design, and documentation
- Often used in practice for use-case implementation and workflows
- Allows visualization of security-critical decisions
- Enables economically optimized process analysis
- Supports audit-proof process documentation
Core Components
- Initial Node (start point)
- Final Node (end point)
- Activity (individual step or action)
- Decision Node (branch with conditions)
- Merge Node (merging of paths)
- Fork Node (splitting into parallel flows)
- Join Node (synchronization of parallel paths)
- Swimlanes (actor assignment of activities)
- Guards (conditions on decision branches)
- Object Flows (passing of information between activities)
Practical Example
// Example: Login process
User logs into a system → System checks credentials → if successful proceed to home page, otherwise display error message
Explanation: This simple activity diagram visualizes a login process with branching based on the success or failure of authentication.
Advantages and Disadvantages
Advantages
- Good understandability even for non-developers
- Clearly visualizes complex logic and processes
- Supports process analysis and optimization
- Easy to document and extend
Disadvantages
- Not suitable for very technical processes (e.g., algorithms)
- Risk of over-complexity in large systems
- Misunderstandings due to unclear symbol usage
Typical Exam Questions (with Short Answer)
- What is an activity diagram used for? Modeling flows, processes, or workflows in systems.
- Typical elements? Start node, end node, activity, decision node, fork, join.
- Classification in UML? Belongs to behavioral diagrams.
- Fork vs. Join? Fork divides a flow into parallel paths, join synchronizes them again.
- How is a condition represented on a decision edge? Through guard condition in square brackets.
- Swimlanes used for? To assign activities to specific actors or responsible parties.
- Significance in IHK project work? Clear visualization of system or business processes.
- Support IT security? Explicit representation of security-relevant decision logic and control flows.