A3 architecture overviews
Each sheet takes one aspect of the demo and fits it on one A3 page, for a reader with a quarter of an hour. A reader who finishes a sheet should be able to answer its goal question without opening anything else. An A3 sheet for a fifteen-minute reader says why the overview takes this form.
| Sheet | Title | Goal question | Status |
|---|---|---|---|
| L0 | Federating a systems model | What does this demo claim, what is in the box, and what would I keep or replace if I adopted it? | Approved without external review |
| L1 | Three subgraphs, one graph | What do the three services agree on, and what happens when a number changes? | Not drafted, outstanding work |
| L2a | Adapter: projecting SysML v2 | How does a model file become a subgraph, and where does the adapter stop? | Not drafted, outstanding work |
| L2b | Pipeline example: capacity and verdicts | Why does raising one server change nothing and raising another change everything? | Approved without external review |
The layout follows the A3 architecture overview cookbook of Borches and Bonnema, taken for what it forces on a sheet rather than followed step by step. No artwork from the cookbook is reproduced.
Owner: Roar Elias Georgsen
Each published sheet is built from an HTML source in the repository, which a reader who finds an error can correct as described in illustrations/.
Index: Federating a systems model ยท Repository: https://github.com/Roarge/sysml-federation