@memoarchitect/ontology 0.16.5 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +11 -18
- package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/views/connected_patient_monitor_overview.sysml +1 -3
- package/examples/connected-patient-monitor/model/methodology/project.sysml +2 -6
- package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +35 -47
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/views/embedded_infusion_pump_overview.sysml +1 -3
- package/examples/embedded-infusion-pump/model/methodology/project.sysml +2 -6
- package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +24 -36
- package/examples/functional-logical-physical/model/catalog/viewpoints/logical/views/functional_logical_physical_overview.sysml +1 -3
- package/examples/functional-logical-physical/model/methodology/project.sysml +2 -6
- package/examples/gastric-bypass-variants/memo.identity.yaml +6 -0
- package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +16 -30
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +16 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +16 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +4 -23
- package/examples/gastric-bypass-variants/model/methodology/project.sysml +3 -6
- package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
- package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
- package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
- package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
- package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
- package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
- package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
- package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
- package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
- package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
- package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
- package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +50 -60
- package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
- package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
- package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
- package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
- package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
- package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
- package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
- package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
- package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
- package/examples/gpca-pump/model/methodology/project.sysml +1 -4
- package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
- package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
- package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
- package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
- package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
- package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
- package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
- package/examples/nested-architecture-dsm/README.md +5 -5
- package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
- package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
- package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
- package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
- package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
- package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
- package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
- package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +21 -30
- package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
- package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
- package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
- package/examples/robot-cell-family/model/catalog/sos/chains.sysml +3 -8
- package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
- package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
- package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +3 -6
- package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +6 -11
- package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +6 -11
- package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +6 -11
- package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
- package/examples/robot-platform/model/platform.sysml +1 -3
- package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
- package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
- package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
- package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
- package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
- package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +34 -45
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
- package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
- package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
- package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
- package/examples/surgical-robot/model/methodology/project.sysml +2 -6
- package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
- package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +13 -21
- package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
- package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
- package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
- package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
- package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
- package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
- package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
- package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
- package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
- package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +14 -21
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
- package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
- package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +45 -65
- package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
- package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
- package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
- package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
- package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
- package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
- package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
- package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
- package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
- package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
- package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
- package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
- package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
- package/extensions/README.md +2 -2
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
- package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
- package/extensions/anatomy/memo.package.yaml +1 -1
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +12 -1
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/cloud/src/cloud_extension.sysml +2 -4
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/container/src/container_extension.sysml +2 -5
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/messaging/src/messaging_extension.sysml +4 -5
- package/extensions/ros/memo.package.yaml +1 -1
- package/extensions/ros/src/ros_extension.sysml +5 -10
- 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 +1 -1
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
- package/src/architecture/functional/functions/memo_functions.sysml +31 -44
- package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
- package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
- package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
- package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
- package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
- package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
- package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
- package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
- package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
- package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
- package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
- package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
- package/src/architecture/operational/activities/memo_activities.sysml +2 -2
- package/src/architecture/operational/context/actors/memo_actors.sysml +8 -7
- package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
- package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
- package/src/architecture/operational/rollups/memo_rollups.sysml +24 -8
- package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
- package/src/architecture/operational/structure/memo_operational.sysml +3 -5
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +32 -26
- package/src/architecture/operational/workflows/memo_workflows.sysml +13 -60
- package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
- package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
- package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
- package/src/artifacts/standards/cfr_21_820.sysml +0 -1
- package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
- package/src/artifacts/standards/iec_60601_1.sysml +0 -1
- package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
- package/src/artifacts/standards/iec_60812.sysml +0 -1
- package/src/artifacts/standards/iec_62304.sysml +0 -1
- package/src/artifacts/standards/iec_62366_1.sysml +0 -1
- package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
- package/src/artifacts/standards/iso_13485.sysml +0 -1
- package/src/artifacts/standards/iso_14971.sysml +0 -1
- package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
- package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
- package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
- 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/iec-62366/use-spec.md +1 -1
- package/src/assurance/cybersecurity/memo_cybersecurity.sysml +1 -0
- package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
- package/src/assurance/requirements/memo_requirements.sysml +6 -11
- package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
- package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
- package/src/assurance/safety_risk/memo_risk.sysml +19 -22
- package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
- package/src/core/annotations/memo_annotations.sysml +2 -2
- package/src/core/common/memo_common.sysml +40 -56
- package/src/core/dimensions/dimensions.sysml +9 -12
- package/src/core/enumerations/memo_enumerations.sysml +4 -12
- package/src/core/methodology_scope/methodology_scope.sysml +3 -6
- package/src/core/relationships/memo_relationships.sysml +54 -85
- package/src/core/relationships/memo_workspace_membership.sysml +0 -2
- package/src/memo_namespaces.sysml +9 -0
- package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
- package/src/methodology/core/memo_core.sysml +12 -12
- package/src/methodology/profiles/memo_profiles.sysml +9 -10
- package/src/methodology/workflow/memo_workflow.sysml +7 -8
- package/src/rules/closure/closure_rules.sysml +7 -9
- package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
- package/src/rules/ontology/ontology_invariants.sysml +97 -105
- package/src/rules/quantitative/quantitative_rules.sysml +0 -1
- package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
- package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
- package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
- package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +24 -0
- package/src/viewpoints/context/context_viewpoint.sysml +0 -1
- package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
- package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
- package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
- package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
- package/src/viewpoints/definitions/memo_view_layout.sysml +27 -3
- package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
- package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
- package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
- package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
- package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
- package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
- package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
- package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
- package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
- package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
- package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
- package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
- package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
- package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
- package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
- package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
- package/src/viewpoints/software/software_viewpoint.sysml +0 -1
- package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
- package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
- package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
- package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
- package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
- package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
- package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
- package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
- package/stage1/opensysml-ddad9e2794141c08532910cf.json.gz +0 -0
- package/stage1/syside-8176a62528c701f2f2e0fc7f.ids.gz +0 -0
- package/stage1/syside-8176a62528c701f2f2e0fc7f.json.gz +0 -0
- package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
- package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
|
@@ -13,10 +13,9 @@ package memo_methodology_profiles {
|
|
|
13
13
|
private import memo_core_methodology_scope::*;
|
|
14
14
|
|
|
15
15
|
private import memo_core_common::*;
|
|
16
|
-
private import memo_core_common::MemoIdentity;
|
|
17
16
|
part mdCoreLibrary : MethodologyLibrary {
|
|
18
17
|
@MemoIdentity { :>> providedId = "METHLIB-001"; :>> label = "MedicalDeviceMethodologyLibrary"; }
|
|
19
|
-
attribute :>> version = "0.
|
|
18
|
+
attribute :>> version = "0.18.0";
|
|
20
19
|
attribute :>> domain = "medical device modeling";
|
|
21
20
|
doc /* Methodology layer for selecting, restricting, sequencing, tailoring, and lightly extending use of the medical-device ontology. */
|
|
22
21
|
}
|
|
@@ -37,7 +36,7 @@ package memo_methodology_profiles {
|
|
|
37
36
|
// second scope authority.
|
|
38
37
|
part mdDefaultDefinition : MethodologyDefinition {
|
|
39
38
|
@MemoIdentity { :>> providedId = "METH-MD-DEFAULT"; :>> label = "MedicalDeviceDefault"; }
|
|
40
|
-
attribute :>> version = "0.
|
|
39
|
+
attribute :>> version = "0.18.0";
|
|
41
40
|
attribute :>> domain = "medical device modeling";
|
|
42
41
|
doc /* MEMO default medical-device methodology. Selects every layer, discipline, standard, artifact kind, and viewpoint the resolved ontology and extension packages provide. */
|
|
43
42
|
attribute :>> scopeMode = ScopeModeKind::allAvailable;
|
|
@@ -71,9 +70,10 @@ package memo_methodology_profiles {
|
|
|
71
70
|
attribute :>> strength = RuleStrengthKind::required;
|
|
72
71
|
}
|
|
73
72
|
|
|
74
|
-
// The default method
|
|
75
|
-
// and at each system. `outputKinds` and the rules a step is
|
|
76
|
-
// `#
|
|
73
|
+
// The default method: the steps a family works through, at the system of
|
|
74
|
+
// systems and at each system. `outputKinds` and the rules a step is
|
|
75
|
+
// `#DoneWhen` say when its own work is done; the rules it is `#LinkedWhen`
|
|
76
|
+
// say when it is linked to the other layers.
|
|
77
77
|
|
|
78
78
|
action stepSosContext : MethodologyWorkflowStep {
|
|
79
79
|
@MemoIdentity { :>> providedId = "STEP-SOS-01"; :>> label = "SosContext"; }
|
|
@@ -281,10 +281,9 @@ package memo_methodology_profiles {
|
|
|
281
281
|
attribute :>> passCriteria = "Core traceability, risk, verification, and RMF view support are present.";
|
|
282
282
|
}
|
|
283
283
|
|
|
284
|
-
//
|
|
285
|
-
//
|
|
286
|
-
//
|
|
287
|
-
// references its methodology with a typed SysML reference.
|
|
284
|
+
// A project binding is project content: it lives in the project's own
|
|
285
|
+
// `model/methodology/project.sysml` and references its methodology with a
|
|
286
|
+
// typed SysML reference.
|
|
288
287
|
|
|
289
288
|
part rmpDoc : DhfDocumentBinding {
|
|
290
289
|
@MemoIdentity { :>> providedId = "DHF-001"; :>> label = "RiskManagementPlan"; }
|
|
@@ -21,14 +21,13 @@ package memo_methodology_workflow {
|
|
|
21
21
|
// order and says which step feeds which; it never holds a step back. Teams work
|
|
22
22
|
// each layer independently and link their work as the other side appears.
|
|
23
23
|
//
|
|
24
|
-
// What makes a step DONE is stated, not assumed
|
|
25
|
-
//
|
|
26
|
-
//
|
|
27
|
-
//
|
|
28
|
-
//
|
|
29
|
-
//
|
|
30
|
-
//
|
|
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
|
|
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.
|
|
149
|
-
//
|
|
150
|
-
//
|
|
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
|
|
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,20 +1,23 @@
|
|
|
1
|
-
// Ontology conformance invariants
|
|
2
|
-
//
|
|
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
|
|
5
|
+
// the typed relations — typed references make them checkable.
|
|
6
6
|
//
|
|
7
|
-
// Operational levels (CR-ONT-093..
|
|
8
|
-
//
|
|
9
|
-
//
|
|
10
|
-
// level
|
|
11
|
-
//
|
|
12
|
-
//
|
|
13
|
-
//
|
|
14
|
-
//
|
|
15
|
-
//
|
|
16
|
-
//
|
|
17
|
-
//
|
|
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
|
|
18
21
|
// package level is built as a model element, as ISQ and SI declare theirs.
|
|
19
22
|
package memo_rules_ontology {
|
|
20
23
|
private import ScalarValues::*;
|
|
@@ -23,7 +26,6 @@ package memo_rules_ontology {
|
|
|
23
26
|
private import memo_core_enumerations::*;
|
|
24
27
|
|
|
25
28
|
private import memo_core_common::*;
|
|
26
|
-
private import memo_core_common::MemoIdentity;
|
|
27
29
|
private import memo_artifacts_standards_traceability::EnforcesClause;
|
|
28
30
|
private import memo_artifacts_standards_iec_62366_1::*;
|
|
29
31
|
private import memo_artifacts_standards_iso_13485::*;
|
|
@@ -53,12 +55,12 @@ package memo_rules_ontology {
|
|
|
53
55
|
attribute predicateExpression = "allOfKind('System')->exists(isDefinition == 'true')";
|
|
54
56
|
constraint { true }
|
|
55
57
|
}
|
|
56
|
-
// ─── Use case scope
|
|
58
|
+
// ─── Use case scope ─────────────────────────────────────────
|
|
57
59
|
//
|
|
58
|
-
//
|
|
59
|
-
//
|
|
60
|
-
//
|
|
61
|
-
// is
|
|
60
|
+
// The level of a use case is its declared type (`ClinicalUseCase`, `SystemUseCase`), and
|
|
61
|
+
// CR-ONT-093 keeps it in agreement with the subject (`hasSubject`). Rule 085 reads the subject
|
|
62
|
+
// for what it says about composition, not for the level. A use case with no subject
|
|
63
|
+
// is judged by no rule on the subject.
|
|
62
64
|
|
|
63
65
|
constraint def SosUseCaseIncludesSystemUseCaseRule :> MemoConsistencyRule {
|
|
64
66
|
@MemoIdentity { :>> providedId = "CR-ONT-085"; }
|
|
@@ -71,7 +73,7 @@ package memo_rules_ontology {
|
|
|
71
73
|
attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(SystemOfSystems))) or downstream(includesStep)->exists(downstream(hasSubject)->exists(conformsTo(System)))";
|
|
72
74
|
constraint { true }
|
|
73
75
|
}
|
|
74
|
-
// ─── Release selections
|
|
76
|
+
// ─── Release selections ────────────────────────────────────
|
|
75
77
|
//
|
|
76
78
|
// A release record selects features (`#SelectsFeature`), and through them the variants that realize
|
|
77
79
|
// them (`#RealizesFeature`, variant to feature). The rules read a record's selection by navigation;
|
|
@@ -157,10 +159,11 @@ package memo_rules_ontology {
|
|
|
157
159
|
|
|
158
160
|
// ─── Direction is written on the ports, and an exchange has to agree with them ──
|
|
159
161
|
//
|
|
160
|
-
// A port says `in` or `out` (or `inout`), and a `~` conjugates it. That is
|
|
161
|
-
//
|
|
162
|
-
//
|
|
163
|
-
//
|
|
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.
|
|
164
167
|
constraint def BindingEndsAgreeInDirectionRule :> MemoConsistencyRule {
|
|
165
168
|
@MemoIdentity { :>> providedId = "AR-EXCH-001"; }
|
|
166
169
|
attribute tailoring = RuleTailoringKind::invariant;
|
|
@@ -248,14 +251,11 @@ package memo_rules_ontology {
|
|
|
248
251
|
attribute tailoring = RuleTailoringKind::assurance;
|
|
249
252
|
attribute domain = RuleDomainKind::medicalDevice;
|
|
250
253
|
attribute obligation = RuleObligationKind::required;
|
|
251
|
-
// To confirm: inferred from the clause scope; the FDA human-factors
|
|
252
|
-
//
|
|
253
|
-
//
|
|
254
|
-
//
|
|
255
|
-
//
|
|
256
|
-
// relation the human-factors package declares for exactly this link;
|
|
257
|
-
// reading only `validates` meant a task linked the way the ontology
|
|
258
|
-
// 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.
|
|
259
259
|
attribute appliesTo = "OperativeAction";
|
|
260
260
|
attribute severity = RuleSeverityKind::error;
|
|
261
261
|
attribute rationaleText = "Critical tasks (criticality high or catastrophic) must trace to usability validation (FDA HF guidance; IEC 62366-1 summative evaluation).";
|
|
@@ -276,34 +276,22 @@ package memo_rules_ontology {
|
|
|
276
276
|
constraint { true }
|
|
277
277
|
}
|
|
278
278
|
#EnforcesClause dependency from UseErrorTracesToHazardRule to iec62366_1::iec62366_1Clause5::iec62366_1Clause5_3;
|
|
279
|
-
// ─── Relation end conformance
|
|
279
|
+
// ─── Relation end conformance ─────────────────────────────
|
|
280
280
|
//
|
|
281
|
-
// These rules carry the constraints
|
|
282
|
-
//
|
|
283
|
-
//
|
|
284
|
-
//
|
|
285
|
-
//
|
|
286
|
-
// on, and why `allocate <function> to <actor>` is rejected. See the Track A0
|
|
287
|
-
// 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.
|
|
288
286
|
//
|
|
289
|
-
// Each rule states
|
|
290
|
-
// the
|
|
287
|
+
// Each rule states its end's constraint, in the one vocabulary that spans
|
|
288
|
+
// the metaclasses:
|
|
291
289
|
//
|
|
292
|
-
//
|
|
293
|
-
//
|
|
294
|
-
//
|
|
295
|
-
//
|
|
296
|
-
//
|
|
297
|
-
//
|
|
298
|
-
// Several of these are WIDER than the end they replace, and deliberately so:
|
|
299
|
-
// the ends were being violated by content that already shipped. `composes`
|
|
300
|
-
// was typed MemoPart/MemoPart and links StateMachine (a state def) to
|
|
301
|
-
// OperativeAction (an action def); `verifiedBy`'s source was typed MemoPart and
|
|
302
|
-
// most of its sources are requirement defs; `precedes` was typed
|
|
303
|
-
// a part-only type and joins OperativeAction to OperativeAction.
|
|
304
|
-
// A rule that reproduced the old type exactly would have failed on the
|
|
305
|
-
// flagship example on the day it landed. What each rule asserts is the
|
|
306
|
-
// 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.
|
|
307
295
|
//
|
|
308
296
|
// Subject scope is `Model`, following CR-ONT-001: a statement about the ends
|
|
309
297
|
// of a relation quantifies over its LINKS, not over elements of one kind, so
|
|
@@ -433,16 +421,10 @@ package memo_rules_ontology {
|
|
|
433
421
|
constraint { true }
|
|
434
422
|
}
|
|
435
423
|
|
|
436
|
-
//
|
|
437
|
-
//
|
|
438
|
-
//
|
|
439
|
-
//
|
|
440
|
-
// the ends.
|
|
441
|
-
//
|
|
442
|
-
// It used to read `sourceEndpoint` refs, whose dotted values the builder
|
|
443
|
-
// cut to their first segment, and compare them as strings, which drop
|
|
444
|
-
// everything up to the last `::`. On gpca-pump that matched the enclosing
|
|
445
|
-
// 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.
|
|
446
428
|
constraint def ComponentExchangeSourceEndpointKindRule :> MemoConsistencyRule {
|
|
447
429
|
@MemoIdentity { :>> providedId = "CR-ONT-072"; }
|
|
448
430
|
attribute tailoring = RuleTailoringKind::invariant;
|
|
@@ -479,8 +461,8 @@ package memo_rules_ontology {
|
|
|
479
461
|
attribute obligation = RuleObligationKind::recommended;
|
|
480
462
|
attribute appliesTo = "ComponentFunction";
|
|
481
463
|
attribute severity = RuleSeverityKind::error;
|
|
482
|
-
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.";
|
|
483
|
-
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";
|
|
484
466
|
constraint { true }
|
|
485
467
|
}
|
|
486
468
|
constraint def FunctionDecomposesIntoFunctionsRule :> MemoConsistencyRule {
|
|
@@ -490,8 +472,8 @@ package memo_rules_ontology {
|
|
|
490
472
|
attribute obligation = RuleObligationKind::recommended;
|
|
491
473
|
attribute appliesTo = "MemoFunction";
|
|
492
474
|
attribute severity = RuleSeverityKind::error;
|
|
493
|
-
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.";
|
|
494
|
-
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')";
|
|
495
477
|
constraint { true }
|
|
496
478
|
}
|
|
497
479
|
|
|
@@ -511,13 +493,10 @@ package memo_rules_ontology {
|
|
|
511
493
|
// writing them as containment loses the distinction.
|
|
512
494
|
//
|
|
513
495
|
// They read the `composes` edge, which the builder synthesizes from native
|
|
514
|
-
// nesting
|
|
515
|
-
//
|
|
516
|
-
//
|
|
517
|
-
//
|
|
518
|
-
// cross-family nesting twice, once on each side, and the child's copy
|
|
519
|
-
// blamed the element that was not doing the containing. `downstream` is
|
|
520
|
-
// 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".
|
|
521
500
|
//
|
|
522
501
|
// Ports are exempt. A port is a boundary FEATURE of its owner, not a member
|
|
523
502
|
// of its owner's family, and any element may carry one whatever family it
|
|
@@ -564,16 +543,9 @@ package memo_rules_ontology {
|
|
|
564
543
|
// whose ends are the exchange's own two ports. The ends are compared as
|
|
565
544
|
// elements (`intersects` matches exact ids), not as names.
|
|
566
545
|
//
|
|
567
|
-
// It replaces the same-name coupling this id used to check, which tied a
|
|
568
|
-
// ComponentExchange PART to a flow of the same name. That was unsatisfiable
|
|
569
|
-
// once the model compiled: two members of one namespace may not share a
|
|
570
|
-
// name (`namespace-distinguishability`), and a `bind` could not be named at
|
|
571
|
-
// all. With the exchange an interface there is no second record to keep in
|
|
572
|
-
// step, and what is left to check is transport.
|
|
573
|
-
//
|
|
574
546
|
// `assurance`, not `invariant`: whether every interface must declare its
|
|
575
|
-
// transport is a method's call
|
|
576
|
-
//
|
|
547
|
+
// transport is a method's call, and a method that models interfaces before
|
|
548
|
+
// their flows may tailor it.
|
|
577
549
|
constraint def ExchangeHasFlowRule :> MemoConsistencyRule {
|
|
578
550
|
@MemoIdentity { :>> providedId = "CR-ONT-076"; }
|
|
579
551
|
attribute tailoring = RuleTailoringKind::assurance;
|
|
@@ -619,17 +591,14 @@ package memo_rules_ontology {
|
|
|
619
591
|
|
|
620
592
|
// ─── Assurance-trace warnings ────────────────────────────────────────
|
|
621
593
|
// A WARNING, not an error: it describes a trace graph that is suspicious
|
|
622
|
-
// rather than invalid, and a regulated model has legitimate exceptions.
|
|
623
|
-
//
|
|
624
|
-
// bidirectional
|
|
625
|
-
// 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.
|
|
626
597
|
//
|
|
627
|
-
//
|
|
628
|
-
//
|
|
629
|
-
//
|
|
630
|
-
//
|
|
631
|
-
// requirement derived from "select a drug from the library" says nothing
|
|
632
|
-
// 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.
|
|
633
602
|
|
|
634
603
|
constraint def DerivationGapRule :> MemoConsistencyRule {
|
|
635
604
|
@MemoIdentity { :>> providedId = "CR-ONT-080"; }
|
|
@@ -697,8 +666,8 @@ package memo_rules_ontology {
|
|
|
697
666
|
attribute obligation = RuleObligationKind::recommended;
|
|
698
667
|
attribute appliesTo = "UseCase";
|
|
699
668
|
attribute severity = RuleSeverityKind::error;
|
|
700
|
-
attribute rationaleText = "A use case is at
|
|
701
|
-
attribute predicateExpression = "downstream(hasSubject)->forAll(conformsTo(OperationalEntity) or conformsTo(System) or conformsTo(SystemOfSystems))";
|
|
669
|
+
attribute rationaleText = "A use case is declared at a level, and its subject agrees: a clinical use case has an operational entity (the care team, the setting) as its subject, a system use case a system or a system of systems. A use case of neither type does not say whether it may name a product or carry a number, and a subject of the other level makes the declared type false.";
|
|
670
|
+
attribute predicateExpression = "(conformsTo(ClinicalUseCase) and downstream(hasSubject)->forAll(conformsTo(OperationalEntity))) or (conformsTo(SystemUseCase) and downstream(hasSubject)->forAll(conformsTo(System) or conformsTo(SystemOfSystems)))";
|
|
702
671
|
constraint { true }
|
|
703
672
|
}
|
|
704
673
|
constraint def LevelOneStepCarriesNoNumberRule :> MemoConsistencyRule {
|
|
@@ -709,7 +678,7 @@ package memo_rules_ontology {
|
|
|
709
678
|
attribute appliesTo = "OperativeAction";
|
|
710
679
|
attribute severity = RuleSeverityKind::error;
|
|
711
680
|
attribute rationaleText = "A step of a level-1 workflow is the shared baseline of every variant and carries no planned number: a gastric pouch takes a different time and succeeds at a different rate on each platform, so a number on the step would belong to no variant. Time and success are set on the level-2 activity that refines it.";
|
|
712
|
-
attribute predicateExpression = "(attributes.expectedDuration == '' and attributes.plannedSuccessProbability == '') or not((upstream(composes)->exists(conformsTo(
|
|
681
|
+
attribute predicateExpression = "(attributes.expectedDuration == '' and attributes.plannedSuccessProbability == '') or not((upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))))))";
|
|
713
682
|
constraint { true }
|
|
714
683
|
}
|
|
715
684
|
constraint def RealizerOfLevelOneStepIsLevelTwoRule :> MemoConsistencyRule {
|
|
@@ -720,7 +689,7 @@ package memo_rules_ontology {
|
|
|
720
689
|
attribute appliesTo = "OperativeAction";
|
|
721
690
|
attribute severity = RuleSeverityKind::error;
|
|
722
691
|
attribute rationaleText = "Whatever refines a level-1 step is itself at level 2: a level-1 step refined by another level-1 step, or by an activity of no workflow at all, skips the level that names the variant.";
|
|
723
|
-
attribute predicateExpression = "not(downstream(realizes)->exists((upstream(composes)->exists(conformsTo(
|
|
692
|
+
attribute predicateExpression = "not(downstream(realizes)->exists((upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))))))) or (upstream(composes)->exists(conformsTo(SystemWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(SystemWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(SystemWorkflow)))))";
|
|
724
693
|
constraint { true }
|
|
725
694
|
}
|
|
726
695
|
constraint def InternalSystemActivityPerformsAFunctionRule :> MemoConsistencyRule {
|
|
@@ -742,7 +711,7 @@ package memo_rules_ontology {
|
|
|
742
711
|
attribute appliesTo = "SystemFunction";
|
|
743
712
|
attribute severity = RuleSeverityKind::error;
|
|
744
713
|
attribute rationaleText = "A system function is performed from a level-2 activity or from a step of a functional flow, never from a level-1 step: level 1 names no product, and a function is what a product does.";
|
|
745
|
-
attribute predicateExpression = "upstream(performs)->forAll(not(conformsTo(OperativeAction) and (upstream(composes)->exists(conformsTo(
|
|
714
|
+
attribute predicateExpression = "upstream(performs)->forAll(not(conformsTo(OperativeAction) and (upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow)))))))";
|
|
746
715
|
constraint { true }
|
|
747
716
|
}
|
|
748
717
|
constraint def ProjectDeclaresOneCurrencyRule :> MemoConsistencyRule {
|
|
@@ -764,7 +733,7 @@ package memo_rules_ontology {
|
|
|
764
733
|
attribute appliesTo = "OperativeScenario";
|
|
765
734
|
attribute severity = RuleSeverityKind::error;
|
|
766
735
|
attribute rationaleText = "How likely a path is differs by platform (a robot and a laparoscopic tower do not convert to open at the same rate), so a scenario of a level-1 workflow carries no likelihood; it is set on the level-2 scenario of each variant.";
|
|
767
|
-
attribute predicateExpression = "attributes.likelihood == '' or not(upstream(composes)->exists(conformsTo(
|
|
736
|
+
attribute predicateExpression = "attributes.likelihood == '' or not(upstream(composes)->exists(conformsTo(ClinicalWorkflow)))";
|
|
768
737
|
constraint { true }
|
|
769
738
|
}
|
|
770
739
|
constraint def LevelOneWorkflowCarriesNoCostRule :> MemoConsistencyRule {
|
|
@@ -775,7 +744,7 @@ package memo_rules_ontology {
|
|
|
775
744
|
attribute appliesTo = "OperationalWorkflow";
|
|
776
745
|
attribute severity = RuleSeverityKind::error;
|
|
777
746
|
attribute rationaleText = "What a procedure costs apart from its activities (set-up, capital per case) depends on the platform, so a level-1 workflow carries no per-procedure cost; it is set on the workflow of each level-2 variant.";
|
|
778
|
-
attribute predicateExpression = "attributes.perProcedureCost == '' or not(
|
|
747
|
+
attribute predicateExpression = "attributes.perProcedureCost == '' or not(conformsTo(ClinicalWorkflow))";
|
|
779
748
|
constraint { true }
|
|
780
749
|
}
|
|
781
750
|
constraint def TradeStudyVariantRefinesEveryStepRule :> MemoConsistencyRule {
|
|
@@ -789,4 +758,27 @@ package memo_rules_ontology {
|
|
|
789
758
|
attribute predicateExpression = "not(upstream(hasSubject)->exists(attributes.usageType == 'TradeStudy')) or upstream(hasSubject)->select(attributes.usageType == 'TradeStudy')->forAll(downstream(hasSubject)->forAll(downstream(composes)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))) and downstream(composes)->forAll(downstream(performs)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))))))";
|
|
790
759
|
constraint { true }
|
|
791
760
|
}
|
|
761
|
+
constraint def WorkflowOwnsNoStepsOutsideScenariosRule :> MemoConsistencyRule {
|
|
762
|
+
@MemoIdentity { :>> providedId = "CR-ONT-102"; }
|
|
763
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
764
|
+
attribute domain = RuleDomainKind::modelling;
|
|
765
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
766
|
+
attribute appliesTo = "OperativeAction";
|
|
767
|
+
attribute severity = RuleSeverityKind::error;
|
|
768
|
+
attribute rationaleText = "A workflow is the analysis of a use case (its equipment, environment and needs); the steps that carry it out are the tasks of a use scenario (IEC 62366-1 5.4). A step owned by the workflow itself belongs to no scenario, so it has no pre- or post-condition and no path it is on.";
|
|
769
|
+
attribute predicateExpression = "not(upstream(composes)->exists(conformsTo(OperationalWorkflow))) or upstream(composes)->exists(conformsTo(OperativeScenario))";
|
|
770
|
+
constraint { true }
|
|
771
|
+
}
|
|
772
|
+
constraint def WorkflowRealizesUseCaseOfItsLevelRule :> MemoConsistencyRule {
|
|
773
|
+
@MemoIdentity { :>> providedId = "CR-ONT-103"; }
|
|
774
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
775
|
+
attribute domain = RuleDomainKind::modelling;
|
|
776
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
777
|
+
attribute appliesTo = "OperationalWorkflow";
|
|
778
|
+
attribute severity = RuleSeverityKind::error;
|
|
779
|
+
attribute rationaleText = "A workflow is the analysis of a use case and is at its level: a clinical workflow realizes a clinical use case, a system workflow a system use case. A workflow of the wrong level would carry a number the use case it serves may not, or hide a product from the baseline every variant is compared against.";
|
|
780
|
+
attribute predicateExpression = "(conformsTo(ClinicalWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(ClinicalUseCase))) or (conformsTo(SystemWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(SystemUseCase)))";
|
|
781
|
+
constraint { true }
|
|
782
|
+
}
|
|
783
|
+
#EnforcesClause dependency from WorkflowOwnsNoStepsOutsideScenariosRule to iec62366_1::iec62366_1Clause5::iec62366_1Clause5_4;
|
|
792
784
|
}
|
|
@@ -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
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
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
|
|
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
|
-
|
|
5
|
-
|
|
4
|
+
private import memo_viewpoints_definitions::*;
|
|
5
|
+
private import memo_core_enumerations::*;
|
|
6
6
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
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
|
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
package memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint {
|
|
2
|
+
private import ScalarValues::*;
|
|
3
|
+
|
|
4
|
+
private import memo_viewpoints_definitions::*;
|
|
5
|
+
private import memo_core_enumerations::*;
|
|
6
|
+
private import memo_viewpoints_stakeholders_concerns::*;
|
|
7
|
+
|
|
8
|
+
private import memo_core_common::*;
|
|
9
|
+
viewpoint clinicalWorkflowViewpoint : MemoViewpoint {
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-CLINWF"; :>> label = "ClinicalWorkflowViewpoint"; }
|
|
11
|
+
@MemoIdentity { :>> shortDescription = "Shows clinical use cases, workflows and scenarios: what must happen to the patient, with no product and no number."; }
|
|
12
|
+
doc /* Level 1 of the operational levels: the clinical use cases, their workflows and scenarios, and the steps the care team performs. It names no product and carries no number; the system workflows that refine it are the Operational viewpoint's. Not the Clinical viewpoint, which presents clinical evidence. */
|
|
13
|
+
attribute :>> purpose = "Communicate the clinical baseline every system variant is compared against.";
|
|
14
|
+
ref :>> memoStakeholders = (clinicalEngineer, systemArchitect);
|
|
15
|
+
attribute :>> stage = WorkflowStageKind::context;
|
|
16
|
+
attribute :>> abstractionLevel = "clinical";
|
|
17
|
+
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
18
|
+
attribute :>> presentationKind = (PresentationKind::activityDiagram);
|
|
19
|
+
ref :>> framedConcerns = (safetyConcern, clinicalConcern);
|
|
20
|
+
attribute :>> explorerLane = "architecture";
|
|
21
|
+
attribute :>> explorerOrder = 0;
|
|
22
|
+
attribute :>> userExtensible = true;
|
|
23
|
+
}
|
|
24
|
+
}
|
|
@@ -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."; }
|