Theory 20 minutes + Workshop 60 minutes
Duration: 80 minutes. Artefact produced: system component diagram.
Module Overview
Show what is inside the solution, what is outside it, and where responsibility changes.
Use components to describe logical solution parts without implementation noise.
Make dependencies, integration points, and contracts visible.
Use the diagram to explain impact, ownership, risk, and delivery scope.
Theory
A component diagram shows the important parts of a solution, the interfaces between them, and the responsibilities each part carries. Its job is to make structure and dependency visible enough for architecture, delivery, security, and operations to make better decisions.
Workshop
Create a component view for a migration scenario that includes core systems, identity, integration, reporting, data platform, monitoring, and platform services.
Create a component diagram showing major logical components, external systems, and integration contracts.
Explain how your component diagram helps delivery teams understand scope, ownership, and integration risk.
Component diagram; component responsibility notes; interface list; three architecture risks.
Module 6 — Sequence Diagrams.