@memoarchitect/ontology 0.6.5 → 0.7.0

package/examples/ivd-laboratory-system/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Ivd Laboratory System — project identity and method binding.
+//
+// The native entrypoint. The imports name what this project contains and the
+// binding names the methodology it is governed by. No YAML file participates.
+package memo_examples_ivd_laboratory_system_project {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    // The project's own content, imported so the catalog is one reachable
+    // closure from a single entrypoint.
+    private import memo_examples_ivd_laboratory_system_viewpoints_unassigned::*;
+    private import memo_examples_ivd_laboratory_system_viewpoints_unassigned_views_ivd_laboratory_system_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-LABORATORY-SYSTEM-001";
+        attribute :>> name = "IvdLaboratorySystemProjectMethodBinding";
+        attribute :>> projectName = "Ivd Laboratory System";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/ivd-laboratory-system/model/catalog/viewpoints/unassigned/viewpoint.sysml

@@ -0,0 +1,9 @@
+// unassigned viewpoint.
+//
+// This project does not define its own viewpoint here; it binds the reusable
+// MEMO viewpoint that frames these concerns. The views it governs sit beneath
+// `views/`.
+package memo_examples_ivd_laboratory_system_viewpoints_unassigned {
+    // The reusable package declaring unassigned could not be resolved during
+    // conversion. Import it here so the views beneath this viewpoint resolve.
+}

package/examples/ivd-laboratory-system/model/{viewpoints → catalog/viewpoints/unassigned/views}/ivd_laboratory_system_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_ivd_laboratory_system_viewpoints {
+package memo_examples_ivd_laboratory_system_viewpoints_unassigned_views_ivd_laboratory_system_overview {
     private import memo_examples_ivd_laboratory_system::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml

@@ -5,6 +5,7 @@ package memo_examples_manual_surgical_instrument {
     private import ScalarValues::*;
 
     private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
     private import memo_architecture_operational_activities::*;
     private import memo_architecture_implementation_hardware_structure::*;
 

package/examples/manual-surgical-instrument/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Manual Surgical Instrument — project identity and method binding.
+//
+// The native entrypoint. The imports name what this project contains and the
+// binding names the methodology it is governed by. No YAML file participates.
+package memo_examples_manual_surgical_instrument_project {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    // The project's own content, imported so the catalog is one reachable
+    // closure from a single entrypoint.
+    private import memo_examples_manual_surgical_instrument_viewpoints_unassigned::*;
+    private import memo_examples_manual_surgical_instrument_viewpoints_unassigned_views_manual_surgical_instrument_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-SURGICAL-INSTRUMENT-001";
+        attribute :>> name = "ManualSurgicalInstrumentProjectMethodBinding";
+        attribute :>> projectName = "Manual Surgical Instrument";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/manual-surgical-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml

@@ -0,0 +1,9 @@
+// unassigned viewpoint.
+//
+// This project does not define its own viewpoint here; it binds the reusable
+// MEMO viewpoint that frames these concerns. The views it governs sit beneath
+// `views/`.
+package memo_examples_manual_surgical_instrument_viewpoints_unassigned {
+    // The reusable package declaring unassigned could not be resolved during
+    // conversion. Import it here so the views beneath this viewpoint resolve.
+}

package/examples/manual-surgical-instrument/model/{viewpoints → catalog/viewpoints/unassigned/views}/manual_surgical_instrument_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_manual_surgical_instrument_viewpoints {
+package memo_examples_manual_surgical_instrument_viewpoints_unassigned_views_manual_surgical_instrument_overview {
     private import memo_examples_manual_surgical_instrument::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

package/examples/multidimensional-layers/model/catalog/project.sysml

@@ -0,0 +1,24 @@
+// Multidimensional Layers — project identity and method binding.
+//
+// The native entrypoint. The imports name what this project contains and the
+// binding names the methodology it is governed by. No YAML file participates.
+package memo_examples_multidimensional_layers_project {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_methodology_core::*;
+    private import memo_methodology_profiles::*;
+
+    // The project's own content, imported so the catalog is one reachable
+    // closure from a single entrypoint.
+    private import memo_examples_multidimensional_layers_viewpoints_unassigned::*;
+    private import memo_examples_multidimensional_layers_viewpoints_unassigned_views_multidimensional_layers_overview::*;
+
+    part projectBinding : ProjectMethodBinding {
+        attribute :>> id = "PMB-MULTIDIMENSIONAL-LAYERS-001";
+        attribute :>> name = "MultidimensionalLayersProjectMethodBinding";
+        attribute :>> projectName = "Multidimensional Layers";
+        ref :>> selectedMethodology = mdDefaultDefinition;
+        attribute :>> scopeMode = ScopeModeKind::explicit;
+    }
+}

package/examples/multidimensional-layers/model/catalog/viewpoints/unassigned/viewpoint.sysml

@@ -0,0 +1,9 @@
+// unassigned viewpoint.
+//
+// This project does not define its own viewpoint here; it binds the reusable
+// MEMO viewpoint that frames these concerns. The views it governs sit beneath
+// `views/`.
+package memo_examples_multidimensional_layers_viewpoints_unassigned {
+    // The reusable package declaring unassigned could not be resolved during
+    // conversion. Import it here so the views beneath this viewpoint resolve.
+}

package/examples/multidimensional-layers/model/{viewpoints → catalog/viewpoints/unassigned/views}/multidimensional_layers_overview.sysml

@@ -1,4 +1,4 @@
-package memo_examples_multidimensional_layers_viewpoints {
+package memo_examples_multidimensional_layers_viewpoints_unassigned_views_multidimensional_layers_overview {
     private import memo_examples_multidimensional_layers::*;
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;

package/examples/nested-architecture-dsm/README.md

@@ -0,0 +1,49 @@
+# Nested Architecture DSM
+
+A small infusion-pump model whose only purpose is to exercise the two matrix
+analyses — the Design Structure Matrix and the Traceability Matrix — with a
+hierarchy deep enough that expanding and collapsing changes what you see.
+
+## What is in it
+
+| Axis material | Elements | Nesting |
+| --- | --- | --- |
+| Logical structure | 1 system, 5 subsystems, 12 components | 4 levels (`System → Subsystem → Subsystem → LogicalComponent`) |
+| Functional architecture | 18 system functions | 3 levels, four capability trees |
+| Requirements | 7 requirements | flat |
+
+Nesting is declared with `Composes`, so both matrices build their trees from
+the model rather than from a naming convention.
+
+## What it is set up to show
+
+- **Roll-up.** `SafetyMonitorSubsystem` sits one level deeper than its peers, so
+  a collapsed `ControlSubsystem` row genuinely sums its descendants instead of
+  standing in for a single child.
+- **Feedback.** `DriveActuator` and `MeasureDeliveredVolume` exchange in both
+  directions, so a partitioned DSM still shows one real feedback mark rather
+  than an empty lower triangle.
+- **Cross-tree dependency.** `EnforceDoseLimits → DriveActuator` and
+  `SelectPowerSource → DriveActuator` cross capability trees, which is what a
+  collapsed matrix rolls into a single number between two capabilities.
+- **Asymmetric axes.** Functions on the rows and blocks on the columns, joined
+  by `AllocatedTo` — including `MeterFluid → FluidPathSubsystem`, an allocation
+  made at subsystem level rather than to one component.
+- **A traceability gap.** `StatusVisibility` is satisfied by nothing, so
+  coverage reads under 100% and there is an empty row to author a link into.
+
+## Suggested run
+
+```bash
+memo-architect --example nested-architecture-dsm
+```
+
+In **DSM**: set rows and columns to `SystemFunction`, dependency to
+`exchangesWith`, and switch ordering between *Name* and *Partition* — the
+feedback count drops and one mark stays below the diagonal. Then set columns to
+the logical kinds and dependency to `allocatedTo` for the allocation view.
+
+In **Traceability**: rows `Requirement`, columns `SystemFunction`, trace via
+`satisfiedBy`. Turn on **Edit links** and click the empty `StatusVisibility` row
+to author the missing trace; it is written back to
+`model/catalog/traces.sysml`.

package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml

@@ -0,0 +1,174 @@
+// Functional architecture — the row axis of the DSM.
+//
+// Four capability trees, each decomposed with Composes, plus the functional
+// exchanges between the leaves. The exchanges are deliberately not a clean
+// pipeline: DriveActuator and MeasureDeliveredVolume feed each other, so a
+// partitioned DSM still shows one genuine feedback mark instead of an empty
+// lower triangle.
+package memo_examples_nested_architecture_dsm_architecture_functional_functions {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
+    private import memo_architecture_functional_functions::*;
+
+    // ── Deliver therapy ──────────────────────────────────────────
+    part fnDeliverTherapy : SystemFunction {
+        attribute :>> id = "NDS-FN-001"; attribute :>> name = "DeliverTherapy";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "fluid delivered to the patient line at the prescribed rate";
+    }
+    part fnMeterFluid : SystemFunction {
+        attribute :>> id = "NDS-FN-002"; attribute :>> name = "MeterFluid";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "measured volume displaced per control period";
+    }
+    part fnDriveActuator : SystemFunction {
+        attribute :>> id = "NDS-FN-003"; attribute :>> name = "DriveActuator";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "rate command from the dose control loop";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnMeasureDelivered : SystemFunction {
+        attribute :>> id = "NDS-FN-004"; attribute :>> name = "MeasureDeliveredVolume";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "cumulative delivered volume";
+    }
+    part fnControlDose : SystemFunction {
+        attribute :>> id = "NDS-FN-005"; attribute :>> name = "ControlDose";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnComputeRate : SystemFunction {
+        attribute :>> id = "NDS-FN-006"; attribute :>> name = "ComputeInfusionRate";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "rate command, saturated at the prescribed ceiling";
+    }
+    part fnValidatePrescription : SystemFunction {
+        attribute :>> id = "NDS-FN-007"; attribute :>> name = "ValidatePrescription";
+        attribute :>> functionCategory = "therapy";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::clinical;
+        attribute :>> outputSummary = "accepted or rejected prescription, with the reason";
+    }
+    connection : Composes connect parent ::> fnDeliverTherapy to child ::> fnMeterFluid;
+    connection : Composes connect parent ::> fnDeliverTherapy to child ::> fnControlDose;
+    connection : Composes connect parent ::> fnMeterFluid to child ::> fnDriveActuator;
+    connection : Composes connect parent ::> fnMeterFluid to child ::> fnMeasureDelivered;
+    connection : Composes connect parent ::> fnControlDose to child ::> fnComputeRate;
+    connection : Composes connect parent ::> fnControlDose to child ::> fnValidatePrescription;
+
+    // ── Ensure safety ────────────────────────────────────────────
+    part fnEnsureSafety : SystemFunction {
+        attribute :>> id = "NDS-FN-008"; attribute :>> name = "EnsureSafety";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnDetectOcclusion : SystemFunction {
+        attribute :>> id = "NDS-FN-009"; attribute :>> name = "DetectOcclusion";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "line pressure above the occlusion threshold";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnDetectAirInLine : SystemFunction {
+        attribute :>> id = "NDS-FN-010"; attribute :>> name = "DetectAirInLine";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "air bolus detected in the patient line";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnEnforceDoseLimits : SystemFunction {
+        attribute :>> id = "NDS-FN-011"; attribute :>> name = "EnforceDoseLimits";
+        attribute :>> functionCategory = "protection";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> concernKind = ConcernKind::safety;
+        attribute :>> outputSummary = "delivery stopped when the commanded dose leaves the accepted envelope";
+    }
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnDetectOcclusion;
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnDetectAirInLine;
+    connection : Composes connect parent ::> fnEnsureSafety to child ::> fnEnforceDoseLimits;
+
+    // ── Inform the user ──────────────────────────────────────────
+    part fnInformUser : SystemFunction {
+        attribute :>> id = "NDS-FN-012"; attribute :>> name = "InformUser";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+    }
+    part fnRenderStatus : SystemFunction {
+        attribute :>> id = "NDS-FN-013"; attribute :>> name = "RenderTherapyStatus";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+        attribute :>> outputSummary = "rate, volume delivered and time remaining";
+    }
+    part fnAnnunciateAlarm : SystemFunction {
+        attribute :>> id = "NDS-FN-014"; attribute :>> name = "AnnunciateAlarm";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::catastrophic;
+        attribute :>> trigger = "any active alarm condition";
+        attribute :>> concernKind = ConcernKind::safety;
+    }
+    part fnAcceptInput : SystemFunction {
+        attribute :>> id = "NDS-FN-015"; attribute :>> name = "AcceptClinicianInput";
+        attribute :>> functionCategory = "interaction";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::usability;
+        attribute :>> outputSummary = "confirmed prescription changes";
+    }
+    connection : Composes connect parent ::> fnInformUser to child ::> fnRenderStatus;
+    connection : Composes connect parent ::> fnInformUser to child ::> fnAnnunciateAlarm;
+    connection : Composes connect parent ::> fnInformUser to child ::> fnAcceptInput;
+
+    // ── Manage power ─────────────────────────────────────────────
+    part fnManagePower : SystemFunction {
+        attribute :>> id = "NDS-FN-016"; attribute :>> name = "ManagePower";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::reliability;
+    }
+    part fnMonitorBattery : SystemFunction {
+        attribute :>> id = "NDS-FN-017"; attribute :>> name = "MonitorBatteryState";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> concernKind = ConcernKind::reliability;
+        attribute :>> outputSummary = "state of charge and remaining run time";
+    }
+    part fnSelectPowerSource : SystemFunction {
+        attribute :>> id = "NDS-FN-018"; attribute :>> name = "SelectPowerSource";
+        attribute :>> functionCategory = "platform";
+        attribute :>> criticality = CriticalityKind::high;
+        attribute :>> trigger = "mains loss or rail brownout";
+        attribute :>> concernKind = ConcernKind::reliability;
+    }
+    connection : Composes connect parent ::> fnManagePower to child ::> fnMonitorBattery;
+    connection : Composes connect parent ::> fnManagePower to child ::> fnSelectPowerSource;
+
+    // ── Functional exchange ──────────────────────────────────────
+    // Cross-tree marks are the interesting ones: they are what a collapsed DSM
+    // rolls up into a single number between two capabilities.
+    connection : ExchangesWith connect source ::> fnMeasureDelivered to target ::> fnComputeRate;
+    connection : ExchangesWith connect source ::> fnComputeRate to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnDriveActuator to target ::> fnMeasureDelivered;
+    connection : ExchangesWith connect source ::> fnValidatePrescription to target ::> fnComputeRate;
+    connection : ExchangesWith connect source ::> fnAcceptInput to target ::> fnValidatePrescription;
+    connection : ExchangesWith connect source ::> fnDetectOcclusion to target ::> fnEnforceDoseLimits;
+    connection : ExchangesWith connect source ::> fnDetectAirInLine to target ::> fnAnnunciateAlarm;
+    connection : ExchangesWith connect source ::> fnEnforceDoseLimits to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnMeasureDelivered to target ::> fnRenderStatus;
+    connection : ExchangesWith connect source ::> fnMonitorBattery to target ::> fnAnnunciateAlarm;
+    connection : ExchangesWith connect source ::> fnSelectPowerSource to target ::> fnDriveActuator;
+    connection : ExchangesWith connect source ::> fnDetectOcclusion to target ::> fnAnnunciateAlarm;
+}

package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml

@@ -0,0 +1,183 @@
+// Logical structure — the column axis of the DSM.
+//
+// Four levels deep on purpose (System → Subsystem → Subsystem → component),
+// so expanding and collapsing the matrix has something real to do. Nesting is
+// declared with Composes rather than left implicit, which is what the DSM
+// reads to build the column tree.
+package memo_examples_nested_architecture_dsm_architecture_logical_structure {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
+    private import memo_architecture_logical_structure::*;
+
+    // ── Level 0: the system ──────────────────────────────────────
+    part sysTherapyDelivery : System {
+        attribute :>> id = "NDS-SYS-001"; attribute :>> name = "TherapyDeliverySystem";
+        attribute :>> componentRole = ComponentRoleKind::generic;
+        attribute :>> systemType = SystemTypeKind::logical;
+        attribute :>> systemBoundaryDescription = "Everything inside the pump enclosure, including its power path and user interface.";
+        attribute :>> responsibility = "Deliver a prescribed infusion safely and report what it delivered.";
+    }
+
+    // ── Level 1: subsystems ──────────────────────────────────────
+    part subFluidPath : Subsystem {
+        attribute :>> id = "NDS-SUB-001"; attribute :>> name = "FluidPathSubsystem";
+        attribute :>> componentRole = ComponentRoleKind::generic;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Move fluid from the reservoir to the patient line at a commanded rate.";
+    }
+    part subControl : Subsystem {
+        attribute :>> id = "NDS-SUB-002"; attribute :>> name = "ControlSubsystem";
+        attribute :>> componentRole = ComponentRoleKind::controlElement;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Decide what the fluid path should do, and hold the therapy state.";
+    }
+    part subUserInterface : Subsystem {
+        attribute :>> id = "NDS-SUB-003"; attribute :>> name = "UserInterfaceSubsystem";
+        attribute :>> componentRole = ComponentRoleKind::userInterface;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Present therapy state to the clinician and accept their input.";
+    }
+    part subPower : Subsystem {
+        attribute :>> id = "NDS-SUB-004"; attribute :>> name = "PowerSubsystem";
+        attribute :>> componentRole = ComponentRoleKind::generic;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Supply and monitor power across mains and battery operation.";
+    }
+
+    connection : Composes connect parent ::> sysTherapyDelivery to child ::> subFluidPath;
+    connection : Composes connect parent ::> sysTherapyDelivery to child ::> subControl;
+    connection : Composes connect parent ::> sysTherapyDelivery to child ::> subUserInterface;
+    connection : Composes connect parent ::> sysTherapyDelivery to child ::> subPower;
+
+    // ── Level 2: a subsystem inside a subsystem ──────────────────
+    // The safety monitor is nested one level deeper than its peers, which is
+    // what makes a collapsed ControlSubsystem row a genuine roll-up rather
+    // than a rename of its children.
+    part subSafetyMonitor : Subsystem {
+        attribute :>> id = "NDS-SUB-005"; attribute :>> name = "SafetyMonitorSubsystem";
+        attribute :>> componentRole = ComponentRoleKind::channel;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Watch the control path from outside it and stop delivery on breach.";
+        attribute :>> safetyPartition = "monitor partition, separate MPU region from the control partition";
+    }
+    connection : Composes connect parent ::> subControl to child ::> subSafetyMonitor;
+
+    // ── Level 2/3: components ────────────────────────────────────
+    part lcPumpMechanism : LogicalComponent {
+        attribute :>> id = "NDS-LC-001"; attribute :>> name = "PumpMechanism";
+        attribute :>> componentRole = ComponentRoleKind::controlElement;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Displace fluid under command.";
+        attribute :>> controlledVariable = "delivered volume per stroke";
+    }
+    part lcOcclusionChannel : LogicalComponent {
+        attribute :>> id = "NDS-LC-002"; attribute :>> name = "OcclusionSensingChannel";
+        attribute :>> componentRole = ComponentRoleKind::channel;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Sense line pressure and air in line.";
+        attribute :>> channelRole = ChannelRoleKind::primary;
+    }
+    part lcReservoirInterface : LogicalComponent {
+        attribute :>> id = "NDS-LC-003"; attribute :>> name = "ReservoirInterface";
+        attribute :>> componentRole = ComponentRoleKind::generic;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Seat the reservoir and expose its remaining volume.";
+    }
+    connection : Composes connect parent ::> subFluidPath to child ::> lcPumpMechanism;
+    connection : Composes connect parent ::> subFluidPath to child ::> lcOcclusionChannel;
+    connection : Composes connect parent ::> subFluidPath to child ::> lcReservoirInterface;
+
+    part lcDoseController : LogicalComponent {
+        attribute :>> id = "NDS-LC-004"; attribute :>> name = "DoseController";
+        attribute :>> componentRole = ComponentRoleKind::controlElement;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Turn a prescription into rate commands.";
+        attribute :>> controlLaw = "closed loop on delivered volume, saturated at the prescribed limit";
+        attribute :>> controlledVariable = "infusion rate";
+    }
+    part lcTherapyStateStore : LogicalComponent {
+        attribute :>> id = "NDS-LC-005"; attribute :>> name = "TherapyStateStore";
+        attribute :>> componentRole = ComponentRoleKind::dataStore;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Hold the active therapy record across power cycles.";
+        attribute :>> persistenceRequirement = "survives power loss with the last completed transaction intact";
+        attribute :>> integrityRequirement = "CRC per record, rejected on mismatch";
+    }
+    connection : Composes connect parent ::> subControl to child ::> lcDoseController;
+    connection : Composes connect parent ::> subControl to child ::> lcTherapyStateStore;
+
+    part lcWatchdogChannel : LogicalComponent {
+        attribute :>> id = "NDS-LC-006"; attribute :>> name = "WatchdogChannel";
+        attribute :>> componentRole = ComponentRoleKind::channel;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Reset to the safe state when the control loop misses its deadline.";
+        attribute :>> channelRole = ChannelRoleKind::monitor;
+        attribute :>> diversityBasis = "independent time base from the control partition";
+    }
+    part lcPressureIntegrityChannel : LogicalComponent {
+        attribute :>> id = "NDS-LC-007"; attribute :>> name = "PressureIntegrityChannel";
+        attribute :>> componentRole = ComponentRoleKind::channel;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Cross-check pressure against the commanded rate and stop on divergence.";
+        attribute :>> channelRole = ChannelRoleKind::monitor;
+        attribute :>> diversityBasis = "different measurement principle from the primary occlusion channel";
+    }
+    connection : Composes connect parent ::> subSafetyMonitor to child ::> lcWatchdogChannel;
+    connection : Composes connect parent ::> subSafetyMonitor to child ::> lcPressureIntegrityChannel;
+
+    part lcDisplayManager : LogicalComponent {
+        attribute :>> id = "NDS-LC-008"; attribute :>> name = "DisplayManager";
+        attribute :>> componentRole = ComponentRoleKind::userInterface;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Render therapy state on the main screen.";
+        attribute :>> interactionSummary = "read-only status surface, refreshed once per second";
+    }
+    part lcAlarmAnnunciator : LogicalComponent {
+        attribute :>> id = "NDS-LC-009"; attribute :>> name = "AlarmAnnunciator";
+        attribute :>> componentRole = ComponentRoleKind::userInterface;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Raise audible and visible alarms by priority.";
+        attribute :>> interactionSummary = "IEC 60601-1-8 alarm signals";
+    }
+    part lcKeypadHandler : LogicalComponent {
+        attribute :>> id = "NDS-LC-010"; attribute :>> name = "KeypadHandler";
+        attribute :>> componentRole = ComponentRoleKind::userInterface;
+        attribute :>> systemType = SystemTypeKind::software;
+        attribute :>> responsibility = "Debounce and interpret key presses.";
+        attribute :>> interactionSummary = "physical keypad, confirm-before-apply for every rate change";
+    }
+    connection : Composes connect parent ::> subUserInterface to child ::> lcDisplayManager;
+    connection : Composes connect parent ::> subUserInterface to child ::> lcAlarmAnnunciator;
+    connection : Composes connect parent ::> subUserInterface to child ::> lcKeypadHandler;
+
+    part lcBatteryManager : LogicalComponent {
+        attribute :>> id = "NDS-LC-011"; attribute :>> name = "BatteryManager";
+        attribute :>> componentRole = ComponentRoleKind::generic;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Charge, gauge and protect the battery.";
+    }
+    part lcPowerRailMonitor : LogicalComponent {
+        attribute :>> id = "NDS-LC-012"; attribute :>> name = "PowerRailMonitor";
+        attribute :>> componentRole = ComponentRoleKind::channel;
+        attribute :>> systemType = SystemTypeKind::hardware;
+        attribute :>> responsibility = "Detect rail brownout and request a source switch.";
+        attribute :>> channelRole = ChannelRoleKind::monitor;
+    }
+    connection : Composes connect parent ::> subPower to child ::> lcBatteryManager;
+    connection : Composes connect parent ::> subPower to child ::> lcPowerRailMonitor;
+
+    // ── Component-to-component dependency ────────────────────────
+    // What the DSM plots when both axes are architecture: who needs whom.
+    connection : ExchangesWith connect source ::> lcOcclusionChannel to target ::> lcDoseController;
+    connection : ExchangesWith connect source ::> lcDoseController to target ::> lcPumpMechanism;
+    connection : ExchangesWith connect source ::> lcPumpMechanism to target ::> lcTherapyStateStore;
+    connection : ExchangesWith connect source ::> lcTherapyStateStore to target ::> lcDisplayManager;
+    connection : ExchangesWith connect source ::> lcWatchdogChannel to target ::> lcDoseController;
+    connection : ExchangesWith connect source ::> lcPressureIntegrityChannel to target ::> lcAlarmAnnunciator;
+    connection : ExchangesWith connect source ::> lcKeypadHandler to target ::> lcDoseController;
+    connection : ExchangesWith connect source ::> lcReservoirInterface to target ::> lcPumpMechanism;
+    connection : ExchangesWith connect source ::> lcBatteryManager to target ::> lcPowerRailMonitor;
+    connection : ExchangesWith connect source ::> lcPowerRailMonitor to target ::> lcAlarmAnnunciator;
+}

package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml

@@ -0,0 +1,53 @@
+// Stakeholder needs — the outermost row of a full trace chain.
+//
+// Need → Requirement → Function → VerificationCase is the chain the
+// traceability view is meant to walk one hop at a time.
+package memo_examples_nested_architecture_dsm_assurance_requirements_needs {
+    private import ScalarValues::*;
+
+    private import memo_core_enumerations::*;
+    private import memo_core_relationships::*;
+    private import memo_assurance_requirements_needs::*;
+    private import memo_examples_nested_architecture_dsm_assurance_requirements::*;
+
+    requirement needAccurateTherapy : Need {
+        attribute :>> id = "NDS-NEED-001"; attribute :>> name = "AccurateTherapyDelivery";
+        attribute :>> needKind = NeedKind::'stakeholder';
+        attribute :>> statement = "Clinicians need the delivered dose to match the prescription closely enough to be clinically safe.";
+        attribute :>> priority = "high";
+    }
+    requirement needProtectionFromHarm : Need {
+        attribute :>> id = "NDS-NEED-002"; attribute :>> name = "ProtectionFromDeliveryFaults";
+        attribute :>> needKind = NeedKind::'stakeholder';
+        attribute :>> statement = "Patients need delivery to stop before a line fault or air bolus reaches them.";
+        attribute :>> priority = "high";
+    }
+    requirement needUninterruptedTherapy : Need {
+        attribute :>> id = "NDS-NEED-003"; attribute :>> name = "UninterruptedTherapy";
+        attribute :>> needKind = NeedKind::operational;
+        attribute :>> statement = "Wards need therapy to continue through transport and mains interruptions.";
+        attribute :>> priority = "medium";
+        attribute :>> operationalContextReference = "intra-hospital transport, up to four hours off mains";
+    }
+    requirement needLegibleStatus : Need {
+        attribute :>> id = "NDS-NEED-004"; attribute :>> name = "LegibleTherapyStatus";
+        attribute :>> needKind = NeedKind::'stakeholder';
+        attribute :>> statement = "Clinicians need to read therapy state and alarms correctly from the bedside.";
+        attribute :>> priority = "high";
+        attribute :>> userPopulationReference = "ward nurses, including those wearing corrective lenses";
+    }
+
+    // Need → Requirement.
+    connection derAccuracy : DerivesFrom connect sourceDriver ::> needAccurateTherapy to targetRequirement ::> reqDoseAccuracy;
+    connection derOcclusion : DerivesFrom connect sourceDriver ::> needProtectionFromHarm to targetRequirement ::> reqOcclusionDetection;
+    connection derAirInLine : DerivesFrom connect sourceDriver ::> needProtectionFromHarm to targetRequirement ::> reqAirInLine;
+    connection derAlarm : DerivesFrom connect sourceDriver ::> needLegibleStatus to targetRequirement ::> reqAlarmAnnunciation;
+    connection derBattery : DerivesFrom connect sourceDriver ::> needUninterruptedTherapy to targetRequirement ::> reqBatteryEndurance;
+    connection derConfirmation : DerivesFrom connect sourceDriver ::> needLegibleStatus to targetRequirement ::> reqPrescriptionConfirmation;
+    connection derStatus : DerivesFrom connect sourceDriver ::> needLegibleStatus to targetRequirement ::> reqStatusVisibility;
+
+    // Software requirements derive from the system requirement they refine
+    // (IEC 62304), which is a second, requirement-to-requirement trace axis.
+    connection derAlarmFromSystem : DerivesFrom connect sourceDriver ::> reqOcclusionDetection to targetRequirement ::> reqAlarmAnnunciation;
+    connection derConfirmationFromSystem : DerivesFrom connect sourceDriver ::> reqDoseAccuracy to targetRequirement ::> reqPrescriptionConfirmation;
+}