A diagram is a thinking and communication tool. The best diagram is not the most technically impressive one—it is the simplest model that answers the audience’s question without hiding important complexity.
Choose the model that makes the important relationship or behavior easiest to understand.
Use case diagrams show actors, system boundaries, and goals. They are useful early because they focus on who needs what from the system without prescribing interface detail.
Model only the detail needed for the decision and audience.
A team needs to understand both the customer flow and payment-service behavior.
Use an activity diagram for select dates → property → details → pay → confirmation.
Add decision paths for availability and payment failure.
Use a sequence diagram for UI, booking service, payment gateway, and notification service.
Validate each model with the audience that owns its decisions.
The process model aligns business and UX, while the sequence model gives engineering and QA an unambiguous interaction view.
Open each answer, then practice saying it naturally in your own words.
Choose by purpose: use case for goals, activity or BPMN for flow, sequence for interactions, DFD for information movement, and domain models for structure.
A role or external system interacting with the solution.
A BPMN point where process flow branches or joins.
A participant’s timeline in a sequence diagram.
A visual area grouping activities by role or system.
Answer all three questions. Score 2 out of 3 to pass this section and update your course progress.
Choose one answer for every question, then submit your quiz.