@memoarchitect/ontology 0.16.0 → 0.16.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/examples/connected-patient-monitor/memo.identity.yaml +16 -1
- package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +5 -1
- package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/connected-patient-monitor/model/catalog/viewpoints/{unassigned → logical}/views/connected_patient_monitor_overview.sysml +3 -2
- package/examples/connected-patient-monitor/model/methodology/project.sysml +1 -2
- package/examples/embedded-infusion-pump/memo.identity.yaml +79 -0
- package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +131 -4
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/{unassigned → logical}/views/embedded_infusion_pump_overview.sysml +3 -2
- package/examples/embedded-infusion-pump/model/methodology/project.sysml +1 -2
- package/examples/functional-logical-physical/memo.identity.yaml +31 -1
- package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +71 -0
- package/examples/functional-logical-physical/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/functional-logical-physical/model/catalog/viewpoints/{unassigned → logical}/views/functional_logical_physical_overview.sysml +3 -2
- package/examples/functional-logical-physical/model/methodology/project.sysml +1 -2
- package/examples/gpca-pump/memo.identity.yaml +53 -13
- package/examples/gpca-pump/methodology/gpca_profiles.sysml +4 -15
- package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +23 -10
- package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +7 -6
- package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +74 -28
- package/examples/gpca-pump/model/catalog/gpca_devices.sysml +23 -0
- package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +11 -29
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +17 -0
- package/examples/gpca-pump/model/catalog/gpca_physical.sysml +2 -1
- package/examples/gpca-pump/model/catalog/gpca_standards.sysml +4 -4
- package/examples/gpca-pump/model/catalog/gpca_system.sysml +4 -3
- package/examples/gpca-pump/model/catalog/gpca_trace.sysml +11 -3
- package/examples/gpca-pump/model/catalog/gpca_verification.sysml +12 -12
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +1 -1
- package/examples/{ros-mobile-robot/model/catalog/viewpoints/unassigned → gpca-pump/model/catalog/viewpoints/shared}/viewpoint.sysml +3 -2
- package/examples/gpca-pump/model/catalog/viewpoints/{logical → shared}/views/document_architecture_description_view.sysml +3 -3
- package/examples/gpca-pump/model/catalog/viewpoints/{requirements → shared}/views/document_dhf_index_view.sysml +3 -3
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +1 -1
- package/examples/gpca-pump/model/methodology/project.sysml +1 -5
- package/examples/ivd-laboratory-system/memo.identity.yaml +43 -0
- package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +16 -1
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/{unassigned → logical}/views/ivd_laboratory_system_overview.sysml +3 -2
- package/examples/ivd-laboratory-system/model/methodology/project.sysml +1 -2
- package/examples/manual-surgical-instrument/memo.identity.yaml +28 -0
- package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -0
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/{unassigned → logical}/views/manual_surgical_instrument_overview.sysml +3 -2
- package/examples/manual-surgical-instrument/model/methodology/project.sysml +1 -2
- package/examples/multidimensional-layers/memo.identity.yaml +34 -0
- package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +34 -4
- package/examples/multidimensional-layers/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/multidimensional-layers/model/catalog/viewpoints/{unassigned → logical}/views/multidimensional_layers_overview.sysml +3 -1
- package/examples/multidimensional-layers/model/methodology/project.sysml +1 -2
- package/examples/nested-architecture-dsm/memo.identity.yaml +27 -0
- package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +9 -9
- package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +64 -0
- package/examples/nested-architecture-dsm/model/catalog/nested_architecture_dsm_system.sysml +5 -0
- package/examples/nested-architecture-dsm/model/catalog/traces.sysml +6 -0
- package/examples/reusable-instrument/memo.identity.yaml +46 -0
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +28 -0
- package/examples/reusable-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/reusable-instrument/model/catalog/viewpoints/{unassigned → logical}/views/reusable_instrument_overview.sysml +3 -1
- package/examples/reusable-instrument/model/methodology/project.sysml +1 -2
- package/examples/robot-cell-family/memo.identity.yaml +96 -81
- package/examples/robot-cell-family/model/{sos → catalog/sos}/chains.sysml +5 -5
- package/examples/robot-cell-family/model/{sos → catalog/sos}/icds.sysml +1 -1
- package/examples/robot-cell-family/model/{sos → catalog/sos}/sos.sysml +4 -4
- package/examples/robot-cell-family/model/{sos → catalog/sos}/use_cases.sysml +4 -4
- package/examples/robot-cell-family/model/{systems → catalog/systems}/manipulation/manipulation_system.sysml +11 -3
- package/examples/robot-cell-family/model/{systems → catalog/systems}/navigation/navigation_system.sysml +9 -4
- package/examples/robot-cell-family/model/{systems → catalog/systems}/perception/perception_system.sysml +8 -3
- package/examples/robot-cell-family/model/methodology/project.sysml +6 -6
- package/examples/ros-mobile-robot/memo.identity.yaml +22 -1
- package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +89 -26
- package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/ros-mobile-robot/model/catalog/viewpoints/{unassigned → logical}/views/ros_mobile_robot_overview.sysml +3 -1
- package/examples/ros-mobile-robot/model/methodology/project.sysml +1 -2
- package/examples/software-only-medical-device/memo.identity.yaml +46 -0
- package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +34 -1
- package/examples/software-only-medical-device/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/software-only-medical-device/model/catalog/viewpoints/{unassigned → logical}/views/software_only_medical_device_overview.sysml +3 -1
- package/examples/software-only-medical-device/model/methodology/project.sysml +1 -2
- package/examples/surgical-closure-workflow/memo.identity.yaml +103 -0
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +28 -0
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/{unassigned → logical}/views/surgical_closure_workflow_overview.sysml +3 -1
- package/examples/surgical-closure-workflow/model/methodology/project.sysml +1 -2
- package/examples/surgical-robot/memo.identity.yaml +40 -0
- package/examples/surgical-robot/model/catalog/surgical_robot.sysml +6 -1
- package/examples/surgical-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/surgical-robot/model/catalog/viewpoints/{unassigned → logical}/views/surgical_robot_overview.sysml +3 -1
- package/examples/surgical-robot/model/methodology/project.sysml +1 -2
- package/examples/sysml-diagram-samples/README.md +5 -3
- package/examples/sysml-diagram-samples/memo.identity.yaml +548 -391
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/action_flow_view.sysml +2 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/browser_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/context_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/drill_down_view.sysml +30 -5
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/functional_flow_view.sysml +15 -3
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/grid_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/interconnection_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/operational_behaviour_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/package_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/requirements_view.sysml +7 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/sequence_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/standard_activity_view.sysml +2 -3
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/state_transition_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/tree_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/use_case_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/sysml_diagram_samples_system.sysml +5 -0
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/viewpoint.sysml +8 -0
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/{unassigned → shared}/views/diagram_samples.sysml +78 -44
- package/examples/sysml-diagram-samples/model/methodology/project.sysml +0 -16
- package/examples/temperature-alarm/memo.identity.yaml +22 -1
- package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +48 -0
- package/examples/temperature-alarm/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/temperature-alarm/model/catalog/viewpoints/{unassigned → logical}/views/temperature_alarm_overview.sysml +3 -1
- package/examples/temperature-alarm/model/methodology/project.sysml +1 -2
- package/examples/ui-screen-regions/memo.identity.yaml +33 -0
- package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +3 -0
- package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +2 -1
- package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +60 -0
- package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +3 -3
- package/examples/ui-screen-regions/model/catalog/ui_screen_regions_system.sysml +5 -0
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +2 -1
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +2 -1
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/messaging/src/messaging_extension.sysml +2 -1
- package/extensions/ros/memo.package.yaml +1 -1
- package/extensions/ros/src/ros_extension.sysml +3 -2
- package/methodologies/default/memo.package.yaml +1 -1
- package/methodologies/gpca/memo.package.yaml +1 -1
- package/ontology/memo.package.yaml +1 -1
- package/package.json +4 -4
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/behavior/memo_behavior.sysml +19 -8
- package/src/architecture/functional/constraints/memo_constraints.sysml +5 -4
- package/src/architecture/functional/functions/memo_functions.sysml +18 -6
- package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +2 -3
- package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +5 -4
- package/src/architecture/implementation/software/structure/memo_software_structure.sysml +0 -1
- package/src/architecture/implementation/ui/memo_ui.sysml +16 -0
- package/src/architecture/logical/interfaces/memo_interfaces.sysml +9 -3
- package/src/architecture/logical/structure/memo_logical_structure.sysml +9 -0
- package/src/architecture/operational/activities/memo_activities.sysml +3 -2
- package/src/architecture/operational/scenarios/memo_scenarios.sysml +6 -1
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +0 -4
- package/src/architecture/realization/deployment/memo_deployment.sysml +3 -2
- package/src/architecture/realization/physical/memo_physical_architecture.sysml +11 -4
- package/src/artifacts/configuration_management/memo_configuration_management.sysml +17 -4
- package/src/artifacts/templates/dhf/fda-cybersecurity/security-arch.md +1 -1
- package/src/artifacts/templates/dhf/fda-cybersecurity/threat-model.md +1 -1
- package/src/artifacts/templates/dhf/iec-62304/detailed-design.md +1 -1
- package/src/artifacts/templates/dhf/iec-62304/sad.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/task-analysis.md +7 -7
- package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
- package/src/artifacts/templates/dhf/system/sad.md +1 -1
- package/src/artifacts/templates/dhf/system/standards-checklist.md +2 -2
- package/src/assurance/safety_risk/memo_risk.sysml +15 -0
- package/src/assurance/verification_validation/memo_assurance.sysml +25 -0
- package/src/core/common/memo_common.sysml +22 -0
- package/src/core/enumerations/memo_enumerations.sysml +23 -5
- package/src/core/relationships/memo_relationships.sysml +5 -0
- package/src/core/relationships/memo_workspace_membership.sysml +11 -0
- package/src/core/stdlib/quantities/quantities.sysml +22 -0
- package/src/memo_namespaces.sysml +5 -0
- package/src/methodology/core/memo_core.sysml +2 -12
- package/src/methodology/profiles/memo_profiles.sysml +2 -2
- package/src/rules/closure/closure_rules.sysml +46 -3
- package/src/rules/ontology/ontology_invariants.sysml +67 -30
- package/src/rules/quantitative/quantitative_rules.sysml +29 -0
- package/src/viewpoints/clinical/clinical_viewpoint.sysml +1 -1
- package/src/viewpoints/context/context_viewpoint.sysml +1 -1
- package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +1 -1
- package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +1 -1
- package/src/viewpoints/functional/functional_viewpoint.sysml +1 -1
- package/src/viewpoints/logical/logical_viewpoint.sysml +1 -1
- package/src/viewpoints/operational/operational_viewpoint.sysml +1 -1
- package/src/viewpoints/physical/physical_viewpoint.sysml +1 -1
- package/src/viewpoints/requirements/requirements_viewpoint.sysml +1 -1
- package/src/viewpoints/risk/risk_viewpoint.sysml +1 -1
- package/src/viewpoints/software/software_viewpoint.sysml +1 -1
- package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +14 -3
- package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +1 -1
- package/src/viewpoints/usability/usability_viewpoint.sysml +1 -1
- package/src/viewpoints/verification/verification_viewpoint.sysml +1 -1
- package/stage1/opensysml-23e5a5f26f7b25370edc4f26.json.gz +0 -0
- package/stage1/syside-27179e19589cf7a97f4dd15a.ids.gz +0 -0
- package/stage1/syside-27179e19589cf7a97f4dd15a.json.gz +0 -0
- package/stage1/syside-eb527547500a60b508b4578c.ids.gz +0 -0
- package/stage1/syside-eb527547500a60b508b4578c.json.gz +0 -0
- package/examples/connected-patient-monitor/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/functional-logical-physical/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/multidimensional-layers/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/reusable-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/software-only-medical-device/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/surgical-robot/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -74
- package/examples/temperature-alarm/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- /package/examples/robot-cell-family/model/{shared → catalog/shared}/shared.sysml +0 -0
- /package/examples/sysml-diagram-samples/model/{sysml_v2_activity_example.sysml → catalog/sysml_v2_activity_example.sysml} +0 -0
|
@@ -164,18 +164,19 @@ package memo_core_enumerations {
|
|
|
164
164
|
//
|
|
165
165
|
// Track A2 removed this from PORTS: a port usage says `in` / `out` /
|
|
166
166
|
// `inout` natively, which is the language's own spelling and the only one
|
|
167
|
-
// a conforming tool reads. The enum survives because
|
|
167
|
+
// a conforming tool reads. The enum survives because three non-port
|
|
168
168
|
// constructs still carry a direction and none of them is a port, so none
|
|
169
169
|
// of them can use the keyword:
|
|
170
170
|
//
|
|
171
171
|
// Interface.direction / .directionality (interface def)
|
|
172
172
|
// LogicalConnector.direction (connection def)
|
|
173
|
-
// ComponentExchange.direction (interface def)
|
|
174
173
|
// OperationalInteraction.direction (part def)
|
|
175
174
|
//
|
|
176
|
-
// Deleting it would have cost those
|
|
177
|
-
// was only ever the port case. `LogicalExchange.direction` was a
|
|
178
|
-
// went when the exchange became a flow between ports (2026-09-25)
|
|
175
|
+
// Deleting it would have cost those three their direction; the reinvention
|
|
176
|
+
// was only ever the port case. `LogicalExchange.direction` was a fourth and
|
|
177
|
+
// went when the exchange became a flow between ports (2026-09-25), and
|
|
178
|
+
// `ComponentExchange.direction` a fifth when the ports at its ends were held to
|
|
179
|
+
// say it (2026-10-25, rule AR-EXCH-002).
|
|
179
180
|
enum def DirectionKind {
|
|
180
181
|
enum input;
|
|
181
182
|
enum output;
|
|
@@ -206,6 +207,23 @@ package memo_core_enumerations {
|
|
|
206
207
|
enum maintenance;
|
|
207
208
|
enum obsolete;
|
|
208
209
|
}
|
|
210
|
+
// How much of the product a test exercises, and where it is carried out: the protocol of a
|
|
211
|
+
// verification case (FDA's recommended performance-testing information), not a record of a run.
|
|
212
|
+
enum def TestLevelKind {
|
|
213
|
+
enum unit;
|
|
214
|
+
enum integration;
|
|
215
|
+
enum subassembly;
|
|
216
|
+
enum system;
|
|
217
|
+
enum systemWithAccessories;
|
|
218
|
+
}
|
|
219
|
+
enum def TestEnvironmentKind {
|
|
220
|
+
enum bench;
|
|
221
|
+
enum inSilico;
|
|
222
|
+
enum exVivo;
|
|
223
|
+
enum cadaver;
|
|
224
|
+
enum animal;
|
|
225
|
+
enum clinical;
|
|
226
|
+
}
|
|
209
227
|
enum def MemoVerificationMethodKind {
|
|
210
228
|
enum inspection;
|
|
211
229
|
enum analytical;
|
|
@@ -65,6 +65,11 @@ package memo_core_relationships {
|
|
|
65
65
|
* pair of elements — KerML Feature::isUnique over the relation.
|
|
66
66
|
* Unset is read as true. */
|
|
67
67
|
attribute isUnique : Boolean;
|
|
68
|
+
doc /* True when this relation is a connector between two parts, the kind of link that makes a part
|
|
69
|
+
* count as wired in an internal block diagram (rule AR-IBD-001). Trace, allocation, deployment and
|
|
70
|
+
* satisfaction links are not. Unset is read as false. Interface and flow usages are connectors by
|
|
71
|
+
* their language construct and need no value. */
|
|
72
|
+
attribute isConnector : Boolean;
|
|
68
73
|
}
|
|
69
74
|
|
|
70
75
|
// ─── Typed dependencies ─────────────────────────────────────────────
|
|
@@ -110,6 +110,8 @@ package memo_core_relationships_workspace_membership {
|
|
|
110
110
|
part membershipRealizedByScenario : WorkspaceMembershipEntry { attribute :>> relation = "realizedByScenario"; attribute :>> direction = WorkspaceMembershipKind::targetFollowsSource; }
|
|
111
111
|
// Neither: a cyber element and a safety item are each placed on their own.
|
|
112
112
|
part membershipImpactsSafety : WorkspaceMembershipEntry { attribute :>> relation = "impactsSafety"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
113
|
+
// Neither: a benefit and the risk it is weighed against are each placed on their own.
|
|
114
|
+
part membershipWeighedAgainst : WorkspaceMembershipEntry { attribute :>> relation = "weighedAgainst"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
113
115
|
// A security property follows its asset.
|
|
114
116
|
part membershipHasSecurityProperty : WorkspaceMembershipEntry { attribute :>> relation = "hasSecurityProperty"; attribute :>> direction = WorkspaceMembershipKind::targetFollowsSource; }
|
|
115
117
|
// An attack surface follows the asset it exposes.
|
|
@@ -213,6 +215,10 @@ package memo_core_relationships_workspace_membership {
|
|
|
213
215
|
// Neither: a chain that performs functions of three systems belongs to none of them. Decided 2026-10-14:
|
|
214
216
|
// a chain step is the system of systems' own, so `performs` places nothing in a system.
|
|
215
217
|
part membershipPerforms : WorkspaceMembershipEntry { attribute :>> relation = "performs"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
218
|
+
// Neither: a step subsets the function it carries out; the function is not placed by it, as `performs` places nothing.
|
|
219
|
+
part membershipSubsets : WorkspaceMembershipEntry { attribute :>> relation = "subsets"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
220
|
+
// Neither: navigation joins two screens; the screen it opens is not placed by the element that opens it.
|
|
221
|
+
part membershipNavigatesTo : WorkspaceMembershipEntry { attribute :>> relation = "navigatesTo"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
216
222
|
// Neither: a use case that includes others belongs to the system of systems; pulling it would put it in every system it includes.
|
|
217
223
|
part membershipIncludesStep : WorkspaceMembershipEntry { attribute :>> relation = "includesStep"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
218
224
|
// Neither: a bare dependency says nothing about placement.
|
|
@@ -275,6 +281,11 @@ package memo_core_relationships_workspace_membership {
|
|
|
275
281
|
// A device follows the releases it covers, and they follow their items: a device that covers releases of
|
|
276
282
|
// two systems is shared, and one that covers none is Unassigned (an approval for nothing).
|
|
277
283
|
part membershipCovers : WorkspaceMembershipEntry { attribute :>> relation = "covers"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
|
|
284
|
+
// An intended use follows the device it states the purpose of: it is in whichever workspace the device is.
|
|
285
|
+
part membershipIntendedUseOf : WorkspaceMembershipEntry { attribute :>> relation = "intendedUseOf"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
|
|
286
|
+
// Two devices used together are peers; neither places the other (a pump and its infusion set may be approved
|
|
287
|
+
// for different systems).
|
|
288
|
+
part membershipUsedWith : WorkspaceMembershipEntry { attribute :>> relation = "usedWith"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
278
289
|
|
|
279
290
|
// Neither: a step is not placed by the rule that says when it is done.
|
|
280
291
|
part membershipDoneWhen : WorkspaceMembershipEntry { attribute :>> relation = "doneWhen"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
// Re-export-only wrapper. No new types.
|
|
2
|
+
//
|
|
3
|
+
// The quantity value types (`DurationValue`, `FrequencyValue`, `StorageCapacityValue`, …), the SI units (`s`, `Hz`,
|
|
4
|
+
// `V`, `A`, `B`) and the prefixes (`milli`, `mega`, `kibi`) a measurable attribute is typed and written with.
|
|
5
|
+
//
|
|
6
|
+
// A range on a parameter or an attribute is a constraint on its TYPE, so every use of the type
|
|
7
|
+
// carries it:
|
|
8
|
+
//
|
|
9
|
+
// attribute def DoseMass :> MassValue {
|
|
10
|
+
// assert constraint { self >= 0 [kg] and self <= 5 [kg] }
|
|
11
|
+
// }
|
|
12
|
+
// action def DeliverDose { in amount : DoseMass; }
|
|
13
|
+
//
|
|
14
|
+
// The builder emits that constraint as an element owned by the type, with its expression and unit, so
|
|
15
|
+
// it is found with `where: owner == "<the type's qualified id>"`. No kind for a range exists.
|
|
16
|
+
package memo_core_stdlib_quantities {
|
|
17
|
+
private import ScalarValues::*;
|
|
18
|
+
|
|
19
|
+
public import ISQ::*;
|
|
20
|
+
public import SI::*;
|
|
21
|
+
public import SIPrefixes::*;
|
|
22
|
+
}
|
|
@@ -455,6 +455,7 @@ package memo_namespace_core_stdlib {
|
|
|
455
455
|
alias collections for memo_namespace_core_stdlib_collections;
|
|
456
456
|
alias functions for memo_namespace_core_stdlib_functions;
|
|
457
457
|
alias scalars for memo_namespace_core_stdlib_scalars;
|
|
458
|
+
alias quantities for memo_namespace_core_stdlib_quantities;
|
|
458
459
|
alias time for memo_namespace_core_stdlib_time;
|
|
459
460
|
}
|
|
460
461
|
|
|
@@ -609,6 +610,10 @@ package memo_namespace_core_stdlib_scalars {
|
|
|
609
610
|
public import memo_core_stdlib_scalars::*;
|
|
610
611
|
}
|
|
611
612
|
|
|
613
|
+
package memo_namespace_core_stdlib_quantities {
|
|
614
|
+
public import memo_core_stdlib_quantities::*;
|
|
615
|
+
}
|
|
616
|
+
|
|
612
617
|
package memo_namespace_core_stdlib_time {
|
|
613
618
|
public import memo_core_stdlib_time::*;
|
|
614
619
|
}
|
|
@@ -126,18 +126,8 @@ package memo_methodology_core {
|
|
|
126
126
|
// this binding (`public import memo_extension_ros::*;`), the same way
|
|
127
127
|
// a methodology selects them. There is no list to keep beside it.
|
|
128
128
|
attribute scopeMode : ScopeModeKind;
|
|
129
|
-
// The
|
|
130
|
-
//
|
|
131
|
-
// `memo standards check`, the standards checklist, the Architect gap
|
|
132
|
-
// badges — reads this, so the regime axis is a model fact stated in
|
|
133
|
-
// SysML rather than a per-document array maintained in 44 places.
|
|
134
|
-
// Empty means the model has not declared its regimes; a report that
|
|
135
|
-
// needs them says so rather than assuming a default market.
|
|
136
|
-
//
|
|
137
|
-
// DEPRECATED in 0.14.0 (plan O1, O6): a `RegulatedDevice` states its own
|
|
138
|
-
// jurisdiction, one approval each. This is read only when the model declares
|
|
139
|
-
// no device, and ignored with a warning when it declares both.
|
|
140
|
-
attribute regulatoryRegime : RegulatoryRegimeKind[0..*];
|
|
129
|
+
// The approvals this model targets are `RegulatedDevice` parts (one jurisdiction each), not a setting here:
|
|
130
|
+
// `memo standards check`, the standards checklist and the Architect gap badges read their jurisdictions.
|
|
141
131
|
part rulePolicy : RulePolicy[0..*];
|
|
142
132
|
}
|
|
143
133
|
|
|
@@ -16,7 +16,7 @@ package memo_methodology_profiles {
|
|
|
16
16
|
private import memo_core_common::MemoIdentity;
|
|
17
17
|
part mdCoreLibrary : MethodologyLibrary {
|
|
18
18
|
@MemoIdentity { :>> providedId = "METHLIB-001"; :>> label = "MedicalDeviceMethodologyLibrary"; }
|
|
19
|
-
attribute :>> version = "0.16.
|
|
19
|
+
attribute :>> version = "0.16.2";
|
|
20
20
|
attribute :>> domain = "medical device modeling";
|
|
21
21
|
doc /* Methodology layer for selecting, restricting, sequencing, tailoring, and lightly extending use of the medical-device ontology. */
|
|
22
22
|
}
|
|
@@ -37,7 +37,7 @@ package memo_methodology_profiles {
|
|
|
37
37
|
// second scope authority.
|
|
38
38
|
part mdDefaultDefinition : MethodologyDefinition {
|
|
39
39
|
@MemoIdentity { :>> providedId = "METH-MD-DEFAULT"; :>> label = "MedicalDeviceDefault"; }
|
|
40
|
-
attribute :>> version = "0.16.
|
|
40
|
+
attribute :>> version = "0.16.2";
|
|
41
41
|
attribute :>> domain = "medical device modeling";
|
|
42
42
|
doc /* MEMO default medical-device methodology. Selects every layer, discipline, standard, artifact kind, and viewpoint the resolved ontology and extension packages provide. */
|
|
43
43
|
attribute :>> scopeMode = ScopeModeKind::allAvailable;
|
|
@@ -140,8 +140,8 @@ package memo_rules_closure {
|
|
|
140
140
|
attribute obligation = RuleObligationKind::recommended;
|
|
141
141
|
attribute appliesTo = "SystemFunction";
|
|
142
142
|
attribute severity = RuleSeverityKind::warning;
|
|
143
|
-
attribute rationaleText = "Functions should be allocated to implementation elements.";
|
|
144
|
-
attribute predicateExpression = "allocatedTo->size() >= 1";
|
|
143
|
+
attribute rationaleText = "Functions should be allocated to implementation elements. A function definition is a type and is not allocated; its usages are.";
|
|
144
|
+
attribute predicateExpression = "isDefinition == 'true' or allocatedTo->size() >= 1";
|
|
145
145
|
constraint { true }
|
|
146
146
|
}
|
|
147
147
|
|
|
@@ -169,7 +169,7 @@ package memo_rules_closure {
|
|
|
169
169
|
// function is what triggers it. Without it the rule reported gpca-pump's
|
|
170
170
|
// startup chain's own two steps, and ui-screen-regions' two functions
|
|
171
171
|
// that a control invokes, as reached by nothing.
|
|
172
|
-
attribute predicateExpression = "flow->size() >= 1 or succession->size() >= 1 or downstream(composes)->size() >= 1 or upstream(performs)->size() >= 1";
|
|
172
|
+
attribute predicateExpression = "isDefinition == 'true' or flow->size() >= 1 or succession->size() >= 1 or downstream(composes)->size() >= 1 or upstream(performs)->size() >= 1";
|
|
173
173
|
constraint { true }
|
|
174
174
|
}
|
|
175
175
|
|
|
@@ -442,6 +442,49 @@ package memo_rules_closure {
|
|
|
442
442
|
}
|
|
443
443
|
#EnforcesClause dependency from ResidualRiskEvaluatedRule to iso14971::iso14971Clause8;
|
|
444
444
|
|
|
445
|
+
// ISO 14971 clauses 5.2, 5.3 and 7.4 on the links the model already has: a misuse is not an item of the risk
|
|
446
|
+
// chain, so it reaches the chain by `causes` (the risk can start at any element: an operational flow, an
|
|
447
|
+
// FMEA row, a use error, a misuse); a safety-related characteristic reaches a hazard by `impactsSafety`; a
|
|
448
|
+
// benefit is weighed against a risk by `weighedAgainst`.
|
|
449
|
+
constraint def MisuseReachesSituationRule :> MemoConsistencyRule {
|
|
450
|
+
@MemoIdentity { :>> providedId = "CR-MED-027"; }
|
|
451
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
452
|
+
attribute domain = RuleDomainKind::medicalDevice;
|
|
453
|
+
attribute obligation = RuleObligationKind::required;
|
|
454
|
+
attribute appliesTo = "ReasonablyForeseeableMisuse";
|
|
455
|
+
attribute severity = RuleSeverityKind::warning;
|
|
456
|
+
attribute rationaleText = "Reasonably foreseeable misuse is an input to the risk analysis: a misuse that leads to no hazardous situation has not been analysed, and one that is not recorded as leading anywhere cannot be shown to have been considered.";
|
|
457
|
+
attribute predicateExpression = "downstream(causes)->exists(conformsTo(HazardousSituation) or downstream(tracesRisk)->exists(conformsTo(HazardousSituation)))";
|
|
458
|
+
constraint { true }
|
|
459
|
+
}
|
|
460
|
+
#EnforcesClause dependency from MisuseReachesSituationRule to iso14971::iso14971Clause5::iso14971Clause5_2;
|
|
461
|
+
|
|
462
|
+
constraint def CharacteristicReachesHazardRule :> MemoConsistencyRule {
|
|
463
|
+
@MemoIdentity { :>> providedId = "CR-MED-028"; }
|
|
464
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
465
|
+
attribute domain = RuleDomainKind::medicalDevice;
|
|
466
|
+
attribute obligation = RuleObligationKind::required;
|
|
467
|
+
attribute appliesTo = "SafetyRelatedCharacteristic";
|
|
468
|
+
attribute severity = RuleSeverityKind::warning;
|
|
469
|
+
attribute rationaleText = "A characteristic that could affect safety is identified so that the hazards it bears on are analysed: one linked to no hazard has been identified and then left unused.";
|
|
470
|
+
attribute predicateExpression = "downstream(impactsSafety)->exists(conformsTo(RiskItem))";
|
|
471
|
+
constraint { true }
|
|
472
|
+
}
|
|
473
|
+
#EnforcesClause dependency from CharacteristicReachesHazardRule to iso14971::iso14971Clause5::iso14971Clause5_3;
|
|
474
|
+
|
|
475
|
+
constraint def BenefitRiskWeighedRule :> MemoConsistencyRule {
|
|
476
|
+
@MemoIdentity { :>> providedId = "CR-MED-029"; }
|
|
477
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
478
|
+
attribute domain = RuleDomainKind::medicalDevice;
|
|
479
|
+
attribute obligation = RuleObligationKind::required;
|
|
480
|
+
attribute appliesTo = "ResidualRisk";
|
|
481
|
+
attribute severity = RuleSeverityKind::warning;
|
|
482
|
+
attribute rationaleText = "Where a residual risk calls for a benefit-risk analysis, the benefit it is weighed against is stated.";
|
|
483
|
+
attribute predicateExpression = "attributes.benefitRiskRequired != 'true' or upstream(weighedAgainst)->exists(conformsTo(Benefit))";
|
|
484
|
+
constraint { true }
|
|
485
|
+
}
|
|
486
|
+
#EnforcesClause dependency from BenefitRiskWeighedRule to iso14971::iso14971Clause7::iso14971Clause7_4;
|
|
487
|
+
|
|
445
488
|
constraint def SoupAnomaliesRule :> MemoConsistencyRule {
|
|
446
489
|
@MemoIdentity { :>> providedId = "CR-MED-015"; }
|
|
447
490
|
attribute tailoring = RuleTailoringKind::assurance;
|
|
@@ -58,34 +58,6 @@ package memo_rules_ontology {
|
|
|
58
58
|
attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(SystemOfSystems))) or downstream(includesStep)->exists(downstream(hasSubject)->exists(conformsTo(System)))";
|
|
59
59
|
constraint { true }
|
|
60
60
|
}
|
|
61
|
-
constraint def SystemUseCaseIncludedRule :> MemoConsistencyRule {
|
|
62
|
-
@MemoIdentity { :>> providedId = "CR-ONT-086"; }
|
|
63
|
-
attribute tailoring = RuleTailoringKind::methodology;
|
|
64
|
-
attribute domain = RuleDomainKind::modelling;
|
|
65
|
-
attribute obligation = RuleObligationKind::recommended;
|
|
66
|
-
attribute appliesTo = "UseCase";
|
|
67
|
-
attribute severity = RuleSeverityKind::warning;
|
|
68
|
-
attribute rationaleText = "A use case whose subject is a system is included by a use case of the system of systems, or says it stands alone (standalone = true).";
|
|
69
|
-
attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(System))) or upstream(includesStep)->size() >= 1 or attributes.standalone == 'true'";
|
|
70
|
-
constraint { true }
|
|
71
|
-
}
|
|
72
|
-
// A system is a boundary (plan O16). The workspace closure never reaches another system or the
|
|
73
|
-
// system of systems, and drops such a link silently; this rule reports it. Evaluated by the
|
|
74
|
-
// workspace evaluator because it needs what each workspace holds, which no predicate can say:
|
|
75
|
-
// the subject is the element inside a system that is typed by, or relates to, a System-kind or
|
|
76
|
-
// SystemOfSystems-kind element outside it. The system of systems' own references to its systems
|
|
77
|
-
// are what it is for and are not findings.
|
|
78
|
-
constraint def SystemBoundaryRule :> MemoConsistencyRule {
|
|
79
|
-
@MemoIdentity { :>> providedId = "CR-ONT-087"; }
|
|
80
|
-
attribute tailoring = RuleTailoringKind::methodology;
|
|
81
|
-
attribute domain = RuleDomainKind::modelling;
|
|
82
|
-
attribute obligation = RuleObligationKind::recommended;
|
|
83
|
-
attribute evaluator = "workspace";
|
|
84
|
-
attribute appliesTo = "Model";
|
|
85
|
-
attribute severity = RuleSeverityKind::warning;
|
|
86
|
-
attribute rationaleText = "A system does not reference another system or the system of systems from inside itself. Two systems meet at an interface the system of systems owns.";
|
|
87
|
-
constraint { true }
|
|
88
|
-
}
|
|
89
61
|
// ─── Release selections (plan O14) ────────────────────────────────────
|
|
90
62
|
//
|
|
91
63
|
// A release record selects features (`#SelectsFeature`), and through them the variants that realize
|
|
@@ -169,6 +141,39 @@ package memo_rules_ontology {
|
|
|
169
141
|
// represent that transitive containment query.
|
|
170
142
|
constraint { true }
|
|
171
143
|
}
|
|
144
|
+
|
|
145
|
+
// ─── Direction is written on the ports, and an exchange has to agree with them ──
|
|
146
|
+
//
|
|
147
|
+
// A port says `in` or `out` (or `inout`), and a `~` conjugates it. That is the only place direction is
|
|
148
|
+
// written: an exchange's own direction was the same fact a second time, and nothing checked the two
|
|
149
|
+
// agreed. These two rules check the exchange against its ports, so a contradiction cannot be written.
|
|
150
|
+
// Both judge only ends that are ports with a stated direction; a port that says none is not judged.
|
|
151
|
+
constraint def BindingEndsAgreeInDirectionRule :> MemoConsistencyRule {
|
|
152
|
+
@MemoIdentity { :>> providedId = "AR-EXCH-001"; }
|
|
153
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
154
|
+
attribute domain = RuleDomainKind::modelling;
|
|
155
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
156
|
+
attribute appliesTo = "MemoPort";
|
|
157
|
+
attribute evaluator = "architecture";
|
|
158
|
+
attribute severity = RuleSeverityKind::error;
|
|
159
|
+
attribute rationaleText = "A binding makes its two ports one connection point, so they have the direction between them: a boundary port bound to a port of a nested part passes the same direction through. A binding of an in port to an out port joins things that cannot be the same point.";
|
|
160
|
+
attribute predicateExpression = "bindEndsAgreeInDirection";
|
|
161
|
+
// The generic expression evaluator reads a port's attributes, not its stated direction and
|
|
162
|
+
// conjugation, so a function computes the predicate (as for AR-IBD-001).
|
|
163
|
+
constraint { true }
|
|
164
|
+
}
|
|
165
|
+
constraint def ExchangeLeavesOutEntersInRule :> MemoConsistencyRule {
|
|
166
|
+
@MemoIdentity { :>> providedId = "AR-EXCH-002"; }
|
|
167
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
168
|
+
attribute domain = RuleDomainKind::modelling;
|
|
169
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
170
|
+
attribute appliesTo = "MemoPort";
|
|
171
|
+
attribute evaluator = "architecture";
|
|
172
|
+
attribute severity = RuleSeverityKind::error;
|
|
173
|
+
attribute rationaleText = "An interface or a flow between two ports carries its content from the one to the other, so it leaves a port that sends (out or inout) and enters one that receives (in or inout). An exchange that leaves an in port or enters an out port contradicts the ports it joins.";
|
|
174
|
+
attribute predicateExpression = "exchangeLeavesOutEntersIn";
|
|
175
|
+
constraint { true }
|
|
176
|
+
}
|
|
172
177
|
// ─── Deployment and realization ──────────────────────────────────────
|
|
173
178
|
|
|
174
179
|
constraint def RuntimeTracesToModuleRule :> MemoConsistencyRule {
|
|
@@ -209,6 +214,22 @@ package memo_rules_ontology {
|
|
|
209
214
|
constraint { true }
|
|
210
215
|
}
|
|
211
216
|
#EnforcesClause dependency from SafetyCriticalFunctionVerifiedRule to iso13485::iso13485Clause7::iso13485Clause7_3::iso13485Clause7_3_6;
|
|
217
|
+
// A flow's step is its own position of a function (`action step :> fn;`), and evidence is scoped to
|
|
218
|
+
// the position: a test of the function, or of another step, does not count for it. So a step whose
|
|
219
|
+
// function is safety-critical needs a verification case of its own. The step reaches its function
|
|
220
|
+
// through the `subsets` edge.
|
|
221
|
+
constraint def SafetyCriticalStepVerifiedRule :> MemoConsistencyRule {
|
|
222
|
+
@MemoIdentity { :>> providedId = "CR-ONT-091"; }
|
|
223
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
224
|
+
attribute domain = RuleDomainKind::medicalDevice;
|
|
225
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
226
|
+
attribute appliesTo = "ActionUsage";
|
|
227
|
+
attribute severity = RuleSeverityKind::warning;
|
|
228
|
+
attribute rationaleText = "A step of a flow whose function is safety-critical (criticality high or catastrophic) must trace to a verification case of its own; a test of the function or of another step does not cover it.";
|
|
229
|
+
attribute predicateExpression = "not(downstream(subsets)->exists(criticality == 'high' or criticality == 'catastrophic')) or verifiedBy->size() >= 1";
|
|
230
|
+
constraint { true }
|
|
231
|
+
}
|
|
232
|
+
#EnforcesClause dependency from SafetyCriticalStepVerifiedRule to iso13485::iso13485Clause7::iso13485Clause7_3::iso13485Clause7_3_6;
|
|
212
233
|
constraint def CriticalTaskValidatedRule :> MemoConsistencyRule {
|
|
213
234
|
@MemoIdentity { :>> providedId = "CR-ONT-041"; }
|
|
214
235
|
attribute tailoring = RuleTailoringKind::assurance;
|
|
@@ -373,7 +394,7 @@ package memo_rules_ontology {
|
|
|
373
394
|
attribute appliesTo = "Model";
|
|
374
395
|
attribute severity = RuleSeverityKind::error;
|
|
375
396
|
attribute rationaleText = "A performer is an operational entity, an actor, or a system action — a part or a behaviour. The end's own documentation said 'or system action' while its MemoPart type forbade one.";
|
|
376
|
-
attribute predicateExpression = "sourcesOf(performs)->forAll(conformsTo(MemoPart) or construct == 'action')";
|
|
397
|
+
attribute predicateExpression = "sourcesOf(performs)->forAll(conformsTo(MemoPart) or construct == 'action' or construct == 'verification')";
|
|
377
398
|
constraint { true }
|
|
378
399
|
}
|
|
379
400
|
constraint def BindsToInterfaceEndKindRule :> MemoConsistencyRule {
|
|
@@ -457,7 +478,7 @@ package memo_rules_ontology {
|
|
|
457
478
|
attribute appliesTo = "MemoFunction";
|
|
458
479
|
attribute severity = RuleSeverityKind::error;
|
|
459
480
|
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.";
|
|
460
|
-
attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction))";
|
|
481
|
+
attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction) or kind == 'ForkNode' or kind == 'JoinNode' or kind == 'DecisionNode' or kind == 'MergeNode')";
|
|
461
482
|
constraint { true }
|
|
462
483
|
}
|
|
463
484
|
|
|
@@ -636,4 +657,20 @@ package memo_rules_ontology {
|
|
|
636
657
|
attribute predicateExpression = "targetsOf(causes)->forAll(conformsTo(RiskItem) or conformsTo(FaultTreeNode))";
|
|
637
658
|
constraint { true }
|
|
638
659
|
}
|
|
660
|
+
|
|
661
|
+
// ─── Views and viewpoints ───────────────────────────────────────────
|
|
662
|
+
|
|
663
|
+
// ISO 42010 conformance is many-to-many, but never empty: `MemoView.viewpointDefinition` is `[1..*]`. A view
|
|
664
|
+
// that traces to a viewpoint is filed under it in Architect; one that traces to none has nowhere to be found.
|
|
665
|
+
constraint def ViewTracesToViewpointRule :> MemoConsistencyRule {
|
|
666
|
+
@MemoIdentity { :>> providedId = "CR-ONT-092"; }
|
|
667
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
668
|
+
attribute domain = RuleDomainKind::modelling;
|
|
669
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
670
|
+
attribute appliesTo = "MemoView";
|
|
671
|
+
attribute severity = RuleSeverityKind::error;
|
|
672
|
+
attribute rationaleText = "Every view traces to at least one viewpoint (ISO/IEC/IEEE 42010): the viewpoint says what the view is for and who reads it. A view with none cannot be filed under a viewpoint, so Architect lists it as uncategorised.";
|
|
673
|
+
attribute predicateExpression = "attributes.viewpointDefinition != ''";
|
|
674
|
+
constraint { true }
|
|
675
|
+
}
|
|
639
676
|
}
|
|
@@ -32,6 +32,35 @@ package memo_rules_quantitative {
|
|
|
32
32
|
constraint { true }
|
|
33
33
|
}
|
|
34
34
|
|
|
35
|
+
constraint def SoftwareComponentWcetWithinDeadlineRule :> MemoConsistencyRule {
|
|
36
|
+
@MemoIdentity { :>> providedId = "QT-004"; }
|
|
37
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
38
|
+
attribute domain = RuleDomainKind::modelling;
|
|
39
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
40
|
+
attribute appliesTo = "SoftwareComponent";
|
|
41
|
+
attribute severity = RuleSeverityKind::warning;
|
|
42
|
+
attribute rationaleText = "A component whose worst-case execution time exceeds its deadline cannot meet it. Both are durations, compared in one unit whatever each was written in.";
|
|
43
|
+
attribute predicateExpression = "attributes.wcetMs == '' or attributes.deadlineMs == '' or wcetMs <= deadlineMs";
|
|
44
|
+
constraint { true }
|
|
45
|
+
}
|
|
46
|
+
|
|
47
|
+
// The `require`, `assume` and `assert constraint`s a model declares are claims about its own values. A
|
|
48
|
+
// function evaluates them (`validator/model-constraints.ts`): names resolve from the owning element, its
|
|
49
|
+
// package, then a unique short name, and a quantity compares as a quantity. A constraint it cannot
|
|
50
|
+
// resolve is reported as not evaluated, which is information, never a pass.
|
|
51
|
+
constraint def ModelConstraintHoldsRule :> MemoConsistencyRule {
|
|
52
|
+
@MemoIdentity { :>> providedId = "MC-001"; }
|
|
53
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
54
|
+
attribute domain = RuleDomainKind::modelling;
|
|
55
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
56
|
+
attribute appliesTo = "Model";
|
|
57
|
+
attribute evaluator = "constraints";
|
|
58
|
+
attribute severity = RuleSeverityKind::error;
|
|
59
|
+
attribute rationaleText = "A constraint a model declares is a claim about its own values; one that does not hold is a defect in the model or in the claim.";
|
|
60
|
+
attribute predicateExpression = "modelConstraintsHold";
|
|
61
|
+
constraint { true }
|
|
62
|
+
}
|
|
63
|
+
|
|
35
64
|
// QT-003 (RequirementVerificationRatio, "≥80% of requirements verified") is an
|
|
36
65
|
// aggregate coverage metric over the whole requirement set, not a per-subject
|
|
37
66
|
// predicate, so it has no `constraint { … }` form. It remains a
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_clinical_clinical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows clinical context, users, use environment, and clinical evidence."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context and assurance layers for clinical stakeholders — intended use, patient/clinician interaction, clinical evidence, and clinical safety claims. */
|
|
14
14
|
attribute :>> purpose = "Communicate clinical use context and clinical evidence for the device.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (clinicalEngineer, regulatoryEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "clinical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::documentSection, ViewOutputKind::table);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_context_context_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use context, and system boundary."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context layer to communicate who interacts with the device, under which use conditions, and where trust or safety boundaries exist. */
|
|
14
14
|
attribute :>> purpose = "Communicate operational context and boundaries.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "system";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows assets, trust boundaries, threats, vulnerabilities, cyber hazards, cyber risks, and mitigations."; }
|
|
13
13
|
doc /* Default viewpoint derived from the cybersecurity layer, using STRIDE-style threat categories by default while allowing safety and privacy impacts to be traced into the broader model. */
|
|
14
14
|
attribute :>> purpose = "Communicate cybersecurity design, threat analysis, and cyber risk posture.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (securityEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::risk;
|
|
17
17
|
attribute :>> abstractionLevel = "analysis";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -37,7 +37,7 @@ package memo_viewpoints_definitions {
|
|
|
37
37
|
*/
|
|
38
38
|
// Redefines the standard library's `RequirementCheck::stakeholders`,
|
|
39
39
|
// which a viewpoint inherits through `ViewpointCheck`.
|
|
40
|
-
ref :>> stakeholders : MemoStakeholder[0..*];
|
|
40
|
+
ref memoStakeholders :>> stakeholders : MemoStakeholder[0..*];
|
|
41
41
|
attribute stage : WorkflowStageKind;
|
|
42
42
|
attribute abstractionLevel : String;
|
|
43
43
|
attribute outputKind : ViewOutputKind[*];
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_functional_functional_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows system functions, their decomposition, and allocation."; }
|
|
13
13
|
doc /* Default viewpoint derived from the functions layer for what the system does, independent of how it is structured — function trees, function allocation, and behavior triggers. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's functional decomposition and behavior.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "functional";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_logical_logical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows logical decomposition and interfaces."; }
|
|
13
13
|
doc /* Default viewpoint derived from the logical architecture layer for subsystem structure, responsibilities, and major interactions, independent of physical realization. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's logical decomposition.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "logical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_operational_operational_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use contexts, operational scenarios, and system capabilities."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context, operational, and system layers for how actors use the device — operational scenarios, capabilities, and the functional chains that realize them. */
|
|
14
14
|
attribute :>> purpose = "Communicate how actors interact with the system and which capabilities they invoke.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (projectLead, systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "operational";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_physical_physical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows physical components, hardware structure, and their interconnections."; }
|
|
13
13
|
doc /* Default viewpoint derived from the physical and hardware structure layers for bill-of-materials, hardware decomposition, physical interfaces, and network/connectivity topology. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's physical realization and interconnections.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (hardwareEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "physical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_requirements_requirements_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows stakeholder needs and their decomposition into system, software, and hardware requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the requirements layer for requirements traceability — the chain from stakeholder need through system, software, and hardware requirements, supporting IEC 62304 §5.1.1 and ISO 13485 §7.3.3. */
|
|
14
14
|
attribute :>> purpose = "Communicate requirements decomposition and traceability.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (regulatoryEngineer, systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::requirements;
|
|
17
17
|
attribute :>> abstractionLevel = "requirements";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::matrix);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_risk_risk_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows hazards, risks, controls, and assurance links."; }
|
|
13
13
|
doc /* Default viewpoint derived from the risk layer for ISO 14971-style reasoning across hazard, hazardous situation, harm, control, and verification evidence. */
|
|
14
14
|
attribute :>> purpose = "Communicate safety risk chains and controls.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::risk;
|
|
17
17
|
attribute :>> abstractionLevel = "analysis";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::table);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_software_software_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows software systems, components, SOUP, and software interfaces."; }
|
|
13
13
|
doc /* Default viewpoint derived from the software structure layer for IEC 62304 software architecture description — software item decomposition, SOUP inventory, and software-to-software interfaces, distinct from system-level logical decomposition. */
|
|
14
14
|
attribute :>> purpose = "Describe the software architecture for IEC 62304 design documentation.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (softwareArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "software";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -26,7 +26,12 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
26
26
|
// A concern is an interest in the system held by one or more stakeholders.
|
|
27
27
|
// `concern def` is the native SysML construct for it; a viewpoint frames
|
|
28
28
|
// the concerns it addresses.
|
|
29
|
-
|
|
29
|
+
//
|
|
30
|
+
// It extends the standard concern's `stakeholders` (the Parts interested in
|
|
31
|
+
// it) to the MEMO stakeholder catalog, as a viewpoint does for its own.
|
|
32
|
+
abstract concern def MemoConcern {
|
|
33
|
+
ref memoStakeholders :>> stakeholders : MemoStakeholder[0..*];
|
|
34
|
+
}
|
|
30
35
|
|
|
31
36
|
concern def SafetyConcern :> MemoConcern {
|
|
32
37
|
@MemoIdentity { :>> providedId = "CNC-1"; }
|
|
@@ -136,7 +141,13 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
136
141
|
// A stakeholder holds concerns. These are the engineering and regulatory
|
|
137
142
|
// roles a viewpoint is written FOR; the clinical actors who operate the
|
|
138
143
|
// device are OperationalParticipants and are a different population.
|
|
139
|
-
|
|
144
|
+
//
|
|
145
|
+
// SysML v2 has no stakeholder definition to specialize: a stakeholder is a
|
|
146
|
+
// `Part` that a concern or viewpoint lists in `RequirementCheck::stakeholders`
|
|
147
|
+
// (declared with a `stakeholder` member). So the catalog is standard parts,
|
|
148
|
+
// not `MemoPart`s — MemoPart's lifecycle and dimension attributes describe
|
|
149
|
+
// model elements, not the people a viewpoint is written for.
|
|
150
|
+
abstract part def MemoStakeholder :> Parts::Part;
|
|
140
151
|
|
|
141
152
|
part def SystemArchitect :> MemoStakeholder {
|
|
142
153
|
@MemoIdentity { :>> providedId = "STK-1"; :>> label = "System Architect"; }
|
|
@@ -174,7 +185,7 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
174
185
|
|
|
175
186
|
// ─── The catalog, as usages ─────────────────────────────────────────
|
|
176
187
|
//
|
|
177
|
-
// A viewpoint's `
|
|
188
|
+
// A viewpoint's `memoStakeholders` and `framedConcerns`, and a quality
|
|
178
189
|
// attribute's `addressesConcerns`, are features. What a feature is bound to
|
|
179
190
|
// has to be a feature as well, not a definition, so each concern and each
|
|
180
191
|
// stakeholder above has exactly one usage for those bindings to name.
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows screen captures with the UI element tree laid out over them."; }
|
|
13
13
|
doc /* Frames the user interface spatially: a captured rendering of a screen, and the UIElement tree laid out over it by each element's bounds. Supports IEC 62366-1 use-related design review and the UI description in the software design specification, by making 'which control is this, and what does it do' answerable from the picture. There is one tree, not two — the elements carrying the geometry are the same elements carrying the requirements, functions, use errors, and risk controls. */
|
|
14
14
|
attribute :>> purpose = "Review the interface as the user sees it, with every functional area backed by a design record.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (usabilityEngineer, softwareArchitect, safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "implementation";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::documentSection);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_usability_usability_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context and requirements layers for IEC 62366-1 usability engineering — actors, use contexts, identified use errors, and requirements tagged with the usability concern. Reuses existing context-layer elements (Actor, UseContext, UseError) rather than a separate usability layer. */
|
|
14
14
|
attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (usabilityEngineer, safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::requirements;
|
|
17
17
|
attribute :>> abstractionLevel = "usability";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::documentSection);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_verification_verification_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the requirements and assurance layers for V&V coverage — which requirements are verified/validated, by which case, and what evidence was produced, supporting ISO 13485 §7.3.6/§7.3.7 and IEC 62304 §5.7/§5.8. */
|
|
14
14
|
attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (verificationEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::verificationStage;
|
|
17
17
|
attribute :>> abstractionLevel = "verification";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::matrix);
|
|
Binary file
|
|
Binary file
|
|
Binary file
|