Embedded Infusion Pump¶
Use this example to separate three software questions.
- The module view names software items and units.
- The runtime view records tasks, timing, and fault containment.
- The deployment view records build units and processing nodes.
- Typed links connect the same design across all three views.
Where this sits in MEMO¶
Every tutorial is one slice of the same structure. This example populates these layers:
| Layer | Element types it uses | Reference |
|---|---|---|
| Implementation and realization | SoftwareDeploymentUnit, ProcessingNode, RuntimeEnvironment, SoftwareComponent, SoftwareModule |
Implementation and realization |
| Views and methodology | MemoDiagramView |
Views and methodology |
Typed links it uses: BuildsInto, DeploysTo, HostedBy, ProvidesEnvironment, Realizes — see Relationships for what each one claims and which ends are legal.
Layers it does not populate: operational, functional, logical, assurance. A MEMO project includes only the layers selected by its methodology. For a device modelled all the way through, see the GPCA Pump case study.
Narrative treatment: Requirements and Architecture.
Source model: examples/embedded-infusion-pump