A3 architecture overviews
Each sheet takes one aspect of the demo and gives it a model side and a summary side, laid out for a reader with a quarter of an hour. The model side draws the aspect and the summary side says what it means, so that a reader who finishes a sheet can answer its goal question without opening anything else.
| 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 yet drafted, follows the first implementation phases |
| L2a | Adapter: projecting SysML v2 | How does a model file become a subgraph, and where does the adapter stop? | Not yet drafted, follows the first implementation phases |
| L2b | Pipeline example: capacity and verdicts | Why does raising one server change nothing and raising another change everything? | Approved without external review |
Layout after the A3 architecture overview cookbook of Borches and Bonnema. No artwork from the cookbook is reproduced.
Owner: Roar Georgsen
Index: Federating a systems model ยท Repository: https://github.com/Roarge/sysml-federation