@memoarchitect/ontology 0.16.1 → 0.16.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (210) hide show
  1. package/README.md +2 -2
  2. package/examples/connected-patient-monitor/memo.identity.yaml +16 -1
  3. package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +5 -1
  4. package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  5. package/examples/connected-patient-monitor/model/catalog/viewpoints/{unassigned → logical}/views/connected_patient_monitor_overview.sysml +3 -2
  6. package/examples/connected-patient-monitor/model/methodology/project.sysml +1 -2
  7. package/examples/embedded-infusion-pump/memo.identity.yaml +79 -0
  8. package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +131 -4
  9. package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  10. package/examples/embedded-infusion-pump/model/catalog/viewpoints/{unassigned → logical}/views/embedded_infusion_pump_overview.sysml +3 -2
  11. package/examples/embedded-infusion-pump/model/methodology/project.sysml +1 -2
  12. package/examples/functional-logical-physical/memo.identity.yaml +31 -1
  13. package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +71 -0
  14. package/examples/functional-logical-physical/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  15. package/examples/functional-logical-physical/model/catalog/viewpoints/{unassigned → logical}/views/functional_logical_physical_overview.sysml +3 -2
  16. package/examples/functional-logical-physical/model/methodology/project.sysml +1 -2
  17. package/examples/gpca-pump/memo.identity.yaml +53 -13
  18. package/examples/gpca-pump/methodology/gpca_profiles.sysml +4 -15
  19. package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +23 -10
  20. package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +7 -6
  21. package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +74 -28
  22. package/examples/gpca-pump/model/catalog/gpca_devices.sysml +23 -0
  23. package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +11 -29
  24. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +17 -0
  25. package/examples/gpca-pump/model/catalog/gpca_physical.sysml +2 -1
  26. package/examples/gpca-pump/model/catalog/gpca_standards.sysml +4 -4
  27. package/examples/gpca-pump/model/catalog/gpca_system.sysml +4 -3
  28. package/examples/gpca-pump/model/catalog/gpca_trace.sysml +11 -3
  29. package/examples/gpca-pump/model/catalog/gpca_verification.sysml +12 -12
  30. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +1 -1
  31. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +1 -1
  32. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +1 -1
  33. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +1 -1
  34. package/examples/{ros-mobile-robot/model/catalog/viewpoints/unassigned → gpca-pump/model/catalog/viewpoints/shared}/viewpoint.sysml +3 -2
  35. package/examples/gpca-pump/model/catalog/viewpoints/{logical → shared}/views/document_architecture_description_view.sysml +3 -3
  36. package/examples/gpca-pump/model/catalog/viewpoints/{requirements → shared}/views/document_dhf_index_view.sysml +3 -3
  37. package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +1 -1
  38. package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +1 -1
  39. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +1 -1
  40. package/examples/gpca-pump/model/methodology/project.sysml +1 -5
  41. package/examples/ivd-laboratory-system/memo.identity.yaml +43 -0
  42. package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +16 -1
  43. package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  44. package/examples/ivd-laboratory-system/model/catalog/viewpoints/{unassigned → logical}/views/ivd_laboratory_system_overview.sysml +3 -2
  45. package/examples/ivd-laboratory-system/model/methodology/project.sysml +1 -2
  46. package/examples/manual-surgical-instrument/memo.identity.yaml +28 -0
  47. package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -0
  48. package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  49. package/examples/manual-surgical-instrument/model/catalog/viewpoints/{unassigned → logical}/views/manual_surgical_instrument_overview.sysml +3 -2
  50. package/examples/manual-surgical-instrument/model/methodology/project.sysml +1 -2
  51. package/examples/multidimensional-layers/memo.identity.yaml +34 -0
  52. package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +34 -4
  53. package/examples/multidimensional-layers/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  54. package/examples/multidimensional-layers/model/catalog/viewpoints/{unassigned → logical}/views/multidimensional_layers_overview.sysml +3 -1
  55. package/examples/multidimensional-layers/model/methodology/project.sysml +1 -2
  56. package/examples/nested-architecture-dsm/memo.identity.yaml +27 -0
  57. package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +9 -9
  58. package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +64 -0
  59. package/examples/nested-architecture-dsm/model/catalog/nested_architecture_dsm_system.sysml +5 -0
  60. package/examples/nested-architecture-dsm/model/catalog/traces.sysml +6 -0
  61. package/examples/reusable-instrument/memo.identity.yaml +46 -0
  62. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +28 -0
  63. package/examples/reusable-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  64. package/examples/reusable-instrument/model/catalog/viewpoints/{unassigned → logical}/views/reusable_instrument_overview.sysml +3 -1
  65. package/examples/reusable-instrument/model/methodology/project.sysml +1 -2
  66. package/examples/robot-cell-family/memo.identity.yaml +96 -81
  67. package/examples/robot-cell-family/model/{sos → catalog/sos}/chains.sysml +5 -5
  68. package/examples/robot-cell-family/model/{sos → catalog/sos}/icds.sysml +1 -1
  69. package/examples/robot-cell-family/model/{sos → catalog/sos}/sos.sysml +4 -4
  70. package/examples/robot-cell-family/model/{sos → catalog/sos}/use_cases.sysml +4 -4
  71. package/examples/robot-cell-family/model/{systems → catalog/systems}/manipulation/manipulation_system.sysml +11 -3
  72. package/examples/robot-cell-family/model/{systems → catalog/systems}/navigation/navigation_system.sysml +9 -4
  73. package/examples/robot-cell-family/model/{systems → catalog/systems}/perception/perception_system.sysml +8 -3
  74. package/examples/robot-cell-family/model/methodology/project.sysml +6 -6
  75. package/examples/ros-mobile-robot/memo.identity.yaml +22 -1
  76. package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +89 -26
  77. package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  78. package/examples/ros-mobile-robot/model/catalog/viewpoints/{unassigned → logical}/views/ros_mobile_robot_overview.sysml +3 -1
  79. package/examples/ros-mobile-robot/model/methodology/project.sysml +1 -2
  80. package/examples/software-only-medical-device/memo.identity.yaml +46 -0
  81. package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +34 -1
  82. package/examples/software-only-medical-device/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  83. package/examples/software-only-medical-device/model/catalog/viewpoints/{unassigned → logical}/views/software_only_medical_device_overview.sysml +3 -1
  84. package/examples/software-only-medical-device/model/methodology/project.sysml +1 -2
  85. package/examples/surgical-closure-workflow/memo.identity.yaml +103 -0
  86. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +28 -0
  87. package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  88. package/examples/surgical-closure-workflow/model/catalog/viewpoints/{unassigned → logical}/views/surgical_closure_workflow_overview.sysml +3 -1
  89. package/examples/surgical-closure-workflow/model/methodology/project.sysml +1 -2
  90. package/examples/surgical-robot/memo.identity.yaml +40 -0
  91. package/examples/surgical-robot/model/catalog/surgical_robot.sysml +6 -1
  92. package/examples/surgical-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  93. package/examples/surgical-robot/model/catalog/viewpoints/{unassigned → logical}/views/surgical_robot_overview.sysml +3 -1
  94. package/examples/surgical-robot/model/methodology/project.sysml +1 -2
  95. package/examples/sysml-diagram-samples/README.md +5 -3
  96. package/examples/sysml-diagram-samples/memo.identity.yaml +548 -391
  97. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/action_flow_view.sysml +2 -2
  98. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/browser_view.sysml +1 -2
  99. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/context_view.sysml +1 -2
  100. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/drill_down_view.sysml +30 -5
  101. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/functional_flow_view.sysml +15 -3
  102. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/grid_view.sysml +1 -2
  103. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/interconnection_view.sysml +1 -2
  104. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/operational_behaviour_view.sysml +1 -2
  105. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/package_view.sysml +1 -2
  106. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/requirements_view.sysml +7 -2
  107. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/sequence_view.sysml +1 -2
  108. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/standard_activity_view.sysml +2 -3
  109. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/state_transition_view.sysml +1 -2
  110. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/tree_view.sysml +1 -2
  111. package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/use_case_view.sysml +1 -2
  112. package/examples/sysml-diagram-samples/model/catalog/sysml_diagram_samples_system.sysml +5 -0
  113. package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/viewpoint.sysml +8 -0
  114. package/examples/sysml-diagram-samples/model/catalog/viewpoints/{unassigned → shared}/views/diagram_samples.sysml +78 -44
  115. package/examples/sysml-diagram-samples/model/methodology/project.sysml +0 -16
  116. package/examples/temperature-alarm/memo.identity.yaml +22 -1
  117. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +48 -0
  118. package/examples/temperature-alarm/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
  119. package/examples/temperature-alarm/model/catalog/viewpoints/{unassigned → logical}/views/temperature_alarm_overview.sysml +3 -1
  120. package/examples/temperature-alarm/model/methodology/project.sysml +1 -2
  121. package/examples/ui-screen-regions/memo.identity.yaml +33 -0
  122. package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +3 -0
  123. package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +2 -1
  124. package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +60 -0
  125. package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +3 -3
  126. package/examples/ui-screen-regions/model/catalog/ui_screen_regions_system.sysml +5 -0
  127. package/extensions/aadl/memo.package.yaml +1 -1
  128. package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +2 -1
  129. package/extensions/clinical/memo.package.yaml +1 -1
  130. package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +2 -1
  131. package/extensions/cloud/memo.package.yaml +1 -1
  132. package/extensions/container/memo.package.yaml +1 -1
  133. package/extensions/messaging/memo.package.yaml +1 -1
  134. package/extensions/messaging/src/messaging_extension.sysml +2 -1
  135. package/extensions/ros/memo.package.yaml +1 -1
  136. package/extensions/ros/src/ros_extension.sysml +3 -2
  137. package/methodologies/default/memo.package.yaml +1 -1
  138. package/methodologies/gpca/memo.package.yaml +1 -1
  139. package/ontology/memo.package.yaml +1 -1
  140. package/package.json +4 -4
  141. package/profile/memo.package.yaml +1 -1
  142. package/src/architecture/functional/behavior/memo_behavior.sysml +19 -8
  143. package/src/architecture/functional/constraints/memo_constraints.sysml +5 -4
  144. package/src/architecture/functional/functions/memo_functions.sysml +18 -6
  145. package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +2 -3
  146. package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +5 -4
  147. package/src/architecture/implementation/software/structure/memo_software_structure.sysml +0 -1
  148. package/src/architecture/implementation/ui/memo_ui.sysml +16 -0
  149. package/src/architecture/logical/interfaces/memo_interfaces.sysml +9 -3
  150. package/src/architecture/logical/structure/memo_logical_structure.sysml +9 -0
  151. package/src/architecture/operational/activities/memo_activities.sysml +3 -2
  152. package/src/architecture/operational/scenarios/memo_scenarios.sysml +6 -1
  153. package/src/architecture/operational/use_cases/memo_use_cases.sysml +0 -4
  154. package/src/architecture/realization/deployment/memo_deployment.sysml +3 -2
  155. package/src/architecture/realization/physical/memo_physical_architecture.sysml +11 -4
  156. package/src/artifacts/configuration_management/memo_configuration_management.sysml +17 -4
  157. package/src/artifacts/templates/dhf/fda-cybersecurity/security-arch.md +1 -1
  158. package/src/artifacts/templates/dhf/fda-cybersecurity/threat-model.md +1 -1
  159. package/src/artifacts/templates/dhf/iec-62304/detailed-design.md +1 -1
  160. package/src/artifacts/templates/dhf/iec-62304/sad.md +1 -1
  161. package/src/artifacts/templates/dhf/iec-62366/task-analysis.md +7 -7
  162. package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
  163. package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
  164. package/src/artifacts/templates/dhf/system/sad.md +1 -1
  165. package/src/artifacts/templates/dhf/system/standards-checklist.md +2 -2
  166. package/src/assurance/safety_risk/memo_risk.sysml +15 -0
  167. package/src/assurance/verification_validation/memo_assurance.sysml +25 -0
  168. package/src/core/common/memo_common.sysml +22 -0
  169. package/src/core/enumerations/memo_enumerations.sysml +23 -5
  170. package/src/core/relationships/memo_relationships.sysml +5 -0
  171. package/src/core/relationships/memo_workspace_membership.sysml +11 -0
  172. package/src/core/stdlib/quantities/quantities.sysml +22 -0
  173. package/src/memo_namespaces.sysml +5 -0
  174. package/src/methodology/core/memo_core.sysml +2 -12
  175. package/src/methodology/profiles/memo_profiles.sysml +2 -2
  176. package/src/rules/closure/closure_rules.sysml +46 -3
  177. package/src/rules/ontology/ontology_invariants.sysml +67 -30
  178. package/src/rules/quantitative/quantitative_rules.sysml +29 -0
  179. package/src/viewpoints/clinical/clinical_viewpoint.sysml +1 -1
  180. package/src/viewpoints/context/context_viewpoint.sysml +1 -1
  181. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +1 -1
  182. package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +1 -1
  183. package/src/viewpoints/functional/functional_viewpoint.sysml +1 -1
  184. package/src/viewpoints/logical/logical_viewpoint.sysml +1 -1
  185. package/src/viewpoints/operational/operational_viewpoint.sysml +1 -1
  186. package/src/viewpoints/physical/physical_viewpoint.sysml +1 -1
  187. package/src/viewpoints/requirements/requirements_viewpoint.sysml +1 -1
  188. package/src/viewpoints/risk/risk_viewpoint.sysml +1 -1
  189. package/src/viewpoints/software/software_viewpoint.sysml +1 -1
  190. package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +14 -3
  191. package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +1 -1
  192. package/src/viewpoints/usability/usability_viewpoint.sysml +1 -1
  193. package/src/viewpoints/verification/verification_viewpoint.sysml +1 -1
  194. package/stage1/opensysml-23e5a5f26f7b25370edc4f26.json.gz +0 -0
  195. package/stage1/syside-eb527547500a60b508b4578c.ids.gz +0 -0
  196. package/stage1/syside-eb527547500a60b508b4578c.json.gz +0 -0
  197. package/examples/connected-patient-monitor/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  198. package/examples/embedded-infusion-pump/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  199. package/examples/functional-logical-physical/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  200. package/examples/ivd-laboratory-system/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  201. package/examples/manual-surgical-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  202. package/examples/multidimensional-layers/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  203. package/examples/reusable-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  204. package/examples/software-only-medical-device/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  205. package/examples/surgical-closure-workflow/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  206. package/examples/surgical-robot/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  207. package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -74
  208. package/examples/temperature-alarm/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
  209. /package/examples/robot-cell-family/model/{shared → catalog/shared}/shared.sysml +0 -0
  210. /package/examples/sysml-diagram-samples/model/{sysml_v2_activity_example.sysml → catalog/sysml_v2_activity_example.sysml} +0 -0
@@ -69,6 +69,7 @@
69
69
  // Both had part-typed ends until A0; both are metaclass-neutral now, which is
70
70
  // precisely what makes an action-def function usable at all.
71
71
  package memo_architecture_functional_functions {
72
+ private import memo_core_stdlib_quantities::*;
72
73
  private import Metaobjects::SemanticMetadata;
73
74
  private import ScalarValues::*;
74
75
 
@@ -78,11 +79,14 @@ package memo_architecture_functional_functions {
78
79
  private import memo_architecture_operational_activities::*;
79
80
  private import memo_architecture_operational_scenarios::*;
80
81
 
81
- abstract action def MemoFunction specializes MemoAction {
82
+ abstract action def MemoFunction specializes MemoAction, MemoConstrainedOccurrence {
82
83
  attribute functionCategory : String;
83
84
  attribute actionKind : ActionKind;
84
85
  attribute trigger : String;
85
- attribute outputSummary : String;
86
+ // What the function produces, in words: the part the typed `out` parameters cannot say (their type
87
+ // names the item, not that it is debounced, range-checked or timestamped). It does not restate the
88
+ // parameters, and what goes in is the `in` parameters alone (decided 2026-10-25, user).
89
+ attribute outputDescription : String;
86
90
  attribute concernKind : ConcernKind;
87
91
  attribute criticality : CriticalityKind;
88
92
  }
@@ -102,17 +106,25 @@ package memo_architecture_functional_functions {
102
106
  // named flow from an `out` parameter of one function to an `in` parameter
103
107
  // of another:
104
108
  //
105
- // flow lfFlowCommand : FunctionalExchange
109
+ // flow lfFlowCommand : FunctionalTransfer
106
110
  // from fnManageInfusion.flowCommandOut to fnCommandPump.flowCommandIn {
107
111
  // attribute :>> latencyBudgetMs = 20.0;
108
112
  // }
109
113
  abstract flow def FunctionalExchange {
110
114
  attribute flowKind : FlowKind;
111
- attribute latencyBudgetMs : Real;
112
- attribute staleAfterMs : Real;
115
+ attribute latencyBudgetMs : DurationValue;
116
+ attribute staleAfterMs : DurationValue;
113
117
  attribute integrityLevel : String;
114
118
  }
115
119
 
120
+ // The concrete exchange. A concrete `flow def` must declare its two ends, so this is the member
121
+ // of the family a model types its flows by; the ends are left untyped, as an exchange runs from
122
+ // an `out` parameter of one function to an `in` parameter of another (or between ports).
123
+ flow def FunctionalTransfer specializes FunctionalExchange {
124
+ end source;
125
+ end target;
126
+ }
127
+
116
128
  // A system function enables operational work; it does not perform it.
117
129
 
118
130
  // A reusable functional route through system responsibilities. Functional
@@ -131,7 +143,7 @@ package memo_architecture_functional_functions {
131
143
  // has not been allowed to say so.
132
144
  action def FunctionalFlow specializes MemoAction {
133
145
  attribute flowCategory : FunctionalFlowKind;
134
- attribute endToEndLatencyBudgetMs : String;
146
+ attribute endToEndLatencyBudgetMs : DurationValue;
135
147
  attribute safetyRelevant : Boolean;
136
148
  attribute securityRelevant : Boolean;
137
149
  }
@@ -7,6 +7,7 @@
7
7
  // declared here; acoustic and thermal parts have no dedicated subgroup and stay
8
8
  // with the roots.
9
9
  package memo_architecture_implementation_hardware_common {
10
+ private import memo_core_stdlib_quantities::*;
10
11
  private import ScalarValues::*;
11
12
 
12
13
  private import memo_core_common::*;
@@ -26,8 +27,7 @@ package memo_architecture_implementation_hardware_common {
26
27
  part def PhysicalAssembly specializes PhysicalElement {
27
28
  attribute responsibility : String;
28
29
  attribute safetyRole : String;
29
- attribute partNumber : String;
30
- attribute mtbfHours : String;
30
+ attribute mtbfHours : DurationValue;
31
31
  attribute protectionClass : String;
32
32
  attribute ipRating : String;
33
33
  }
@@ -36,7 +36,6 @@ package memo_architecture_implementation_hardware_common {
36
36
  part def HardwareAssembly specializes PhysicalAssembly;
37
37
 
38
38
  part def PhysicalComponent specializes PhysicalElement {
39
- attribute partNumber : String;
40
39
  attribute materialSummary : String;
41
40
  // ISO 10993-1 contact characterization; required when true.
42
41
  attribute patientContact : Boolean;
@@ -11,6 +11,7 @@
11
11
  // name and property. This comment pointed at `examples/aadl-mapping` for a
12
12
  // long time and that directory never existed; the pointer above resolves.
13
13
  package memo_architecture_implementation_software_runtime {
14
+ private import memo_core_stdlib_quantities::*;
14
15
  private import Metaobjects::SemanticMetadata;
15
16
  private import ScalarValues::*;
16
17
 
@@ -35,9 +36,9 @@ package memo_architecture_implementation_software_runtime {
35
36
  part def SoftwareComponent specializes SoftwareElement {
36
37
  attribute runtimeKind : RuntimeKind;
37
38
  attribute responsibility : String;
38
- attribute periodMs : Real;
39
- attribute deadlineMs : Real;
40
- attribute wcetMs : Real;
39
+ attribute periodMs : DurationValue;
40
+ attribute deadlineMs : DurationValue;
41
+ attribute wcetMs : DurationValue;
41
42
  attribute schedulingPolicy : SchedulingPolicyKind;
42
43
  attribute priority : Integer;
43
44
  attribute activation : String;
@@ -46,7 +47,7 @@ package memo_architecture_implementation_software_runtime {
46
47
  // Maximum resident memory allocation in megabytes. The public name
47
48
  // predates MEMO's unit-suffixed scalar convention, so document the
48
49
  // unit here rather than silently changing the published feature name.
49
- attribute memoryBudget : Real;
50
+ attribute memoryBudget : StorageCapacityValue;
50
51
  attribute healthMonitoring : String;
51
52
  attribute restartPolicy : String;
52
53
  attribute faultContainment : String;
@@ -33,7 +33,6 @@ package memo_architecture_implementation_software_structure {
33
33
  }
34
34
 
35
35
  part def SoftwareSystem specializes SoftwareElement {
36
- attribute version : String;
37
36
  attribute operatingSystem : String;
38
37
  }
39
38
 
@@ -324,6 +324,22 @@ package memo_architecture_implementation_ui {
324
324
  // Conflating the two was the mistake that made "clicking takes you to a
325
325
  // child view" look like spatial nesting; it is a separate frame reached
326
326
  // from here, and only this relation says so.
327
+ //
328
+ // connection goToSettings : NavigatesTo
329
+ // connect element ::> homeScreen.settingsButton to screen ::> settingsScreen;
330
+ //
331
+ // A screen is a UIElement whose `formKind` is `screen`; the end says UIElement because the form is an
332
+ // attribute, not a subtype.
333
+ connection def NavigatesTo :> MemoRelationship {
334
+ end element : UIElement :>> source;
335
+ end screen : UIElement :>> target;
336
+ }
337
+ abstract connection navigatesToLinks : NavigatesTo[*];
338
+ metadata def <navigatesTo> NavigatesToMetadata :> SemanticMetadata {
339
+ :> annotatedElement : SysML::ConnectionDefinition;
340
+ :> annotatedElement : SysML::ConnectionUsage;
341
+ :>> baseType = navigatesToLinks meta SysML::Usage;
342
+ }
327
343
 
328
344
  // ── §18 traceability ─────────────────────────────────────────
329
345
  // Source is `MemoPart`, not a UI-specific base: a foot pedal and a
@@ -35,6 +35,7 @@
35
35
  // A delegation that is a binding is not a ComponentExchange: nothing
36
36
  // interacts, and one feature is seen from both sides.
37
37
  package memo_architecture_logical_interfaces {
38
+ private import memo_core_stdlib_quantities::*;
38
39
  private import ScalarValues::*;
39
40
 
40
41
  private import memo_core_common::*;
@@ -68,7 +69,7 @@ package memo_architecture_logical_interfaces {
68
69
  attribute direction : DirectionKind;
69
70
  attribute protocol : String; // "SPI", "CAN", "Ethernet", "REST", "4-20mA"
70
71
  attribute protocolSemantics : String;
71
- attribute timeoutMs : Real[0..1];
72
+ attribute timeoutMs : DurationValue[0..1];
72
73
  attribute retryPolicy : String[0..1];
73
74
  attribute interactionPattern : String; // request-response, pub-sub, streaming…
74
75
  attribute timingSummary : String;
@@ -107,7 +108,7 @@ package memo_architecture_logical_interfaces {
107
108
  attribute integrityClass : String;
108
109
  attribute availabilityClass : String;
109
110
  attribute controlType : String[0..1];
110
- attribute timeoutMs : Real[0..1];
111
+ attribute timeoutMs : DurationValue[0..1];
111
112
  attribute retryPolicy : String[0..1];
112
113
  }
113
114
 
@@ -136,9 +137,14 @@ package memo_architecture_logical_interfaces {
136
137
  // }
137
138
  // flow ceTlmOutToOutputFlow of InterfaceItem
138
139
  // from tlm.portTlmModeOut to outputBus.portOutputTlmModeIn;
140
+ //
141
+ // It carries no direction. The ports at its two ends say `in`, `out` or `inout`, and a transfer runs from
142
+ // the one that sends to the one that receives (SysML-textual-bnf.kebnf:276, `FeatureDirection`); a second,
143
+ // writable direction is the same fact stated twice, and nothing could check the two agreed. Rule
144
+ // AR-EXCH-002 holds the exchange to its ports instead. "Input to X" is relative to a system of interest the
145
+ // model does not have, so it is a question to ask with X given, not a value on the exchange.
139
146
  interface def ComponentExchange specializes MemoInterface {
140
147
  attribute exchangeKind : FlowKind;
141
- attribute direction : DirectionKind;
142
148
  // Connection timing discipline from the source architecture
143
149
  // (e.g. AADL Communication_Properties::Timing — immediate
144
150
  // connections deliver in the same execution step).
@@ -103,6 +103,8 @@ package memo_architecture_logical_structure {
103
103
  // battery are not — which is why ownership is recorded here and is the
104
104
  // attribute that distinguishes an SoS from a merely large system.
105
105
  attribute systemBoundaryDescription : String;
106
+ // A short code the system's part numbers are written under (for example GPCA). A label: nothing checks a part number against it.
107
+ attribute systemPrefix : String[0..1];
106
108
  attribute origin : SystemOriginKind[0..1];
107
109
  attribute constituentOwnership : String;
108
110
  // A constituent may itself coordinate systems-of-systems, or it may be
@@ -165,6 +167,7 @@ package memo_architecture_logical_structure {
165
167
 
166
168
  // A typed logical connection between two components' ports.
167
169
  connection def LogicalConnector :> MemoRelationship {
170
+ attribute :>> isConnector = true;
168
171
  attribute contentKind : FlowContentKind;
169
172
  attribute direction : DirectionKind;
170
173
  end sourceComponent : LogicalComponent :>> source;
@@ -205,6 +208,12 @@ package memo_architecture_logical_structure {
205
208
  attribute latencyRequirement : String;
206
209
  }
207
210
 
211
+ // The concrete exchange a model types its logical flows by; the ends stay untyped for the reason above.
212
+ flow def LogicalTransfer specializes LogicalExchange {
213
+ end source;
214
+ end target;
215
+ }
216
+
208
217
  // States and modes of the logical solution (kept distinct from UI state
209
218
  // and from physical device configuration).
210
219
 
@@ -7,6 +7,7 @@
7
7
  // to an action performed in a context (TaskDifficultyAssessment), never to an
8
8
  // instrument.
9
9
  package memo_architecture_operational_activities {
10
+ private import memo_core_stdlib_quantities::*;
10
11
  private import Metaobjects::SemanticMetadata;
11
12
  private import ScalarValues::*;
12
13
 
@@ -38,7 +39,7 @@ package memo_architecture_operational_activities {
38
39
  attribute postCondition : String;
39
40
  attribute criticality : CriticalityKind;
40
41
  attribute taskGoal : String;
41
- attribute expectedDuration : String;
42
+ attribute expectedDuration : DurationValue;
42
43
  attribute frequencyOfUse : String;
43
44
  attribute potentialHarm : String[0..1];
44
45
  attribute severityIfFailed : SeverityKind[0..1];
@@ -60,7 +61,7 @@ package memo_architecture_operational_activities {
60
61
  attribute trainingDemand : DemandLevelKind;
61
62
  attribute ergonomicDemand : DemandLevelKind;
62
63
  attribute environmentalDemand : DemandLevelKind;
63
- attribute expectedDuration : String;
64
+ attribute expectedDuration : DurationValue;
64
65
  attribute assessor : String;
65
66
  attribute assessmentMethod : String;
66
67
 
@@ -23,7 +23,12 @@ package memo_architecture_operational_scenarios {
23
23
  enum alternate;
24
24
  }
25
25
 
26
- action def OperativeScenario specializes MemoAction {
26
+ // A scenario is a `MemoConstrainedOccurrence`: it carries the native `precondition` and
27
+ // `postcondition` constraints a function does, redefined with an expression
28
+ // (`constraint :>> precondition { level >= 0 }`). `preCondition` and `postCondition` below are the
29
+ // same two conditions in words, for what no expression says ("patient assessed"); the constraint
30
+ // is for one that can be checked.
31
+ action def OperativeScenario specializes MemoAction, MemoConstrainedOccurrence {
27
32
  attribute scenarioKind : ScenarioKind default ScenarioKind::nominal;
28
33
  attribute initialState : String;
29
34
  attribute trigger : String;
@@ -35,10 +35,6 @@ package memo_architecture_operational_use_cases {
35
35
  attribute postCondition : String;
36
36
  // clinical / service / manufacturing / development
37
37
  attribute useCaseKind : UseCaseKind;
38
- // A system use case that no clinical use case includes is a finding (rule CR-ONT-086)
39
- // unless it says so: set this for a use case that is deliberately carried out alone,
40
- // such as a service procedure. It is not a second kind of use case.
41
- attribute standalone : Boolean;
42
38
 
43
39
  // The device or system under consideration supports the goal. Native
44
40
  // `subject`, not `ref` (R10-S6): a use case needs an explicit subject
@@ -9,6 +9,7 @@
9
9
  // other way and between different things. Software reaches a node through
10
10
  // DeploysTo.
11
11
  package memo_architecture_realization_deployment {
12
+ private import memo_core_stdlib_quantities::*;
12
13
  private import Metaobjects::SemanticMetadata;
13
14
  private import ScalarValues::*;
14
15
  // The standard's allocation base, which the two AADL bindings below root
@@ -139,7 +140,7 @@ package memo_architecture_realization_deployment {
139
140
  // (MemoInterface, PhysicalComponent) so one binding serves every layer.
140
141
  allocation def ConnectionBinding :> MemoRelationship, Allocations::Allocation {
141
142
  attribute allocatedBandwidth : String;
142
- attribute mediumLatencyMs : Real;
143
+ attribute mediumLatencyMs : DurationValue;
143
144
  end boundExchange : MemoInterface :>> source;
144
145
  end medium : PhysicalComponent :>> target;
145
146
  }
@@ -174,7 +175,7 @@ package memo_architecture_realization_deployment {
174
175
  // hardware binding it traverses. `latencyBudgetMs` and `analysisPurpose`
175
176
  // (latency | fault-propagation | security) drive the AADL-style analysis.
176
177
  part def EndToEndFlow specializes MemoPart {
177
- attribute latencyBudgetMs : Real;
178
+ attribute latencyBudgetMs : DurationValue;
178
179
  attribute analysisPurpose : String;
179
180
  ref sourceFunction : MemoFunction[0..1];
180
181
  ref sinkFunction : MemoFunction[0..1];
@@ -2,6 +2,7 @@
2
2
  // software runs on and the ports the outside world plugs into. The broader
3
3
  // physical taxonomy lives in memo_architecture_implementation_hardware_structure.
4
4
  package memo_architecture_realization_physical {
5
+ private import memo_core_stdlib_quantities::*;
5
6
  private import ScalarValues::*;
6
7
 
7
8
  private import memo_core_common::*;
@@ -16,7 +17,7 @@ package memo_architecture_realization_physical {
16
17
  part def ProcessingNode specializes PhysicalElement {
17
18
  attribute nodeKind : ProcessingNodeKind;
18
19
  attribute processorArchitecture : String;
19
- attribute memoryMB : String;
20
+ attribute memoryMB : StorageCapacityValue;
20
21
  attribute operatingSystem : String;
21
22
  attribute safetyPartition : Boolean;
22
23
  attribute redundancyKind : String;
@@ -26,7 +27,7 @@ package memo_architecture_realization_physical {
26
27
  }
27
28
  part def MemoryDevice specializes PhysicalElement {
28
29
  attribute memoryKind : String;
29
- attribute capacityMB : String;
30
+ attribute capacityMB : StorageCapacityValue;
30
31
  attribute nonVolatile : Boolean;
31
32
  }
32
33
  // A physical boundary feature: the connector the outside world plugs into.
@@ -101,8 +102,8 @@ package memo_architecture_realization_physical {
101
102
  attribute signalingKind : SignalingKind;
102
103
  attribute mediumKind : PhysicalMediumKind;
103
104
  attribute electricalStandard : String;
104
- attribute nominalVoltageV : Real[0..1];
105
- attribute nominalCurrentA : Real[0..1];
105
+ attribute nominalVoltageV : ElectricPotentialDifferenceValue[0..1];
106
+ attribute nominalCurrentA : ElectricCurrentValue[0..1];
106
107
  attribute bitRateBps : String;
107
108
  attribute signalRange : String;
108
109
  attribute connectorStandard : String;
@@ -119,4 +120,10 @@ package memo_architecture_realization_physical {
119
120
  attribute minValue : String;
120
121
  attribute maxValue : String;
121
122
  }
123
+
124
+ // The concrete flow a model types its physical flows by; a concrete `flow def` declares its two ends.
125
+ flow def PhysicalTransfer specializes PhysicalFlow {
126
+ end source;
127
+ end target;
128
+ }
122
129
  }
@@ -40,8 +40,8 @@ package memo_artifacts_configuration_management {
40
40
  // `#Contains` the records of the system releases it pins, and is the validated configuration:
41
41
  // `#VerifiedByCase` names the verification cases that validated it.
42
42
  part def ReleaseRecord :> MemoPart {
43
- attribute partNumber : String[1];
44
- attribute revision : String[1];
43
+ attribute :>> partNumber : String[1];
44
+ attribute :>> revision : String[1];
45
45
  attribute softwareVersion : String[0..1];
46
46
  attribute codeTag : String[0..1];
47
47
  // The commit of the model this release was built from. A record cannot hold the hash of the
@@ -81,8 +81,15 @@ package memo_artifacts_configuration_management {
81
81
  // documents it must have. It replaces `ModelMethodBinding.regulatoryRegime`, which stated one regime set
82
82
  // for a whole model and is read only when the model declares no device.
83
83
  //
84
- // `IntendedUseOf` and `UsedWith` (plan O6) are not declared: the plan names no end for either, and an end
85
- // is not invented to fill a name. `Covers` is the link every part of M5 needs.
84
+ // The device's other two links (plan O6), both typed dependencies like `Covers`:
85
+ //
86
+ // #IntendedUseOf dependency from pumpIntendedUse to deviceFda;
87
+ // #UsedWith dependency from deviceFda to deviceInfusionSet;
88
+ //
89
+ // `IntendedUseOf` runs from the intended use (a `requirement def`, `IntendedUse`) to the device, as its
90
+ // name reads; a device can have one per indication. `UsedWith` runs between regulated devices: the
91
+ // compatible devices and accessories that are themselves approved. An accessory that is not a device is
92
+ // not a target (decided 2026-10-25, user).
86
93
  part def RegulatedDevice :> MemoPart {
87
94
  attribute jurisdiction : RegulatoryRegimeKind[1];
88
95
  attribute submissionId : String[0..1];
@@ -91,6 +98,12 @@ package memo_artifacts_configuration_management {
91
98
  metadata def Covers :> MemoTypedDependency {
92
99
  doc /* `#Covers dependency from <device>, to <record>, <record>;` The approval covers these system releases. */
93
100
  }
101
+ metadata def IntendedUseOf :> MemoTypedDependency {
102
+ doc /* `#IntendedUseOf dependency from <intended use> to <device>;` The intended use (a requirement) states what this device is for. */
103
+ }
104
+ metadata def UsedWith :> MemoTypedDependency {
105
+ doc /* `#UsedWith dependency from <device> to <device>, <device>;` The device is used with these regulated devices (compatible devices and approved accessories). */
106
+ }
94
107
 
95
108
  // A project is a change set in an iteration (plan O7): the work that produces releases. It holds a link to
96
109
  // where the work is tracked and nothing else; the merge request is the approval. It FEEDS the release records
@@ -31,7 +31,7 @@ This section describes the security architecture of **{{project.product}}**. The
31
31
  Define the trusted zones, the communication paths crossing zone boundaries, and the protection applied at each crossing.
32
32
 
33
33
  ```memo-query
34
- kind: Interface
34
+ kind: [LogicalInterface, PhysicalInterface]
35
35
  display: table
36
36
  columns: name, layer, doc
37
37
  sort: name
@@ -37,7 +37,7 @@ empty: "No system assets defined."
37
37
  Entry points and externally reachable interfaces constituting the attack surface, drawn from the model:
38
38
 
39
39
  ```memo-query
40
- kind: Interface
40
+ kind: [LogicalInterface, PhysicalInterface]
41
41
  display: table
42
42
  columns: name, layer, doc
43
43
  sort: name
@@ -47,7 +47,7 @@ _[TODO: Document state machine diagrams for stateful components]_
47
47
  ### 3.3 Interface Specifications
48
48
 
49
49
  ```memo-query
50
- kind: Interface
50
+ kind: [LogicalInterface, PhysicalInterface]
51
51
  display: table
52
52
  columns: name, layer, doc
53
53
  sort: name
@@ -69,7 +69,7 @@ empty: "No SoftwareUnit elements defined."
69
69
  ### 3.3 Interfaces
70
70
 
71
71
  ```memo-query
72
- kind: Interface
72
+ kind: [LogicalInterface, PhysicalInterface]
73
73
  display: table
74
74
  columns: name, layer, doc
75
75
  sort: name
@@ -23,11 +23,11 @@ Documents task analysis for **{{project.product}}** per IEC 62366-1:2015+AMD1:20
23
23
  This section is generated from the system model. The table below lists the user tasks and task steps currently defined:
24
24
 
25
25
  ```memo-query
26
- kind: [UserTask, TaskStep]
26
+ kind: [OperativeAction]
27
27
  display: table
28
28
  columns: name, layer, doc
29
29
  sort: name
30
- empty: "No UserTask or TaskStep elements defined."
30
+ empty: "No OperativeAction elements defined."
31
31
  ```
32
32
 
33
33
  ### 2.1 Task Boundary — What Each Task Acts Through
@@ -35,12 +35,12 @@ empty: "No UserTask or TaskStep elements defined."
35
35
  A task is cyber-physical when the element it is allocated to is a user interface, an operator interface element, or a port. The set below is derived by traversing `allocatedTo` from the tasks above, so it follows the model rather than the wording of a task name.
36
36
 
37
37
  ```memo-query
38
- kind: [UserTask, TaskStep]
38
+ kind: [OperativeAction]
39
39
  traverse: outgoing allocatedTo
40
40
  display: table
41
41
  columns: name, kind, layer, doc
42
42
  sort: name
43
- empty: "No tasks are allocated to an interface element. Add AllocatedTo links from UserTask to the UI, operator interface, or port the task acts through."
43
+ empty: "No tasks are allocated to an interface element. Add AllocatedTo links from the OperativeAction to the UI, operator interface, or port the task acts through."
44
44
  ```
45
45
 
46
46
  ### 2.2 Operator-Facing Boundary Elements
@@ -48,7 +48,7 @@ empty: "No tasks are allocated to an interface element. Add AllocatedTo links fr
48
48
  The user-facing elements a task can act through, hardware and software alike:
49
49
 
50
50
  ```memo-query
51
- kind: [UserInterface, OperatorInterfaceElement, Interface, MemoPort, PhysicalPort]
51
+ kind: [UserInterface, OperatorInterfaceElement, LogicalInterface, PhysicalInterface, MemoPort, PhysicalPort]
52
52
  display: table
53
53
  columns: name, kind, layer, doc
54
54
  sort: name
@@ -62,12 +62,12 @@ empty: "No user interface or operator interface elements defined."
62
62
  A task is critical when incorrect performance can lead to a hazardous situation. The table below is derived by traversing `causes` from the task set — the `useErrorLeadsToHazard` edge of IEC 62366-1 §5.4:
63
63
 
64
64
  ```memo-query
65
- kind: [UserTask, TaskStep]
65
+ kind: [OperativeAction]
66
66
  traverse: outgoing causes
67
67
  display: table
68
68
  columns: name, kind, layer, doc
69
69
  sort: name
70
- empty: "No hazardous situations linked to user tasks. Add Causes links (causeKind = useErrorLeadsToHazard) from UserTask to HazardousSituation."
70
+ empty: "No hazardous situations linked to user tasks. Add Causes links (causeKind = useErrorLeadsToHazard) from the OperativeAction to HazardousSituation."
71
71
  ```
72
72
 
73
73
  Complete this section for **{{project.product}}** using the guidance below.
@@ -39,7 +39,7 @@ _[TODO: Describe all use environments: clinical, home, ambulatory, etc.]_
39
39
  This section is generated from the system model. The table below lists the **Use-Related Hazards** elements currently defined:
40
40
 
41
41
  ```memo-query
42
- kind: [UseCase, UserTask]
42
+ kind: [UseCase, OperativeAction]
43
43
  display: table
44
44
  columns: name, layer, doc
45
45
  sort: name
@@ -23,7 +23,7 @@ This Use-Related Risk Analysis (URRA) identifies use errors and use-related haza
23
23
  This section is generated from the system model. The table below lists the **Use Scenarios** elements currently defined:
24
24
 
25
25
  ```memo-query
26
- kind: [UseCase, UserTask]
26
+ kind: [UseCase, OperativeAction]
27
27
  display: table
28
28
  columns: name, layer, doc
29
29
  sort: name
@@ -87,7 +87,7 @@ empty: "No runtime environments or deployment units defined."
87
87
  Cyber-physical interactions and data flows between components:
88
88
 
89
89
  ```memo-query
90
- kind: [Interface, LogicalInterface, ComponentExchange, InterfaceElement, MemoPort, DataPort, SensorPort, CommandPort, SoftwarePort, PhysicalPort, LogicalPort]
90
+ kind: [LogicalInterface, PhysicalInterface, ComponentExchange, InterfaceElement, MemoPort, DataPort, SensorPort, CommandPort, SoftwarePort, PhysicalPort, LogicalPort]
91
91
  display: table
92
92
  columns: name, kind, layer, doc
93
93
  sort: name
@@ -28,7 +28,7 @@ It replaces a hand-maintained conformance matrix. The difference that matters is
28
28
 
29
29
  A **Gap** is not a defect in the model. Coverage is profile-dependent — that is why it is a report and not a consistency rule, and why `memo_rules_coverage` is deliberately empty. A gap says the project has not claimed that clause *yet*, which is the normal state of a project in flight.
30
30
 
31
- **Scope.** The clauses below are those of the standards the project's `regulatoryRegime` declaration pulls in. Method and reference standards that no regime mandates — the FMEA method, the architecture-description standard — are listed separately in §4; their clauses are claimable but not required, so they have no gap count.
31
+ **Scope.** The clauses below are those of the standards the project's regulated devices (their jurisdictions) pull in. Method and reference standards that no regime mandates — the FMEA method, the architecture-description standard — are listed separately in §4; their clauses are claimable but not required, so they have no gap count.
32
32
 
33
33
  `memo validate --standards` prints the same numbers at the command line, from the same computation.
34
34
 
@@ -38,7 +38,7 @@ A **Gap** is not a defect in the model. Coverage is profile-dependent — that i
38
38
 
39
39
  ```memo-standards
40
40
  display: summary
41
- empty: "No standards are in scope. Declare `regulatoryRegime` on the model's ModelMethodBinding."
41
+ empty: "No standards are in scope. Declare a `RegulatedDevice` with a jurisdiction."
42
42
  ```
43
43
 
44
44
  ---
@@ -238,4 +238,19 @@ package memo_assurance_safety_risk {
238
238
  :> annotatedElement : SysML::ConnectionUsage;
239
239
  :>> baseType = mitigatesLinks meta SysML::Usage;
240
240
  }
241
+
242
+ // ISO 14971 clause 7.4: where the residual risk is judged unacceptable, the benefit of the intended use is
243
+ // weighed against it. Nothing in the chain reached a Benefit, which is a part and not a RiskItem, and the
244
+ // generic relations that accept the pair say something else (`causes` between a benefit and a risk would say
245
+ // the benefit gives rise to it). Named from the benefit's side, the way AssessedAgainst is from the risk's.
246
+ connection def WeighedAgainst :> MemoRelationship {
247
+ end benefit : Benefit :>> source;
248
+ end risk : Risk :>> target;
249
+ }
250
+ abstract connection weighedAgainstLinks : WeighedAgainst[*];
251
+ metadata def <weighedAgainst> WeighedAgainstMetadata :> SemanticMetadata {
252
+ :> annotatedElement : SysML::ConnectionDefinition;
253
+ :> annotatedElement : SysML::ConnectionUsage;
254
+ :>> baseType = weighedAgainstLinks meta SysML::Usage;
255
+ }
241
256
  }
@@ -5,6 +5,8 @@ package memo_assurance_verification_validation {
5
5
  private import memo_core_common::*;
6
6
  private import memo_core_enumerations::*;
7
7
  private import memo_core_relationships::*;
8
+ private import memo_core_stdlib_time::*;
9
+ private import memo_artifacts_configuration_management::*; // ReleaseRecord
8
10
  private import memo_architecture_operational_scenarios::*;
9
11
  private import memo_architecture_operational_use_cases::*;
10
12
  private import memo_architecture_functional_functions::*;
@@ -30,6 +32,29 @@ package memo_assurance_verification_validation {
30
32
  verification def VerificationCase :> MemoVerificationCase, VerificationCases::VerificationCase {
31
33
  attribute methodKind : MemoVerificationMethodKind;
32
34
  attribute acceptanceCriteria : String;
35
+ // The protocol: what is tested and how, before any run. A run records what happened (TestRun).
36
+ attribute testLevel : TestLevelKind[0..1];
37
+ attribute testEnvironment : TestEnvironmentKind[0..1];
38
+ attribute sampleSize : Integer[0..1];
39
+ attribute sampleSizeRationale : String[0..1];
40
+ attribute worstCaseCondition : String[0..1];
41
+ }
42
+ // A measured result: the criterion it answers, and the value as a quantity with its unit.
43
+ attribute def MeasuredValue {
44
+ attribute criterion : String;
45
+ attribute value : Quantities::ScalarQuantityValue;
46
+ }
47
+ // One execution of a verification case, and what came of it. A case is the plan and a run is the
48
+ // record, so a run is evidence the case produces (`ProducesEvidence`), one case to many runs. The
49
+ // verdict is the standard library's (VerificationCases.sysml:58), not a string.
50
+ part def TestRun specializes MemoEvidence {
51
+ attribute verdict : VerificationCases::VerdictKind;
52
+ attribute executedAt : Iso8601DateTime[0..1];
53
+ attribute softwareVersion : String[0..1];
54
+ attribute measuredValues : MeasuredValue[0..*];
55
+ // What was tested, and the release or variant it was tested in.
56
+ ref testedItem : Base::Anything[0..*];
57
+ ref testedConfiguration : ReleaseRecord[0..*];
33
58
  }
34
59
  // Orders a reusable TestStep within a verification or validation case.
35
60
  connection def PerformsStep :> MemoRelationship {
@@ -130,6 +130,10 @@ package memo_core_common {
130
130
  attribute concerns : ConcernKind[0..*];
131
131
  attribute applicableStandards : ExternalReference[0..*];
132
132
  attribute codes : TerminologyCode[0..*];
133
+ // The part's identity in the product structure, assigned by the user, not by MEMO. A revision is
134
+ // alphabetic: A, B, … Z, AA.
135
+ attribute partNumber : String[0..1];
136
+ attribute revision : String[0..1];
133
137
  }
134
138
 
135
139
  // ─── Role bases retained from the original kernel, re-founded on
@@ -169,6 +173,24 @@ package memo_core_common {
169
173
  attribute status : ElementStatusKind;
170
174
  }
171
175
 
176
+ // An occurrence whose start is guarded by a precondition and whose end by a postcondition: it
177
+ // starts only once the precondition holds and is done only once the postcondition does. The
178
+ // two are native `constraint` features a usage redefines with its own expression:
179
+ //
180
+ // action fnDose : SystemFunction {
181
+ // in rate : Real;
182
+ // constraint :>> precondition { rate >= 0 }
183
+ // }
184
+ //
185
+ // The shape is the SYSMOD method's `ConstrainedOccurrence`. It is declared on an `occurrence def`
186
+ // because `startShot` and `endShot` are found through one; `MemoFunction` specializes it.
187
+ abstract occurrence def MemoConstrainedOccurrence {
188
+ constraint precondition;
189
+ constraint postcondition;
190
+ ref occurrence :>> startShot { assert constraint :> precondition; }
191
+ ref occurrence :>> endShot { assert constraint :> postcondition; }
192
+ }
193
+
172
194
  // Boundary feature foundation for typed ports.
173
195
  port def MemoPort {
174
196
  attribute status : ElementStatusKind;