Activity diagrams in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of activity diagrams

What is the main purpose of an activity diagram in software engineering?

A To model the flow of control or data from one activity to another within a system

B To define the structure and relationships between classes in a system

C To represent the physical deployment of software components on hardware nodes

D To specify the detailed user interface layout of an application

💡 Hint

Think about diagrams that show steps or actions and how they connect.

Activity diagrams focus on the flow of activities or actions, showing how one step leads to another in a process or system.

📋 Factual

intermediate

Identifying key elements in activity diagrams

Which of the following is NOT a standard element used in UML activity diagrams?

A Fork node

B Decision node

C Class node

D Initial node

💡 Hint

Consider elements that represent control flow versus structural elements.

Class nodes are part of class diagrams, not activity diagrams. Activity diagrams use nodes like decision, fork, and initial nodes to represent flow control.

🔍 Analysis

advanced

Analyzing flow in an activity diagram snippet

Consider an activity diagram where an initial node leads to a fork node splitting into two parallel activities, which then join back at a join node before reaching the final node. What does this structure represent?

A Parallel execution of activities that synchronize before completion

B Conditional branching where only one activity executes

C Sequential execution of activities one after another

D Looping of activities until a condition is met

💡 Hint

Think about what fork and join nodes do in activity diagrams.

Fork nodes split the flow into parallel paths, and join nodes synchronize these paths back into one flow, representing parallel execution that must complete before continuing.

❓ Comparison

advanced

Comparing activity diagrams and flowcharts

Which statement best describes a key difference between UML activity diagrams and traditional flowcharts?

A Flowcharts are part of UML, but activity diagrams are not

B Flowcharts use swimlanes to show responsibilities, but activity diagrams do not

C Activity diagrams only show data flow, while flowcharts show control flow

D Activity diagrams can model concurrent activities, while flowcharts typically cannot

💡 Hint

Consider how each diagram handles multiple activities happening at the same time.

Activity diagrams support modeling concurrent or parallel activities using fork and join nodes, while traditional flowcharts generally represent sequential steps without concurrency.

❓ Reasoning

expert

Determining the number of activities in a complex diagram

An activity diagram includes: 1 initial node, 3 action nodes, 1 decision node with 2 outgoing flows, 2 merge nodes, 1 fork node splitting into 2 parallel actions, 1 join node, and 1 final node. How many distinct action activities are represented?

A 6

B 5

C 7

D 8

💡 Hint

Count all action nodes including those after the fork node.

There are 3 action nodes plus 2 parallel actions after the fork node, totaling 5 distinct action activities. Decision, merge, fork, and join nodes are control nodes, not actions.