@memoarchitect/ontology 0.17.1 → 0.19.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 (268) 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/memo.identity.yaml +26 -0
  17. package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
  18. package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
  19. package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
  20. package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
  21. package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
  22. package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
  23. package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
  24. package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
  25. package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
  26. package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
  27. package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
  28. package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
  29. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +45 -55
  30. package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
  31. package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
  32. package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
  33. package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
  34. package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
  35. package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
  36. package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
  37. package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
  38. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
  39. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
  40. package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
  41. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
  42. package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
  43. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
  44. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
  45. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
  46. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
  47. package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
  48. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
  49. package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
  50. package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
  51. package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
  52. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
  53. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
  54. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
  55. package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
  56. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
  57. package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
  58. package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
  59. package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
  60. package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
  61. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
  62. package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
  63. package/examples/gpca-pump/model/methodology/project.sysml +1 -4
  64. package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
  65. package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
  66. package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
  67. package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
  68. package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
  69. package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
  70. package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
  71. package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
  72. package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
  73. package/examples/nested-architecture-dsm/README.md +5 -5
  74. package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
  75. package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
  76. package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
  77. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
  78. package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
  79. package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
  80. package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
  81. package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
  82. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +18 -27
  83. package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
  84. package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
  85. package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
  86. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +2 -7
  87. package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
  88. package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
  89. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +1 -4
  90. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +4 -9
  91. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +4 -9
  92. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +4 -9
  93. package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
  94. package/examples/robot-platform/model/platform.sysml +1 -3
  95. package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
  96. package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
  97. package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
  98. package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
  99. package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
  100. package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
  101. package/examples/surgical-closure-workflow/memo.identity.yaml +1 -0
  102. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +32 -43
  103. package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
  104. package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
  105. package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
  106. package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
  107. package/examples/surgical-robot/model/methodology/project.sysml +2 -6
  108. package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
  109. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +8 -16
  110. package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
  111. package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
  112. package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
  113. package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
  114. package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
  115. package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
  116. package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
  117. package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
  118. package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
  119. package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
  120. package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
  121. package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
  122. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +5 -12
  123. package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
  124. package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
  125. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +43 -63
  126. package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
  127. package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
  128. package/examples/ui-screen-regions/memo.identity.yaml +6 -0
  129. package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
  130. package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
  131. package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
  132. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
  133. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
  134. package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
  135. package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
  136. package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
  137. package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
  138. package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
  139. package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
  140. package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
  141. package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
  142. package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
  143. package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
  144. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
  145. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
  146. package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
  147. package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
  148. package/extensions/README.md +2 -2
  149. package/extensions/aadl/memo.package.yaml +1 -1
  150. package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
  151. package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
  152. package/extensions/anatomy/memo.package.yaml +1 -1
  153. package/extensions/clinical/memo.package.yaml +1 -1
  154. package/extensions/cloud/memo.package.yaml +1 -1
  155. package/extensions/cloud/src/cloud_extension.sysml +2 -4
  156. package/extensions/container/memo.package.yaml +1 -1
  157. package/extensions/container/src/container_extension.sysml +2 -5
  158. package/extensions/messaging/memo.package.yaml +1 -1
  159. package/extensions/messaging/src/messaging_extension.sysml +4 -5
  160. package/extensions/ros/memo.package.yaml +1 -1
  161. package/extensions/ros/src/ros_extension.sysml +5 -10
  162. package/methodologies/default/memo.package.yaml +1 -1
  163. package/methodologies/gpca/memo.package.yaml +1 -1
  164. package/ontology/memo.package.yaml +1 -1
  165. package/package.json +1 -1
  166. package/profile/memo.package.yaml +1 -1
  167. package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
  168. package/src/architecture/functional/functions/memo_functions.sysml +31 -44
  169. package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
  170. package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
  171. package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
  172. package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
  173. package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
  174. package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
  175. package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
  176. package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
  177. package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
  178. package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
  179. package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
  180. package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
  181. package/src/architecture/operational/activities/memo_activities.sysml +2 -2
  182. package/src/architecture/operational/context/actors/memo_actors.sysml +12 -10
  183. package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
  184. package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
  185. package/src/architecture/operational/rollups/memo_rollups.sysml +5 -4
  186. package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
  187. package/src/architecture/operational/structure/memo_operational.sysml +3 -5
  188. package/src/architecture/operational/use_cases/memo_use_cases.sysml +18 -23
  189. package/src/architecture/operational/workflows/memo_workflows.sysml +4 -7
  190. package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
  191. package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
  192. package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
  193. package/src/artifacts/standards/cfr_21_820.sysml +0 -1
  194. package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
  195. package/src/artifacts/standards/iec_60601_1.sysml +0 -1
  196. package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
  197. package/src/artifacts/standards/iec_60812.sysml +0 -1
  198. package/src/artifacts/standards/iec_62304.sysml +0 -1
  199. package/src/artifacts/standards/iec_62366_1.sysml +0 -1
  200. package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
  201. package/src/artifacts/standards/iso_13485.sysml +0 -1
  202. package/src/artifacts/standards/iso_14971.sysml +0 -1
  203. package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
  204. package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
  205. package/src/assurance/cybersecurity/memo_cybersecurity.sysml +7 -2
  206. package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
  207. package/src/assurance/requirements/memo_requirements.sysml +6 -11
  208. package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
  209. package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
  210. package/src/assurance/safety_risk/memo_risk.sysml +19 -22
  211. package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
  212. package/src/core/annotations/memo_annotations.sysml +2 -2
  213. package/src/core/common/memo_common.sysml +40 -56
  214. package/src/core/dimensions/dimensions.sysml +9 -12
  215. package/src/core/enumerations/memo_enumerations.sysml +6 -12
  216. package/src/core/methodology_scope/methodology_scope.sysml +3 -6
  217. package/src/core/relationships/memo_relationships.sysml +54 -85
  218. package/src/memo_namespaces.sysml +3 -0
  219. package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
  220. package/src/methodology/core/memo_core.sysml +12 -12
  221. package/src/methodology/profiles/memo_profiles.sysml +9 -10
  222. package/src/methodology/workflow/memo_workflow.sysml +7 -8
  223. package/src/rules/closure/closure_rules.sysml +7 -9
  224. package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
  225. package/src/rules/ontology/ontology_invariants.sysml +63 -95
  226. package/src/rules/quantitative/quantitative_rules.sysml +0 -1
  227. package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
  228. package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
  229. package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
  230. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +0 -1
  231. package/src/viewpoints/context/context_viewpoint.sysml +0 -1
  232. package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
  233. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
  234. package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
  235. package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
  236. package/src/viewpoints/definitions/memo_view_layout.sysml +26 -4
  237. package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
  238. package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
  239. package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
  240. package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
  241. package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
  242. package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
  243. package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
  244. package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
  245. package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
  246. package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
  247. package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
  248. package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
  249. package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
  250. package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
  251. package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
  252. package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
  253. package/src/viewpoints/software/software_viewpoint.sysml +0 -1
  254. package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
  255. package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
  256. package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
  257. package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
  258. package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
  259. package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
  260. package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
  261. package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
  262. package/stage1/opensysml-2902fc96d9371a808836d5f2.json.gz +0 -0
  263. package/stage1/syside-4582d53a6eb0fc817277b4d3.ids.gz +0 -0
  264. package/stage1/syside-4582d53a6eb0fc817277b4d3.json.gz +0 -0
  265. package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
  266. package/stage1/opensysml-78b939a8e298313dd51f9813.json.gz +0 -0
  267. package/stage1/syside-d48ff8bfaf540531526ec21a.ids.gz +0 -0
  268. package/stage1/syside-d48ff8bfaf540531526ec21a.json.gz +0 -0
@@ -1,9 +1,9 @@
1
- // User interface and interaction (§18). A small semantic hierarchy: concrete
2
- // widget forms (button, knob, chart …) are enum classifications, not classes.
3
- // UI state is distinct from system state (memo_architecture_functional_behavior) and
4
- // from device modes (memo_architecture_logical_structure::LogicalMode).
5
- // UI is an implementation concern (rendered UI is software; physical controls
6
- // are hardware), so it lives in the implementation layer, not operational.
1
+ // User interface and interaction. A small semantic hierarchy: concrete widget
2
+ // forms (button, knob, chart …) are enum classifications, not classes. UI state
3
+ // is distinct from system state (memo_architecture_functional_behavior) and
4
+ // from device modes (memo_architecture_logical_structure::LogicalMode). UI is
5
+ // an implementation concern (rendered UI is software; physical controls are
6
+ // hardware), so it lives in the implementation layer, not operational.
7
7
  package memo_architecture_implementation_ui {
8
8
  private import Metaobjects::SemanticMetadata;
9
9
  private import ScalarValues::*;
@@ -93,7 +93,7 @@ package memo_architecture_implementation_ui {
93
93
  enum imported;
94
94
  }
95
95
 
96
- // The interaction intents a step or action can carry (§18).
96
+ // The interaction intents a step or action can carry.
97
97
  enum def InteractionIntentKind {
98
98
  enum userInput;
99
99
  enum feedback;
@@ -115,15 +115,10 @@ package memo_architecture_implementation_ui {
115
115
  attribute uiTechnology : String;
116
116
  }
117
117
 
118
- // `InteractionElement` was an abstract base over UIElement and
119
- // OperatorInterfaceElement, existing so the §18 relations could type
120
- // against "something the user interacts with". It was both redundant and
121
- // too narrow: the nearest real common ancestor is already `MemoPart`, and
122
- // IEC 62366-1 puts the whole means of interaction in scope — a mis-keyed
123
- // connector, a moulded marking on a housing, a tube routed backwards are
124
- // use errors at parts that were never interaction elements and so could
125
- // not be named. `ErrorAtElement` and `ElementTriggersAction` now take
126
- // `MemoPart`; the attributes moved to whichever type actually set them.
118
+ // `ErrorAtElement` and `ElementTriggersAction` take `MemoPart`: IEC 62366-1
119
+ // puts the whole means of interaction in scope, and a mis-keyed connector,
120
+ // a moulded marking on a housing, a tube routed backwards are use errors at
121
+ // parts that are not interface elements.
127
122
 
128
123
  // One UIElement — the single UI part type. The widget form — holding
129
124
  // (screen/panel/dialog), acting (button/knob/slider), presenting
@@ -204,10 +199,9 @@ package memo_architecture_implementation_ui {
204
199
  // device shows back — because a front panel is one interface, not two.
205
200
  //
206
201
  // It is a PhysicalComponent, so it inherits part number, material, and the
207
- // ISO 10993-1 patient-contact characterization that a touched surface
208
- // needs and that software can never have. That inheritance is the reason
209
- // these forms had to leave UIElement: as UIElementFormKind members they
210
- // were software items with no way to state any of it.
202
+ // ISO 10993-1 patient-contact characterization that a touched surface needs
203
+ // and that software can never have. That inheritance is why these forms are
204
+ // not UIElement forms: a UIElement is software and cannot state any of it.
211
205
  enum def OperatorInterfaceFormKind {
212
206
  // ── actuated by the operator ──
213
207
  enum knob;
@@ -275,11 +269,9 @@ package memo_architecture_implementation_ui {
275
269
 
276
270
  // Clicking a button IS an operative action: it has a trigger, a
277
271
  // precondition, a criticality, a potential harm and a frequency of use,
278
- // exactly as turning a knob does. Specializing MemoAction directly made
279
- // UIAction a SIBLING of OperativeAction, which cost two things — a UI
280
- // action could carry none of those ten attributes, and `CommitsUseError`
281
- // (source end: OperativeAction) would not accept it, so a use error
282
- // committed by a click was unmodellable.
272
+ // exactly as turning a knob does. So UIAction specializes OperativeAction:
273
+ // it carries those attributes, and `CommitsUseError` (source end:
274
+ // OperativeAction) accepts a use error committed by a click.
283
275
  //
284
276
  // The three attributes here are what a UI action adds on top: what the
285
277
  // user meant by it, what came back, and whether it asks first.
@@ -296,14 +288,11 @@ package memo_architecture_implementation_ui {
296
288
  attribute exitPoint : String;
297
289
  }
298
290
 
299
- // `PresentsState` had zero usages anywhere in the tree (R10-S6). Its
300
- // audited native form, `exhibit state`, does not actually fit: `UIState`
301
- // is a `part def` with plain string attributes, not a `state def`, and
302
- // a SysML v2 compiler rejects `exhibit` referencing anything that does not conform to
303
- // `States::StateAction` ("An exhibit state must reference another
304
- // state"). Free deletion rather than a migration — nothing referenced
305
- // it, so nothing to preserve. If `UIState` is ever restructured onto a
306
- // real state machine, `exhibit state` becomes available then.
291
+ // `UIState` is a `part def` with plain string attributes, not a `state
292
+ // def`, so `exhibit state` cannot name it: a SysML v2 compiler rejects
293
+ // `exhibit` referencing anything that does not conform to
294
+ // `States::StateAction`. If `UIState` is restructured onto a real state
295
+ // machine, `exhibit state` becomes available.
307
296
 
308
297
  // ── Screen layout relations ──────────────────────────────────
309
298
  // Which modelled screen an image is a rendering of.
@@ -319,14 +308,13 @@ package memo_architecture_implementation_ui {
319
308
  }
320
309
 
321
310
  // Activating this element opens another screen. This is NAVIGATION, not
322
- // containment — the opened screen is not laid out inside the element, so
323
- // it is not a Composes child and the geometric rules do not relate them.
324
- // Conflating the two was the mistake that made "clicking takes you to a
325
- // child view" look like spatial nesting; it is a separate frame reached
326
- // from here, and only this relation says so.
311
+ // containment — the opened screen is not laid out inside the element, so it
312
+ // is not a Composes child and the geometric rules do not relate them.
313
+ // "Clicking takes you to a child view" is not spatial nesting: it is a
314
+ // separate frame reached from here, and only this relation says so.
327
315
  //
328
- // connection goToSettings : NavigatesTo
329
- // connect element ::> homeScreen.settingsButton to screen ::> settingsScreen;
316
+ // connection goToSettings : NavigatesTo connect homeScreen.settingsButton
317
+ // to settingsScreen;
330
318
  //
331
319
  // A screen is a UIElement whose `formKind` is `screen`; the end says UIElement because the form is an
332
320
  // attribute, not a subtype.
@@ -341,7 +329,7 @@ package memo_architecture_implementation_ui {
341
329
  :>> baseType = navigatesToLinks meta SysML::Usage;
342
330
  }
343
331
 
344
- // ── §18 traceability ─────────────────────────────────────────
332
+ // ── Traceability ─────────────────────────────────────────
345
333
  // Source is `MemoPart`, not a UI-specific base: a foot pedal and a
346
334
  // rendered button trigger the same kind of action, and the two are a
347
335
  // PhysicalComponent and a SoftwareElement whose only common ancestor is
@@ -357,8 +345,8 @@ package memo_architecture_implementation_ui {
357
345
  :> annotatedElement : SysML::ConnectionUsage;
358
346
  :>> baseType = elementTriggersActionLinks meta SysML::Usage;
359
347
  }
360
- // `ActionInvokesFunction` is native `perform` (R10-S6): write
361
- // `perform <systemFunction>;` inside the `UIAction` usage instead.
348
+ // A UI action invokes a function by native `perform`: write `perform
349
+ // <systemFunction>;` inside the `UIAction` usage.
362
350
  connection def FlowServesUseCase :> MemoRelationship {
363
351
  end interactionFlow : InteractionFlow :>> source;
364
352
  end useCase : UseCase :>> target;
@@ -377,6 +365,7 @@ package memo_architecture_implementation_ui {
377
365
  // backwards — not only on a control. Narrowing this to an interaction
378
366
  // base made those unmodellable.
379
367
  connection def ErrorAtElement :> MemoRelationship {
368
+ attribute :>> isTrace = true;
380
369
  end useError : UseError :>> source;
381
370
  end element : MemoPart :>> target;
382
371
  }
@@ -389,6 +378,7 @@ package memo_architecture_implementation_ui {
389
378
  // A risk control implemented by a UI element or by task design
390
379
  // (confirmation dialog, lockout, guarded control).
391
380
  connection def ControlImplementedBy :> MemoRelationship {
381
+ attribute :>> isTrace = true;
392
382
  end riskControl : RiskControlMeasure :>> source;
393
383
  end implementingElement :>> target;
394
384
  }
@@ -3,18 +3,13 @@
3
3
  //
4
4
  // ─── A component exchange is an interface ────────────────────────────────
5
5
  //
6
- // `ComponentExchange` is an `interface def`: the edge between two ports IS
7
- // the exchange. It was a `part def` whose `sourceEndpoint`/`targetEndpoint`
8
- // refs named the ports, beside a separate `flow` or `bind` naming them again,
9
- // and CR-ONT-076 existed only to keep the two representations in step. It
10
- // also lost information: the builder stored a dotted ref value as its first
11
- // segment only, so every endpoint read as the enclosing device, and
12
- // CR-ONT-072/073 checked the device instead of the port.
6
+ // `ComponentExchange` is an `interface def`: the edge between two ports IS the
7
+ // exchange.
13
8
  //
14
- // Its ends are the ports, and they are ports, never components: §6.2 of the
15
- // architecture plan requires an actual boundary port, and a rule
16
- // (CR-ONT-072/073) says so because the compiler does not — it accepts a
17
- // part at an interface end even when the definition types its ends.
9
+ // Its ends are the ports, and they are ports, never components: an exchange
10
+ // needs an actual boundary port, and a rule (CR-ONT-072/073) says so because
11
+ // the compiler does not — it accepts a part at an interface end even when the
12
+ // definition types its ends.
18
13
  //
19
14
  // ─── Transport, delegation, and the choice between them ──────────────────
20
15
  //
@@ -43,14 +38,14 @@ package memo_architecture_logical_interfaces {
43
38
  private import memo_architecture_functional_functions::*;
44
39
 
45
40
  // ─── One Interface definition ────────────────────────────────────
46
- // Realization domain (hardware vs software), signaling family
47
- // (digital / analog / synchronous / asynchronous) and concrete protocol
48
- // (SPI, CAN, Ethernet, 4-20mA, REST, gRPC, message-queue …) are captured
49
- // by `interfaceKind` + `protocol`, NOT by a class branch. Every
50
- // descriptive attribute below is optional, so an interface carries only
51
- // the ones that apply to it. There is no HardwareInterface /
52
- // DigitalInterface / SPIInterface / RestInterface … hierarchy: those were
53
- // 20+ classes that differed only in the value of `protocol`.
41
+ // Realization domain (hardware vs software), signaling family (digital /
42
+ // analog / synchronous / asynchronous) and concrete protocol (SPI, CAN,
43
+ // Ethernet, 4-20mA, REST, gRPC, message-queue …) are captured by
44
+ // `interfaceKind` + `protocol`, NOT by a class branch. Every descriptive
45
+ // attribute below is optional, so an interface carries only the ones that
46
+ // apply to it. There is no HardwareInterface / DigitalInterface /
47
+ // SPIInterface / RestInterface … hierarchy: such classes would differ only
48
+ // in the value of `protocol`.
54
49
 
55
50
  // The common contract of an interface, whatever layer it is on: what
56
51
  // crosses, which way, under what timing, and how much it matters to
@@ -154,16 +149,15 @@ package memo_architecture_logical_interfaces {
154
149
  // data port), modeled as a first-class element so exchanges can
155
150
  // reference it and views can render the system boundary.
156
151
  //
157
- // A `port def` (Track A1) — see PhysicalPort in
158
- // memo_architecture_realization_physical for why the specialization moved
159
- // off InterfaceElement, why `direction` is native now (Track A2), and why
160
- // `portKind` is duplicated on both ports instead of hoisted onto a base.
152
+ // A `port def` — see PhysicalPort in memo_architecture_realization_physical
153
+ // for why `direction` is native and why `portKind` is declared on both
154
+ // ports instead of on a base.
161
155
  port def SoftwarePort specializes MemoPort {
162
156
  attribute portKind : InterfaceKind;
163
- // AADL port category (plan C2). Sampled vs. queued delivery decides
164
- // whether a missed deadline drops a sample or grows a queue, which the
165
- // timing analysis and the safety case both need and neither could ask
166
- // the model for. `portKind` says what crosses; this says how.
157
+ // AADL port category. Sampled vs. queued delivery decides whether a
158
+ // missed deadline drops a sample or grows a queue, which the timing
159
+ // analysis and the safety case both need. `portKind` says what crosses;
160
+ // this says how.
167
161
  attribute portCategory : PortCategoryKind;
168
162
  attribute dataTypeName : String;
169
163
  }
@@ -1,5 +1,5 @@
1
- // Logical architecture (§10). Technology-independent structure: what parts of
2
- // the solution exist and how they interact, before committing to software,
1
+ // Logical architecture. Technology-independent structure: what parts of the
2
+ // solution exist and how they interact, before committing to software,
3
3
  // electronics, or mechanics. Redundancy is expressed by typed channel roles
4
4
  // plus independence constraints — never by duplicating identically named
5
5
  // components.
@@ -13,7 +13,7 @@ package memo_architecture_logical_structure {
13
13
  private import memo_architecture_logical_interfaces::Interface;
14
14
 
15
15
  // What a logical connection carries: information and control, but also
16
- // energy, material, fluid, and mechanical force (§10).
16
+ // energy, material, fluid, and mechanical force.
17
17
  enum def FlowContentKind {
18
18
  enum information;
19
19
  enum command;
@@ -190,19 +190,16 @@ package memo_architecture_logical_structure {
190
190
  // attribute :>> contentKind = FlowContentKind::measurement;
191
191
  // }
192
192
  //
193
- // It was a `part def` holding `sourcePort`, `targetPort` and
194
- // `exchangedItem` refs. No example set either port, so no exchange said
195
- // what it connected. The flow's ends are those ports now,
196
- // and its payload the item feature on them. `direction` is not carried
197
- // over: the ports say `in` and `out`, and a second writable direction is
198
- // the duplicate §8 of the architecture plan forbids.
193
+ // The flow's ends are those ports, and its payload the item feature on
194
+ // them. It declares no `direction`: the ports say `in` and `out`, and a
195
+ // second writable direction would be a duplicate.
199
196
  //
200
- // The ends are not restricted to `LogicalPort`. Two of the three examples
201
- // move a specimen or a force between hardware parts, and a flow def that
202
- // named `LogicalPort` ends would have refused them. `payload` is not
203
- // declared either: `of <type>` on a usage of a flow def that declares a
204
- // feature is not distinguishable (namespace distinguishability) from the
205
- // library's own `payload`, so the payload lives on the ports.
197
+ // The ends are not restricted to `LogicalPort`. A flow may move a specimen
198
+ // or a force between hardware parts, and a flow def that named
199
+ // `LogicalPort` ends would refuse it. `payload` is not declared either: `of
200
+ // <type>` on a usage of a flow def that declares a feature is not
201
+ // distinguishable (namespace distinguishability) from the library's own
202
+ // `payload`, so the payload lives on the ports.
206
203
  abstract flow def LogicalExchange {
207
204
  attribute contentKind : FlowContentKind;
208
205
  attribute latencyRequirement : String;
@@ -222,7 +219,7 @@ package memo_architecture_logical_structure {
222
219
  attribute executionSemantics : String;
223
220
  }
224
221
 
225
- // Isolation, fault containment, and trust boundaries (§10).
222
+ // Isolation, fault containment, and trust boundaries.
226
223
  part def IsolationBoundary specializes MemoPart {
227
224
  attribute boundaryKind : String;
228
225
  attribute isolationMechanism : String;
@@ -243,7 +240,7 @@ package memo_architecture_logical_structure {
243
240
  :> annotatedElement : SysML::ConnectionUsage;
244
241
  :>> baseType = independentOfLinks meta SysML::Usage;
245
242
  }
246
- // `MonitorsChannel` is native `dependency` (R10-S6): write
247
- // `dependency <monitorChannel> to <monitoredComponent>;` instead.
243
+ // A channel monitoring a component is a native `dependency`: write
244
+ // `dependency <monitorChannel> to <monitoredComponent>;`.
248
245
 
249
246
  }
@@ -68,8 +68,8 @@ package memo_architecture_operational_activities {
68
68
  attribute feedbackExpected : String;
69
69
  }
70
70
 
71
- // Difficulty of a task in a particular context (§17). Associated by
72
- // typed references, not inheritance; assessments are evidence-bearing.
71
+ // Difficulty of a task in a particular context. Associated by typed
72
+ // references, not inheritance; assessments are evidence-bearing.
73
73
  part def TaskDifficultyAssessment specializes MemoPart {
74
74
  attribute overallDifficulty : DemandLevelKind;
75
75
  attribute physicalDemand : DemandLevelKind;
@@ -1,10 +1,11 @@
1
- // Operational participants (§4) interact with the system. A stakeholder —
2
- // someone with a concern about the system who need not interact with it — is
3
- // a native SysML notion (a Part in a stakeholder membership on a concern or
4
- // viewpoint), not a separate MEMO type; the same Part may fill both roles.
5
- // "User" is reserved for a human who interacts with the medical device.
6
- // A User is also a `MemoResource`: staff are a resource with a capacity cost rate, and are already the
7
- // performers, so there is no "personnel" resource kind, which would be a second spelling of User.
1
+ // Operational participants interact with the system. A stakeholder — someone
2
+ // with a concern about the system who need not interact with it — is a native
3
+ // SysML notion (a Part in a stakeholder membership on a concern or viewpoint),
4
+ // not a separate MEMO type; the same Part may fill both roles. "User" is
5
+ // reserved for a human who interacts with the medical device. A User is also a
6
+ // `MemoResource`: staff are a resource with a capacity cost rate, and are
7
+ // already the performers, so there is no "personnel" resource kind, which would
8
+ // be a second spelling of User.
8
9
  package memo_architecture_operational_context_actors {
9
10
  private import ScalarValues::*;
10
11
 
@@ -32,7 +33,8 @@ package memo_architecture_operational_context_actors {
32
33
  attribute serviceScope : String[0..1];
33
34
  }
34
35
 
35
- // A non-human actor (external system, external device, or environmental
36
- // agent). The specific kind is described by externalKind.
37
-
36
+ // An actor that is not the device's user, such as a threat or a person present
37
+ // who does not use the device. An organization, an external system or a device is
38
+ // an OperationalEntity. `actor` is a SysML keyword, hence the prefix.
39
+ part def MemoActor specializes OperationalParticipant;
38
40
  }
@@ -1,4 +1,4 @@
1
- // ISO/IEC/IEEE 42010 architecture-description core (§4): ArchitectureDescription,
1
+ // ISO/IEC/IEEE 42010 architecture-description core: ArchitectureDescription,
2
2
  // ModelKind, and CorrespondenceRule below. Stakeholders and concerns — 42010's
3
3
  // other cornerstones — are native SysML v2 constructs (stakeholder memberships
4
4
  // and `concern def`), used directly rather than reinvented as MEMO types. A
@@ -2,13 +2,12 @@
2
2
  // reasonably foreseeable misuse are assurance requirements/risk inputs and
3
3
  // live in memo_assurance_requirements.
4
4
  //
5
- // This package once defined `ExchangesWith` for directional context-level data
6
- // flow between boundary entities. It is deleted: SysML v2's own `flow` covers
7
- // every case and is strictly stronger, because `of <ItemDef>` says WHAT moves
8
- // and two untyped connection ends cannot. Delegation between a boundary port
9
- // and the interior it stands for is `bind` — identity, not transport. SysML v2
10
- // keeps the two apart the same way: training ch. 13 wires components with
11
- // `flow`, ch. 12 delegates across a boundary with `bind`.
5
+ // Directional context-level data flow between boundary entities is SysML v2's
6
+ // own `flow`, because `of <ItemDef>` says WHAT moves and two untyped connection
7
+ // ends cannot. Delegation between a boundary port and the interior it stands
8
+ // for is `bind` — identity, not transport. SysML v2 keeps the two apart the
9
+ // same way: training ch. 13 wires components with `flow`, ch. 12 delegates
10
+ // across a boundary with `bind`.
12
11
  package memo_architecture_operational_context_use_context {
13
12
  private import Metaobjects::SemanticMetadata;
14
13
  private import ScalarValues::*;
@@ -66,12 +65,9 @@ package memo_architecture_operational_context_use_context {
66
65
  :>> baseType = interactsInContextLinks meta SysML::Usage;
67
66
  }
68
67
 
69
- // `InteractsWith` is native `connect` (2026-08-18): write
70
- // `connection connect <participant> to <target>;`. It carried no
71
- // attributes, and the operational-context package already scopes the ends.
72
- // `ConnectsPhysically` is native `connect` (R10-S6): write
73
- // `connection connect source ::> <a> to target ::> <b>;` — the ordinary
74
- // untyped binary connection — instead of a connection def for it.
68
+ // An interaction between participants, or a physical connection, is native
69
+ // `connect`: write `connection connect <a> to <b>;`, the ordinary untyped
70
+ // binary connection.
75
71
  connection def AppliesInContext :> MemoRelationship {
76
72
  end useContext : UseContext :>> source;
77
73
  end subjectElement : MemoPart :>> target;
@@ -1,7 +1,8 @@
1
- // Roll-ups of a level-2 procedure flow (plan decision 9). A number is entered once, on an
2
- // activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of its `instruments`),
3
- // and every figure above it is derived here: a scenario, a procedure, a variant. A `TradeStudy`
4
- // compares variants by these, so nothing a study reads is typed in twice.
1
+ // Roll-ups of a level-2 procedure flow. A number is entered once, on an
2
+ // activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of
3
+ // its `instruments`), and every figure above it is derived here: a scenario, a
4
+ // procedure, a variant. A `TradeStudy` compares variants by these, so nothing a
5
+ // study reads is typed in twice.
5
6
  //
6
7
  // ─── Traversal ──────────────────────────────────────────────────────────
7
8
  // `ActivitiesOf` is the one place that decides which activities count, and every roll-up reads
@@ -48,11 +48,10 @@ package memo_architecture_operational_scenarios {
48
48
  // (a robot and a laparoscopic tower do not convert to open at the same rate); level 2 only.
49
49
  attribute likelihood : ProbabilityValue[0..1];
50
50
 
51
- // The workflow this scenario belongs to is the one it is nested in
52
- // (a `HasScenario` relation was removed for that reason); a
51
+ // The workflow this scenario belongs to is the one it is nested in; a
53
52
  // nominal/alternate pair are scenarios of the same workflow,
54
- // distinguished by scenarioKind — no baseScenario back-ref.
55
- // Actors are derived from `perform` on the nested steps, not listed.
53
+ // distinguished by scenarioKind — no baseScenario back-ref. Actors are
54
+ // derived from `perform` on the nested steps, not listed.
56
55
  ref useContext : UseContext[0..1];
57
56
  // threat scenario
58
57
  attribute actorDescription : String;
@@ -69,6 +68,6 @@ package memo_architecture_operational_scenarios {
69
68
  }
70
69
 
71
70
  // A workflow is composed of one or more scenarios (nominal + alternate
72
- // paths). ScenarioOccurrence/Executes were removed: an actual execution is
73
- // a native SysML *usage* of the scenario, not a separate def + relation.
71
+ // paths). An actual execution is a native SysML *usage* of the scenario,
72
+ // not a separate def + relation.
74
73
  }
@@ -10,11 +10,9 @@ package memo_architecture_operational_structure {
10
10
  // IEC 62366-1 / ISO 14971 intended use: the medical device's declared
11
11
  // purpose and the root of the operational spine. A MemoMission, because
12
12
  // "mission" has no medical-device meaning — intended use is what a device
13
- // exists to do. Was in memo_assurance_requirements; moved here as the
14
- // operational-world root. It is a `requirement def`: the intended use is
15
- // the top obligation the device's design inputs derive from, and ISO 14971
16
- // 5.2 asks for it to be documented as the starting point of risk analysis.
17
- // It was a `part def`, which made it a structural thing.
13
+ // exists to do. It is a `requirement def`: the intended use is the top
14
+ // obligation the device's design inputs derive from, and ISO 14971 5.2 asks
15
+ // for it to be documented as the starting point of risk analysis.
18
16
  requirement def IntendedUse :> MemoMission {
19
17
  attribute indication : String;
20
18
  attribute contraindication : String;
@@ -1,6 +1,6 @@
1
- // Use cases (§5). A UseCase is a goal a person or organization wants to
2
- // achieve with system support — there is no separate Goal class. Clinical,
3
- // service, manufacturing, and development use cases specialize the same base.
1
+ // Use cases. A UseCase is a goal a person or organization wants to achieve with
2
+ // system support — there is no separate Goal class. Clinical, service,
3
+ // manufacturing, and development use cases specialize the same base.
4
4
  //
5
5
  // A use case is at one of two levels, and the level is its own type (`ClinicalUseCase` or
6
6
  // `SystemUseCase`), kept in agreement with its subject by CR-ONT-093.
@@ -49,18 +49,15 @@ package memo_architecture_operational_use_cases {
49
49
  attribute useCaseKind : UseCaseKind;
50
50
 
51
51
  // The device or system under consideration supports the goal. Native
52
- // `subject`, not `ref` (R10-S6): a use case needs an explicit subject
53
- // before it can declare `actor` (the subject parameter comes first),
54
- // and "the device/system under consideration"
55
- // is exactly what a case's subject means, so this was a duplicate
56
- // waiting to surface once `actor` needed a subject to attach to.
52
+ // `subject`, not `ref`: a use case needs an explicit subject before it
53
+ // can declare `actor` (the subject parameter comes first), and "the
54
+ // device/system under consideration" is exactly what a case's subject
55
+ // means.
57
56
  subject supportingSystem : MemoPart[0..1];
58
57
  ref useContext : UseContext[0..1];
59
58
  // Who takes part is native `actor` (`actor <role> = <participant>;`),
60
- // inherited from `UseCases::UseCase`. `primaryUser` and
61
- // `supportingActors` refs stood here as a second way of saying the
62
- // same thing and were removed; which actor initiates is carried by
63
- // the actor's name, as the note on `Initiates` below says.
59
+ // inherited from `UseCases::UseCase`. Which actor initiates is carried
60
+ // by the actor's name, as the note below says.
64
61
  }
65
62
 
66
63
  // The two levels are types, declared and not derived. A clinical use case has an
@@ -74,6 +71,7 @@ package memo_architecture_operational_use_cases {
74
71
  }
75
72
 
76
73
  connection def Motivates :> MemoRelationship {
74
+ attribute :>> isTrace = true;
77
75
  end motivatingNeed : Need :>> source;
78
76
  end motivatedUseCase : UseCase :>> target;
79
77
  }
@@ -83,15 +81,12 @@ package memo_architecture_operational_use_cases {
83
81
  :> annotatedElement : SysML::ConnectionUsage;
84
82
  :>> baseType = motivatesLinks meta SysML::Usage;
85
83
  }
86
- // `Initiates` and `ParticipatesIn` are native `actor` (R10-S6): both were
87
- // a bare typed edge onto UseCase with no attributes of their own, and
88
- // native `actor` does not distinguish an initiating actor from a
89
- // participating one — that distinction now lives in how the actor is
90
- // named on the use case, not in a relationship type. Write
91
- // `actor <role> = <existingElement>;` inside the use case instead.
92
- // UML use-case decomposition (`Includes`) is native `include use case` /
93
- // `include` (R10-S6); write that instead of a connection here. SysML v2
94
- // has no use-case `extend` (the textual BNF defines IncludeUseCaseUsage
95
- // and nothing for extend), and MEMO does not add one: an optional path
96
- // through a use case is an alternate scenario, not a second use case.
84
+ // Who initiates or takes part in a use case is native `actor`: write `actor
85
+ // <role> = <existingElement>;` inside the use case. Native `actor` does not
86
+ // distinguish an initiating actor from a participating one; that is in how
87
+ // the actor is named on the use case. UML use-case decomposition is native
88
+ // `include use case` / `include`. SysML v2 has no use-case `extend` (the
89
+ // textual BNF defines IncludeUseCaseUsage and nothing for extend), and MEMO
90
+ // does not add one: an optional path through a use case is an alternate
91
+ // scenario, not a second use case.
97
92
  }
@@ -97,12 +97,9 @@ package memo_architecture_operational_workflows {
97
97
  }
98
98
 
99
99
  // ── Workflow-level relationships ─────────────────────────────
100
- // An element supports (affords, enables) an action — e.g. a UI element
101
- // that affords a user task. Use-case and capability tracing are direct
102
- // refs now (OperationalWorkflow.useCase,
103
- // OperativeAction.contributesToCapabilities), so the former
104
- // SupportKind discriminator is gone: what used to be three enum values
105
- // that each implied a different target type are now two typed refs plus
106
- // this one plain relation.
100
+ // An element supports (affords, enables) an action — e.g. a UI element that
101
+ // affords a user task. Use-case and capability tracing are direct refs
102
+ // (OperationalWorkflow.useCase, OperativeAction.contributesToCapabilities),
103
+ // so this is one plain relation.
107
104
 
108
105
  }
@@ -2,12 +2,10 @@
2
2
  // SoftwareDeploymentUnit deploysTo ProcessingNode. Software deploys only to capable
3
3
  // execution nodes (rules/crosslayer).
4
4
  //
5
- // `HostedBy` is NOT part of that chain, and this comment used to claim it was
6
- // ("SoftwareComponent hostedBy ProcessingNode"). It is
7
- // `processingNode : ProcessingNode -> hostAssembly : PhysicalAssembly`:
8
- // physical hosting of a node by the assembly it is mounted in, running the
9
- // other way and between different things. Software reaches a node through
10
- // DeploysTo.
5
+ // `HostedBy` is NOT part of that chain. It is `processingNode : ProcessingNode
6
+ // -> hostAssembly : PhysicalAssembly`: physical hosting of a node by the
7
+ // assembly it is mounted in, running the other way and between different
8
+ // things. Software reaches a node through DeploysTo.
11
9
  package memo_architecture_realization_deployment {
12
10
  private import memo_core_stdlib_quantities::*;
13
11
  private import Metaobjects::SemanticMetadata;
@@ -41,7 +39,7 @@ package memo_architecture_realization_deployment {
41
39
  attribute certificationEvidence : String;
42
40
  }
43
41
 
44
- // A module BUILDS INTO a deployment unit: that is an allocation, and the
42
+ // A module BUILDS INTO a deployment unit: that is an allocation, and the
45
43
  // language has one. Rooted like MemoryBinding / ConnectionBinding below,
46
44
  // so the whole deployment family spells allocation the same way.
47
45
  allocation def BuildsInto :> MemoRelationship, Allocations::Allocation {
@@ -72,8 +70,7 @@ package memo_architecture_realization_deployment {
72
70
  :> annotatedElement : SysML::AllocationUsage;
73
71
  :>> baseType = realizedByLinks meta SysML::Usage;
74
72
  }
75
- // Every usage of this already writes `allocation x : DeploysTo allocate a
76
- // to b;` -- the declaration was the only part still saying `connection`.
73
+ // Written `allocation x : DeploysTo allocate a to b;`.
77
74
  allocation def DeploysTo :> MemoRelationship, Allocations::Allocation {
78
75
  attribute deploymentKind : DeploymentKind;
79
76
  end deploymentUnit : SoftwareDeploymentUnit :>> source;
@@ -96,24 +93,21 @@ package memo_architecture_realization_deployment {
96
93
  :>> baseType = providesEnvironmentLinks meta SysML::Usage;
97
94
  }
98
95
 
99
- // ─── AADL bindings (SAE AS5506) — plan C1 ────────────────────────────
96
+ // ─── AADL bindings (SAE AS5506) ────────────────────────────
100
97
  //
101
98
  // AADL's analytic power is that EVERYTHING is bound to something, and the
102
- // binding is where latency, bandwidth and fault propagation accrue. MEMO
103
- // had one binding of three: `DeploysTo` is `actual_processor_binding`.
104
- // Without the other two, `SoftwareComponent.memoryBudget` is unanalysable
105
- // and `EndToEndFlow.latencyBudgetMs` cannot be checked against the media
106
- // the flow traverses — the analysis the flow comment below describes and
107
- // the model could not perform.
99
+ // binding is where latency, bandwidth and fault propagation accrue.
100
+ // `DeploysTo` is `actual_processor_binding`. Without the other two,
101
+ // `SoftwareComponent.memoryBudget` is unanalysable and
102
+ // `EndToEndFlow.latencyBudgetMs` cannot be checked against the media the
103
+ // flow traverses.
108
104
  //
109
105
  // Both are `allocation def`s rooted on the standard's
110
106
  // `Allocations::Allocation`, because a binding IS an allocation and the
111
107
  // language says so. The double specialization keeps MEMO's identification
112
108
  // core from `MemoRelationship` while adding the standard's allocation
113
109
  // semantics; both root on `Connections::BinaryConnection`, so this is a
114
- // diamond and not a conflict. Verified with a SysML v2 compiler against a
115
- // negative control (a non-existent supertype is reported), so the clean
116
- // result is the checker agreeing rather than the checker skipping.
110
+ // diamond and not a conflict.
117
111
 
118
112
  // AADL `actual_memory_binding`. Which memory a software component's code
119
113
  // and data occupy — what makes a memory budget a claim about a device
@@ -134,10 +128,10 @@ package memo_architecture_realization_deployment {
134
128
  // interface: a network medium under a component exchange, a cable or
135
129
  // harness under a hardware `Interface`, a connector, a tube. The source is
136
130
  // the interface usage rather than a link, because the interface is the
137
- // ELEMENT that owns the budget (§19.3) and a link instance is not
138
- // something the graph can bind to; it is also exactly where the latency
139
- // the medium contributes has to be accounted. Ends are the two bases
140
- // (MemoInterface, PhysicalComponent) so one binding serves every layer.
131
+ // ELEMENT that owns the budget and a link instance is not something the
132
+ // graph can bind to; it is also exactly where the latency the medium
133
+ // contributes has to be accounted. Ends are the two bases (MemoInterface,
134
+ // PhysicalComponent) so one binding serves every layer.
141
135
  allocation def ConnectionBinding :> MemoRelationship, Allocations::Allocation {
142
136
  attribute allocatedBandwidth : String;
143
137
  attribute mediumLatencyMs : DurationValue;
@@ -198,7 +192,7 @@ package memo_architecture_realization_deployment {
198
192
  :>> baseType = flowComprisesSpecLinks meta SysML::Usage;
199
193
  }
200
194
  // The flow traverses a software→hardware binding; latency accrues here.
201
- // A binding IS an allocation, exactly as MemoryBinding and
195
+ // A binding IS an allocation, exactly as MemoryBinding and
202
196
  // ConnectionBinding already declare.
203
197
  allocation def FlowTraversesBinding :> MemoRelationship, Allocations::Allocation {
204
198
  end endToEndFlow : EndToEndFlow :>> source;