@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
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
// Execution-platform elements of the physical architecture
|
|
2
|
-
//
|
|
3
|
-
//
|
|
1
|
+
// Execution-platform elements of the physical architecture: the nodes software
|
|
2
|
+
// runs on and the ports the outside world plugs into. The broader physical
|
|
3
|
+
// taxonomy lives in memo_architecture_implementation_hardware_structure.
|
|
4
4
|
package memo_architecture_realization_physical {
|
|
5
5
|
private import memo_core_stdlib_quantities::*;
|
|
6
6
|
private import ScalarValues::*;
|
|
@@ -32,31 +32,28 @@ package memo_architecture_realization_physical {
|
|
|
32
32
|
}
|
|
33
33
|
// A physical boundary feature: the connector the outside world plugs into.
|
|
34
34
|
//
|
|
35
|
-
// A `port def
|
|
36
|
-
//
|
|
37
|
-
//
|
|
38
|
-
// a part (CR-ONT-002, since rewritten). Track A0 made those ends
|
|
39
|
-
// metaclass-neutral, and KerML forbids a port from specializing a
|
|
40
|
-
// part-based type, so the specialization moves to `MemoPort`.
|
|
35
|
+
// A `port def`, not a part. Exchange ends are metaclass-neutral, and KerML
|
|
36
|
+
// forbids a port from specializing a part-based type, so it specializes
|
|
37
|
+
// `MemoPort`.
|
|
41
38
|
//
|
|
42
|
-
// `direction
|
|
43
|
-
// natively
|
|
44
|
-
//
|
|
39
|
+
// It declares no `direction`: the port usage carries `in` / `out` / `inout`
|
|
40
|
+
// natively. `DirectionKind` is for the non-port constructs that need one —
|
|
41
|
+
// see memo_core_enumerations.
|
|
45
42
|
//
|
|
46
43
|
// `portKind` is declared here AND on SoftwarePort rather than on a shared
|
|
47
44
|
// base. `MemoPort` is the identification core and nothing else — the block
|
|
48
|
-
// comment in memo_core_common makes that a stated invariant across all
|
|
49
|
-
//
|
|
45
|
+
// comment in memo_core_common makes that a stated invariant across all five
|
|
46
|
+
// bases — and pushing `portKind` down onto DataPort, SensorPort,
|
|
50
47
|
// CommandPort, and LogicalPort would give them a second classifier beside
|
|
51
48
|
// the ones they already carry (`interfaceType`, `sensorDomain`,
|
|
52
49
|
// `commandDomain`, `contentKind`). An intermediate `abstract port def`
|
|
53
|
-
// holding one attribute is a class standing in for an attribute
|
|
54
|
-
//
|
|
50
|
+
// holding one attribute is a class standing in for an attribute. One
|
|
51
|
+
// attribute, two sites, no new type.
|
|
55
52
|
port def PhysicalPort specializes MemoPort {
|
|
56
53
|
attribute portKind : InterfaceKind;
|
|
57
|
-
// AADL port category
|
|
58
|
-
//
|
|
59
|
-
//
|
|
54
|
+
// AADL port category — see SoftwarePort. A physical port carries it for
|
|
55
|
+
// the same reason: a sampled sensor line and a queued interrupt line
|
|
56
|
+
// fail differently under overload.
|
|
60
57
|
attribute portCategory : PortCategoryKind;
|
|
61
58
|
attribute connectorType : String;
|
|
62
59
|
}
|
|
@@ -15,15 +15,17 @@ package memo_artifacts_configuration_management {
|
|
|
15
15
|
}
|
|
16
16
|
|
|
17
17
|
part def ConfigurationItem :> MemoPart {
|
|
18
|
-
// No version and no baseline: both belong to a release of the item, not
|
|
19
|
-
//
|
|
18
|
+
// No version and no baseline: both belong to a release of the item, not
|
|
19
|
+
// to the item. A `ReleaseRecord` whose `#ReleaseOf` is this item
|
|
20
|
+
// carries them.
|
|
20
21
|
attribute controlLevel : String;
|
|
21
22
|
}
|
|
22
23
|
|
|
23
|
-
// A release record is one release of one item: rev D and rev E of a part,
|
|
24
|
-
// release, are separate records, each with its own
|
|
25
|
-
// definition of the item is held once and
|
|
26
|
-
//
|
|
24
|
+
// A release record is one release of one item: rev D and rev E of a part,
|
|
25
|
+
// or its EU and its US release, are separate records, each with its own
|
|
26
|
+
// part number and revision. The definition of the item is held once and
|
|
27
|
+
// carries no revision. The record is an element with a status (inherited
|
|
28
|
+
// from MemoPart: proposed, draft, ... released), so a release moves through
|
|
27
29
|
// the lifecycle the way any element does.
|
|
28
30
|
//
|
|
29
31
|
// part relPumpD : ReleaseRecord {
|
|
@@ -66,9 +68,11 @@ package memo_artifacts_configuration_management {
|
|
|
66
68
|
doc /* `#AffectsRelease dependency from <change request> to <record>;` The release a change request is raised against. */
|
|
67
69
|
}
|
|
68
70
|
|
|
69
|
-
// A regulated device is one approval in one jurisdiction
|
|
70
|
-
// clear. It is not an item and not a release: it
|
|
71
|
-
//
|
|
71
|
+
// A regulated device is one approval in one jurisdiction: the thing a
|
|
72
|
+
// regulator is asked to clear. It is not an item and not a release: it
|
|
73
|
+
// COVERS the system releases the approval names, so two markets can ship
|
|
74
|
+
// different releases of one system, each with its own design history and
|
|
75
|
+
// risk file.
|
|
72
76
|
//
|
|
73
77
|
// part deviceFda : RegulatedDevice {
|
|
74
78
|
// attribute :>> jurisdiction = RegulatoryRegimeKind::FDA_510k;
|
|
@@ -76,20 +80,22 @@ package memo_artifacts_configuration_management {
|
|
|
76
80
|
// }
|
|
77
81
|
// #Covers dependency from deviceFda to relPumpD;
|
|
78
82
|
//
|
|
79
|
-
// The jurisdiction is a `RegulatoryRegimeKind`, the same enum the standards
|
|
80
|
-
// templates (`required_for`) are written against,
|
|
81
|
-
//
|
|
82
|
-
//
|
|
83
|
+
// The jurisdiction is a `RegulatoryRegimeKind`, the same enum the standards
|
|
84
|
+
// library and the document templates (`required_for`) are written against,
|
|
85
|
+
// so a device selects the standards it must meet and the documents it must
|
|
86
|
+
// have. `ModelMethodBinding.regulatoryRegime` states one regime set for a
|
|
87
|
+
// whole model and is read only when the model declares no device.
|
|
83
88
|
//
|
|
84
|
-
// The device's other two links
|
|
89
|
+
// The device's other two links, both typed dependencies like `Covers`:
|
|
85
90
|
//
|
|
86
91
|
// #IntendedUseOf dependency from pumpIntendedUse to deviceFda;
|
|
87
92
|
// #UsedWith dependency from deviceFda to deviceInfusionSet;
|
|
88
93
|
//
|
|
89
|
-
// `IntendedUseOf` runs from the intended use (a `requirement def`,
|
|
90
|
-
// name reads; a device can have one
|
|
91
|
-
//
|
|
92
|
-
//
|
|
94
|
+
// `IntendedUseOf` runs from the intended use (a `requirement def`,
|
|
95
|
+
// `IntendedUse`) to the device, as its name reads; a device can have one
|
|
96
|
+
// per indication. `UsedWith` runs between regulated devices: the compatible
|
|
97
|
+
// devices and accessories that are themselves approved. An accessory that
|
|
98
|
+
// is not a device is not a target.
|
|
93
99
|
part def RegulatedDevice :> MemoPart {
|
|
94
100
|
attribute jurisdiction : RegulatoryRegimeKind[1];
|
|
95
101
|
attribute submissionId : String[0..1];
|
|
@@ -105,10 +111,12 @@ package memo_artifacts_configuration_management {
|
|
|
105
111
|
doc /* `#UsedWith dependency from <device> to <device>, <device>;` The device is used with these regulated devices (compatible devices and approved accessories). */
|
|
106
112
|
}
|
|
107
113
|
|
|
108
|
-
// A project is a change set in an iteration
|
|
109
|
-
// where the work is tracked and nothing else;
|
|
110
|
-
//
|
|
111
|
-
//
|
|
114
|
+
// A project is a change set in an iteration: the work that produces
|
|
115
|
+
// releases. It holds a link to where the work is tracked and nothing else;
|
|
116
|
+
// the merge request is the approval. It FEEDS the release records it
|
|
117
|
+
// contributes to, and a variant records the project that introduced it, so
|
|
118
|
+
// "which work gave us this option, and which releases did it reach" is two
|
|
119
|
+
// links.
|
|
112
120
|
//
|
|
113
121
|
// part prjIrrigatedTip : Project { attribute :>> trackerLink = "https://tracker.example/PRJ-12"; }
|
|
114
122
|
// #Feeds dependency from prjIrrigatedTip to relGeneratorEu, relGeneratorUs;
|
|
@@ -16,7 +16,6 @@ package memo_artifacts_standards_cfr_21_820 {
|
|
|
16
16
|
private import memo_artifacts_standards_traceability::*;
|
|
17
17
|
|
|
18
18
|
private import memo_core_common::*;
|
|
19
|
-
private import memo_core_common::MemoIdentity;
|
|
20
19
|
part cfr21Part820 : RegulatoryStandard {
|
|
21
20
|
@MemoIdentity { :>> providedId = "STD-21-CFR-820"; }
|
|
22
21
|
attribute :>> designation = "21 CFR Part 820";
|
|
@@ -8,10 +8,8 @@
|
|
|
8
8
|
// the traceability question is identical, only the enforceability differs, and
|
|
9
9
|
// that difference is data on the clause rather than a second mechanism.
|
|
10
10
|
//
|
|
11
|
-
// Reference granularity is the guidance's own lettered section structure
|
|
12
|
-
//
|
|
13
|
-
// templates previously cited decimal numbers ("3.2", "5.2") that match no
|
|
14
|
-
// section of the published guidance; those were replaced when this pack landed.
|
|
11
|
+
// Reference granularity is the guidance's own lettered section structure (IV,
|
|
12
|
+
// V.A, …), not a decimal clause numbering — this document has none.
|
|
15
13
|
package memo_artifacts_standards_fda_cybersecurity_2023 {
|
|
16
14
|
private import ScalarValues::*;
|
|
17
15
|
private import memo_core_enumerations::*;
|
|
@@ -19,7 +17,6 @@ package memo_artifacts_standards_fda_cybersecurity_2023 {
|
|
|
19
17
|
private import memo_artifacts_standards_traceability::*;
|
|
20
18
|
|
|
21
19
|
private import memo_core_common::*;
|
|
22
|
-
private import memo_core_common::MemoIdentity;
|
|
23
20
|
part fdaCybersecurity2023 : RegulatoryStandard {
|
|
24
21
|
@MemoIdentity { :>> providedId = "STD-FDA-CYBER-2023"; }
|
|
25
22
|
attribute :>> designation = "FDA Cybersecurity Guidance 2023";
|
|
@@ -16,7 +16,6 @@ package memo_artifacts_standards_iec_60601_1 {
|
|
|
16
16
|
private import memo_artifacts_standards_traceability::*;
|
|
17
17
|
|
|
18
18
|
private import memo_core_common::*;
|
|
19
|
-
private import memo_core_common::MemoIdentity;
|
|
20
19
|
part iec60601_1 : RegulatoryStandard {
|
|
21
20
|
@MemoIdentity { :>> providedId = "STD-IEC-60601-1"; }
|
|
22
21
|
attribute :>> designation = "IEC 60601-1:2005+AMD1:2012+AMD2:2020";
|
|
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iec_60601_1_2 {
|
|
|
11
11
|
private import memo_artifacts_standards_traceability::*;
|
|
12
12
|
|
|
13
13
|
private import memo_core_common::*;
|
|
14
|
-
private import memo_core_common::MemoIdentity;
|
|
15
14
|
part iec60601_1_2 : RegulatoryStandard {
|
|
16
15
|
@MemoIdentity { :>> providedId = "STD-IEC-60601-1-2-COLLATERAL"; }
|
|
17
16
|
attribute :>> designation = "IEC 60601-1-2:2014+AMD1:2020";
|
|
@@ -15,7 +15,6 @@ package memo_artifacts_standards_iec_60812 {
|
|
|
15
15
|
private import memo_artifacts_standards_traceability::*;
|
|
16
16
|
|
|
17
17
|
private import memo_core_common::*;
|
|
18
|
-
private import memo_core_common::MemoIdentity;
|
|
19
18
|
part iec60812 : RegulatoryStandard {
|
|
20
19
|
@MemoIdentity { :>> providedId = "STD-IEC-60812"; }
|
|
21
20
|
attribute :>> designation = "IEC 60812:2018";
|
|
@@ -17,7 +17,6 @@ package memo_artifacts_standards_iec_62304 {
|
|
|
17
17
|
private import memo_artifacts_standards_traceability::*;
|
|
18
18
|
|
|
19
19
|
private import memo_core_common::*;
|
|
20
|
-
private import memo_core_common::MemoIdentity;
|
|
21
20
|
part iec62304 : RegulatoryStandard {
|
|
22
21
|
@MemoIdentity { :>> providedId = "STD-IEC-62304"; }
|
|
23
22
|
attribute :>> designation = "IEC 62304:2006+AMD1:2015";
|
|
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iec_62366_1 {
|
|
|
11
11
|
private import memo_artifacts_standards_traceability::*;
|
|
12
12
|
|
|
13
13
|
private import memo_core_common::*;
|
|
14
|
-
private import memo_core_common::MemoIdentity;
|
|
15
14
|
part iec62366_1 : RegulatoryStandard {
|
|
16
15
|
@MemoIdentity { :>> providedId = "STD-IEC-62366-1"; }
|
|
17
16
|
attribute :>> designation = "IEC 62366-1:2015+AMD1:2020";
|
|
@@ -9,7 +9,6 @@ package memo_artifacts_standards_iec_81001_5_1 {
|
|
|
9
9
|
private import memo_artifacts_standards_traceability::*;
|
|
10
10
|
|
|
11
11
|
private import memo_core_common::*;
|
|
12
|
-
private import memo_core_common::MemoIdentity;
|
|
13
12
|
part iec81001_5_1 : RegulatoryStandard {
|
|
14
13
|
@MemoIdentity { :>> providedId = "STD-IEC-81001-5-1"; }
|
|
15
14
|
attribute :>> designation = "IEC 81001-5-1:2021";
|
|
@@ -67,5 +66,5 @@ package memo_artifacts_standards_iec_81001_5_1 {
|
|
|
67
66
|
|
|
68
67
|
|
|
69
68
|
|
|
70
|
-
|
|
69
|
+
|
|
71
70
|
}
|
|
@@ -11,7 +11,6 @@ package memo_artifacts_standards_iso_13485 {
|
|
|
11
11
|
private import memo_artifacts_standards_traceability::*;
|
|
12
12
|
|
|
13
13
|
private import memo_core_common::*;
|
|
14
|
-
private import memo_core_common::MemoIdentity;
|
|
15
14
|
part iso13485 : RegulatoryStandard {
|
|
16
15
|
@MemoIdentity { :>> providedId = "STD-ISO-13485"; }
|
|
17
16
|
attribute :>> designation = "ISO 13485:2016";
|
|
@@ -9,7 +9,6 @@ package memo_artifacts_standards_iso_14971 {
|
|
|
9
9
|
private import memo_artifacts_standards_traceability::*;
|
|
10
10
|
|
|
11
11
|
private import memo_core_common::*;
|
|
12
|
-
private import memo_core_common::MemoIdentity;
|
|
13
12
|
part iso14971 : RegulatoryStandard {
|
|
14
13
|
@MemoIdentity { :>> providedId = "STD-ISO-14971"; }
|
|
15
14
|
attribute :>> designation = "ISO 14971:2019";
|
|
@@ -13,7 +13,6 @@ package memo_artifacts_standards_iso_iec_ieee_42010 {
|
|
|
13
13
|
private import memo_artifacts_standards_traceability::*;
|
|
14
14
|
|
|
15
15
|
private import memo_core_common::*;
|
|
16
|
-
private import memo_core_common::MemoIdentity;
|
|
17
16
|
part isoIecIeee42010 : RegulatoryStandard {
|
|
18
17
|
@MemoIdentity { :>> providedId = "STD-ISO-IEC-IEEE-42010"; }
|
|
19
18
|
attribute :>> designation = "ISO/IEC/IEEE 42010:2022";
|
|
@@ -98,6 +98,7 @@ package memo_artifacts_standards_traceability {
|
|
|
98
98
|
// =========================================================================
|
|
99
99
|
|
|
100
100
|
connection def ConformsTo :> MemoRelationship {
|
|
101
|
+
attribute :>> isTrace = true;
|
|
101
102
|
doc /* Any model element claims conformance to a standard clause.
|
|
102
103
|
* This is the edge the standards traceability matrix and the
|
|
103
104
|
* clause coverage report are computed over. */
|
|
@@ -115,6 +116,7 @@ package memo_artifacts_standards_traceability {
|
|
|
115
116
|
}
|
|
116
117
|
|
|
117
118
|
connection def TracesToDocument :> MemoRelationship {
|
|
119
|
+
attribute :>> isTrace = true;
|
|
118
120
|
doc /* Where the evidence for a clause claim is written down. The target
|
|
119
121
|
* is the existing controlled-artifact type — MEMO does not model a
|
|
120
122
|
* separate Document/DocumentSection family, because
|
|
@@ -45,7 +45,7 @@ empty: "No user need elements defined. Add Need or Requirement elements."
|
|
|
45
45
|
Use cases describing how intended users interact with **{{project.product}}**, drawn from the model:
|
|
46
46
|
|
|
47
47
|
```memo-query
|
|
48
|
-
kind:
|
|
48
|
+
kind: [ClinicalUseCase, SystemUseCase]
|
|
49
49
|
display: table
|
|
50
50
|
columns: name, layer, doc
|
|
51
51
|
sort: name
|
|
@@ -31,7 +31,7 @@ _[TODO: Describe participant demographics, number, and selection criteria]_
|
|
|
31
31
|
This section is generated from the system model. The table below lists the **Test Scenarios** elements currently defined:
|
|
32
32
|
|
|
33
33
|
```memo-query
|
|
34
|
-
kind: [
|
|
34
|
+
kind: [ClinicalUseCase, SystemUseCase, ValidationCase]
|
|
35
35
|
display: table
|
|
36
36
|
columns: name, layer, doc
|
|
37
37
|
sort: name
|
|
@@ -39,7 +39,7 @@ _[TODO: Describe all use environments: clinical, home, ambulatory, etc.]_
|
|
|
39
39
|
This section is generated from the system model. The table below lists the **Use-Related Hazards** elements currently defined:
|
|
40
40
|
|
|
41
41
|
```memo-query
|
|
42
|
-
kind: [
|
|
42
|
+
kind: [ClinicalUseCase, SystemUseCase, OperativeAction]
|
|
43
43
|
display: table
|
|
44
44
|
columns: name, layer, doc
|
|
45
45
|
sort: name
|
|
@@ -23,7 +23,7 @@ This Use-Related Risk Analysis (URRA) identifies use errors and use-related haza
|
|
|
23
23
|
This section is generated from the system model. The table below lists the **Use Scenarios** elements currently defined:
|
|
24
24
|
|
|
25
25
|
```memo-query
|
|
26
|
-
kind: [
|
|
26
|
+
kind: [ClinicalUseCase, SystemUseCase, OperativeAction]
|
|
27
27
|
display: table
|
|
28
28
|
columns: name, layer, doc
|
|
29
29
|
sort: name
|
|
@@ -39,7 +39,7 @@ _[TODO: Describe physical, social, technical environments where the device will
|
|
|
39
39
|
Use cases describing how intended users interact with **{{project.product}}**, drawn from the model:
|
|
40
40
|
|
|
41
41
|
```memo-query
|
|
42
|
-
kind:
|
|
42
|
+
kind: [ClinicalUseCase, SystemUseCase]
|
|
43
43
|
display: table
|
|
44
44
|
columns: name, layer, doc
|
|
45
45
|
sort: name
|
|
@@ -293,6 +293,7 @@ package memo_assurance_cybersecurity {
|
|
|
293
293
|
:>> baseType = realizedByScenarioLinks meta SysML::Usage;
|
|
294
294
|
}
|
|
295
295
|
connection def ImpactsSafety :> MemoRelationship {
|
|
296
|
+
attribute :>> isTrace = true;
|
|
296
297
|
attribute tracePurpose : String;
|
|
297
298
|
end cyberElement : MemoPart :>> source;
|
|
298
299
|
end safetyElement : RiskItem :>> target;
|
|
@@ -20,6 +20,7 @@ package memo_assurance_human_factors {
|
|
|
20
20
|
}
|
|
21
21
|
|
|
22
22
|
connection def CommitsUseError :> MemoRelationship {
|
|
23
|
+
attribute :>> isTrace = true;
|
|
23
24
|
end task : OperativeAction :>> source;
|
|
24
25
|
end useError : UseError :>> target;
|
|
25
26
|
}
|
|
@@ -30,6 +31,7 @@ package memo_assurance_human_factors {
|
|
|
30
31
|
:>> baseType = commitsUseErrorLinks meta SysML::Usage;
|
|
31
32
|
}
|
|
32
33
|
connection def EvaluatesTask :> MemoRelationship {
|
|
34
|
+
attribute :>> isTrace = true;
|
|
33
35
|
end evaluation : MemoEvidence :>> source;
|
|
34
36
|
end task : OperativeAction :>> target;
|
|
35
37
|
}
|
|
@@ -41,13 +43,14 @@ package memo_assurance_human_factors {
|
|
|
41
43
|
}
|
|
42
44
|
|
|
43
45
|
// ── Relations owned by this package ─────────────────────────────
|
|
44
|
-
//
|
|
45
|
-
// types declared here, and core must not depend on a domain
|
|
46
|
-
// The source end is untyped for the reason `Validates`' is: a UI
|
|
47
|
-
// is a part and a task is an action
|
|
48
|
-
//
|
|
49
|
-
//
|
|
46
|
+
// Declared here, not in memo_core_relationships: their ends are typed
|
|
47
|
+
// against types declared here, and core must not depend on a domain
|
|
48
|
+
// package. The source end is untyped for the reason `Validates`' is: a UI
|
|
49
|
+
// element is a part and a task is an action, so no one type spans both. The
|
|
50
|
+
// target is the usability TEST — a validation case — and not the evidence
|
|
51
|
+
// it produces; `ProducesEvidence` links the two.
|
|
50
52
|
connection def TestedByUsability :> MemoRelationship {
|
|
53
|
+
attribute :>> isTrace = true;
|
|
51
54
|
end uiElementOrTask :>> source;
|
|
52
55
|
end usabilityTest : MemoVerificationCase :>> target;
|
|
53
56
|
}
|
|
@@ -10,15 +10,11 @@ package memo_assurance_requirements {
|
|
|
10
10
|
// What a requirement is about: the system, the software, the hardware, or
|
|
11
11
|
// the instructions for use. One axis, and the members are its values.
|
|
12
12
|
//
|
|
13
|
-
//
|
|
14
|
-
//
|
|
15
|
-
// the
|
|
16
|
-
//
|
|
17
|
-
//
|
|
18
|
-
// incomplete by construction (there is no `ifuSpecification`, and there
|
|
19
|
-
// would have to be one for every future pairing), and nothing ever used the
|
|
20
|
-
// four: 250 requirements across the examples say system, software or
|
|
21
|
-
// hardware. A role, if a project needs one, is its own attribute.
|
|
13
|
+
// The design-control ROLE — input versus output, 21 CFR 820.30(c)/(d) and
|
|
14
|
+
// ISO 13485 §7.3.3/§7.3.4 — is a different axis and is not here: multiplied
|
|
15
|
+
// into the subject, a requirement could not say "software" without also
|
|
16
|
+
// committing to a role. A role, if a project needs one, is its own
|
|
17
|
+
// attribute.
|
|
22
18
|
//
|
|
23
19
|
// The instructions for use are neither hardware nor software: the device
|
|
24
20
|
// satisfies such a requirement with words rather than with a part or a
|
|
@@ -33,7 +29,6 @@ package memo_assurance_requirements {
|
|
|
33
29
|
|
|
34
30
|
requirement def Requirement specializes MemoRequirement {
|
|
35
31
|
attribute requirementType : RequirementTypeKind;
|
|
36
|
-
attribute :>> statement : String;
|
|
37
32
|
attribute sourceKind : RequirementSourceKind;
|
|
38
33
|
attribute concernKind : ConcernKind;
|
|
39
34
|
// Editorial state is the inherited `status : ElementStatusKind` — the
|
|
@@ -46,7 +41,7 @@ package memo_assurance_requirements {
|
|
|
46
41
|
attribute assumptionSummary : String;
|
|
47
42
|
attribute guaranteeSummary : String;
|
|
48
43
|
// Authoring notation. `notation` selects the syntactic discipline the
|
|
49
|
-
// `
|
|
44
|
+
// `doc` follows; the slot attributes below carry the parsed clauses
|
|
50
45
|
// so tools can lint pattern conformance and render either style.
|
|
51
46
|
attribute notation : RequirementNotationKind;
|
|
52
47
|
attribute earsPattern : EarsPatternKind; // applies when notation = ears
|
|
@@ -1,8 +1,7 @@
|
|
|
1
|
-
// Needs
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
// (DerivesFrom, Motivates).
|
|
1
|
+
// Needs. A Need is a problem-space expectation stated in stakeholder language;
|
|
2
|
+
// requirements (memo_assurance_requirements) are the solution-space obligations
|
|
3
|
+
// derived from needs. Need specializes the part-based RequirementDriver so it
|
|
4
|
+
// can serve as a typed end of trace relations (DerivesFrom, Motivates).
|
|
6
5
|
package memo_assurance_requirements_needs {
|
|
7
6
|
private import ScalarValues::*;
|
|
8
7
|
|
|
@@ -188,6 +188,7 @@ package memo_assurance_safety_risk_analysis {
|
|
|
188
188
|
:>> baseType = identifiesHazardLinks meta SysML::Usage;
|
|
189
189
|
}
|
|
190
190
|
connection def HasFailureMode :> MemoRelationship {
|
|
191
|
+
attribute :>> isTrace = true;
|
|
191
192
|
end element : MemoPart :>> source;
|
|
192
193
|
end failureMode : FailureMode :>> target;
|
|
193
194
|
}
|
|
@@ -7,7 +7,7 @@ package memo_assurance_safety_risk {
|
|
|
7
7
|
private import memo_core_enumerations::*;
|
|
8
8
|
private import memo_assurance_requirements::*;
|
|
9
9
|
// For HazardRelatedScenario below. Assurance may depend on architecture;
|
|
10
|
-
// the reverse is
|
|
10
|
+
// the reverse is not allowed.
|
|
11
11
|
private import memo_architecture_operational_scenarios::*;
|
|
12
12
|
|
|
13
13
|
// ISO 14971 / IEC 62366-1 risk-analysis input. A model element so hazards,
|
|
@@ -45,15 +45,14 @@ package memo_assurance_safety_risk {
|
|
|
45
45
|
attribute riskLevelMapping : String;
|
|
46
46
|
attribute acceptabilityThresholds : String;
|
|
47
47
|
}
|
|
48
|
-
//
|
|
49
|
-
//
|
|
50
|
-
//
|
|
51
|
-
//
|
|
52
|
-
//
|
|
53
|
-
//
|
|
54
|
-
//
|
|
55
|
-
//
|
|
56
|
-
// affect safety. This is the modelable output of ISO 14971 §5.3.
|
|
48
|
+
// A risk decomposes into the ISO 14971 chain below: a Hazard,
|
|
49
|
+
// SequenceOfEvents, HazardousSituation and Harm are independent elements,
|
|
50
|
+
// not owned by a risk, because the same hazard is the hazard of many risks.
|
|
51
|
+
// A Risk is linked to each by EstimatedFor, and the chain runs through
|
|
52
|
+
// TracesRisk / LeadsToHarm, with ResidualRisk after mitigation. The risk
|
|
53
|
+
// itself is reached by EstimatedFor / ReducedBy / EvaluatedIn below. A
|
|
54
|
+
// device characteristic whose implementation, failure, or misuse can affect
|
|
55
|
+
// safety. This is the modelable output of ISO 14971 §5.3.
|
|
57
56
|
part def SafetyRelatedCharacteristic specializes MemoPart {
|
|
58
57
|
attribute characteristic : String;
|
|
59
58
|
attribute safetyImpact : String;
|
|
@@ -128,6 +127,7 @@ package memo_assurance_safety_risk {
|
|
|
128
127
|
// types declared here, and core must not depend on a domain package.
|
|
129
128
|
// ISO 14971 risk chain — distinct sequence-of-events relations over risk elements.
|
|
130
129
|
connection def TracesRisk :> MemoRelationship {
|
|
130
|
+
attribute :>> isTrace = true;
|
|
131
131
|
end sourceRiskElement : RiskItem :>> source;
|
|
132
132
|
end targetRiskElement : RiskItem :>> target;
|
|
133
133
|
}
|
|
@@ -151,13 +151,11 @@ package memo_assurance_safety_risk {
|
|
|
151
151
|
:>> baseType = leadsToHarmLinks meta SysML::Usage;
|
|
152
152
|
}
|
|
153
153
|
// IEC 62366-1 3.9's hazard-related use scenario: the scenario a hazard can
|
|
154
|
-
// arise in. It is declared HERE
|
|
155
|
-
//
|
|
156
|
-
//
|
|
157
|
-
// assurance may depend on architecture, and the scenario package cannot
|
|
158
|
-
// see `Hazard`. On this side both ends are visible and the dependency runs
|
|
159
|
-
// the direction it already runs.
|
|
154
|
+
// arise in. It is declared HERE because assurance may depend on
|
|
155
|
+
// architecture, and the scenario package cannot see `Hazard`. On this side
|
|
156
|
+
// both ends are visible.
|
|
160
157
|
connection def HazardRelatedScenario :> MemoRelationship {
|
|
158
|
+
attribute :>> isTrace = true;
|
|
161
159
|
end hazard : RiskItem :>> source;
|
|
162
160
|
end scenario : OperativeScenario :>> target;
|
|
163
161
|
}
|
|
@@ -178,12 +176,10 @@ package memo_assurance_safety_risk {
|
|
|
178
176
|
:>> baseType = assessedAgainstLinks meta SysML::Usage;
|
|
179
177
|
}
|
|
180
178
|
// A risk is not a link in the chain (see RiskItem), so TracesRisk cannot
|
|
181
|
-
// reach it
|
|
182
|
-
//
|
|
183
|
-
// (
|
|
184
|
-
//
|
|
185
|
-
// all three as TracesRisk into a Risk and the builder rejected every one.
|
|
186
|
-
// Named from the risk's side, like AssessedAgainst.
|
|
179
|
+
// reach it. These three say which hazardous situation or harm a risk was
|
|
180
|
+
// estimated for (ISO 14971 §5.5), which control reduced it to a residual
|
|
181
|
+
// risk (§7), and which overall evaluation covered that residual (§8). Named
|
|
182
|
+
// from the risk's side, like AssessedAgainst.
|
|
187
183
|
connection def EstimatedFor :> MemoRelationship {
|
|
188
184
|
end risk : Risk :>> source;
|
|
189
185
|
end riskElement : RiskItem :>> target;
|
|
@@ -227,6 +223,7 @@ package memo_assurance_safety_risk {
|
|
|
227
223
|
enum fmeaAction;
|
|
228
224
|
}
|
|
229
225
|
connection def Mitigates :> MemoRelationship {
|
|
226
|
+
attribute :>> isTrace = true;
|
|
230
227
|
attribute mitigationKind : MitigationKind;
|
|
231
228
|
// Untyped: controls/hazards may be item defs (RiskControlMeasure, Hazard, …).
|
|
232
229
|
end control :>> source;
|
|
@@ -12,18 +12,14 @@ package memo_assurance_verification_validation {
|
|
|
12
12
|
private import memo_architecture_functional_functions::*;
|
|
13
13
|
// Verification and validation cases are SysML v2 verification cases
|
|
14
14
|
// (behaviours that check requirements), not verifiable structures — they
|
|
15
|
-
// derive from the MemoVerificationCase foundation, not MemoPart.
|
|
16
|
-
//
|
|
17
|
-
//
|
|
18
|
-
//
|
|
19
|
-
//
|
|
20
|
-
//
|
|
21
|
-
//
|
|
22
|
-
//
|
|
23
|
-
// a second spelling of `status`.
|
|
24
|
-
// Specializes the standard library verification case as well as MEMO's
|
|
25
|
-
// base, rather than shadowing it — see the note on UseCase.
|
|
26
|
-
// Reusable test action, distinct from a case's pass/fail criteria.
|
|
15
|
+
// derive from the MemoVerificationCase foundation, not MemoPart. `status`
|
|
16
|
+
// is NOT redeclared here: every MEMO base carries `status :
|
|
17
|
+
// ElementStatusKind`, the one status vocabulary in MEMO. An EXECUTION state
|
|
18
|
+
// such as "planned" belongs in an attribute of its own (see
|
|
19
|
+
// RiskControlMeasure.verificationStatus). Specializes the standard library
|
|
20
|
+
// verification case as well as MEMO's base, rather than shadowing it — see
|
|
21
|
+
// the note on UseCase. Reusable test action, distinct from a case's
|
|
22
|
+
// pass/fail criteria.
|
|
27
23
|
action def TestStep specializes MemoAction {
|
|
28
24
|
attribute stepAction : String;
|
|
29
25
|
attribute expectedResult : String;
|
|
@@ -74,10 +70,10 @@ package memo_assurance_verification_validation {
|
|
|
74
70
|
attribute acceptanceCriteria : String;
|
|
75
71
|
attribute clinicalContext : String;
|
|
76
72
|
}
|
|
77
|
-
// Operational validation confirms the user's goal is achieved in the
|
|
78
|
-
//
|
|
79
|
-
//
|
|
80
|
-
//
|
|
81
|
-
//
|
|
82
|
-
//
|
|
73
|
+
// Operational validation confirms the user's goal is achieved in the use
|
|
74
|
+
// environment: ValidationCase validates a UseCase. Safety-critical
|
|
75
|
+
// functions must trace to verification (rules/coverage). `ExecutesScenario`
|
|
76
|
+
// is native `perform`: OperativeScenario is an `action def`, so write
|
|
77
|
+
// `perform <scenario>;` inside the verification case, as `InvolvesFunction`
|
|
78
|
+
// already does.
|
|
83
79
|
}
|
|
@@ -11,8 +11,8 @@
|
|
|
11
11
|
//
|
|
12
12
|
// Annotations attach to every metaclass — parts, actions, requirements, views,
|
|
13
13
|
// connections, and MEMO specializations — so CommentsOn, RationaleFor, and
|
|
14
|
-
// NotesOn leave their subject ends untyped,
|
|
15
|
-
// memo_core_relationships.
|
|
14
|
+
// NotesOn leave their subject ends untyped, as SysML's native `dependency`
|
|
15
|
+
// does (see memo_core_relationships).
|
|
16
16
|
package memo_core_annotations {
|
|
17
17
|
private import Metaobjects::SemanticMetadata;
|
|
18
18
|
private import ScalarValues::*;
|