@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
@@ -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::*;
@@ -1,21 +1,23 @@
1
- // Ontology conformance invariants (§25, 0.5 rework). Same native pattern as
2
- // memo_rules_closure: `constraint def` bodies with declarative rule metadata
1
+ // Ontology conformance invariants. Same native pattern as memo_rules_closure:
2
+ // `constraint def` bodies with declarative rule metadata
3
3
  // (`predicateExpression`) evaluated by the external constraint engine.
4
4
  // Structural invariants (endpoint existence, cycle freedom) are expressed over
5
- // the typed relations introduced in 0.5 — typed references make them checkable.
5
+ // the typed relations — typed references make them checkable.
6
6
  //
7
- // Operational levels (CR-ONT-093..103). A use case and a workflow are each declared at a level by
8
- // their type: `ClinicalUseCase` and `ClinicalWorkflow` are level 1 (clinical, no product, no
9
- // number), `SystemUseCase` and `SystemWorkflow` level 2 (one variant of a platform, which carries
10
- // every number). 093 keeps a use case's type and subject in agreement, 103 a workflow's type and
11
- // the use case it `realizesUseCase`. The level of a step is the type of the workflow it sits in,
12
- // reached from the step by `composes` (a step nested in a scenario) or through the scenario that
13
- // `performs` it (a step declared once and used in several); a step outside any workflow has no
14
- // level and is judged by no level rule.
15
- // Each rule reads a type and the `performs` and `realizes` edges the builder already produces.
16
- // Rule 6 of the plan, that every variant of a `TradeStudy` refines every step compared (101),
17
- // reads the study's `hasSubject` edges: its subject is the alternatives it analyses.
18
- // The one-currency rule (098) counts the project's `CurrencyUnit` declarations: a unit declared at
7
+ // Operational levels (CR-ONT-093..103). A use case and a workflow are each
8
+ // declared at a level by their type: `ClinicalUseCase` and `ClinicalWorkflow`
9
+ // are level 1 (clinical, no product, no number), `SystemUseCase` and
10
+ // `SystemWorkflow` level 2 (one variant of a platform, which carries every
11
+ // number). 093 keeps a use case's type and subject in agreement, 103 a
12
+ // workflow's type and the use case it `realizesUseCase`. The level of a step is
13
+ // the type of the workflow it sits in, reached from the step by `composes` (a
14
+ // step nested in a scenario) or through the scenario that `performs` it (a step
15
+ // declared once and used in several); a step outside any workflow has no level
16
+ // and is judged by no level rule. Each rule reads a type and the `performs` and
17
+ // `realizes` edges the builder already produces. Rule 101, that every variant
18
+ // of a `TradeStudy` refines every step compared, reads the study's `hasSubject`
19
+ // edges: its subject is the alternatives it analyses. The one-currency rule
20
+ // (098) counts the project's `CurrencyUnit` declarations: a unit declared at
19
21
  // package level is built as a model element, as ISQ and SI declare theirs.
20
22
  package memo_rules_ontology {
21
23
  private import ScalarValues::*;
@@ -24,7 +26,6 @@ package memo_rules_ontology {
24
26
  private import memo_core_enumerations::*;
25
27
 
26
28
  private import memo_core_common::*;
27
- private import memo_core_common::MemoIdentity;
28
29
  private import memo_artifacts_standards_traceability::EnforcesClause;
29
30
  private import memo_artifacts_standards_iec_62366_1::*;
30
31
  private import memo_artifacts_standards_iso_13485::*;
@@ -54,7 +55,7 @@ package memo_rules_ontology {
54
55
  attribute predicateExpression = "allOfKind('System')->exists(isDefinition == 'true')";
55
56
  constraint { true }
56
57
  }
57
- // ─── Use case scope (plan O8) ─────────────────────────────────────────
58
+ // ─── Use case scope ─────────────────────────────────────────
58
59
  //
59
60
  // The level of a use case is its declared type (`ClinicalUseCase`, `SystemUseCase`), and
60
61
  // CR-ONT-093 keeps it in agreement with the subject (`hasSubject`). Rule 085 reads the subject
@@ -72,7 +73,7 @@ package memo_rules_ontology {
72
73
  attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(SystemOfSystems))) or downstream(includesStep)->exists(downstream(hasSubject)->exists(conformsTo(System)))";
73
74
  constraint { true }
74
75
  }
75
- // ─── Release selections (plan O14) ────────────────────────────────────
76
+ // ─── Release selections ────────────────────────────────────
76
77
  //
77
78
  // A release record selects features (`#SelectsFeature`), and through them the variants that realize
78
79
  // them (`#RealizesFeature`, variant to feature). The rules read a record's selection by navigation;
@@ -158,10 +159,11 @@ package memo_rules_ontology {
158
159
 
159
160
  // ─── Direction is written on the ports, and an exchange has to agree with them ──
160
161
  //
161
- // A port says `in` or `out` (or `inout`), and a `~` conjugates it. That is the only place direction is
162
- // written: an exchange's own direction was the same fact a second time, and nothing checked the two
163
- // agreed. These two rules check the exchange against its ports, so a contradiction cannot be written.
164
- // Both judge only ends that are ports with a stated direction; a port that says none is not judged.
162
+ // A port says `in` or `out` (or `inout`), and a `~` conjugates it. That is
163
+ // the only place direction is written. These two rules check the exchange
164
+ // against its ports, so a contradiction cannot be written. Both judge only
165
+ // ends that are ports with a stated direction; a port that says none is not
166
+ // judged.
165
167
  constraint def BindingEndsAgreeInDirectionRule :> MemoConsistencyRule {
166
168
  @MemoIdentity { :>> providedId = "AR-EXCH-001"; }
167
169
  attribute tailoring = RuleTailoringKind::invariant;
@@ -249,14 +251,11 @@ package memo_rules_ontology {
249
251
  attribute tailoring = RuleTailoringKind::assurance;
250
252
  attribute domain = RuleDomainKind::medicalDevice;
251
253
  attribute obligation = RuleObligationKind::required;
252
- // To confirm: inferred from the clause scope; the FDA human-factors guidance it also cites is not in the library yet.
253
- // The selector used to be `[criticality=high]`, which left the
254
- // catastrophic tasks — the most critical — outside the rule while the
255
- // predicate still spelled out the catastrophic case. The criticality
256
- // test lives in the predicate alone now. `testedByUsability` is the
257
- // relation the human-factors package declares for exactly this link;
258
- // reading only `validates` meant a task linked the way the ontology
259
- // asks was still reported.
254
+ // To confirm: inferred from the clause scope; the FDA human-factors
255
+ // guidance it also cites is not in the library yet. The criticality
256
+ // test lives in the predicate alone, so catastrophic tasks are in
257
+ // scope. `testedByUsability` is the relation the human-factors package
258
+ // declares for exactly this link.
260
259
  attribute appliesTo = "OperativeAction";
261
260
  attribute severity = RuleSeverityKind::error;
262
261
  attribute rationaleText = "Critical tasks (criticality high or catastrophic) must trace to usability validation (FDA HF guidance; IEC 62366-1 summative evaluation).";
@@ -277,34 +276,22 @@ package memo_rules_ontology {
277
276
  constraint { true }
278
277
  }
279
278
  #EnforcesClause dependency from UseErrorTracesToHazardRule to iec62366_1::iec62366_1Clause5::iec62366_1Clause5_3;
280
- // ─── Relation end conformance (Track A0) ─────────────────────────────
279
+ // ─── Relation end conformance ─────────────────────────────
281
280
  //
282
- // These rules carry the constraints that `connection def` end TYPES used to
283
- // carry in memo_core_relationships. The types had to go: KerML forbids a
284
- // port or a behaviour from specializing a part-based type, so a
285
- // `MemoPart`-typed end forced every endpoint to be a part — which is why
286
- // ports are part defs, why a function is a part with its behaviour stapled
287
- // on, and why `allocate <function> to <actor>` is rejected. See the Track A0
288
- // note at the top of memo_core_relationships.
281
+ // These rules carry the constraints on `connection def` ends that a type
282
+ // cannot state: KerML forbids a port or a behaviour from specializing a
283
+ // part-based type, so a `MemoPart`-typed end would force every endpoint to
284
+ // be a part. See the note on metaclass-neutral ends in
285
+ // memo_core_relationships.
289
286
  //
290
- // Each rule states what its end stated, in the one vocabulary that survives
291
- // the metaclass split:
287
+ // Each rule states its end's constraint, in the one vocabulary that spans
288
+ // the metaclasses:
292
289
  //
293
- // * `conformsTo(Base)` — SysML specialization against a MEMO base. This is
294
- // the part the end type expressed, and it still works within a metaclass.
295
- // * `construct == 'action' | 'port' | 'state' | …` — the SysML METACLASS.
296
- // No MEMO base can say this, because the bases are per-metaclass by
297
- // construction; a type-based end could only ever admit one of them.
298
- //
299
- // Several of these are WIDER than the end they replace, and deliberately so:
300
- // the ends were being violated by content that already shipped. `composes`
301
- // was typed MemoPart/MemoPart and links StateMachine (a state def) to
302
- // OperativeAction (an action def); `verifiedBy`'s source was typed MemoPart and
303
- // most of its sources are requirement defs; `precedes` was typed
304
- // a part-only type and joins OperativeAction to OperativeAction.
305
- // A rule that reproduced the old type exactly would have failed on the
306
- // flagship example on the day it landed. What each rule asserts is the
307
- // constraint the end MEANT, stated so it can be checked.
290
+ // * `conformsTo(Base)` — SysML specialization against a MEMO base. This
291
+ // works within a metaclass. * `construct == 'action' | 'port' | 'state' |
292
+ // …` — the SysML METACLASS. No MEMO base can say this, because the bases
293
+ // are per-metaclass by construction; a type-based end could only ever admit
294
+ // one of them.
308
295
  //
309
296
  // Subject scope is `Model`, following CR-ONT-001: a statement about the ends
310
297
  // of a relation quantifies over its LINKS, not over elements of one kind, so
@@ -434,16 +421,10 @@ package memo_rules_ontology {
434
421
  constraint { true }
435
422
  }
436
423
 
437
- // CR-ONT-002's replacement, now asked of the edge. A ComponentExchange is
438
- // an interface, so its ends are the ports it connects, and `sourceEnd` /
439
- // `targetEnd` are those elements. The compiler does not check this:
440
- // a compiler accepts a part at an interface end even when the definition types
441
- // the ends.
442
- //
443
- // It used to read `sourceEndpoint` refs, whose dotted values the builder
444
- // cut to their first segment, and compare them as strings, which drop
445
- // everything up to the last `::`. On gpca-pump that matched the enclosing
446
- // device for 44 of 46 exchanges and passed.
424
+ // A ComponentExchange is an interface, so its ends are the ports it
425
+ // connects, and `sourceEnd` / `targetEnd` are those elements. The compiler
426
+ // does not check this: a compiler accepts a part at an interface end even
427
+ // when the definition types the ends.
447
428
  constraint def ComponentExchangeSourceEndpointKindRule :> MemoConsistencyRule {
448
429
  @MemoIdentity { :>> providedId = "CR-ONT-072"; }
449
430
  attribute tailoring = RuleTailoringKind::invariant;
@@ -480,8 +461,8 @@ package memo_rules_ontology {
480
461
  attribute obligation = RuleObligationKind::recommended;
481
462
  attribute appliesTo = "ComponentFunction";
482
463
  attribute severity = RuleSeverityKind::error;
483
- attribute rationaleText = "A component function is the responsibility of exactly one component, and AllocatedTo is what names it. A component function allocated nowhere is a responsibility nobody has accepted; one allocated twice is a responsibility nobody owns. A system-level responsibility with no single owner is a SystemFunction, which allows that.";
484
- attribute predicateExpression = "allocatedTo->size() == 1";
464
+ attribute rationaleText = "A component function is the responsibility of exactly one component, and AllocatedTo is what names it. A component function allocated nowhere is a responsibility nobody has accepted; one allocated twice is a responsibility nobody owns. A system-level responsibility with no single owner is a SystemFunction, which allows that. A definition is a type and is not allocated; its usages are.";
465
+ attribute predicateExpression = "isDefinition == 'true' or allocatedTo->size() == 1";
485
466
  constraint { true }
486
467
  }
487
468
  constraint def FunctionDecomposesIntoFunctionsRule :> MemoConsistencyRule {
@@ -491,8 +472,8 @@ package memo_rules_ontology {
491
472
  attribute obligation = RuleObligationKind::recommended;
492
473
  attribute appliesTo = "MemoFunction";
493
474
  attribute severity = RuleSeverityKind::error;
494
- attribute rationaleText = "The functional chain decomposes functions into functions. A function composed of a component, or owned by one, is confusing allocation with decomposition — the component is named by AllocatedTo, never by Composes.";
495
- attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction) or kind == 'ForkNode' or kind == 'JoinNode' or kind == 'DecisionNode' or kind == 'MergeNode')";
475
+ attribute rationaleText = "The functional chain decomposes functions into functions. A function composed of a component, or owned by one, is confusing allocation with decomposition — the component is named by AllocatedTo, never by Composes. A functional flow is a behaviour, not a component: a function step inside one is decomposition.";
476
+ attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction) or conformsTo(FunctionalFlow) or kind == 'ForkNode' or kind == 'JoinNode' or kind == 'DecisionNode' or kind == 'MergeNode')";
496
477
  constraint { true }
497
478
  }
498
479
 
@@ -512,13 +493,10 @@ package memo_rules_ontology {
512
493
  // writing them as containment loses the distinction.
513
494
  //
514
495
  // They read the `composes` edge, which the builder synthesizes from native
515
- // nesting, so they cover the nesting spelling and the retired connection
516
- // form identically. They read it DOWNSTREAM: a bare relation name navigates
517
- // both ways, so `composes` alone also reached the subject's own parent and
518
- // judged a software system by the assembly it sat in. That reported one
519
- // cross-family nesting twice, once on each side, and the child's copy
520
- // blamed the element that was not doing the containing. `downstream` is
521
- // transitive, so the rule reads as "the subtree stays in the family".
496
+ // nesting. They read it DOWNSTREAM: a bare relation name navigates both
497
+ // ways, so `composes` alone would reach the subject's own parent and report
498
+ // one cross-family nesting twice. `downstream` is transitive, so the rule
499
+ // reads as "the subtree stays in the family".
522
500
  //
523
501
  // Ports are exempt. A port is a boundary FEATURE of its owner, not a member
524
502
  // of its owner's family, and any element may carry one whatever family it
@@ -565,16 +543,9 @@ package memo_rules_ontology {
565
543
  // whose ends are the exchange's own two ports. The ends are compared as
566
544
  // elements (`intersects` matches exact ids), not as names.
567
545
  //
568
- // It replaces the same-name coupling this id used to check, which tied a
569
- // ComponentExchange PART to a flow of the same name. That was unsatisfiable
570
- // once the model compiled: two members of one namespace may not share a
571
- // name (`namespace-distinguishability`), and a `bind` could not be named at
572
- // all. With the exchange an interface there is no second record to keep in
573
- // step, and what is left to check is transport.
574
- //
575
546
  // `assurance`, not `invariant`: whether every interface must declare its
576
- // transport is a method's call (§9.2 of the architecture plan), and a
577
- // method that models interfaces before their flows may tailor it.
547
+ // transport is a method's call, and a method that models interfaces before
548
+ // their flows may tailor it.
578
549
  constraint def ExchangeHasFlowRule :> MemoConsistencyRule {
579
550
  @MemoIdentity { :>> providedId = "CR-ONT-076"; }
580
551
  attribute tailoring = RuleTailoringKind::assurance;
@@ -620,17 +591,14 @@ package memo_rules_ontology {
620
591
 
621
592
  // ─── Assurance-trace warnings ────────────────────────────────────────
622
593
  // A WARNING, not an error: it describes a trace graph that is suspicious
623
- // rather than invalid, and a regulated model has legitimate exceptions.
624
- // It needed `upstream` / `downstream` — the bare relation name is
625
- // bidirectional, so before those existed no rule could ask which way a
626
- // derivation ran.
594
+ // rather than invalid, and a regulated model has legitimate exceptions. It
595
+ // reads `upstream` / `downstream` because the bare relation name is
596
+ // bidirectional.
627
597
  //
628
- // CR-ONT-081 (RedundantAncestorTraceRule) was deleted 2026-09-25. It called
629
- // a trace redundant when one element satisfied both a requirement and one
630
- // derived from it, "already implied by the derivation". It is not: a
631
- // `derive` does not make its source satisfied, and a response-time
632
- // requirement derived from "select a drug from the library" says nothing
633
- // about whether the selector lets you select one.
598
+ // A trace is not redundant when one element satisfies both a requirement
599
+ // and one derived from it: a `derive` does not make its source satisfied,
600
+ // and a response-time requirement derived from "select a drug from the
601
+ // library" says nothing about whether the selector lets you select one.
634
602
 
635
603
  constraint def DerivationGapRule :> MemoConsistencyRule {
636
604
  @MemoIdentity { :>> providedId = "CR-ONT-080"; }
@@ -7,7 +7,6 @@ package memo_rules_quantitative {
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
  constraint def HazardMaxControlsRule :> MemoConsistencyRule {
12
11
  @MemoIdentity { :>> providedId = "QT-001"; }
13
12
  attribute tailoring = RuleTailoringKind::assurance;
@@ -1,7 +1,7 @@
1
- // Ontology-level viewpoint catalog (§22). Rendering-independent: each
2
- // viewpoint states the concern it frames and the SysML v2 standard view kind
3
- // it resolves to (general | interconnection | actionflow | statetransition |
4
- // sequence | grid | browser | geometry). No renderer semantics here.
1
+ // Ontology-level viewpoint catalog. Rendering-independent: each viewpoint
2
+ // states the concern it frames and the SysML v2 standard view kind it resolves
3
+ // to (general | interconnection | actionflow | statetransition | sequence |
4
+ // grid | browser | geometry). No renderer semantics here.
5
5
  package memo_viewpoints_catalog {
6
6
  private import ScalarValues::*;
7
7
 
@@ -9,7 +9,6 @@ package memo_viewpoints_catalog {
9
9
  private import memo_core_enumerations::*;
10
10
  private import memo_viewpoints_definitions::*;
11
11
 
12
- private import memo_core_common::MemoIdentity;
13
12
  // A cataloged viewpoint: the Viewpoint descriptor plus its default
14
13
  // resolution to a standard SysML v2 view kind.
15
14
 
@@ -167,7 +166,7 @@ package memo_viewpoints_catalog {
167
166
  attribute :>> defaultViewKind = DiagramViewKind::geometry;
168
167
  }
169
168
 
170
- // ── Compatibility mappings (§22): legacy diagram intents resolve to
169
+ // ── Compatibility mappings: legacy diagram intents resolve to
171
170
  // standard view kinds; C4 and AADL stay in examples/ mappings. ──
172
171
  part def DiagramIntentMapping specializes MemoPart {
173
172
  attribute legacyIntent : String;
@@ -6,7 +6,6 @@ package memo_viewpoints_clinical_clinical_viewpoint {
6
6
  private import memo_viewpoints_stakeholders_concerns::*;
7
7
 
8
8
  private import memo_core_common::*;
9
- private import memo_core_common::MemoIdentity;
10
9
  viewpoint clinicalViewpoint : MemoViewpoint {
11
10
  @MemoIdentity { :>> providedId = "VP-CLIN"; :>> label = "ClinicalViewpoint"; }
12
11
  @MemoIdentity { :>> shortDescription = "Shows clinical context, users, use environment, and clinical evidence."; }
@@ -1,13 +1,13 @@
1
1
  package memo_viewpoints_clinical_views_clinical_evidence_view {
2
2
  private import ScalarValues::*;
3
3
 
4
- private import memo_viewpoints_definitions::*;
5
- private import memo_core_enumerations::*;
4
+ private import memo_viewpoints_definitions::*;
5
+ private import memo_core_enumerations::*;
6
6
 
7
- view def MemoClinicalEvidenceView :> MemoDocumentView {
8
- attribute :>> viewKind = DocumentViewKind::clinical;
9
- attribute :>> generationRule = "Include use contexts, actors, and clinical evidence supporting the device's intended use, filtered to clinical concern.";
10
- attribute :>> outputKind = (ViewOutputKind::documentSection);
11
- attribute :>> presentationKind = (PresentationKind::narrativeSection);
12
- }
7
+ view def MemoClinicalEvidenceView :> MemoDocumentView {
8
+ attribute :>> viewKind = DocumentViewKind::clinical;
9
+ attribute :>> generationRule = "Include use contexts, actors, and clinical evidence supporting the device's intended use, filtered to clinical concern.";
10
+ attribute :>> outputKind = (ViewOutputKind::documentSection);
11
+ attribute :>> presentationKind = (PresentationKind::narrativeSection);
12
+ }
13
13
  }
@@ -6,7 +6,6 @@ package memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint {
6
6
  private import memo_viewpoints_stakeholders_concerns::*;
7
7
 
8
8
  private import memo_core_common::*;
9
- private import memo_core_common::MemoIdentity;
10
9
  viewpoint clinicalWorkflowViewpoint : MemoViewpoint {
11
10
  @MemoIdentity { :>> providedId = "VP-CLINWF"; :>> label = "ClinicalWorkflowViewpoint"; }
12
11
  @MemoIdentity { :>> shortDescription = "Shows clinical use cases, workflows and scenarios: what must happen to the patient, with no product and no number."; }
@@ -6,7 +6,6 @@ package memo_viewpoints_context_context_viewpoint {
6
6
  private import memo_viewpoints_stakeholders_concerns::*;
7
7
 
8
8
  private import memo_core_common::*;
9
- private import memo_core_common::MemoIdentity;
10
9
  viewpoint contextViewpoint : MemoViewpoint {
11
10
  @MemoIdentity { :>> providedId = "VP-CTX"; :>> label = "ContextViewpoint"; }
12
11
  @MemoIdentity { :>> shortDescription = "Shows actors, use context, and system boundary."; }
@@ -1,28 +1,27 @@
1
1
  package memo_viewpoints_context_views_system_context_view {
2
2
  private import ScalarValues::*;
3
3
 
4
- private import memo_viewpoints_definitions::*;
5
- private import memo_core_enumerations::*;
4
+ private import memo_viewpoints_definitions::*;
5
+ private import memo_core_enumerations::*;
6
6
  private import memo_viewpoints_context_context_viewpoint::*;
7
7
 
8
8
  private import memo_core_common::*;
9
- private import memo_core_common::MemoIdentity;
10
- view systemContextView : MemoDiagramView {
11
- expose memo_viewpoints_context_views_system_context_view::*;
12
- attribute depth = 2;
13
- @MemoIdentity { :>> providedId = "VIEW-CTX-001"; :>> label = "SystemContextView"; }
14
- @MemoIdentity { :>> shortDescription = "Actors, use context, and system boundary."; }
15
- attribute :>> outputKind = (ViewOutputKind::diagram);
16
- attribute :>> presentationKind = (PresentationKind::blockDiagram);
17
- attribute :>> diagramType = "bdd";
18
- attribute :>> autoPopulate = true;
19
- attribute :>> queryDescription = "Include actors, use contexts, and trust boundaries at the system boundary.";
20
- part :>> selectionQuery {
21
- @MemoIdentity { :>> providedId = "QRY-CTX-001"; :>> label = "SystemContextQuery"; }
22
- attribute :>> includeElementKinds = ("OperationalParticipant", "UseContext", "TrustBoundary");
23
- attribute :>> includeLayers = ("context");
24
- attribute :>> rationaleText = "Auto-populate the system context view from the context layer.";
9
+ view systemContextView : MemoDiagramView {
10
+ expose memo_viewpoints_context_views_system_context_view::*;
11
+ attribute depth = 2;
12
+ @MemoIdentity { :>> providedId = "VIEW-CTX-001"; :>> label = "SystemContextView"; }
13
+ @MemoIdentity { :>> shortDescription = "Actors, use context, and system boundary."; }
14
+ attribute :>> outputKind = (ViewOutputKind::diagram);
15
+ attribute :>> presentationKind = (PresentationKind::blockDiagram);
16
+ attribute :>> diagramType = "bdd";
17
+ attribute :>> autoPopulate = true;
18
+ attribute :>> queryDescription = "Include actors, use contexts, and trust boundaries at the system boundary.";
19
+ part :>> selectionQuery {
20
+ @MemoIdentity { :>> providedId = "QRY-CTX-001"; :>> label = "SystemContextQuery"; }
21
+ attribute :>> includeElementKinds = ("OperationalParticipant", "UseContext", "TrustBoundary");
22
+ attribute :>> includeLayers = ("context");
23
+ attribute :>> rationaleText = "Auto-populate the system context view from the context layer.";
24
+ }
25
+ ref :>> viewpointDefinition = contextViewpoint;
25
26
  }
26
- ref :>> viewpointDefinition = contextViewpoint;
27
- }
28
27
  }
@@ -6,7 +6,6 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
6
6
  private import memo_viewpoints_stakeholders_concerns::*;
7
7
 
8
8
  private import memo_core_common::*;
9
- private import memo_core_common::MemoIdentity;
10
9
  viewpoint cybersecurityViewpoint : MemoViewpoint {
11
10
  @MemoIdentity { :>> providedId = "VP-CYB"; :>> label = "CybersecurityViewpoint"; }
12
11
  @MemoIdentity { :>> shortDescription = "Shows assets, trust boundaries, threats, vulnerabilities, cyber hazards, cyber risks, and mitigations."; }
@@ -1,13 +1,13 @@
1
1
  package memo_viewpoints_cybersecurity_views_cybersecurity_assessment_view {
2
2
  private import ScalarValues::*;
3
3
 
4
- private import memo_viewpoints_definitions::*;
5
- private import memo_core_enumerations::*;
4
+ private import memo_viewpoints_definitions::*;
5
+ private import memo_core_enumerations::*;
6
6
 
7
- view def MemoCybersecurityAssessmentView :> MemoDocumentView {
8
- attribute :>> viewKind = DocumentViewKind::cybersecurityAssessment;
9
- attribute :>> generationRule = "Include cyber risks, exploitability, mitigations, security requirements, verification, residual risk, and postmarket evidence references.";
10
- attribute :>> outputKind = (ViewOutputKind::documentSection);
11
- attribute :>> presentationKind = (PresentationKind::riskTable);
12
- }
7
+ view def MemoCybersecurityAssessmentView :> MemoDocumentView {
8
+ attribute :>> viewKind = DocumentViewKind::cybersecurityAssessment;
9
+ attribute :>> generationRule = "Include cyber risks, exploitability, mitigations, security requirements, verification, residual risk, and postmarket evidence references.";
10
+ attribute :>> outputKind = (ViewOutputKind::documentSection);
11
+ attribute :>> presentationKind = (PresentationKind::riskTable);
12
+ }
13
13
  }
@@ -1,13 +1,13 @@
1
1
  package memo_viewpoints_cybersecurity_views_threat_model_view {
2
2
  private import ScalarValues::*;
3
3
 
4
- private import memo_viewpoints_definitions::*;
5
- private import memo_core_enumerations::*;
4
+ private import memo_viewpoints_definitions::*;
5
+ private import memo_core_enumerations::*;
6
6
 
7
- view def MemoCybersecurityThreatModelView :> MemoDocumentView {
8
- attribute :>> viewKind = DocumentViewKind::threatModel;
9
- attribute :>> generationRule = "Include assets, trust boundaries, threat scenarios, vulnerabilities, mitigations, and trace links to safety/privacy concerns.";
10
- attribute :>> outputKind = (ViewOutputKind::documentSection);
11
- attribute :>> presentationKind = (PresentationKind::narrativeSection);
12
- }
7
+ view def MemoCybersecurityThreatModelView :> MemoDocumentView {
8
+ attribute :>> viewKind = DocumentViewKind::threatModel;
9
+ attribute :>> generationRule = "Include assets, trust boundaries, threat scenarios, vulnerabilities, mitigations, and trace links to safety/privacy concerns.";
10
+ attribute :>> outputKind = (ViewOutputKind::documentSection);
11
+ attribute :>> presentationKind = (PresentationKind::narrativeSection);
12
+ }
13
13
  }
@@ -1,9 +1,8 @@
1
1
  // Where a view's boxes sit. A drawing's layout is presentation, and it is
2
2
  // written in the view that owns it: `@MemoLayout` and its `@MemoLayout*`
3
3
  // siblings annotate a `view` usage (their `annotatedElement` is never anything
4
- // else), inside the view's own body. It used to live in a `.viewlayout`
5
- // companion beside the file, which the compiler, review and the pinned build
6
- // could not see.
4
+ // else), inside the view's own body. That way the compiler, review and a pinned
5
+ // build can all see it.
7
6
  //
8
7
  // Flat on purpose. Each box, port, connector route and note is one metadata
9
8
  // usage with primitive values, because a metadata body can redefine an
@@ -64,6 +63,9 @@ package memo_viewpoints_definitions_layout {
64
63
  attribute layoutContractVersion : String[0..1];
65
64
  attribute layoutPreset : String[0..1];
66
65
  attribute layoutSeed : Real[0..1];
66
+ /** How this view's connectors are drawn, and whether they follow the router or a person. */
67
+ attribute routingType : String[0..1];
68
+ attribute routingMode : String[0..1];
67
69
  }
68
70
 
69
71
  /** Renderer namespaces and forward-compatible presentation fields only.
@@ -108,6 +110,9 @@ package memo_viewpoints_definitions_layout {
108
110
  attribute y : Real;
109
111
  attribute side : MemoLayoutSide[0..1];
110
112
  attribute size : Real[0..1];
113
+ /** A port nested in a port: how far along its parent, and whether it faces out. */
114
+ attribute alongOffset : Real[0..1];
115
+ attribute faceOuter : Boolean[0..1];
111
116
  }
112
117
 
113
118
  /**
@@ -132,7 +137,7 @@ package memo_viewpoints_definitions_layout {
132
137
  attribute strokeWidth : Real[0..1];
133
138
  attribute labelVisible : Boolean[0..1];
134
139
  attribute lineStyle : MemoLayoutLineStyle[0..1];
135
- attribute route : Real[0..*] ordered;
140
+ attribute route : Real[0..*] ordered nonunique;
136
141
  /** A short token for the connector's ends, so a route is kept only while it still joins what it was drawn between. */
137
142
  attribute attachment : String[0..1];
138
143
  attribute sourceElement : String[0..1];
@@ -144,6 +149,23 @@ package memo_viewpoints_definitions_layout {
144
149
  attribute sourceT : Real[0..1];
145
150
  attribute targetSide : MemoLayoutSide[0..1];
146
151
  attribute targetT : Real[0..1];
152
+ /**
153
+ * False when the router computed `route`, so the next routing may replace it.
154
+ * A route is stored because routing a whole board on every open is too slow.
155
+ */
156
+ attribute manualRoute : Boolean[0..1];
157
+ attribute routingType : String[0..1];
158
+ attribute routingOverride : String[0..1];
159
+ /** Where the connector's label sits, on the board. */
160
+ attribute labelX : Real[0..1];
161
+ attribute labelY : Real[0..1];
162
+ /** Where each end leaves its box, relative to the box, and on which wall. */
163
+ attribute sourceOffsetX : Real[0..1];
164
+ attribute sourceOffsetY : Real[0..1];
165
+ attribute sourceOffsetSide : MemoLayoutSide[0..1];
166
+ attribute targetOffsetX : Real[0..1];
167
+ attribute targetOffsetY : Real[0..1];
168
+ attribute targetOffsetSide : MemoLayoutSide[0..1];
147
169
  }
148
170
 
149
171
  /** A note, text label or constraint box that belongs to the drawing and not to the model. */