Functional, Logical, Physical¶
Use this example to see that realization is a graph, not a pipeline.
- An operational activity needs a pressure-limiting function.
- The function is allocated to a logical pressure-protection element.
- The same logical element is realized by software and a mechanical part.
- Follow the typed links instead of assuming every function becomes software.
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 |
|---|---|---|
| Operational | OperationalActivity |
Operational |
| Functional | SystemFunction |
Functional |
| Logical | LogicalComponent |
Logical |
| Implementation and realization | MechanicalPart, SoftwareModule |
Implementation and realization |
| Views and methodology | MemoDiagramView |
Views and methodology |
Typed links it uses: AllocatedTo, Enables, Realizes — see Relationships for what each one claims and which ends are legal.
Layers it does not populate: 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: Context and Use · Functional Analysis · Requirements and Architecture.
Source model: examples/functional-logical-physical