Activity diagrams in LLD - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the correct purpose of an activity diagram

Which of the following best describes the main purpose of an activity diagram in system design?

A To illustrate the database schema and table relations

B To define the static structure of classes and their relationships

C To represent the physical deployment of software components

D To show the sequence of actions and decisions in a process flow

💡 Hint

Think about how activity diagrams help visualize workflows.

Activity diagrams focus on the flow of activities and decisions, showing how a process progresses step-by-step.

❓ Architecture

intermediate

Trace the flow in an activity diagram for user login

Given an activity diagram for a user login process, which step logically follows after 'Validate Credentials' if the credentials are correct?

A Grant access to the user dashboard

B Display error message

C Request password reset

D Log out the user

💡 Hint

Consider what happens when validation succeeds.

When credentials are valid, the system proceeds to grant access rather than showing errors or resetting passwords.

❓ scaling

advanced

Choose the best way to represent parallel activities in an activity diagram

In an activity diagram, how should you represent two activities that can happen at the same time?

A Use a merge node to combine activities

B Use a decision node to choose one activity

C Use a fork node to split the flow into parallel paths

D Use an initial node to start both activities sequentially

💡 Hint

Parallel means happening simultaneously, not choosing between options.

A fork node splits the flow into multiple parallel paths, allowing activities to run concurrently.

❓ tradeoff

advanced

Select the tradeoff when using activity diagrams for complex systems

What is a common tradeoff when using detailed activity diagrams for very complex systems?

A They simplify understanding by showing only high-level steps

B They can become cluttered and hard to read due to too many activities

C They eliminate the need for other UML diagrams

D They automatically generate code without errors

💡 Hint

Think about what happens when too many details are shown.

Detailed activity diagrams may become overwhelming and reduce clarity if too many activities and flows are included.

❓ estimation

expert

Estimate the number of swimlanes needed for a multi-role process

A process involves three roles: Customer, Sales Agent, and Manager. To clearly show responsibilities in an activity diagram, how many swimlanes should be used?

A Three swimlanes, one for each role

B Two swimlanes, grouping Customer and Sales Agent together

C Four swimlanes, adding one for system processes

D One swimlane for all roles combined

💡 Hint

Swimlanes separate activities by who performs them.

Each role should have its own swimlane to clearly show which activities belong to whom.

Practice

1. What is the main purpose of an activity diagram in system design?

easy

A. To visually show the flow of tasks and decisions in a process

B. To list all database tables and their relationships

C. To define the hardware requirements for a system

D. To write the detailed code for each function

Solution

1. Step 1: Understand activity diagram purpose

   Activity diagrams are used to show how tasks flow and decisions are made in a process.

2. Step 2: Compare with other options

   Options B, C, and D describe database design, hardware planning, and coding, which are not the role of activity diagrams.

3. Final Answer:

   To visually show the flow of tasks and decisions in a process -> Option A

4. Quick Check:

   Activity diagram = task flow visualization [OK]

Hint: Activity diagrams map task flows, not data or code [OK]

Common Mistakes:

• Confusing activity diagrams with database diagrams
• Thinking activity diagrams show code details
• Mixing hardware design with activity flow

2. Which of the following is the correct symbol for a decision point in an activity diagram?

easy

A. A rectangle with rounded corners

B. A circle with a thick border

C. A diamond shape

D. A parallelogram

Solution

1. Step 1: Recall activity diagram symbols

   Decision points in activity diagrams are shown as diamond shapes to represent branching.

2. Step 2: Identify other symbols

   Rectangles with rounded corners are actions, circles with thick borders are start/end nodes, and parallelograms are not standard in activity diagrams.

3. Final Answer:

   A diamond shape -> Option C

4. Quick Check:

   Decision symbol = diamond [OK]

Hint: Decision points always use diamond shapes [OK]

Common Mistakes:

• Confusing decision diamonds with action rectangles
• Using circles for decisions
• Mixing input/output symbols with decisions

3. Consider this activity diagram snippet:

Start -> Action A -> Decision (Yes/No)
Yes -> Action B -> End
No -> Action C -> End

What is the correct flow if the decision is 'No'?

medium

A. Start -> Action A -> Action B -> End

B. Start -> Action A -> End

C. Start -> Action A -> Decision -> Action B -> Action C -> End

D. Start -> Action A -> Action C -> End

Solution

1. Step 1: Trace the flow for 'No' decision

   From the decision node, if the answer is 'No', the flow goes to Action C, then to End.

2. Step 2: Verify other options

   Start -> Action A -> Action B -> End follows 'Yes' path, Start -> Action A -> Decision -> Action B -> Action C -> End incorrectly chains both actions, Start -> Action A -> End skips actions after decision.

3. Final Answer:

   Start -> Action A -> Action C -> End -> Option D

4. Quick Check:

   'No' decision leads to Action C [OK]

Hint: Follow arrows from decision to correct action [OK]

Common Mistakes:

• Mixing 'Yes' and 'No' paths
• Skipping actions after decision
• Assuming both paths run together

4. In an activity diagram, a developer mistakenly connects two actions with a double arrow instead of a single arrow. What is the likely issue?

medium

A. There is no difference; arrows can be single or double

B. The flow will be interpreted as parallel execution, causing confusion

C. The double arrow means the process loops infinitely

D. The diagram will show a syntax error and not render

Solution

1. Step 1: Understand arrow meaning in activity diagrams

   Single arrows show normal flow; double arrows often indicate parallel or concurrent flows.

2. Step 2: Analyze impact of double arrow misuse

   Using double arrows between two actions may confuse readers into thinking tasks run in parallel, which is incorrect if not intended.

3. Final Answer:

   The flow will be interpreted as parallel execution, causing confusion -> Option B

4. Quick Check:

   Double arrow = parallel flow confusion [OK]

Hint: Single arrow = flow; double arrow = parallel flow [OK]

Common Mistakes:

• Assuming double arrows cause syntax errors
• Thinking double arrows mean loops
• Ignoring arrow style importance

5. You need to design an activity diagram for a user login process that includes entering credentials, validating them, and either granting access or showing an error. Which sequence correctly represents this flow?

hard

A. Start -> Enter Credentials -> Validate -> Decision (Valid?) -> Access Granted / Show Error -> End

B. Start -> Validate -> Enter Credentials -> Decision (Valid?) -> Access Granted / Show Error -> End

C. Start -> Enter Credentials -> Decision (Valid?) -> Validate -> Access Granted / Show Error -> End

D. Start -> Enter Credentials -> Access Granted -> Validate -> Show Error -> End

Solution

1. Step 1: Identify correct logical order

   User must first enter credentials, then system validates them before deciding validity.

2. Step 2: Check each option's sequence

   Start -> Enter Credentials -> Validate -> Decision (Valid?) -> Access Granted / Show Error -> End follows logical order: enter -> validate -> decision -> outcome. Others have steps out of order.

3. Final Answer:

   Start -> Enter Credentials -> Validate -> Decision (Valid?) -> Access Granted / Show Error -> End -> Option A

4. Quick Check:

   Login flow = enter -> validate -> decide -> outcome [OK]

Hint: Follow real process order: input, check, decide, respond [OK]

Common Mistakes:

• Placing validation before input
• Skipping decision step
• Mixing outcome order