@memoarchitect/ontology 0.17.1 → 0.18.0

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 (265) hide show
  1. package/README.md +1 -1
  2. package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +11 -18
  3. package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/views/connected_patient_monitor_overview.sysml +1 -3
  4. package/examples/connected-patient-monitor/model/methodology/project.sysml +2 -6
  5. package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +35 -47
  6. package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/views/embedded_infusion_pump_overview.sysml +1 -3
  7. package/examples/embedded-infusion-pump/model/methodology/project.sysml +2 -6
  8. package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +24 -36
  9. package/examples/functional-logical-physical/model/catalog/viewpoints/logical/views/functional_logical_physical_overview.sysml +1 -3
  10. package/examples/functional-logical-physical/model/methodology/project.sysml +2 -6
  11. package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +5 -19
  12. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +1 -5
  13. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +1 -5
  14. package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +1 -5
  15. package/examples/gastric-bypass-variants/model/methodology/project.sysml +2 -6
  16. package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
  17. package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
  18. package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
  19. package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
  20. package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
  21. package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
  22. package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
  23. package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
  24. package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
  25. package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
  26. package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
  27. package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
  28. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +45 -55
  29. package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
  30. package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
  31. package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
  32. package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
  33. package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
  34. package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
  35. package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
  36. package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
  37. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
  38. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
  39. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
  40. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
  41. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
  42. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
  43. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
  44. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
  45. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
  46. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
  47. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
  48. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
  49. package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
  50. package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
  51. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
  52. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
  53. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
  54. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
  55. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
  56. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
  57. package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
  58. package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
  59. package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
  60. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
  61. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
  62. package/examples/gpca-pump/model/methodology/project.sysml +1 -4
  63. package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
  64. package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
  65. package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
  66. package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
  67. package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
  68. package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
  69. package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
  70. package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
  71. package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
  72. package/examples/nested-architecture-dsm/README.md +5 -5
  73. package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
  74. package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
  75. package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
  76. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
  77. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
  78. package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
  79. package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
  80. package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
  81. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +18 -27
  82. package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
  83. package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
  84. package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
  85. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +2 -7
  86. package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
  87. package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
  88. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +1 -4
  89. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +4 -9
  90. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +4 -9
  91. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +4 -9
  92. package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
  93. package/examples/robot-platform/model/platform.sysml +1 -3
  94. package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
  95. package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
  96. package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
  97. package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
  98. package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
  99. package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
  100. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +32 -43
  101. package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
  102. package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
  103. package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
  104. package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
  105. package/examples/surgical-robot/model/methodology/project.sysml +2 -6
  106. package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
  107. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +8 -16
  108. package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
  109. package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
  110. package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
  111. package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
  112. package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
  113. package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
  114. package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
  115. package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
  116. package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
  117. package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
  118. package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
  119. package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
  120. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +5 -12
  121. package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
  122. package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
  123. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +43 -63
  124. package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
  125. package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
  126. package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
  127. package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
  128. package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
  129. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
  130. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
  131. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
  132. package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
  133. package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
  134. package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
  135. package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
  136. package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
  137. package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
  138. package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
  139. package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
  140. package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
  141. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
  142. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
  143. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
  144. package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
  145. package/extensions/README.md +2 -2
  146. package/extensions/aadl/memo.package.yaml +1 -1
  147. package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
  148. package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
  149. package/extensions/anatomy/memo.package.yaml +1 -1
  150. package/extensions/clinical/memo.package.yaml +1 -1
  151. package/extensions/cloud/memo.package.yaml +1 -1
  152. package/extensions/cloud/src/cloud_extension.sysml +2 -4
  153. package/extensions/container/memo.package.yaml +1 -1
  154. package/extensions/container/src/container_extension.sysml +2 -5
  155. package/extensions/messaging/memo.package.yaml +1 -1
  156. package/extensions/messaging/src/messaging_extension.sysml +4 -5
  157. package/extensions/ros/memo.package.yaml +1 -1
  158. package/extensions/ros/src/ros_extension.sysml +5 -10
  159. package/methodologies/default/memo.package.yaml +1 -1
  160. package/methodologies/gpca/memo.package.yaml +1 -1
  161. package/ontology/memo.package.yaml +1 -1
  162. package/package.json +1 -1
  163. package/profile/memo.package.yaml +1 -1
  164. package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
  165. package/src/architecture/functional/functions/memo_functions.sysml +31 -44
  166. package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
  167. package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
  168. package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
  169. package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
  170. package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
  171. package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
  172. package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
  173. package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
  174. package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
  175. package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
  176. package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
  177. package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
  178. package/src/architecture/operational/activities/memo_activities.sysml +2 -2
  179. package/src/architecture/operational/context/actors/memo_actors.sysml +8 -7
  180. package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
  181. package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
  182. package/src/architecture/operational/rollups/memo_rollups.sysml +5 -4
  183. package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
  184. package/src/architecture/operational/structure/memo_operational.sysml +3 -5
  185. package/src/architecture/operational/use_cases/memo_use_cases.sysml +18 -23
  186. package/src/architecture/operational/workflows/memo_workflows.sysml +4 -7
  187. package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
  188. package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
  189. package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
  190. package/src/artifacts/standards/cfr_21_820.sysml +0 -1
  191. package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
  192. package/src/artifacts/standards/iec_60601_1.sysml +0 -1
  193. package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
  194. package/src/artifacts/standards/iec_60812.sysml +0 -1
  195. package/src/artifacts/standards/iec_62304.sysml +0 -1
  196. package/src/artifacts/standards/iec_62366_1.sysml +0 -1
  197. package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
  198. package/src/artifacts/standards/iso_13485.sysml +0 -1
  199. package/src/artifacts/standards/iso_14971.sysml +0 -1
  200. package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
  201. package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
  202. package/src/assurance/cybersecurity/memo_cybersecurity.sysml +1 -0
  203. package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
  204. package/src/assurance/requirements/memo_requirements.sysml +6 -11
  205. package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
  206. package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
  207. package/src/assurance/safety_risk/memo_risk.sysml +19 -22
  208. package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
  209. package/src/core/annotations/memo_annotations.sysml +2 -2
  210. package/src/core/common/memo_common.sysml +40 -56
  211. package/src/core/dimensions/dimensions.sysml +9 -12
  212. package/src/core/enumerations/memo_enumerations.sysml +4 -12
  213. package/src/core/methodology_scope/methodology_scope.sysml +3 -6
  214. package/src/core/relationships/memo_relationships.sysml +54 -85
  215. package/src/memo_namespaces.sysml +3 -0
  216. package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
  217. package/src/methodology/core/memo_core.sysml +12 -12
  218. package/src/methodology/profiles/memo_profiles.sysml +9 -10
  219. package/src/methodology/workflow/memo_workflow.sysml +7 -8
  220. package/src/rules/closure/closure_rules.sysml +7 -9
  221. package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
  222. package/src/rules/ontology/ontology_invariants.sysml +63 -95
  223. package/src/rules/quantitative/quantitative_rules.sysml +0 -1
  224. package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
  225. package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
  226. package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
  227. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +0 -1
  228. package/src/viewpoints/context/context_viewpoint.sysml +0 -1
  229. package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
  230. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
  231. package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
  232. package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
  233. package/src/viewpoints/definitions/memo_view_layout.sysml +25 -3
  234. package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
  235. package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
  236. package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
  237. package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
  238. package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
  239. package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
  240. package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
  241. package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
  242. package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
  243. package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
  244. package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
  245. package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
  246. package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
  247. package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
  248. package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
  249. package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
  250. package/src/viewpoints/software/software_viewpoint.sysml +0 -1
  251. package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
  252. package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
  253. package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
  254. package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
  255. package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
  256. package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
  257. package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
  258. package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
  259. package/stage1/opensysml-ddad9e2794141c08532910cf.json.gz +0 -0
  260. package/stage1/syside-8176a62528c701f2f2e0fc7f.ids.gz +0 -0
  261. package/stage1/syside-8176a62528c701f2f2e0fc7f.json.gz +0 -0
  262. package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
  263. package/stage1/opensysml-78b939a8e298313dd51f9813.json.gz +0 -0
  264. package/stage1/syside-d48ff8bfaf540531526ec21a.ids.gz +0 -0
  265. package/stage1/syside-d48ff8bfaf540531526ec21a.json.gz +0 -0
@@ -1,11 +1,8 @@
1
1
  // Methodology scope helpers.
2
2
  //
3
- // `MethodologyScope` and `MethodologyLayerSet` were removed when the semantic
4
- // contract flipped. A methodology's effective selection is declared on
5
- // `MethodologyDefinition` itself — `scopeMode` plus the `included*` lists — so
6
- // that one element answers "what is in scope". A second scope part sitting
7
- // beside the methodology meant two authorities for the same question, and the
8
- // tools read the one the methodology definition did not declare.
3
+ // A methodology's effective selection is declared on `MethodologyDefinition`
4
+ // itself — `scopeMode` plus the `included*` lists — so that one element answers
5
+ // "what is in scope".
9
6
  package memo_core_methodology_scope {
10
7
  private import ScalarValues::*;
11
8
 
@@ -21,31 +21,24 @@ package memo_core_relationships {
21
21
  //
22
22
  // A relation is a MEMO element like any other, so it carries the same
23
23
  // identification core as the part/action/item/requirement bases in
24
- // memo_core_common — with four exceptions, R10-S5 (2026-08-13). `name`,
25
- // `description`, `rationale` and `status` were declared here too, and a
26
- // tree measurement found them dead weight: across every connection usage
27
- // in src/ and examples/ (876 of them, 77 with a body at all), exactly one
28
- // ever set `rationale` and none ever set `name`, `description` or
29
- // `status`. The former `linkStatus` (planned/active/verified/obsolete) is
30
- // already gone for the same reason: a link being "verified" was never an
31
- // editorial state.
24
+ // memo_core_common — with four exceptions: `name`, `description`,
25
+ // `rationale` and `status` are native.
32
26
  //
33
- // The replacement is native, not a MEMO-authored substitute:
34
- // - `name` → the connection usage's own declared name
35
- // (`connection linkFoo : Bar …`), which every usage already has.
36
- // - `description` → `doc /* … */` on the usage.
37
- // - `rationale` → standard `Rationale` metadata: `@Rationale { :>> text
38
- // = "…"; }` (ModelingMetadata.sysml:95). `text` is exported into
39
- // `rel.attributes.rationale` by the builder, same key as before.
40
- // - `status` → standard `StatusInfo` metadata: `@StatusInfo { :>>
41
- // status = StatusKind::…; }` (ModelingMetadata.sysml:60). StatusKind
42
- // (open/tbd/tbr/tbc/done/closed) is NOT ElementStatusKind
43
- // (proposed/draft/inReview/approved/released/deprecated/retired) — the
44
- // mapping between them, and why no MEMO-side conversion code exists, is
45
- // recorded in docs/reference/naming-and-native-constructs.md. Exported
46
- // into `rel.attributes.status`.
47
- // Both metadata defs live in the standard `ModelingMetadata` package;
48
- // `private import ModelingMetadata::*;` wherever they are applied.
27
+ // Their native forms: - `name` → the connection usage's own declared
28
+ // name (`connection linkFoo : Bar …`), which every usage already has. -
29
+ // `description` → `doc /* … */` on the usage. - `rationale` → standard
30
+ // `Rationale` metadata: `@Rationale { :>> text = "…"; }`
31
+ // (ModelingMetadata.sysml:95). `text` is exported into
32
+ // `rel.attributes.rationale` by the builder. - `status` → standard
33
+ // `StatusInfo` metadata: `@StatusInfo { :>> status = StatusKind::…; }`
34
+ // (ModelingMetadata.sysml:60). StatusKind (open/tbd/tbr/tbc/done/closed) is
35
+ // NOT ElementStatusKind
36
+ // (proposed/draft/inReview/approved/released/deprecated/retired) — the
37
+ // mapping between them, and why no MEMO-side conversion code exists, is
38
+ // recorded in docs/reference/naming-and-native-constructs.md. Exported into
39
+ // `rel.attributes.status`. Both metadata defs live in the standard
40
+ // `ModelingMetadata` package; `private import ModelingMetadata::*;`
41
+ // wherever they are applied.
49
42
  //
50
43
  // isReflexive/isUnique are structural properties of the relation itself,
51
44
  // declared here so authoring and validation read them from the ontology
@@ -70,6 +63,11 @@ package memo_core_relationships {
70
63
  * satisfaction links are not. Unset is read as false. Interface and flow usages are connectors by
71
64
  * their language construct and need no value. */
72
65
  attribute isConnector : Boolean;
66
+ doc /* True when this relation records where an element's obligation comes from or how it is answered:
67
+ * a link to a requirement, a risk, a verification, a standard or a controlled document. Authoring
68
+ * surfaces offer these as traces, and a coverage report reads them as traceability. Structure,
69
+ * allocation, deployment and context links are not. Unset is read as false. */
70
+ attribute isTrace : Boolean;
73
71
  }
74
72
 
75
73
  // ─── Typed dependencies ─────────────────────────────────────────────
@@ -89,47 +87,31 @@ package memo_core_relationships {
89
87
  // (see the note above on metaclass-neutral ends).
90
88
  abstract metadata def MemoTypedDependency;
91
89
 
92
- // ─── Metaclass-neutral ends (Track A0) ──────────────────────────────
90
+ // ─── Metaclass-neutral ends ──────────────────────────────
93
91
  //
94
92
  // An end is left UNTYPED (`:>> source` / `:>> target`) wherever its
95
93
  // legitimate endpoints do not share a MEMO base, and a rule in
96
- // memo_rules_ontology states the constraint the type used to state.
94
+ // memo_rules_ontology states the constraint.
97
95
  //
98
96
  // The reason is structural, not stylistic. KerML will not let a port or a
99
97
  // behaviour specialize a part-based type, so a `MemoPart`-typed end forces
100
- // everything it accepts to be a part. That is what made PhysicalPort and
101
- // SoftwarePort part defs (so they could terminate exchanges), what made
102
- // SystemFunction a part def with its behaviour stapled on through a
103
- // separate action def, and what makes `allocate <function> to <actor>` —
104
- // ARCADIA's own System Analysis mechanism — illegal, since Actor is a
105
- // MemoPart but not a narrower part subtype.
98
+ // everything it accepts to be a part. It would also make `allocate
99
+ // <function> to <actor>` — ARCADIA's own System Analysis mechanism —
100
+ // illegal, since Actor is a MemoPart but not a narrower part subtype.
106
101
  //
107
- // Several of the relaxed ends were ALREADY being violated by real content
108
- // before they were relaxed: `composes` links parts to OperativeAction
109
- // (an action def) and to SoftwarePort/PhysicalPort;
110
- // `precedes` links OperativeAction to OperativeAction; `allocatedTo`
111
- // has ActionUsage sources; `bindsToInterface` targets an `interface def`,
112
- // which an InterfaceElement-typed end cannot hold. The types were not
113
- // buying the strictness they appeared to buy.
114
- //
115
- // What is NOT relaxed stays typed on purpose: `verificationCase` and
102
+ // Ends that are typed are typed on purpose: `verificationCase` and
116
103
  // `validationCase` are verification defs, `performed` and `enabled` are
117
104
  // MemoActions, `targetRequirement` is a MemoRequirementElement. Those ends
118
105
  // name one metaclass and mean it.
119
106
  //
120
- // The strictness did not evaporate — see CR-ONT-060..CR-ONT-071 in
121
- // src/rules/ontology/ontology_invariants.sysml. Relaxing the ends without
122
- // those rules would have been a silent loss of every constraint the ends
123
- // were carrying.
124
- //
125
- // The general relation that can join any two model elements, whatever
126
- // their metaclass. MemoLink leaves both ends untyped and adds no
127
- // domain-specific semantics, which is what makes it universal.
107
+ // The constraints on untyped ends are rules: see CR-ONT-060..CR-ONT-071 in
108
+ // src/rules/ontology/ontology_invariants.sysml.
128
109
  //
129
- // It is deliberately the weakest relation in the ontology. Reach for it
130
- // only when no specific relation carries the meaning, and say why in the
131
- // inherited `rationale` — an untyped link with no stated reason is an
132
- // audit gap, not a model fact.
110
+ // There is no general MEMO relation joining any two elements whatever
111
+ // their metaclass: SysML's native `dependency` already is one. Use
112
+ // `dependency` when no specific relation carries the meaning, and say why
113
+ // in a comment — an untyped link with no stated reason is an audit gap,
114
+ // not a model fact.
133
115
 
134
116
  // An item belongs to the scope of one system or system of systems: a need,
135
117
  // requirement, risk or verification case that describes, constrains or
@@ -152,6 +134,7 @@ package memo_core_relationships {
152
134
  }
153
135
 
154
136
  connection def DerivesFrom :> MemoRelationship {
137
+ attribute :>> isTrace = true;
155
138
  // Drivers span metaclasses — a need is a requirement def, a hazard an
156
139
  // item, a threat an item — so the source end stays untyped. The target
157
140
  // is now typed: since Requirement re-rooted onto MemoRequirement, one
@@ -165,17 +148,12 @@ package memo_core_relationships {
165
148
  :> annotatedElement : SysML::ConnectionUsage;
166
149
  :>> baseType = derivesFromLinks meta SysML::Usage;
167
150
  }
168
- // `Realizes` (realizing/concrete element → realized/abstract element) is
169
- // native `#refinement dependency` (R10-S6): write
170
- // `#refinement dependency <realizing> to <realized>;` instead. It used to
171
- // unify RealizesInterface, RealizesComponentExchange,
172
- // RealizedByArchitecture, RealizesScenario, ModuleRealizesLogical,
173
- // ComponentRealizesModule, PhysicalModuleRealizesLogical,
174
- // Implements{Component,Procedure}, UIRealizesFunctional,
175
- // FunctionalRealizesOper{ative,ational} and ScenarioRealizesUseCase; the
176
- // native form keeps that reach, since `#refinement` places no metaclass
151
+ // A realization (realizing/concrete element → realized/abstract element) is
152
+ // native `#refinement dependency`: write `#refinement dependency
153
+ // <realizing> to <realized>;`. `#refinement` places no metaclass
177
154
  // restriction on either end.
178
155
  connection def ProducesEvidence :> MemoRelationship {
156
+ attribute :>> isTrace = true;
179
157
  end producer : MemoVerificationCase :>> source;
180
158
  end producedEvidence : MemoEvidence :>> target;
181
159
  }
@@ -185,12 +163,10 @@ package memo_core_relationships {
185
163
  :> annotatedElement : SysML::ConnectionUsage;
186
164
  :>> baseType = producesEvidenceLinks meta SysML::Usage;
187
165
  }
188
- // `Precedes` is native `succession` (`first a then b;`), R10-S6.
189
- // `sameStepRequired`/`precedenceRationale` had zero usages anywhere in
190
- // the tree (same free-deletion shape R10-S5 found for `rationale`), so
191
- // there was no content to carry forward.
166
+ // Precedence is native `succession` (`first a then b;`).
192
167
 
193
168
  connection def DerivesCyberRequirement :> MemoRelationship {
169
+ attribute :>> isTrace = true;
194
170
  end sourceThreatOrRisk : RequirementDriver :>> source;
195
171
  end targetRequirement : MemoRequirementElement :>> target;
196
172
  }
@@ -213,6 +189,7 @@ package memo_core_relationships {
213
189
  }
214
190
 
215
191
  connection def Validates :> MemoRelationship {
192
+ attribute :>> isTrace = true;
216
193
  // Validation targets include use cases and other behavioural elements,
217
194
  // so the target remains untyped across SysML metaclass families.
218
195
  end validationTarget :>> source;
@@ -225,16 +202,12 @@ package memo_core_relationships {
225
202
  :>> baseType = validatesLinks meta SysML::Usage;
226
203
  }
227
204
 
228
- // Enables unifies the former EnablesWorkflow / EnablesActivity synonyms
229
- // (an enabling system/function enables a workflow/activity).
230
- // `Enables` is native `dependency` (2026-08-18): write
231
- // `dependency from <enabling> to <enabled>;`. Same call as `Supports`,
232
- // which was deleted as a duplicate of both `dependency` and `Enables`.
205
+ // An enabling system or function enabling a workflow or activity is a
206
+ // native `dependency`: write `dependency from <enabling> to <enabled>;`.
233
207
 
234
- // A processing node hosted by an assembly is allocated to it. The end
235
- // NAMES were already right; two of the three usages wrote them in reverse
236
- // order, and the builder binds by position, so those two edges pointed the
237
- // wrong way. See the reversed-end-name lint in memo-tools.
208
+ // A processing node hosted by an assembly is allocated to it. The builder
209
+ // binds ends by position, so write them in this order. See the
210
+ // reversed-end-name lint in memo-tools.
238
211
  allocation def HostedBy :> MemoRelationship, Allocations::Allocation {
239
212
  end processingNode : MemoPart :>> source;
240
213
  end hostAssembly : MemoPart :>> target;
@@ -249,17 +222,13 @@ package memo_core_relationships {
249
222
 
250
223
 
251
224
 
252
- // `Composes` is deleted (R10-S7). Containment is NESTING — the child is
253
- // declared inside the parent — which is how SysML v2 models composition:
254
- // composite feature ownership, not a link. The relation specialized
255
- // `Connections::BinaryConnection`, "a link between two things WITHIN some
256
- // containing structure", so it was the wrong category for the containment
257
- // itself, and the corpus has no composition connection to specialize.
225
+ // Containment is NESTING — the child is declared inside the parent — which
226
+ // is how SysML v2 models composition: composite feature ownership, not a
227
+ // link.
258
228
  //
259
- // Nothing is lost: the builder synthesizes a `composes` edge from every
260
- // nested part and item, so rules, the DSM and traceability read exactly the
261
- // graph they read before. The edge type is registered natively in
262
- // memo-tools' relationship registry.
229
+ // The builder synthesizes a `composes` edge from every nested part and
230
+ // item, so rules, the DSM and traceability read containment as a graph. The
231
+ // edge type is registered natively in memo-tools' relationship registry.
263
232
 
264
233
 
265
234
  connection def BindsToInterface :> MemoRelationship {
@@ -7,6 +7,9 @@ package memo {
7
7
  public import memo_core_common::*;
8
8
  public import memo_core_relationships::*;
9
9
  public import memo_core_annotations::*;
10
+ public import memo_core_stdlib_quantities::*;
11
+ public import memo_core_stdlib_money::*;
12
+ public import memo_core_stdlib_analysis::*;
10
13
 
11
14
  public import memo_architecture_operational_context_actors::*;
12
15
  public import memo_architecture_operational_context_stakeholders::*;
@@ -4,7 +4,6 @@ package memo_methodology_archetypes {
4
4
  private import memo_methodology_core::*;
5
5
 
6
6
  private import memo_core_common::*;
7
- private import memo_core_common::MemoIdentity;
8
7
  part minimal : Archetype {
9
8
  @MemoIdentity { :>> providedId = "ARCH-MINIMAL"; }
10
9
  attribute :>> label = "Minimal";
@@ -81,21 +81,21 @@ package memo_methodology_core {
81
81
  //
82
82
  // The standards, artifact kinds and viewpoints a methodology selects
83
83
  // are TYPED: a standard is a RegulatoryStandard, an artifact kind is an
84
- // ArtifactKind literal, a viewpoint is a MemoViewpoint. They were
85
- // strings ("ISO 14155", "RiskManagementPlan", "VP-CTX"), and three
86
- // standards and an artifact kind in the GPCA methodology named nothing
87
- // the ontology declares: a string that matches nothing selects nothing,
88
- // and nothing said so. Now the compiler does.
84
+ // ArtifactKind literal, a viewpoint is a MemoViewpoint. A string that
85
+ // matches nothing selects nothing and nothing says so; a typed
86
+ // reference the compiler checks.
89
87
  ref includedStandard : RegulatoryStandard[0..*];
90
88
  attribute includedArtifactKind : ArtifactKind[0..*];
91
89
  ref includedViewpoint : MemoViewpoint[0..*];
92
90
  part rulePolicy : RulePolicy[0..*];
93
91
  }
94
92
 
95
- // Which viewpoints a role works with (plan O12). A viewpoint names the stakeholders it is written for,
96
- // and that is what a role sees by default; a methodology may say otherwise for a role, and then THIS is
97
- // what the role sees, an override and not an addition. A method that names a base starts from its
98
- // role views, and a later one for the same stakeholder replaces the earlier.
93
+ // Which viewpoints a role works with. A viewpoint names the stakeholders it
94
+ // is written for, and that is what a role sees by default; a methodology
95
+ // may say otherwise for a role, and then THIS is what the role sees, an
96
+ // override and not an addition. A method that names a base starts from its
97
+ // role views, and a later one for the same stakeholder replaces the
98
+ // earlier.
99
99
  //
100
100
  // part rvSafety : RoleView { ref :>> forStakeholder = safetyEngineer; ref :>> shownViewpoint = (vpRiskChain, vpEvidenceTraceability); }
101
101
  part def RoleView :> MemoPart {
@@ -131,9 +131,9 @@ package memo_methodology_core {
131
131
  part rulePolicy : RulePolicy[0..*];
132
132
  }
133
133
 
134
- // DEPRECATED in 0.14.0, deleted in 0.15.0: the former spelling of
135
- // ModelMethodBinding, kept so a model written with it still binds. MEMO
136
- // reads `projectName` when `modelName` is absent and warns on either.
134
+ // The deprecated spelling of ModelMethodBinding, kept so a model written
135
+ // with it still binds. MEMO reads `projectName` when `modelName` is absent
136
+ // and warns on either.
137
137
  part def ProjectMethodBinding :> ModelMethodBinding {
138
138
  attribute projectName : String;
139
139
  }
@@ -13,10 +13,9 @@ package memo_methodology_profiles {
13
13
  private import memo_core_methodology_scope::*;
14
14
 
15
15
  private import memo_core_common::*;
16
- private import memo_core_common::MemoIdentity;
17
16
  part mdCoreLibrary : MethodologyLibrary {
18
17
  @MemoIdentity { :>> providedId = "METHLIB-001"; :>> label = "MedicalDeviceMethodologyLibrary"; }
19
- attribute :>> version = "0.17.1";
18
+ attribute :>> version = "0.18.0";
20
19
  attribute :>> domain = "medical device modeling";
21
20
  doc /* Methodology layer for selecting, restricting, sequencing, tailoring, and lightly extending use of the medical-device ontology. */
22
21
  }
@@ -37,7 +36,7 @@ package memo_methodology_profiles {
37
36
  // second scope authority.
38
37
  part mdDefaultDefinition : MethodologyDefinition {
39
38
  @MemoIdentity { :>> providedId = "METH-MD-DEFAULT"; :>> label = "MedicalDeviceDefault"; }
40
- attribute :>> version = "0.17.1";
39
+ attribute :>> version = "0.18.0";
41
40
  attribute :>> domain = "medical device modeling";
42
41
  doc /* MEMO default medical-device methodology. Selects every layer, discipline, standard, artifact kind, and viewpoint the resolved ontology and extension packages provide. */
43
42
  attribute :>> scopeMode = ScopeModeKind::allAvailable;
@@ -71,9 +70,10 @@ package memo_methodology_profiles {
71
70
  attribute :>> strength = RuleStrengthKind::required;
72
71
  }
73
72
 
74
- // The default method (plan O11): the steps a family works through, at the system of systems
75
- // and at each system. `outputKinds` and the rules a step is `#DoneWhen` say when its own work is done; the rules it is
76
- // `#LinkedWhen` say when it is linked to the other layers.
73
+ // The default method: the steps a family works through, at the system of
74
+ // systems and at each system. `outputKinds` and the rules a step is
75
+ // `#DoneWhen` say when its own work is done; the rules it is `#LinkedWhen`
76
+ // say when it is linked to the other layers.
77
77
 
78
78
  action stepSosContext : MethodologyWorkflowStep {
79
79
  @MemoIdentity { :>> providedId = "STEP-SOS-01"; :>> label = "SosContext"; }
@@ -281,10 +281,9 @@ package memo_methodology_profiles {
281
281
  attribute :>> passCriteria = "Core traceability, risk, verification, and RMF view support are present.";
282
282
  }
283
283
 
284
- // The GPCA binding used to live here, in the reusable default methodology,
285
- // naming its methodology by string. A project binding is project content:
286
- // it now lives in the GPCA project's own `model/methodology/project.sysml` and
287
- // references its methodology with a typed SysML reference.
284
+ // A project binding is project content: it lives in the project's own
285
+ // `model/methodology/project.sysml` and references its methodology with a
286
+ // typed SysML reference.
288
287
 
289
288
  part rmpDoc : DhfDocumentBinding {
290
289
  @MemoIdentity { :>> providedId = "DHF-001"; :>> label = "RiskManagementPlan"; }
@@ -21,14 +21,13 @@ package memo_methodology_workflow {
21
21
  // order and says which step feeds which; it never holds a step back. Teams work
22
22
  // each layer independently and link their work as the other side appears.
23
23
  //
24
- // What makes a step DONE is stated, not assumed (plan O11, T10), in two parts
25
- // judged apart:
26
- // own work every `outputKinds` kind has an element in the workspace, and every
27
- // rule the step `#DoneWhen`s has a subject there and no finding on it;
28
- // links every rule the step `#LinkedWhen`s has no finding. A link rule with
29
- // no subject yet waits for the step that produces its subjects: that
30
- // is another team's work, not this one's.
31
- // A step that states none of these has no done criterion and is never reported as done.
24
+ // What makes a step DONE is stated, not assumed, in two parts judged apart:
25
+ // own work every `outputKinds` kind has an element in the workspace, and
26
+ // every rule the step `#DoneWhen`s has a subject there and no finding on
27
+ // it; links every rule the step `#LinkedWhen`s has no finding. A link
28
+ // rule with no subject yet waits for the step that produces its subjects:
29
+ // that is another team's work, not this one's. A step that states none of
30
+ // these has no done criterion and is never reported as done.
32
31
  action def MethodologyWorkflowStep :> MemoAction {
33
32
  attribute stage : WorkflowStageKind;
34
33
  attribute objectiveDescription : String;
@@ -8,7 +8,6 @@ package memo_rules_closure {
8
8
  private import memo_core_enumerations::*;
9
9
 
10
10
  private import memo_core_common::*;
11
- private import memo_core_common::MemoIdentity;
12
11
  private import memo_artifacts_standards_traceability::EnforcesClause;
13
12
  private import memo_artifacts_standards_fda_cybersecurity_2023::*;
14
13
  private import memo_artifacts_standards_iec_62304::*;
@@ -48,7 +47,9 @@ package memo_rules_closure {
48
47
  attribute tailoring = RuleTailoringKind::assurance;
49
48
  attribute domain = RuleDomainKind::medicalDevice;
50
49
  attribute obligation = RuleObligationKind::required;
51
- // Note: ISO 14971:2019 puts verification of the implementation and effectiveness of a risk control measure in 7.2; the rule text used to say 7.4, which is benefit-risk analysis.
50
+ // Note: ISO 14971:2019 puts verification of the implementation and
51
+ // effectiveness of a risk control measure in 7.2; 7.4 is benefit-risk
52
+ // analysis.
52
53
  attribute appliesTo = "RiskControlMeasure";
53
54
  attribute severity = RuleSeverityKind::error;
54
55
  attribute rationaleText = "Risk controls shall be verified per ISO 14971 clause 7.2.";
@@ -145,12 +146,9 @@ package memo_rules_closure {
145
146
  constraint { true }
146
147
  }
147
148
 
148
- // A function that no edge reaches is not in the chain. This was a
149
- // TypeScript rule (BV-002) applying to every action usage in the model,
150
- // which reported a scenario and a flow step as defects for not being
151
- // wired like a function. It is declared here instead: scoped by the
152
- // ontology to the family it is about, tailorable by a methodology, and
153
- // readable next to the rule that requires the allocation.
149
+ // A function that no edge reaches is not in the chain. It is declared here:
150
+ // scoped by the ontology to the family it is about, tailorable by a
151
+ // methodology, and readable next to the rule that requires the allocation.
154
152
  constraint def FunctionInChainRule :> MemoConsistencyRule {
155
153
  @MemoIdentity { :>> providedId = "CR-MED-023"; }
156
154
  attribute tailoring = RuleTailoringKind::assurance;
@@ -176,7 +174,7 @@ package memo_rules_closure {
176
174
  // A user need names the user whose need it is. IEC 62366-1's user profile
177
175
  // is typed on the User element — population, impairments, training,
178
176
  // qualification — so the need points at that element rather than restating
179
- // any of it in prose, which is what `userPopulationReference` was doing.
177
+ // any of it in prose.
180
178
  constraint def UserNeedIdentifiesUserRule :> MemoConsistencyRule {
181
179
  @MemoIdentity { :>> providedId = "CR-MED-024"; }
182
180
  attribute tailoring = RuleTailoringKind::assurance;
@@ -7,7 +7,6 @@ package memo_rules_crosslayer {
7
7
  private import memo_core_enumerations::*;
8
8
 
9
9
  private import memo_core_common::*;
10
- private import memo_core_common::MemoIdentity;
11
10
  private import memo_artifacts_standards_traceability::EnforcesClause;
12
11
  private import memo_artifacts_standards_iec_62304::*;
13
12
  private import memo_artifacts_standards_iso_14971::*;