Theory 20 minutes + Workshop 60 minutes
Duration: 80 minutes. Artefact produced: interaction sequence diagram.
Module Overview
Describe how actors, systems, services, and events interact over time.
Identify where responsibility, latency, failure, or control changes between parties.
Make API calls, events, requests, and responses visible enough for delivery.
Use the flow to discuss monitoring, recovery, support, and exception handling.
Theory
A component diagram shows structure. A sequence diagram shows behaviour. It explains what happens, in what order, between which participants, and where important handoffs occur. It is valuable when a decision depends on integration flow, error handling, ownership, performance, or operational support.
Workshop
Model the sequence for a user accessing a clinical application through cloud identity, integration services, application services, data services, logging, and monitoring.
Create a sequence diagram for one critical business transaction and label the main failure points.
Explain how the sequence diagram changes the architecture conversation compared with a static component view.
Sequence diagram; participant list; failure points; monitoring and support notes.
Module 7 — Activity and Class Diagrams.