Architecture modeling
On this page 9 topics
Overview
Topics
- C4
- UML
- ArchiMate introduction
- deployment and integration diagrams
Learn first
3.5 h of practice (estimate)
Learning outcomes
- Choose the right notation for the audience: C4 for software structure, UML for behavior and detail, ArchiMate for business–application–technology layering.
- Draw integration diagrams showing systems, interfaces, protocols, data flows, and ownership.
- Draw deployment diagrams showing environments, networks, and trust boundaries.
- Keep models consistent across views and maintained as code where practical.
Lessons
Lab and exercises
Lab
ARC-005-LAB1 · Larkspur current-state model
Outcomes: 1–4 · Time: ~3.5 h
- Draw the system context diagram of today's landscape (stores, web shop, ERP, CRM, payment provider, carriers).
- Create an ArchiMate layered view: business processes, applications, technology.
- Draw an integration diagram of today's interfaces with protocol, direction, data, and owner.
- Add a deployment sketch with environments and trust boundaries.
- Add header blocks (audience, question, legend) and check names are consistent across diagrams.
Acceptance: each diagram has a legend, an audience, and the question it answers.
Exercises (case-based; six exercises)
| ID | Outcome | Task |
|---|---|---|
| ARC-005-EX01 | 1 | For five Larkspur questions, choose the notation (C4, UML, ArchiMate) and justify. |
| ARC-005-EX02 | 1 | Draw a C4 context diagram for the new commerce platform with six neighbours. |
| ARC-005-EX03 | 2 | Draw a sequence diagram for order payment with provider timeout and retry. |
| ARC-005-EX04 | 3 | Draw a deployment diagram with store LAN, data center, and cloud zones; mark where payment data crosses a boundary. |
| ARC-005-EX05 | 4 | Review a given diagram set for naming inconsistencies and missing legends; list fixes. |
| ARC-005-EX06 | 4 | Propose how to keep the Larkspur model as code (text source, generated views, version control) and what you would not model. |
Show solutions
- EX01 Structure of the platform → C4; payment call order and failure → UML sequence; which applications support which processes → ArchiMate; order lifecycle → UML state; which environments hold data → deployment diagram.
- EX02 Neighbours: customers, store staff, ERP, CRM, payment provider, carrier service; each labelled with purpose and protocol.
- EX03 Order service calls provider; on timeout, query status by idempotency key before retrying; show alt and failure branches.
- EX04 Trust boundary lines between store LAN, data center, cloud; the payment provider link crossing the boundary is labelled with TLS and tokenized card data.
- EX05 Typical issues: the same system named "ERP", "SAP", and "Finance system"; arrows without direction; no legend. Fix with a shared glossary and standard legend.
- EX06 Text-based sources (for example C4 DSL or diagram-as-code), generated images, kept in a repo with review; do not model every class or every minor interface.
Outcome 2 is also covered by the lab integration diagram.
Workplace evidence: architecture diagrams that business and engineering stakeholders both used.
Quiz
Outcomes: O1 choosing notation · O2 integration diagrams · O3 deployment diagrams · O4 consistency and models as code.
A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.
Practical part
Model review of the lab diagrams plus exercises ARC-005-EX01 to EX06. Pass: quiz at least 8/10, at least five of six exercises correct, and every lab diagram carrying a legend, audience, and question.
Common mistakes
One diagram for everyone; boxes and arrows without labels or legends.
Assessment
Model review.
Workplace evidence
Architecture diagrams that business and engineering stakeholders both used.
Career relevance
Architecture deliverables (ARC-034).