Activity diagrams in LLD - Architecture Diagram

System Overview - Activity diagrams

An activity diagram visually shows the flow of actions or steps in a process or system. It helps understand how tasks move from one step to another, including decisions and parallel actions.

Key requirements include clear representation of activities, decisions, and flow direction to model workflows effectively.

Architecture Diagram

  +-----------------+       +-----------------+       +-----------------+
  |   Start Node    | ----> |   Activity 1    | ----> | Decision Node   |
  +-----------------+       +-----------------+       +-----------------+
                                                        /               \
                                                       /                 \
                                              +-----------------+   +-----------------+
                                              | Activity 2 (Yes) |   | Activity 3 (No)  |
                                              +-----------------+   +-----------------+
                                                       \                 /
                                                        \               /
                                                      +-----------------+
                                                      |   End Node      |
                                                      +-----------------+

Components

Start Node

start_node

Marks the beginning of the activity flow

Activity 1

activity

Represents the first action or step in the process

Decision Node

decision_node

Represents a branching point based on a condition

Activity 2 (Yes)

activity

Action taken if decision condition is true

Activity 3 (No)

activity

Action taken if decision condition is false

End Node

end_node

Marks the end of the activity flow

Request Flow - 6 Hops

Start Node → Activity 1

Activity 1 → Decision Node

Decision Node → Activity 2 (Yes)

Decision Node → Activity 3 (No)

Activity 2 (Yes) → End Node

Activity 3 (No) → End Node

Failure Scenario

Component Fails:Decision Node

Impact:The process cannot branch correctly, causing the flow to stop or take wrong paths.

Mitigation:Add validation checks before the decision node and fallback default paths to ensure process continuity.

Architecture Quiz - 3 Questions

What is the purpose of the Decision Node in an activity diagram?

A To represent a branching point based on a condition

B To start the process

C To end the process

D To perform an action

Design Principle

Activity diagrams use clear nodes and flows to model processes visually, helping teams understand and communicate workflows with decisions and parallel steps.

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