@memoarchitect/ontology 0.16.1 → 0.16.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/examples/connected-patient-monitor/memo.identity.yaml +16 -1
- package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +5 -1
- package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/connected-patient-monitor/model/catalog/viewpoints/{unassigned → logical}/views/connected_patient_monitor_overview.sysml +3 -2
- package/examples/connected-patient-monitor/model/methodology/project.sysml +1 -2
- package/examples/embedded-infusion-pump/memo.identity.yaml +79 -0
- package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +131 -4
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/{unassigned → logical}/views/embedded_infusion_pump_overview.sysml +3 -2
- package/examples/embedded-infusion-pump/model/methodology/project.sysml +1 -2
- package/examples/functional-logical-physical/memo.identity.yaml +31 -1
- package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +72 -1
- package/examples/functional-logical-physical/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/functional-logical-physical/model/catalog/viewpoints/{unassigned → logical}/views/functional_logical_physical_overview.sysml +3 -2
- package/examples/functional-logical-physical/model/methodology/project.sysml +1 -2
- package/examples/gastric-bypass-variants/README.md +20 -0
- package/examples/gastric-bypass-variants/memo.identity.yaml +337 -0
- package/examples/gastric-bypass-variants/memo.package.yaml +5 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/NOTICE.md +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma.sysml +56 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_alimentary.sysml +1376 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_body_proper.sysml +45 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_material_anatomical_entity.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_segment_of_blood_vessel_tree_organ.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_segment_of_hollow_tree_organ.sysml +21 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_boundary_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_cluster.sysml +45 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_set.sysml +30 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_space.sysml +60 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_structure.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_surface.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_arborial_segment_of_arterial_tree_organ.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_arborial_segment_of_venous_tree_organ.sysml +23 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_blood_vessel.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_bona_fide_anatomical_surface.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cardinal_organ_part.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cardinal_tissue_part.sysml +16 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cell_part_cluster.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_developmental_structure.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_immaterial_anatomical_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_material_anatomical_entity.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_nerve.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ.sysml +65 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component_layer.sysml +54 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component_of_lymphatic_tree_organ.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_region.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_segment.sysml +46 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_zone.sysml +34 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_physical_anatomical_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_portion_of_tissue.sysml +106 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_postnatal_anatomical_structure.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_region_of_organ_component.sysml +55 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_region_of_surface_of_organ.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_blood_vessel_tree_organ.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_hollow_tree_organ.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_neural_tree_organ.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_vascular_tree_organ.sysml +39 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_surface_of_organ_region.sysml +19 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_fascial.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_anatomical_structure.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_cardinal_organ_part.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_organ.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_anatomical_cluster.sysml +9 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_nerve.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_postnatal_anatomical_structure.sysml +8 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_respiratory.sysml +14 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/memo.package.yaml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +416 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +53 -0
- package/examples/gastric-bypass-variants/model/methodology/project.sysml +26 -0
- package/examples/gpca-pump/memo.identity.yaml +53 -13
- package/examples/gpca-pump/methodology/gpca_profiles.sysml +4 -15
- package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +23 -10
- package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +7 -6
- package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +74 -28
- package/examples/gpca-pump/model/catalog/gpca_devices.sysml +23 -0
- package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +11 -29
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +30 -20
- package/examples/gpca-pump/model/catalog/gpca_physical.sysml +2 -1
- package/examples/gpca-pump/model/catalog/gpca_standards.sysml +4 -4
- package/examples/gpca-pump/model/catalog/gpca_system.sysml +4 -3
- package/examples/gpca-pump/model/catalog/gpca_trace.sysml +11 -3
- package/examples/gpca-pump/model/catalog/gpca_verification.sysml +12 -12
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +1 -1
- package/examples/{ros-mobile-robot/model/catalog/viewpoints/unassigned → gpca-pump/model/catalog/viewpoints/shared}/viewpoint.sysml +3 -2
- package/examples/gpca-pump/model/catalog/viewpoints/{logical → shared}/views/document_architecture_description_view.sysml +3 -3
- package/examples/gpca-pump/model/catalog/viewpoints/{requirements → shared}/views/document_dhf_index_view.sysml +3 -3
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +1 -1
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +1 -1
- package/examples/gpca-pump/model/methodology/project.sysml +1 -5
- package/examples/ivd-laboratory-system/memo.identity.yaml +43 -0
- package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +16 -1
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/{unassigned → logical}/views/ivd_laboratory_system_overview.sysml +3 -2
- package/examples/ivd-laboratory-system/model/methodology/project.sysml +1 -2
- package/examples/manual-surgical-instrument/memo.identity.yaml +28 -0
- package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -0
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/{unassigned → logical}/views/manual_surgical_instrument_overview.sysml +3 -2
- package/examples/manual-surgical-instrument/model/methodology/project.sysml +1 -2
- package/examples/multidimensional-layers/memo.identity.yaml +34 -0
- package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +34 -4
- package/examples/multidimensional-layers/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/multidimensional-layers/model/catalog/viewpoints/{unassigned → logical}/views/multidimensional_layers_overview.sysml +3 -1
- package/examples/multidimensional-layers/model/methodology/project.sysml +1 -2
- package/examples/nested-architecture-dsm/memo.identity.yaml +27 -0
- package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +9 -9
- package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +64 -0
- package/examples/nested-architecture-dsm/model/catalog/nested_architecture_dsm_system.sysml +5 -0
- package/examples/nested-architecture-dsm/model/catalog/traces.sysml +6 -0
- package/examples/reusable-instrument/memo.identity.yaml +46 -0
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +29 -2
- package/examples/reusable-instrument/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/reusable-instrument/model/catalog/viewpoints/{unassigned → logical}/views/reusable_instrument_overview.sysml +3 -1
- package/examples/reusable-instrument/model/methodology/project.sysml +1 -2
- package/examples/robot-cell-family/memo.identity.yaml +96 -81
- package/examples/robot-cell-family/model/{sos → catalog/sos}/chains.sysml +6 -7
- package/examples/robot-cell-family/model/{sos → catalog/sos}/icds.sysml +1 -1
- package/examples/robot-cell-family/model/{sos → catalog/sos}/sos.sysml +4 -4
- package/examples/robot-cell-family/model/{sos → catalog/sos}/use_cases.sysml +4 -4
- package/examples/robot-cell-family/model/{systems → catalog/systems}/manipulation/manipulation_system.sysml +11 -3
- package/examples/robot-cell-family/model/{systems → catalog/systems}/navigation/navigation_system.sysml +9 -4
- package/examples/robot-cell-family/model/{systems → catalog/systems}/perception/perception_system.sysml +8 -3
- package/examples/robot-cell-family/model/methodology/project.sysml +6 -6
- package/examples/ros-mobile-robot/memo.identity.yaml +22 -1
- package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +89 -26
- package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/ros-mobile-robot/model/catalog/viewpoints/{unassigned → logical}/views/ros_mobile_robot_overview.sysml +3 -1
- package/examples/ros-mobile-robot/model/methodology/project.sysml +1 -2
- package/examples/software-only-medical-device/memo.identity.yaml +46 -0
- package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +34 -1
- package/examples/software-only-medical-device/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/software-only-medical-device/model/catalog/viewpoints/{unassigned → logical}/views/software_only_medical_device_overview.sysml +3 -1
- package/examples/software-only-medical-device/model/methodology/project.sysml +1 -2
- package/examples/surgical-closure-workflow/memo.identity.yaml +103 -0
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +29 -2
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/{unassigned → logical}/views/surgical_closure_workflow_overview.sysml +3 -1
- package/examples/surgical-closure-workflow/model/methodology/project.sysml +1 -2
- package/examples/surgical-robot/memo.identity.yaml +40 -0
- package/examples/surgical-robot/model/catalog/surgical_robot.sysml +6 -1
- package/examples/surgical-robot/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/surgical-robot/model/catalog/viewpoints/{unassigned → logical}/views/surgical_robot_overview.sysml +3 -1
- package/examples/surgical-robot/model/methodology/project.sysml +1 -2
- package/examples/sysml-diagram-samples/README.md +5 -3
- package/examples/sysml-diagram-samples/memo.identity.yaml +548 -391
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/action_flow_view.sysml +2 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/browser_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/context_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/drill_down_view.sysml +30 -5
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/functional_flow_view.sysml +15 -3
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/grid_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/interconnection_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/operational_behaviour_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/package_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/requirements_view.sysml +7 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/sequence_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/standard_activity_view.sysml +2 -3
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/state_transition_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/tree_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/{viewpoints/unassigned/views → samples}/use_case_view.sysml +1 -2
- package/examples/sysml-diagram-samples/model/catalog/sysml_diagram_samples_system.sysml +5 -0
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/viewpoint.sysml +8 -0
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/{unassigned → shared}/views/diagram_samples.sysml +78 -44
- package/examples/sysml-diagram-samples/model/methodology/project.sysml +0 -16
- package/examples/temperature-alarm/memo.identity.yaml +22 -1
- package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +48 -0
- package/examples/temperature-alarm/model/catalog/viewpoints/logical/viewpoint.sysml +8 -0
- package/examples/temperature-alarm/model/catalog/viewpoints/{unassigned → logical}/views/temperature_alarm_overview.sysml +3 -1
- package/examples/temperature-alarm/model/methodology/project.sysml +1 -2
- package/examples/ui-screen-regions/memo.identity.yaml +33 -0
- package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +3 -0
- package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +2 -1
- package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +60 -0
- package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +3 -3
- package/examples/ui-screen-regions/model/catalog/ui_screen_regions_system.sysml +5 -0
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +2 -1
- package/extensions/anatomy/LICENSES/CC-BY-4.0.txt +395 -0
- package/extensions/anatomy/NOTICE.md +20 -0
- package/extensions/anatomy/data/fma-index.json.gz +0 -0
- package/extensions/anatomy/memo.package.yaml +18 -0
- package/extensions/anatomy/src/anatomy_extension.sysml +9 -0
- package/extensions/anatomy/src/presets/memo_extension_anatomy_presets.sysml +12 -0
- package/extensions/anatomy/src/selector/memo_extension_anatomy_selector.sysml +17 -0
- package/extensions/anatomy/src/vocabulary/memo_extension_anatomy_vocabulary.sysml +115 -0
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/clinical/src/clinical_extension.sysml +3 -1
- package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +12 -5
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/messaging/src/messaging_extension.sysml +2 -1
- package/extensions/ros/memo.package.yaml +1 -1
- package/extensions/ros/src/ros_extension.sysml +3 -2
- package/memo.manifest.yaml +1 -0
- package/methodologies/default/memo.package.yaml +1 -1
- package/methodologies/gpca/memo.package.yaml +1 -1
- package/ontology/memo.package.yaml +1 -1
- package/package.json +4 -4
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/behavior/memo_behavior.sysml +19 -8
- package/src/architecture/functional/constraints/memo_constraints.sysml +5 -4
- package/src/architecture/functional/functions/memo_functions.sysml +28 -11
- package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +2 -3
- package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +5 -4
- package/src/architecture/implementation/software/structure/memo_software_structure.sysml +0 -1
- package/src/architecture/implementation/ui/memo_ui.sysml +16 -0
- package/src/architecture/logical/interfaces/memo_interfaces.sysml +9 -3
- package/src/architecture/logical/structure/memo_logical_structure.sysml +9 -0
- package/src/architecture/operational/activities/memo_activities.sysml +22 -2
- package/src/architecture/operational/context/actors/memo_actors.sysml +3 -1
- package/src/architecture/operational/memo_architecture_operational.sysml +1 -0
- package/src/architecture/operational/rollups/memo_rollups.sysml +109 -0
- package/src/architecture/operational/scenarios/memo_scenarios.sysml +22 -6
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +11 -4
- package/src/architecture/operational/workflows/memo_workflows.sysml +62 -27
- package/src/architecture/realization/deployment/memo_deployment.sysml +3 -2
- package/src/architecture/realization/physical/memo_physical_architecture.sysml +11 -4
- package/src/artifacts/configuration_management/memo_configuration_management.sysml +17 -4
- package/src/artifacts/templates/dhf/fda-cybersecurity/security-arch.md +1 -1
- package/src/artifacts/templates/dhf/fda-cybersecurity/threat-model.md +1 -1
- package/src/artifacts/templates/dhf/iec-62304/detailed-design.md +1 -1
- package/src/artifacts/templates/dhf/iec-62304/sad.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/task-analysis.md +7 -7
- package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
- package/src/artifacts/templates/dhf/system/sad.md +1 -1
- package/src/artifacts/templates/dhf/system/standards-checklist.md +2 -2
- package/src/assurance/requirements/needs/memo_needs.sysml +8 -0
- package/src/assurance/safety_risk/memo_risk.sysml +15 -0
- package/src/assurance/verification_validation/memo_assurance.sysml +25 -0
- package/src/core/common/memo_common.sysml +41 -0
- package/src/core/enumerations/memo_enumerations.sysml +23 -5
- package/src/core/relationships/memo_relationships.sysml +5 -0
- package/src/core/relationships/memo_workspace_membership.sysml +12 -0
- package/src/core/stdlib/analysis/analysis.sysml +11 -0
- package/src/core/stdlib/functions/functions.sysml +2 -0
- package/src/core/stdlib/money/money.sysml +53 -0
- package/src/core/stdlib/quantities/quantities.sysml +24 -0
- package/src/memo_namespaces.sysml +21 -0
- package/src/methodology/core/memo_core.sysml +2 -12
- package/src/methodology/profiles/memo_profiles.sysml +10 -9
- package/src/methodology/workflow/memo_workflow.sysml +16 -6
- package/src/rules/closure/closure_rules.sysml +46 -3
- package/src/rules/ontology/ontology_invariants.sysml +183 -30
- package/src/rules/quantitative/quantitative_rules.sysml +29 -0
- package/src/viewpoints/clinical/clinical_viewpoint.sysml +1 -1
- package/src/viewpoints/context/context_viewpoint.sysml +1 -1
- package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +1 -1
- package/src/viewpoints/definitions/memo_view_layout.sysml +9 -0
- package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +1 -1
- package/src/viewpoints/functional/functional_viewpoint.sysml +1 -1
- package/src/viewpoints/logical/logical_viewpoint.sysml +1 -1
- package/src/viewpoints/operational/operational_viewpoint.sysml +1 -1
- package/src/viewpoints/physical/physical_viewpoint.sysml +1 -1
- package/src/viewpoints/requirements/requirements_viewpoint.sysml +1 -1
- package/src/viewpoints/risk/risk_viewpoint.sysml +1 -1
- package/src/viewpoints/software/software_viewpoint.sysml +1 -1
- package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +14 -3
- package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +1 -1
- package/src/viewpoints/usability/usability_viewpoint.sysml +1 -1
- package/src/viewpoints/verification/verification_viewpoint.sysml +1 -1
- package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
- package/stage1/syside-f7095495f0f20200e0c34176.ids.gz +0 -0
- package/stage1/syside-f7095495f0f20200e0c34176.json.gz +0 -0
- package/examples/connected-patient-monitor/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/functional-logical-physical/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/multidimensional-layers/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/reusable-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/software-only-medical-device/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/surgical-robot/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -74
- package/examples/temperature-alarm/model/catalog/viewpoints/unassigned/viewpoint.sysml +0 -9
- package/stage1/syside-27179e19589cf7a97f4dd15a.ids.gz +0 -0
- package/stage1/syside-27179e19589cf7a97f4dd15a.json.gz +0 -0
- package/stage1/syside-67f92dc96ba75cd05b5c8d13.ids.gz +0 -0
- package/stage1/syside-67f92dc96ba75cd05b5c8d13.json.gz +0 -0
- /package/examples/robot-cell-family/model/{shared → catalog/shared}/shared.sysml +0 -0
- /package/examples/sysml-diagram-samples/model/{sysml_v2_activity_example.sysml → catalog/sysml_v2_activity_example.sysml} +0 -0
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
// Roll-ups of a level-2 procedure flow (plan decision 9). A number is entered once, on an
|
|
2
|
+
// activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of its `instruments`),
|
|
3
|
+
// and every figure above it is derived here: a scenario, a procedure, a variant. A `TradeStudy`
|
|
4
|
+
// compares variants by these, so nothing a study reads is typed in twice.
|
|
5
|
+
//
|
|
6
|
+
// ─── Traversal ──────────────────────────────────────────────────────────
|
|
7
|
+
// `ActivitiesOf` is the one place that decides which activities count, and every roll-up reads
|
|
8
|
+
// it. It reads `enclosedPerformances`, which holds a step's composite `subactions`, the activities
|
|
9
|
+
// it `perform`s by reference (a scenario that performs activities declared once and used in
|
|
10
|
+
// several), and the `includedUseCases` of a use case, which are `enclosedPerformances` and not
|
|
11
|
+
// `subactions`, so a walk over `subactions` alone would miss every reusable system use case. It
|
|
12
|
+
// descends only into what can hold activities: an activity, a scenario or a use case. A
|
|
13
|
+
// `perform` of a `SystemFunction` is therefore never entered, which is the point of the stop:
|
|
14
|
+
// level 3 is how the system does its share, not more time, and following it would count the
|
|
15
|
+
// same work twice.
|
|
16
|
+
//
|
|
17
|
+
// ─── Sums ───────────────────────────────────────────────────────────────
|
|
18
|
+
// Sums and products use `QuantityCalculations`, so a cost, a duration and a probability stay
|
|
19
|
+
// quantities with units; money is `memo_core_stdlib_money`, in the project's one currency.
|
|
20
|
+
// A cost is the activity's duration times each instrument's capacity cost rate, plus each
|
|
21
|
+
// instrument's unit cost. Parallel branches are each paid for, because each resource used is
|
|
22
|
+
// paid for. Time is the sum along the path; a fork whose branches overlap in time is not yet
|
|
23
|
+
// reduced to its longest branch here.
|
|
24
|
+
//
|
|
25
|
+
// `memo evaluate` runs them from these bodies over the built model (memo-tools, analysis/calc), and a
|
|
26
|
+
// `TradeStudy` reads the results, so no figure is written twice. Units follow the SysML library's own
|
|
27
|
+
// conversions, so minutes and hours add and a rate times a duration is an amount.
|
|
28
|
+
package memo_architecture_operational_rollups {
|
|
29
|
+
private import ScalarValues::*;
|
|
30
|
+
private import memo_core_stdlib_functions::*;
|
|
31
|
+
private import memo_core_stdlib_quantities::*;
|
|
32
|
+
private import memo_core_stdlib_money::*;
|
|
33
|
+
private import memo_core_common::*;
|
|
34
|
+
private import memo_architecture_operational_activities::*;
|
|
35
|
+
private import memo_architecture_operational_scenarios::*;
|
|
36
|
+
private import memo_architecture_operational_workflows::*;
|
|
37
|
+
private import memo_architecture_operational_use_cases::*;
|
|
38
|
+
|
|
39
|
+
calc def ActivitiesOf {
|
|
40
|
+
in owner : MemoAction[1];
|
|
41
|
+
return activities : OperativeAction[0..*] = (
|
|
42
|
+
owner.enclosedPerformances->select { in inner : MemoAction[1]; inner istype OperativeAction },
|
|
43
|
+
owner.enclosedPerformances
|
|
44
|
+
->select { in inner : MemoAction[1];
|
|
45
|
+
inner istype OperativeAction or inner istype OperativeScenario or inner istype UseCase }
|
|
46
|
+
->collect { in inner : MemoAction[1]; ActivitiesOf(inner) });
|
|
47
|
+
}
|
|
48
|
+
|
|
49
|
+
calc def ActivityCost {
|
|
50
|
+
in activity : OperativeAction[1];
|
|
51
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum((
|
|
52
|
+
activity.instruments.capacityCostRate->collect { in rate : CostRateValue[1]; (rate * activity.expectedDuration) as MoneyValue },
|
|
53
|
+
activity.instruments.unitCost));
|
|
54
|
+
}
|
|
55
|
+
|
|
56
|
+
calc def ScenarioCost {
|
|
57
|
+
in scenario : MemoAction[1];
|
|
58
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum(
|
|
59
|
+
ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; ActivityCost(activity) });
|
|
60
|
+
}
|
|
61
|
+
|
|
62
|
+
calc def ScenarioDuration {
|
|
63
|
+
in scenario : MemoAction[1];
|
|
64
|
+
return duration : DurationValue[1] = QuantityCalculations::sum(
|
|
65
|
+
ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; activity.expectedDuration });
|
|
66
|
+
}
|
|
67
|
+
|
|
68
|
+
calc def ScenarioSuccess {
|
|
69
|
+
in scenario : MemoAction[1];
|
|
70
|
+
return success : ProbabilityValue[1] = QuantityCalculations::product(
|
|
71
|
+
ActivitiesOf(scenario).plannedSuccessProbability);
|
|
72
|
+
}
|
|
73
|
+
|
|
74
|
+
calc def ProcedureCost {
|
|
75
|
+
in workflow : OperationalWorkflow[1];
|
|
76
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum((
|
|
77
|
+
workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
|
|
78
|
+
->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioCost(s)) as MoneyValue },
|
|
79
|
+
workflow.perProcedureCost));
|
|
80
|
+
}
|
|
81
|
+
|
|
82
|
+
calc def ProcedureDuration {
|
|
83
|
+
in workflow : OperationalWorkflow[1];
|
|
84
|
+
return duration : DurationValue[1] = QuantityCalculations::sum(
|
|
85
|
+
workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
|
|
86
|
+
->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioDuration(s)) as DurationValue });
|
|
87
|
+
}
|
|
88
|
+
|
|
89
|
+
calc def ScenarioWeight {
|
|
90
|
+
in scenario : OperativeScenario[1];
|
|
91
|
+
return weight : Real[1] = if scenario.scenarioKind == ScenarioKind::nominal ? 1.0 else scenario.likelihood;
|
|
92
|
+
}
|
|
93
|
+
|
|
94
|
+
calc def HighDemandCount {
|
|
95
|
+
in assessments : TaskDifficultyAssessment[0..*];
|
|
96
|
+
return count : Natural[1] = assessments->select { in a : TaskDifficultyAssessment[1];
|
|
97
|
+
a.overallDifficulty == DemandLevelKind::high or a.overallDifficulty == DemandLevelKind::extreme }->size();
|
|
98
|
+
}
|
|
99
|
+
|
|
100
|
+
calc def HighestDemand {
|
|
101
|
+
in assessments : TaskDifficultyAssessment[0..*];
|
|
102
|
+
return demand : DemandLevelKind[1] =
|
|
103
|
+
if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::extreme } ? DemandLevelKind::extreme
|
|
104
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::high } ? DemandLevelKind::high
|
|
105
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::moderate } ? DemandLevelKind::moderate
|
|
106
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::low } ? DemandLevelKind::low
|
|
107
|
+
else DemandLevelKind::minimal;
|
|
108
|
+
}
|
|
109
|
+
}
|
|
@@ -1,8 +1,16 @@
|
|
|
1
|
-
// Scenario foundation. A scenario is
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
// scenario
|
|
1
|
+
// Scenario foundation. A scenario is the stepwise sequence of actions that
|
|
2
|
+
// completes a workflow's body of work, with its pre- and post-conditions: IEC
|
|
3
|
+
// 62366-1's use scenario, a sequence of tasks by a user in a use environment
|
|
4
|
+
// and the device's responses. It is where the steps are; the workflow it is
|
|
5
|
+
// nested in is the analysis of that work. A scenario is nominal or alternate,
|
|
6
|
+
// so a nominal scenario and its alternates are siblings in their workflow. A
|
|
7
|
+
// step used in several scenarios is one action def used in each, never copied.
|
|
8
|
+
// An actual or hypothetical execution is a native usage of the scenario, not a
|
|
9
|
+
// separate element.
|
|
10
|
+
//
|
|
11
|
+
// A scenario of a level-1 use case lists steps; a scenario of a level-2 use case lists activities
|
|
12
|
+
// (memo_architecture_operational_activities), and `likelihood` is per variant, so a robot and a
|
|
13
|
+
// laparoscopic tower have different conversion rates for the same alternate scenario.
|
|
6
14
|
package memo_architecture_operational_scenarios {
|
|
7
15
|
private import Metaobjects::SemanticMetadata;
|
|
8
16
|
private import ScalarValues::*;
|
|
@@ -23,7 +31,12 @@ package memo_architecture_operational_scenarios {
|
|
|
23
31
|
enum alternate;
|
|
24
32
|
}
|
|
25
33
|
|
|
26
|
-
|
|
34
|
+
// A scenario is a `MemoConstrainedOccurrence`: it carries the native `precondition` and
|
|
35
|
+
// `postcondition` constraints a function does, redefined with an expression
|
|
36
|
+
// (`constraint :>> precondition { level >= 0 }`). `preCondition` and `postCondition` below are the
|
|
37
|
+
// same two conditions in words, for what no expression says ("patient assessed"); the constraint
|
|
38
|
+
// is for one that can be checked.
|
|
39
|
+
action def OperativeScenario specializes MemoAction, MemoConstrainedOccurrence {
|
|
27
40
|
attribute scenarioKind : ScenarioKind default ScenarioKind::nominal;
|
|
28
41
|
attribute initialState : String;
|
|
29
42
|
attribute trigger : String;
|
|
@@ -31,6 +44,9 @@ package memo_architecture_operational_scenarios {
|
|
|
31
44
|
attribute expectedResult : String;
|
|
32
45
|
attribute postCondition : String;
|
|
33
46
|
attribute pathSummary : String;
|
|
47
|
+
// How likely this path is, among the workflow's scenarios, for the variant it belongs to
|
|
48
|
+
// (a robot and a laparoscopic tower do not convert to open at the same rate); level 2 only.
|
|
49
|
+
attribute likelihood : ProbabilityValue[0..1];
|
|
34
50
|
|
|
35
51
|
// The workflow this scenario belongs to is the one it is nested in
|
|
36
52
|
// (a `HasScenario` relation was removed for that reason); a
|
|
@@ -1,6 +1,17 @@
|
|
|
1
1
|
// Use cases (§5). A UseCase is a goal a person or organization wants to
|
|
2
2
|
// achieve with system support — there is no separate Goal class. Clinical,
|
|
3
3
|
// service, manufacturing, and development use cases specialize the same base.
|
|
4
|
+
//
|
|
5
|
+
// A use case is at one of two levels, and the level is its subject's type, not a field.
|
|
6
|
+
// Level 1 is clinical: the subject is an `OperationalEntity` (the care team, the setting), the
|
|
7
|
+
// use case names no product, and nothing on its workflow, scenarios or steps carries a number.
|
|
8
|
+
// Level 2 is a black box: the subject is a `System` or `SystemOfSystems`, one variant of a
|
|
9
|
+
// platform, and its procedure flow carries every number (time, cost, success, likelihood) for
|
|
10
|
+
// that variant. A level-2 activity refines the level-1 step it carries out by upward
|
|
11
|
+
// `#refinement`, so one level-1 use case is the shared baseline of every variant. Reusable
|
|
12
|
+
// services of the system (dock, teleoperate) are level-2 use cases that a procedure flow
|
|
13
|
+
// `include`s, never copies. The level below, how the system does its share, is the Functional
|
|
14
|
+
// layer, reached by `perform`.
|
|
4
15
|
package memo_architecture_operational_use_cases {
|
|
5
16
|
private import Metaobjects::SemanticMetadata;
|
|
6
17
|
private import ScalarValues::*;
|
|
@@ -35,10 +46,6 @@ package memo_architecture_operational_use_cases {
|
|
|
35
46
|
attribute postCondition : String;
|
|
36
47
|
// clinical / service / manufacturing / development
|
|
37
48
|
attribute useCaseKind : UseCaseKind;
|
|
38
|
-
// A system use case that no clinical use case includes is a finding (rule CR-ONT-086)
|
|
39
|
-
// unless it says so: set this for a use case that is deliberately carried out alone,
|
|
40
|
-
// such as a service procedure. It is not a second kind of use case.
|
|
41
|
-
attribute standalone : Boolean;
|
|
42
49
|
|
|
43
50
|
// The device or system under consideration supports the goal. Native
|
|
44
51
|
// `subject`, not `ref` (R10-S6): a use case needs an explicit subject
|
|
@@ -1,29 +1,40 @@
|
|
|
1
|
-
// First-class operational workflows.
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
//
|
|
6
|
-
//
|
|
1
|
+
// First-class operational workflows. A use case is the user's goal; an
|
|
2
|
+
// OperationalWorkflow is the ANALYSIS of one body of work that pursues it: who
|
|
3
|
+
// does it, where, with what equipment, between which entry and completion
|
|
4
|
+
// conditions, and (from the needs that point at it) what is needed and what
|
|
5
|
+
// is not yet met. It may exist before any device is selected. It is not a
|
|
6
|
+
// sequence of steps: the steps are its scenarios' (memo_architecture_operational_scenarios),
|
|
7
|
+
// each one stepwise path with pre- and post-conditions, and an occurrence is
|
|
8
|
+
// one execution of a scenario.
|
|
9
|
+
//
|
|
10
|
+
// IEC 62366-1 is the guide: the workflow is the use specification (5.1) scoped
|
|
11
|
+
// to one body of work, with the UI characteristics related to safety (5.2) and
|
|
12
|
+
// the known use-related hazards (5.3) its analysis draws on; a scenario is the
|
|
13
|
+
// standard's use scenario, a sequence of tasks by a user in a use environment.
|
|
14
|
+
// The standard has no "workflow"; this is MEMO's.
|
|
15
|
+
//
|
|
16
|
+
// So a workflow is a part, not an action: an action's nested actions are all
|
|
17
|
+
// performed, and a workflow's scenarios are alternatives. It owns its scenarios
|
|
18
|
+
// as nested actions, the way a part owns what it can do.
|
|
19
|
+
//
|
|
20
|
+
// A workflow's equipment is `WorkflowResource` parts, each a `MemoResource` with its cost rate.
|
|
21
|
+
// A generic resource is specialized by the product that fills it (`part def ProductXStapler :>
|
|
22
|
+
// Stapler`), which is why there is no `resolvedProduct` reference: native specialization says it.
|
|
7
23
|
package memo_architecture_operational_workflows {
|
|
8
24
|
private import Metaobjects::SemanticMetadata;
|
|
9
25
|
private import ScalarValues::*;
|
|
10
26
|
|
|
27
|
+
private import memo_core_stdlib_quantities::*;
|
|
28
|
+
private import memo_core_stdlib_money::*;
|
|
29
|
+
|
|
11
30
|
private import memo_core_common::*;
|
|
12
31
|
private import memo_core_enumerations::*;
|
|
13
32
|
private import memo_core_relationships::*;
|
|
14
33
|
private import memo_architecture_operational_context_actors::*;
|
|
34
|
+
private import memo_architecture_operational_context_use_context::*;
|
|
15
35
|
private import memo_architecture_operational_activities::*;
|
|
16
36
|
private import memo_architecture_operational_use_cases::*;
|
|
17
37
|
|
|
18
|
-
// As-is vs. to-be vs. contingency is a typed dimension of the workflow,
|
|
19
|
-
// not a name suffix.
|
|
20
|
-
enum def WorkflowStateKind {
|
|
21
|
-
enum asIs;
|
|
22
|
-
enum toBe;
|
|
23
|
-
enum contingency;
|
|
24
|
-
enum deprecated;
|
|
25
|
-
}
|
|
26
|
-
|
|
27
38
|
enum def StepTransformationKind {
|
|
28
39
|
enum preserves;
|
|
29
40
|
enum automates;
|
|
@@ -31,13 +42,26 @@ package memo_architecture_operational_workflows {
|
|
|
31
42
|
enum eliminates;
|
|
32
43
|
}
|
|
33
44
|
|
|
34
|
-
|
|
35
|
-
|
|
45
|
+
part def OperationalWorkflow specializes MemoPart {
|
|
46
|
+
// Where the body of work starts and ends. A scenario's pre- and
|
|
47
|
+
// post-conditions are its own path's, inside these.
|
|
36
48
|
attribute entryCondition : String;
|
|
37
49
|
attribute completionCondition : String;
|
|
38
50
|
attribute recoveryPathSummary : String;
|
|
39
51
|
attribute timingConstraints : String;
|
|
40
|
-
|
|
52
|
+
// What one procedure costs apart from its activities (set-up, capital per case); a number,
|
|
53
|
+
// so it is set on a level-2 variant's workflow, never on level 1.
|
|
54
|
+
attribute perProcedureCost : MoneyValue[0..1];
|
|
55
|
+
// The context and environment of use (IEC 62366-1 5.1), as modelled
|
|
56
|
+
// elements rather than a sentence: the care setting, jurisdiction and
|
|
57
|
+
// connected use are UseContext's, lighting and noise UseEnvironment's.
|
|
58
|
+
ref useContext : UseContext[0..1];
|
|
59
|
+
ref useEnvironment : UseEnvironment[0..1];
|
|
60
|
+
// The equipment and other resources the work needs are the workflow's
|
|
61
|
+
// own `WorkflowResource` parts. Users are not listed: they are who
|
|
62
|
+
// `perform`s its scenarios' steps. Needs point here (Need.workflow);
|
|
63
|
+
// the workflow does not list them, because assurance may depend on
|
|
64
|
+
// architecture and not the reverse.
|
|
41
65
|
}
|
|
42
66
|
|
|
43
67
|
// The use case a workflow realizes. Many workflows may trace to one use
|
|
@@ -75,12 +99,22 @@ package memo_architecture_operational_workflows {
|
|
|
75
99
|
attribute informationTransferred : String[0..1];
|
|
76
100
|
}
|
|
77
101
|
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
102
|
+
enum def ResourceKind {
|
|
103
|
+
enum instrument;
|
|
104
|
+
enum equipment;
|
|
105
|
+
enum consumable;
|
|
106
|
+
enum material;
|
|
107
|
+
enum information;
|
|
108
|
+
enum space;
|
|
109
|
+
}
|
|
110
|
+
|
|
111
|
+
// Resources a workflow requires: instruments, equipment, consumables, materials, information
|
|
112
|
+
// or space, by reference. Owned by the workflow as its parts. A staff member is not one: that
|
|
113
|
+
// is a `User`, which is a `MemoResource` of its own.
|
|
114
|
+
part def WorkflowResource specializes MemoResource {
|
|
115
|
+
attribute resourceKind : ResourceKind;
|
|
116
|
+
attribute quantity : Natural;
|
|
117
|
+
attribute reprocessingDuration : DurationValue[0..1];
|
|
84
118
|
}
|
|
85
119
|
|
|
86
120
|
// ── Workflow-level relationships ─────────────────────────────
|
|
@@ -92,9 +126,10 @@ package memo_architecture_operational_workflows {
|
|
|
92
126
|
// that each implied a different target type are now two typed refs plus
|
|
93
127
|
// this one plain relation.
|
|
94
128
|
|
|
95
|
-
// ──
|
|
96
|
-
// Transforms
|
|
97
|
-
//
|
|
129
|
+
// ── Technique change ─────────────────────────────────────────
|
|
130
|
+
// Transforms relates a step of one level-1 technique variant of a workflow to the step of
|
|
131
|
+
// the other that preserves, automates, augments or eliminates it. Two platforms' activities
|
|
132
|
+
// correspond through the level-1 step both refine, not through this.
|
|
98
133
|
enum def TransformKind {
|
|
99
134
|
enum step;
|
|
100
135
|
enum workflow;
|
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
// other way and between different things. Software reaches a node through
|
|
10
10
|
// DeploysTo.
|
|
11
11
|
package memo_architecture_realization_deployment {
|
|
12
|
+
private import memo_core_stdlib_quantities::*;
|
|
12
13
|
private import Metaobjects::SemanticMetadata;
|
|
13
14
|
private import ScalarValues::*;
|
|
14
15
|
// The standard's allocation base, which the two AADL bindings below root
|
|
@@ -139,7 +140,7 @@ package memo_architecture_realization_deployment {
|
|
|
139
140
|
// (MemoInterface, PhysicalComponent) so one binding serves every layer.
|
|
140
141
|
allocation def ConnectionBinding :> MemoRelationship, Allocations::Allocation {
|
|
141
142
|
attribute allocatedBandwidth : String;
|
|
142
|
-
attribute mediumLatencyMs :
|
|
143
|
+
attribute mediumLatencyMs : DurationValue;
|
|
143
144
|
end boundExchange : MemoInterface :>> source;
|
|
144
145
|
end medium : PhysicalComponent :>> target;
|
|
145
146
|
}
|
|
@@ -174,7 +175,7 @@ package memo_architecture_realization_deployment {
|
|
|
174
175
|
// hardware binding it traverses. `latencyBudgetMs` and `analysisPurpose`
|
|
175
176
|
// (latency | fault-propagation | security) drive the AADL-style analysis.
|
|
176
177
|
part def EndToEndFlow specializes MemoPart {
|
|
177
|
-
attribute latencyBudgetMs :
|
|
178
|
+
attribute latencyBudgetMs : DurationValue;
|
|
178
179
|
attribute analysisPurpose : String;
|
|
179
180
|
ref sourceFunction : MemoFunction[0..1];
|
|
180
181
|
ref sinkFunction : MemoFunction[0..1];
|
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
// software runs on and the ports the outside world plugs into. The broader
|
|
3
3
|
// physical taxonomy lives in memo_architecture_implementation_hardware_structure.
|
|
4
4
|
package memo_architecture_realization_physical {
|
|
5
|
+
private import memo_core_stdlib_quantities::*;
|
|
5
6
|
private import ScalarValues::*;
|
|
6
7
|
|
|
7
8
|
private import memo_core_common::*;
|
|
@@ -16,7 +17,7 @@ package memo_architecture_realization_physical {
|
|
|
16
17
|
part def ProcessingNode specializes PhysicalElement {
|
|
17
18
|
attribute nodeKind : ProcessingNodeKind;
|
|
18
19
|
attribute processorArchitecture : String;
|
|
19
|
-
attribute memoryMB :
|
|
20
|
+
attribute memoryMB : StorageCapacityValue;
|
|
20
21
|
attribute operatingSystem : String;
|
|
21
22
|
attribute safetyPartition : Boolean;
|
|
22
23
|
attribute redundancyKind : String;
|
|
@@ -26,7 +27,7 @@ package memo_architecture_realization_physical {
|
|
|
26
27
|
}
|
|
27
28
|
part def MemoryDevice specializes PhysicalElement {
|
|
28
29
|
attribute memoryKind : String;
|
|
29
|
-
attribute capacityMB :
|
|
30
|
+
attribute capacityMB : StorageCapacityValue;
|
|
30
31
|
attribute nonVolatile : Boolean;
|
|
31
32
|
}
|
|
32
33
|
// A physical boundary feature: the connector the outside world plugs into.
|
|
@@ -101,8 +102,8 @@ package memo_architecture_realization_physical {
|
|
|
101
102
|
attribute signalingKind : SignalingKind;
|
|
102
103
|
attribute mediumKind : PhysicalMediumKind;
|
|
103
104
|
attribute electricalStandard : String;
|
|
104
|
-
attribute nominalVoltageV :
|
|
105
|
-
attribute nominalCurrentA :
|
|
105
|
+
attribute nominalVoltageV : ElectricPotentialDifferenceValue[0..1];
|
|
106
|
+
attribute nominalCurrentA : ElectricCurrentValue[0..1];
|
|
106
107
|
attribute bitRateBps : String;
|
|
107
108
|
attribute signalRange : String;
|
|
108
109
|
attribute connectorStandard : String;
|
|
@@ -119,4 +120,10 @@ package memo_architecture_realization_physical {
|
|
|
119
120
|
attribute minValue : String;
|
|
120
121
|
attribute maxValue : String;
|
|
121
122
|
}
|
|
123
|
+
|
|
124
|
+
// The concrete flow a model types its physical flows by; a concrete `flow def` declares its two ends.
|
|
125
|
+
flow def PhysicalTransfer specializes PhysicalFlow {
|
|
126
|
+
end source;
|
|
127
|
+
end target;
|
|
128
|
+
}
|
|
122
129
|
}
|
|
@@ -40,8 +40,8 @@ package memo_artifacts_configuration_management {
|
|
|
40
40
|
// `#Contains` the records of the system releases it pins, and is the validated configuration:
|
|
41
41
|
// `#VerifiedByCase` names the verification cases that validated it.
|
|
42
42
|
part def ReleaseRecord :> MemoPart {
|
|
43
|
-
attribute partNumber : String[1];
|
|
44
|
-
attribute revision : String[1];
|
|
43
|
+
attribute :>> partNumber : String[1];
|
|
44
|
+
attribute :>> revision : String[1];
|
|
45
45
|
attribute softwareVersion : String[0..1];
|
|
46
46
|
attribute codeTag : String[0..1];
|
|
47
47
|
// The commit of the model this release was built from. A record cannot hold the hash of the
|
|
@@ -81,8 +81,15 @@ package memo_artifacts_configuration_management {
|
|
|
81
81
|
// documents it must have. It replaces `ModelMethodBinding.regulatoryRegime`, which stated one regime set
|
|
82
82
|
// for a whole model and is read only when the model declares no device.
|
|
83
83
|
//
|
|
84
|
-
//
|
|
85
|
-
//
|
|
84
|
+
// The device's other two links (plan O6), both typed dependencies like `Covers`:
|
|
85
|
+
//
|
|
86
|
+
// #IntendedUseOf dependency from pumpIntendedUse to deviceFda;
|
|
87
|
+
// #UsedWith dependency from deviceFda to deviceInfusionSet;
|
|
88
|
+
//
|
|
89
|
+
// `IntendedUseOf` runs from the intended use (a `requirement def`, `IntendedUse`) to the device, as its
|
|
90
|
+
// name reads; a device can have one per indication. `UsedWith` runs between regulated devices: the
|
|
91
|
+
// compatible devices and accessories that are themselves approved. An accessory that is not a device is
|
|
92
|
+
// not a target (decided 2026-10-25, user).
|
|
86
93
|
part def RegulatedDevice :> MemoPart {
|
|
87
94
|
attribute jurisdiction : RegulatoryRegimeKind[1];
|
|
88
95
|
attribute submissionId : String[0..1];
|
|
@@ -91,6 +98,12 @@ package memo_artifacts_configuration_management {
|
|
|
91
98
|
metadata def Covers :> MemoTypedDependency {
|
|
92
99
|
doc /* `#Covers dependency from <device>, to <record>, <record>;` The approval covers these system releases. */
|
|
93
100
|
}
|
|
101
|
+
metadata def IntendedUseOf :> MemoTypedDependency {
|
|
102
|
+
doc /* `#IntendedUseOf dependency from <intended use> to <device>;` The intended use (a requirement) states what this device is for. */
|
|
103
|
+
}
|
|
104
|
+
metadata def UsedWith :> MemoTypedDependency {
|
|
105
|
+
doc /* `#UsedWith dependency from <device> to <device>, <device>;` The device is used with these regulated devices (compatible devices and approved accessories). */
|
|
106
|
+
}
|
|
94
107
|
|
|
95
108
|
// A project is a change set in an iteration (plan O7): the work that produces releases. It holds a link to
|
|
96
109
|
// where the work is tracked and nothing else; the merge request is the approval. It FEEDS the release records
|
|
@@ -31,7 +31,7 @@ This section describes the security architecture of **{{project.product}}**. The
|
|
|
31
31
|
Define the trusted zones, the communication paths crossing zone boundaries, and the protection applied at each crossing.
|
|
32
32
|
|
|
33
33
|
```memo-query
|
|
34
|
-
kind:
|
|
34
|
+
kind: [LogicalInterface, PhysicalInterface]
|
|
35
35
|
display: table
|
|
36
36
|
columns: name, layer, doc
|
|
37
37
|
sort: name
|
|
@@ -37,7 +37,7 @@ empty: "No system assets defined."
|
|
|
37
37
|
Entry points and externally reachable interfaces constituting the attack surface, drawn from the model:
|
|
38
38
|
|
|
39
39
|
```memo-query
|
|
40
|
-
kind:
|
|
40
|
+
kind: [LogicalInterface, PhysicalInterface]
|
|
41
41
|
display: table
|
|
42
42
|
columns: name, layer, doc
|
|
43
43
|
sort: name
|
|
@@ -23,11 +23,11 @@ Documents task analysis for **{{project.product}}** per IEC 62366-1:2015+AMD1:20
|
|
|
23
23
|
This section is generated from the system model. The table below lists the user tasks and task steps currently defined:
|
|
24
24
|
|
|
25
25
|
```memo-query
|
|
26
|
-
kind: [
|
|
26
|
+
kind: [OperativeAction]
|
|
27
27
|
display: table
|
|
28
28
|
columns: name, layer, doc
|
|
29
29
|
sort: name
|
|
30
|
-
empty: "No
|
|
30
|
+
empty: "No OperativeAction elements defined."
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
### 2.1 Task Boundary — What Each Task Acts Through
|
|
@@ -35,12 +35,12 @@ empty: "No UserTask or TaskStep elements defined."
|
|
|
35
35
|
A task is cyber-physical when the element it is allocated to is a user interface, an operator interface element, or a port. The set below is derived by traversing `allocatedTo` from the tasks above, so it follows the model rather than the wording of a task name.
|
|
36
36
|
|
|
37
37
|
```memo-query
|
|
38
|
-
kind: [
|
|
38
|
+
kind: [OperativeAction]
|
|
39
39
|
traverse: outgoing allocatedTo
|
|
40
40
|
display: table
|
|
41
41
|
columns: name, kind, layer, doc
|
|
42
42
|
sort: name
|
|
43
|
-
empty: "No tasks are allocated to an interface element. Add AllocatedTo links from
|
|
43
|
+
empty: "No tasks are allocated to an interface element. Add AllocatedTo links from the OperativeAction to the UI, operator interface, or port the task acts through."
|
|
44
44
|
```
|
|
45
45
|
|
|
46
46
|
### 2.2 Operator-Facing Boundary Elements
|
|
@@ -48,7 +48,7 @@ empty: "No tasks are allocated to an interface element. Add AllocatedTo links fr
|
|
|
48
48
|
The user-facing elements a task can act through, hardware and software alike:
|
|
49
49
|
|
|
50
50
|
```memo-query
|
|
51
|
-
kind: [UserInterface, OperatorInterfaceElement,
|
|
51
|
+
kind: [UserInterface, OperatorInterfaceElement, LogicalInterface, PhysicalInterface, MemoPort, PhysicalPort]
|
|
52
52
|
display: table
|
|
53
53
|
columns: name, kind, layer, doc
|
|
54
54
|
sort: name
|
|
@@ -62,12 +62,12 @@ empty: "No user interface or operator interface elements defined."
|
|
|
62
62
|
A task is critical when incorrect performance can lead to a hazardous situation. The table below is derived by traversing `causes` from the task set — the `useErrorLeadsToHazard` edge of IEC 62366-1 §5.4:
|
|
63
63
|
|
|
64
64
|
```memo-query
|
|
65
|
-
kind: [
|
|
65
|
+
kind: [OperativeAction]
|
|
66
66
|
traverse: outgoing causes
|
|
67
67
|
display: table
|
|
68
68
|
columns: name, kind, layer, doc
|
|
69
69
|
sort: name
|
|
70
|
-
empty: "No hazardous situations linked to user tasks. Add Causes links (causeKind = useErrorLeadsToHazard) from
|
|
70
|
+
empty: "No hazardous situations linked to user tasks. Add Causes links (causeKind = useErrorLeadsToHazard) from the OperativeAction to HazardousSituation."
|
|
71
71
|
```
|
|
72
72
|
|
|
73
73
|
Complete this section for **{{project.product}}** using the guidance below.
|
|
@@ -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: [UseCase,
|
|
42
|
+
kind: [UseCase, 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: [UseCase,
|
|
26
|
+
kind: [UseCase, OperativeAction]
|
|
27
27
|
display: table
|
|
28
28
|
columns: name, layer, doc
|
|
29
29
|
sort: name
|
|
@@ -87,7 +87,7 @@ empty: "No runtime environments or deployment units defined."
|
|
|
87
87
|
Cyber-physical interactions and data flows between components:
|
|
88
88
|
|
|
89
89
|
```memo-query
|
|
90
|
-
kind: [
|
|
90
|
+
kind: [LogicalInterface, PhysicalInterface, ComponentExchange, InterfaceElement, MemoPort, DataPort, SensorPort, CommandPort, SoftwarePort, PhysicalPort, LogicalPort]
|
|
91
91
|
display: table
|
|
92
92
|
columns: name, kind, layer, doc
|
|
93
93
|
sort: name
|
|
@@ -28,7 +28,7 @@ It replaces a hand-maintained conformance matrix. The difference that matters is
|
|
|
28
28
|
|
|
29
29
|
A **Gap** is not a defect in the model. Coverage is profile-dependent — that is why it is a report and not a consistency rule, and why `memo_rules_coverage` is deliberately empty. A gap says the project has not claimed that clause *yet*, which is the normal state of a project in flight.
|
|
30
30
|
|
|
31
|
-
**Scope.** The clauses below are those of the standards the project's
|
|
31
|
+
**Scope.** The clauses below are those of the standards the project's regulated devices (their jurisdictions) pull in. Method and reference standards that no regime mandates — the FMEA method, the architecture-description standard — are listed separately in §4; their clauses are claimable but not required, so they have no gap count.
|
|
32
32
|
|
|
33
33
|
`memo validate --standards` prints the same numbers at the command line, from the same computation.
|
|
34
34
|
|
|
@@ -38,7 +38,7 @@ A **Gap** is not a defect in the model. Coverage is profile-dependent — that i
|
|
|
38
38
|
|
|
39
39
|
```memo-standards
|
|
40
40
|
display: summary
|
|
41
|
-
empty: "No standards are in scope. Declare `
|
|
41
|
+
empty: "No standards are in scope. Declare a `RegulatedDevice` with a jurisdiction."
|
|
42
42
|
```
|
|
43
43
|
|
|
44
44
|
---
|
|
@@ -15,6 +15,7 @@ package memo_assurance_requirements_needs {
|
|
|
15
15
|
// elements. Assurance may depend on architecture; the reverse may not.
|
|
16
16
|
private import memo_architecture_operational_context_actors::*;
|
|
17
17
|
private import memo_architecture_operational_context_use_context::*;
|
|
18
|
+
private import memo_architecture_operational_workflows::*;
|
|
18
19
|
|
|
19
20
|
// The kind of need. Was a subclass branch (StakeholderNeed / UserNeed /
|
|
20
21
|
// ClinicalUserNeed / PatientUserNeed / BusinessNeed / ServiceNeed /
|
|
@@ -50,6 +51,13 @@ package memo_assurance_requirements_needs {
|
|
|
50
51
|
// carries the care setting, environment and jurisdiction that an
|
|
51
52
|
// `operationalContextReference` string could only describe.
|
|
52
53
|
ref useContext : UseContext[0..1];
|
|
54
|
+
// The body of work the need arises in: its workflow, the analysis of
|
|
55
|
+
// that work (IEC 62366-1 5.1). The need points at the workflow, never
|
|
56
|
+
// the reverse, so a workflow's needs are found upstream of it.
|
|
57
|
+
ref workflow : OperationalWorkflow[0..1];
|
|
58
|
+
// Whether current practice meets the need. False is an unmet need, the
|
|
59
|
+
// gap a device is for; unset is not yet assessed.
|
|
60
|
+
attribute metByCurrentPractice : Boolean[0..1];
|
|
53
61
|
// design-control need (ISO 13485 design input)
|
|
54
62
|
attribute sourceFolder : String;
|
|
55
63
|
}
|
|
@@ -238,4 +238,19 @@ package memo_assurance_safety_risk {
|
|
|
238
238
|
:> annotatedElement : SysML::ConnectionUsage;
|
|
239
239
|
:>> baseType = mitigatesLinks meta SysML::Usage;
|
|
240
240
|
}
|
|
241
|
+
|
|
242
|
+
// ISO 14971 clause 7.4: where the residual risk is judged unacceptable, the benefit of the intended use is
|
|
243
|
+
// weighed against it. Nothing in the chain reached a Benefit, which is a part and not a RiskItem, and the
|
|
244
|
+
// generic relations that accept the pair say something else (`causes` between a benefit and a risk would say
|
|
245
|
+
// the benefit gives rise to it). Named from the benefit's side, the way AssessedAgainst is from the risk's.
|
|
246
|
+
connection def WeighedAgainst :> MemoRelationship {
|
|
247
|
+
end benefit : Benefit :>> source;
|
|
248
|
+
end risk : Risk :>> target;
|
|
249
|
+
}
|
|
250
|
+
abstract connection weighedAgainstLinks : WeighedAgainst[*];
|
|
251
|
+
metadata def <weighedAgainst> WeighedAgainstMetadata :> SemanticMetadata {
|
|
252
|
+
:> annotatedElement : SysML::ConnectionDefinition;
|
|
253
|
+
:> annotatedElement : SysML::ConnectionUsage;
|
|
254
|
+
:>> baseType = weighedAgainstLinks meta SysML::Usage;
|
|
255
|
+
}
|
|
241
256
|
}
|