@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
|
@@ -3,6 +3,19 @@
|
|
|
3
3
|
// (`predicateExpression`) evaluated by the external constraint engine.
|
|
4
4
|
// Structural invariants (endpoint existence, cycle freedom) are expressed over
|
|
5
5
|
// the typed relations introduced in 0.5 — typed references make them checkable.
|
|
6
|
+
//
|
|
7
|
+
// Operational levels (CR-ONT-093..101). A use case is at the level of its subject: an
|
|
8
|
+
// `OperationalEntity` is level 1 (clinical, no product, no number), a `System` or `SystemOfSystems`
|
|
9
|
+
// is level 2 (one variant of a platform, which carries every number). The level of a step is the
|
|
10
|
+
// level of the use case its workflow `realizesUseCase`. The workflow is reached from the step by
|
|
11
|
+
// `composes` (a step nested in a scenario) or through the scenario that `performs` it (a step
|
|
12
|
+
// declared once and used in several); a step outside any workflow has no level and is judged by
|
|
13
|
+
// no level rule.
|
|
14
|
+
// Nothing here is a kind list: each rule reads the subject's type and the `performs` and
|
|
15
|
+
// `realizes` edges the builder already produces. Rule 6 of the plan, that every variant of a `TradeStudy` refines every step compared (101),
|
|
16
|
+
// reads the study's `hasSubject` edges: its subject is the alternatives it analyses.
|
|
17
|
+
// The one-currency rule (098) counts the project's `CurrencyUnit` declarations: a unit declared at
|
|
18
|
+
// package level is built as a model element, as ISQ and SI declare theirs.
|
|
6
19
|
package memo_rules_ontology {
|
|
7
20
|
private import ScalarValues::*;
|
|
8
21
|
|
|
@@ -58,34 +71,6 @@ package memo_rules_ontology {
|
|
|
58
71
|
attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(SystemOfSystems))) or downstream(includesStep)->exists(downstream(hasSubject)->exists(conformsTo(System)))";
|
|
59
72
|
constraint { true }
|
|
60
73
|
}
|
|
61
|
-
constraint def SystemUseCaseIncludedRule :> MemoConsistencyRule {
|
|
62
|
-
@MemoIdentity { :>> providedId = "CR-ONT-086"; }
|
|
63
|
-
attribute tailoring = RuleTailoringKind::methodology;
|
|
64
|
-
attribute domain = RuleDomainKind::modelling;
|
|
65
|
-
attribute obligation = RuleObligationKind::recommended;
|
|
66
|
-
attribute appliesTo = "UseCase";
|
|
67
|
-
attribute severity = RuleSeverityKind::warning;
|
|
68
|
-
attribute rationaleText = "A use case whose subject is a system is included by a use case of the system of systems, or says it stands alone (standalone = true).";
|
|
69
|
-
attribute predicateExpression = "not(downstream(hasSubject)->exists(conformsTo(System))) or upstream(includesStep)->size() >= 1 or attributes.standalone == 'true'";
|
|
70
|
-
constraint { true }
|
|
71
|
-
}
|
|
72
|
-
// A system is a boundary (plan O16). The workspace closure never reaches another system or the
|
|
73
|
-
// system of systems, and drops such a link silently; this rule reports it. Evaluated by the
|
|
74
|
-
// workspace evaluator because it needs what each workspace holds, which no predicate can say:
|
|
75
|
-
// the subject is the element inside a system that is typed by, or relates to, a System-kind or
|
|
76
|
-
// SystemOfSystems-kind element outside it. The system of systems' own references to its systems
|
|
77
|
-
// are what it is for and are not findings.
|
|
78
|
-
constraint def SystemBoundaryRule :> MemoConsistencyRule {
|
|
79
|
-
@MemoIdentity { :>> providedId = "CR-ONT-087"; }
|
|
80
|
-
attribute tailoring = RuleTailoringKind::methodology;
|
|
81
|
-
attribute domain = RuleDomainKind::modelling;
|
|
82
|
-
attribute obligation = RuleObligationKind::recommended;
|
|
83
|
-
attribute evaluator = "workspace";
|
|
84
|
-
attribute appliesTo = "Model";
|
|
85
|
-
attribute severity = RuleSeverityKind::warning;
|
|
86
|
-
attribute rationaleText = "A system does not reference another system or the system of systems from inside itself. Two systems meet at an interface the system of systems owns.";
|
|
87
|
-
constraint { true }
|
|
88
|
-
}
|
|
89
74
|
// ─── Release selections (plan O14) ────────────────────────────────────
|
|
90
75
|
//
|
|
91
76
|
// A release record selects features (`#SelectsFeature`), and through them the variants that realize
|
|
@@ -169,6 +154,39 @@ package memo_rules_ontology {
|
|
|
169
154
|
// represent that transitive containment query.
|
|
170
155
|
constraint { true }
|
|
171
156
|
}
|
|
157
|
+
|
|
158
|
+
// ─── Direction is written on the ports, and an exchange has to agree with them ──
|
|
159
|
+
//
|
|
160
|
+
// A port says `in` or `out` (or `inout`), and a `~` conjugates it. That is the only place direction is
|
|
161
|
+
// written: an exchange's own direction was the same fact a second time, and nothing checked the two
|
|
162
|
+
// agreed. These two rules check the exchange against its ports, so a contradiction cannot be written.
|
|
163
|
+
// Both judge only ends that are ports with a stated direction; a port that says none is not judged.
|
|
164
|
+
constraint def BindingEndsAgreeInDirectionRule :> MemoConsistencyRule {
|
|
165
|
+
@MemoIdentity { :>> providedId = "AR-EXCH-001"; }
|
|
166
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
167
|
+
attribute domain = RuleDomainKind::modelling;
|
|
168
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
169
|
+
attribute appliesTo = "MemoPort";
|
|
170
|
+
attribute evaluator = "architecture";
|
|
171
|
+
attribute severity = RuleSeverityKind::error;
|
|
172
|
+
attribute rationaleText = "A binding makes its two ports one connection point, so they have the direction between them: a boundary port bound to a port of a nested part passes the same direction through. A binding of an in port to an out port joins things that cannot be the same point.";
|
|
173
|
+
attribute predicateExpression = "bindEndsAgreeInDirection";
|
|
174
|
+
// The generic expression evaluator reads a port's attributes, not its stated direction and
|
|
175
|
+
// conjugation, so a function computes the predicate (as for AR-IBD-001).
|
|
176
|
+
constraint { true }
|
|
177
|
+
}
|
|
178
|
+
constraint def ExchangeLeavesOutEntersInRule :> MemoConsistencyRule {
|
|
179
|
+
@MemoIdentity { :>> providedId = "AR-EXCH-002"; }
|
|
180
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
181
|
+
attribute domain = RuleDomainKind::modelling;
|
|
182
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
183
|
+
attribute appliesTo = "MemoPort";
|
|
184
|
+
attribute evaluator = "architecture";
|
|
185
|
+
attribute severity = RuleSeverityKind::error;
|
|
186
|
+
attribute rationaleText = "An interface or a flow between two ports carries its content from the one to the other, so it leaves a port that sends (out or inout) and enters one that receives (in or inout). An exchange that leaves an in port or enters an out port contradicts the ports it joins.";
|
|
187
|
+
attribute predicateExpression = "exchangeLeavesOutEntersIn";
|
|
188
|
+
constraint { true }
|
|
189
|
+
}
|
|
172
190
|
// ─── Deployment and realization ──────────────────────────────────────
|
|
173
191
|
|
|
174
192
|
constraint def RuntimeTracesToModuleRule :> MemoConsistencyRule {
|
|
@@ -209,6 +227,22 @@ package memo_rules_ontology {
|
|
|
209
227
|
constraint { true }
|
|
210
228
|
}
|
|
211
229
|
#EnforcesClause dependency from SafetyCriticalFunctionVerifiedRule to iso13485::iso13485Clause7::iso13485Clause7_3::iso13485Clause7_3_6;
|
|
230
|
+
// A flow's step is its own position of a function (`action step :> fn;`), and evidence is scoped to
|
|
231
|
+
// the position: a test of the function, or of another step, does not count for it. So a step whose
|
|
232
|
+
// function is safety-critical needs a verification case of its own. The step reaches its function
|
|
233
|
+
// through the `subsets` edge.
|
|
234
|
+
constraint def SafetyCriticalStepVerifiedRule :> MemoConsistencyRule {
|
|
235
|
+
@MemoIdentity { :>> providedId = "CR-ONT-091"; }
|
|
236
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
237
|
+
attribute domain = RuleDomainKind::medicalDevice;
|
|
238
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
239
|
+
attribute appliesTo = "ActionUsage";
|
|
240
|
+
attribute severity = RuleSeverityKind::warning;
|
|
241
|
+
attribute rationaleText = "A step of a flow whose function is safety-critical (criticality high or catastrophic) must trace to a verification case of its own; a test of the function or of another step does not cover it.";
|
|
242
|
+
attribute predicateExpression = "not(downstream(subsets)->exists(criticality == 'high' or criticality == 'catastrophic')) or verifiedBy->size() >= 1";
|
|
243
|
+
constraint { true }
|
|
244
|
+
}
|
|
245
|
+
#EnforcesClause dependency from SafetyCriticalStepVerifiedRule to iso13485::iso13485Clause7::iso13485Clause7_3::iso13485Clause7_3_6;
|
|
212
246
|
constraint def CriticalTaskValidatedRule :> MemoConsistencyRule {
|
|
213
247
|
@MemoIdentity { :>> providedId = "CR-ONT-041"; }
|
|
214
248
|
attribute tailoring = RuleTailoringKind::assurance;
|
|
@@ -373,7 +407,7 @@ package memo_rules_ontology {
|
|
|
373
407
|
attribute appliesTo = "Model";
|
|
374
408
|
attribute severity = RuleSeverityKind::error;
|
|
375
409
|
attribute rationaleText = "A performer is an operational entity, an actor, or a system action — a part or a behaviour. The end's own documentation said 'or system action' while its MemoPart type forbade one.";
|
|
376
|
-
attribute predicateExpression = "sourcesOf(performs)->forAll(conformsTo(MemoPart) or construct == 'action')";
|
|
410
|
+
attribute predicateExpression = "sourcesOf(performs)->forAll(conformsTo(MemoPart) or construct == 'action' or construct == 'verification')";
|
|
377
411
|
constraint { true }
|
|
378
412
|
}
|
|
379
413
|
constraint def BindsToInterfaceEndKindRule :> MemoConsistencyRule {
|
|
@@ -457,7 +491,7 @@ package memo_rules_ontology {
|
|
|
457
491
|
attribute appliesTo = "MemoFunction";
|
|
458
492
|
attribute severity = RuleSeverityKind::error;
|
|
459
493
|
attribute rationaleText = "The functional chain decomposes functions into functions. A function composed of a component, or owned by one, is confusing allocation with decomposition — the component is named by AllocatedTo, never by Composes.";
|
|
460
|
-
attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction))";
|
|
494
|
+
attribute predicateExpression = "composes->forAll(conformsTo(MemoFunction) or kind == 'ForkNode' or kind == 'JoinNode' or kind == 'DecisionNode' or kind == 'MergeNode')";
|
|
461
495
|
constraint { true }
|
|
462
496
|
}
|
|
463
497
|
|
|
@@ -636,4 +670,123 @@ package memo_rules_ontology {
|
|
|
636
670
|
attribute predicateExpression = "targetsOf(causes)->forAll(conformsTo(RiskItem) or conformsTo(FaultTreeNode))";
|
|
637
671
|
constraint { true }
|
|
638
672
|
}
|
|
673
|
+
|
|
674
|
+
// ─── Views and viewpoints ───────────────────────────────────────────
|
|
675
|
+
|
|
676
|
+
// ISO 42010 conformance is many-to-many, but never empty: `MemoView.viewpointDefinition` is `[1..*]`. A view
|
|
677
|
+
// that traces to a viewpoint is filed under it in Architect; one that traces to none has nowhere to be found.
|
|
678
|
+
constraint def ViewTracesToViewpointRule :> MemoConsistencyRule {
|
|
679
|
+
@MemoIdentity { :>> providedId = "CR-ONT-092"; }
|
|
680
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
681
|
+
attribute domain = RuleDomainKind::modelling;
|
|
682
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
683
|
+
attribute appliesTo = "MemoView";
|
|
684
|
+
attribute severity = RuleSeverityKind::error;
|
|
685
|
+
attribute rationaleText = "Every view traces to at least one viewpoint (ISO/IEC/IEEE 42010): the viewpoint says what the view is for and who reads it. A view with none cannot be filed under a viewpoint, so Architect lists it as uncategorised.";
|
|
686
|
+
attribute predicateExpression = "attributes.viewpointDefinition != ''";
|
|
687
|
+
constraint { true }
|
|
688
|
+
|
|
689
|
+
}
|
|
690
|
+
|
|
691
|
+
// ─── Operational levels (see the header) ─────────────────────────────
|
|
692
|
+
|
|
693
|
+
constraint def UseCaseSubjectIsAtALevelRule :> MemoConsistencyRule {
|
|
694
|
+
@MemoIdentity { :>> providedId = "CR-ONT-093"; }
|
|
695
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
696
|
+
attribute domain = RuleDomainKind::modelling;
|
|
697
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
698
|
+
attribute appliesTo = "UseCase";
|
|
699
|
+
attribute severity = RuleSeverityKind::error;
|
|
700
|
+
attribute rationaleText = "A use case is at the level of its subject: an operational entity (the care team, the setting) is level 1, a system or a system of systems is level 2. A subject of any other type is at neither level, so the use case cannot say whether it may name a product or carry a number.";
|
|
701
|
+
attribute predicateExpression = "downstream(hasSubject)->forAll(conformsTo(OperationalEntity) or conformsTo(System) or conformsTo(SystemOfSystems))";
|
|
702
|
+
constraint { true }
|
|
703
|
+
}
|
|
704
|
+
constraint def LevelOneStepCarriesNoNumberRule :> MemoConsistencyRule {
|
|
705
|
+
@MemoIdentity { :>> providedId = "CR-ONT-094"; }
|
|
706
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
707
|
+
attribute domain = RuleDomainKind::modelling;
|
|
708
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
709
|
+
attribute appliesTo = "OperativeAction";
|
|
710
|
+
attribute severity = RuleSeverityKind::error;
|
|
711
|
+
attribute rationaleText = "A step of a level-1 workflow is the shared baseline of every variant and carries no planned number: a gastric pouch takes a different time and succeeds at a different rate on each platform, so a number on the step would belong to no variant. Time and success are set on the level-2 activity that refines it.";
|
|
712
|
+
attribute predicateExpression = "(attributes.expectedDuration == '' and attributes.plannedSuccessProbability == '') or not((upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))))))";
|
|
713
|
+
constraint { true }
|
|
714
|
+
}
|
|
715
|
+
constraint def RealizerOfLevelOneStepIsLevelTwoRule :> MemoConsistencyRule {
|
|
716
|
+
@MemoIdentity { :>> providedId = "CR-ONT-095"; }
|
|
717
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
718
|
+
attribute domain = RuleDomainKind::modelling;
|
|
719
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
720
|
+
attribute appliesTo = "OperativeAction";
|
|
721
|
+
attribute severity = RuleSeverityKind::error;
|
|
722
|
+
attribute rationaleText = "Whatever refines a level-1 step is itself at level 2: a level-1 step refined by another level-1 step, or by an activity of no workflow at all, skips the level that names the variant.";
|
|
723
|
+
attribute predicateExpression = "not(downstream(realizes)->exists((upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))))))) or (upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems)))))))";
|
|
724
|
+
constraint { true }
|
|
725
|
+
}
|
|
726
|
+
constraint def InternalSystemActivityPerformsAFunctionRule :> MemoConsistencyRule {
|
|
727
|
+
@MemoIdentity { :>> providedId = "CR-ONT-096"; }
|
|
728
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
729
|
+
attribute domain = RuleDomainKind::modelling;
|
|
730
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
731
|
+
attribute appliesTo = "OperativeAction";
|
|
732
|
+
attribute severity = RuleSeverityKind::warning;
|
|
733
|
+
attribute rationaleText = "An activity that a system built by this organisation performs reaches level 3 by performing the system function that carries it out. An external system, a competitor's or a legacy platform, has no level 3 here and is not asked.";
|
|
734
|
+
attribute predicateExpression = "not(upstream(performs)->exists((conformsTo(System) or conformsTo(SystemOfSystems)) and attributes.origin != 'SystemOriginKind::external')) or downstream(performs)->exists(conformsTo(SystemFunction))";
|
|
735
|
+
constraint { true }
|
|
736
|
+
}
|
|
737
|
+
constraint def FunctionIsNotPerformedFromLevelOneRule :> MemoConsistencyRule {
|
|
738
|
+
@MemoIdentity { :>> providedId = "CR-ONT-097"; }
|
|
739
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
740
|
+
attribute domain = RuleDomainKind::modelling;
|
|
741
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
742
|
+
attribute appliesTo = "SystemFunction";
|
|
743
|
+
attribute severity = RuleSeverityKind::error;
|
|
744
|
+
attribute rationaleText = "A system function is performed from a level-2 activity or from a step of a functional flow, never from a level-1 step: level 1 names no product, and a function is what a product does.";
|
|
745
|
+
attribute predicateExpression = "upstream(performs)->forAll(not(conformsTo(OperativeAction) and (upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))))))))";
|
|
746
|
+
constraint { true }
|
|
747
|
+
}
|
|
748
|
+
constraint def ProjectDeclaresOneCurrencyRule :> MemoConsistencyRule {
|
|
749
|
+
@MemoIdentity { :>> providedId = "CR-ONT-098"; }
|
|
750
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
751
|
+
attribute domain = RuleDomainKind::modelling;
|
|
752
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
753
|
+
attribute appliesTo = "Model";
|
|
754
|
+
attribute severity = RuleSeverityKind::error;
|
|
755
|
+
attribute rationaleText = "A project states every amount in one currency, declared once as a currency unit. No conversion between currencies is modelled, so two currency units make every sum across them meaningless.";
|
|
756
|
+
attribute predicateExpression = "allOfKind('CurrencyUnit')->size() <= 1";
|
|
757
|
+
constraint { true }
|
|
758
|
+
}
|
|
759
|
+
constraint def LevelOneScenarioCarriesNoLikelihoodRule :> MemoConsistencyRule {
|
|
760
|
+
@MemoIdentity { :>> providedId = "CR-ONT-099"; }
|
|
761
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
762
|
+
attribute domain = RuleDomainKind::modelling;
|
|
763
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
764
|
+
attribute appliesTo = "OperativeScenario";
|
|
765
|
+
attribute severity = RuleSeverityKind::error;
|
|
766
|
+
attribute rationaleText = "How likely a path is differs by platform (a robot and a laparoscopic tower do not convert to open at the same rate), so a scenario of a level-1 workflow carries no likelihood; it is set on the level-2 scenario of each variant.";
|
|
767
|
+
attribute predicateExpression = "attributes.likelihood == '' or not(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))))";
|
|
768
|
+
constraint { true }
|
|
769
|
+
}
|
|
770
|
+
constraint def LevelOneWorkflowCarriesNoCostRule :> MemoConsistencyRule {
|
|
771
|
+
@MemoIdentity { :>> providedId = "CR-ONT-100"; }
|
|
772
|
+
attribute tailoring = RuleTailoringKind::invariant;
|
|
773
|
+
attribute domain = RuleDomainKind::modelling;
|
|
774
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
775
|
+
attribute appliesTo = "OperationalWorkflow";
|
|
776
|
+
attribute severity = RuleSeverityKind::error;
|
|
777
|
+
attribute rationaleText = "What a procedure costs apart from its activities (set-up, capital per case) depends on the platform, so a level-1 workflow carries no per-procedure cost; it is set on the workflow of each level-2 variant.";
|
|
778
|
+
attribute predicateExpression = "attributes.perProcedureCost == '' or not(downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))";
|
|
779
|
+
constraint { true }
|
|
780
|
+
}
|
|
781
|
+
constraint def TradeStudyVariantRefinesEveryStepRule :> MemoConsistencyRule {
|
|
782
|
+
@MemoIdentity { :>> providedId = "CR-ONT-101"; }
|
|
783
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
784
|
+
attribute domain = RuleDomainKind::modelling;
|
|
785
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
786
|
+
attribute appliesTo = "OperationalWorkflow";
|
|
787
|
+
attribute severity = RuleSeverityKind::error;
|
|
788
|
+
attribute rationaleText = "Every alternative of a trade study refines every level-1 step that any alternative of it refines, whether its activities are nested in its scenarios or performed by them. An alternative with a step missing reads as zero time and zero cost for it, so the study would prefer it for doing less.";
|
|
789
|
+
attribute predicateExpression = "not(upstream(hasSubject)->exists(attributes.usageType == 'TradeStudy')) or upstream(hasSubject)->select(attributes.usageType == 'TradeStudy')->forAll(downstream(hasSubject)->forAll(downstream(composes)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))) and downstream(composes)->forAll(downstream(performs)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))))))";
|
|
790
|
+
constraint { true }
|
|
791
|
+
}
|
|
639
792
|
}
|
|
@@ -32,6 +32,35 @@ package memo_rules_quantitative {
|
|
|
32
32
|
constraint { true }
|
|
33
33
|
}
|
|
34
34
|
|
|
35
|
+
constraint def SoftwareComponentWcetWithinDeadlineRule :> MemoConsistencyRule {
|
|
36
|
+
@MemoIdentity { :>> providedId = "QT-004"; }
|
|
37
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
38
|
+
attribute domain = RuleDomainKind::modelling;
|
|
39
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
40
|
+
attribute appliesTo = "SoftwareComponent";
|
|
41
|
+
attribute severity = RuleSeverityKind::warning;
|
|
42
|
+
attribute rationaleText = "A component whose worst-case execution time exceeds its deadline cannot meet it. Both are durations, compared in one unit whatever each was written in.";
|
|
43
|
+
attribute predicateExpression = "attributes.wcetMs == '' or attributes.deadlineMs == '' or wcetMs <= deadlineMs";
|
|
44
|
+
constraint { true }
|
|
45
|
+
}
|
|
46
|
+
|
|
47
|
+
// The `require`, `assume` and `assert constraint`s a model declares are claims about its own values. A
|
|
48
|
+
// function evaluates them (`validator/model-constraints.ts`): names resolve from the owning element, its
|
|
49
|
+
// package, then a unique short name, and a quantity compares as a quantity. A constraint it cannot
|
|
50
|
+
// resolve is reported as not evaluated, which is information, never a pass.
|
|
51
|
+
constraint def ModelConstraintHoldsRule :> MemoConsistencyRule {
|
|
52
|
+
@MemoIdentity { :>> providedId = "MC-001"; }
|
|
53
|
+
attribute tailoring = RuleTailoringKind::assurance;
|
|
54
|
+
attribute domain = RuleDomainKind::modelling;
|
|
55
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
56
|
+
attribute appliesTo = "Model";
|
|
57
|
+
attribute evaluator = "constraints";
|
|
58
|
+
attribute severity = RuleSeverityKind::error;
|
|
59
|
+
attribute rationaleText = "A constraint a model declares is a claim about its own values; one that does not hold is a defect in the model or in the claim.";
|
|
60
|
+
attribute predicateExpression = "modelConstraintsHold";
|
|
61
|
+
constraint { true }
|
|
62
|
+
}
|
|
63
|
+
|
|
35
64
|
// QT-003 (RequirementVerificationRatio, "≥80% of requirements verified") is an
|
|
36
65
|
// aggregate coverage metric over the whole requirement set, not a per-subject
|
|
37
66
|
// predicate, so it has no `constraint { … }` form. It remains a
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_clinical_clinical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows clinical context, users, use environment, and clinical evidence."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context and assurance layers for clinical stakeholders — intended use, patient/clinician interaction, clinical evidence, and clinical safety claims. */
|
|
14
14
|
attribute :>> purpose = "Communicate clinical use context and clinical evidence for the device.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (clinicalEngineer, regulatoryEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "clinical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::documentSection, ViewOutputKind::table);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_context_context_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use context, and system boundary."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context layer to communicate who interacts with the device, under which use conditions, and where trust or safety boundaries exist. */
|
|
14
14
|
attribute :>> purpose = "Communicate operational context and boundaries.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "system";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows assets, trust boundaries, threats, vulnerabilities, cyber hazards, cyber risks, and mitigations."; }
|
|
13
13
|
doc /* Default viewpoint derived from the cybersecurity layer, using STRIDE-style threat categories by default while allowing safety and privacy impacts to be traced into the broader model. */
|
|
14
14
|
attribute :>> purpose = "Communicate cybersecurity design, threat analysis, and cyber risk posture.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (securityEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::risk;
|
|
17
17
|
attribute :>> abstractionLevel = "analysis";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -66,6 +66,15 @@ package memo_viewpoints_definitions_layout {
|
|
|
66
66
|
attribute layoutSeed : Real[0..1];
|
|
67
67
|
}
|
|
68
68
|
|
|
69
|
+
/** Renderer namespaces and forward-compatible presentation fields only.
|
|
70
|
+
* Standard geometry remains in the typed MemoLayout* records. The JSON
|
|
71
|
+
* envelope is versioned by its writer; this string creates no model links.
|
|
72
|
+
*/
|
|
73
|
+
metadata def MemoLayoutExtension {
|
|
74
|
+
:> annotatedElement : SysML::ViewUsage;
|
|
75
|
+
attribute payload : String;
|
|
76
|
+
}
|
|
77
|
+
|
|
69
78
|
/**
|
|
70
79
|
* One box. `x` and `y` are in the frame of `parentElement` (the box it is
|
|
71
80
|
* nested in), or on the board when there is none; the frame is recorded
|
|
@@ -37,7 +37,7 @@ package memo_viewpoints_definitions {
|
|
|
37
37
|
*/
|
|
38
38
|
// Redefines the standard library's `RequirementCheck::stakeholders`,
|
|
39
39
|
// which a viewpoint inherits through `ViewpointCheck`.
|
|
40
|
-
ref :>> stakeholders : MemoStakeholder[0..*];
|
|
40
|
+
ref memoStakeholders :>> stakeholders : MemoStakeholder[0..*];
|
|
41
41
|
attribute stage : WorkflowStageKind;
|
|
42
42
|
attribute abstractionLevel : String;
|
|
43
43
|
attribute outputKind : ViewOutputKind[*];
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_functional_functional_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows system functions, their decomposition, and allocation."; }
|
|
13
13
|
doc /* Default viewpoint derived from the functions layer for what the system does, independent of how it is structured — function trees, function allocation, and behavior triggers. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's functional decomposition and behavior.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "functional";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_logical_logical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows logical decomposition and interfaces."; }
|
|
13
13
|
doc /* Default viewpoint derived from the logical architecture layer for subsystem structure, responsibilities, and major interactions, independent of physical realization. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's logical decomposition.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "logical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_operational_operational_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use contexts, operational scenarios, and system capabilities."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context, operational, and system layers for how actors use the device — operational scenarios, capabilities, and the functional chains that realize them. */
|
|
14
14
|
attribute :>> purpose = "Communicate how actors interact with the system and which capabilities they invoke.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (projectLead, systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::context;
|
|
17
17
|
attribute :>> abstractionLevel = "operational";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_physical_physical_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows physical components, hardware structure, and their interconnections."; }
|
|
13
13
|
doc /* Default viewpoint derived from the physical and hardware structure layers for bill-of-materials, hardware decomposition, physical interfaces, and network/connectivity topology. */
|
|
14
14
|
attribute :>> purpose = "Describe the system's physical realization and interconnections.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (hardwareEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "physical";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_requirements_requirements_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows stakeholder needs and their decomposition into system, software, and hardware requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the requirements layer for requirements traceability — the chain from stakeholder need through system, software, and hardware requirements, supporting IEC 62304 §5.1.1 and ISO 13485 §7.3.3. */
|
|
14
14
|
attribute :>> purpose = "Communicate requirements decomposition and traceability.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (regulatoryEngineer, systemArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::requirements;
|
|
17
17
|
attribute :>> abstractionLevel = "requirements";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::matrix);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_risk_risk_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows hazards, risks, controls, and assurance links."; }
|
|
13
13
|
doc /* Default viewpoint derived from the risk layer for ISO 14971-style reasoning across hazard, hazardous situation, harm, control, and verification evidence. */
|
|
14
14
|
attribute :>> purpose = "Communicate safety risk chains and controls.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::risk;
|
|
17
17
|
attribute :>> abstractionLevel = "analysis";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::table);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_software_software_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows software systems, components, SOUP, and software interfaces."; }
|
|
13
13
|
doc /* Default viewpoint derived from the software structure layer for IEC 62304 software architecture description — software item decomposition, SOUP inventory, and software-to-software interfaces, distinct from system-level logical decomposition. */
|
|
14
14
|
attribute :>> purpose = "Describe the software architecture for IEC 62304 design documentation.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (softwareArchitect);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "software";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram);
|
|
@@ -26,7 +26,12 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
26
26
|
// A concern is an interest in the system held by one or more stakeholders.
|
|
27
27
|
// `concern def` is the native SysML construct for it; a viewpoint frames
|
|
28
28
|
// the concerns it addresses.
|
|
29
|
-
|
|
29
|
+
//
|
|
30
|
+
// It extends the standard concern's `stakeholders` (the Parts interested in
|
|
31
|
+
// it) to the MEMO stakeholder catalog, as a viewpoint does for its own.
|
|
32
|
+
abstract concern def MemoConcern {
|
|
33
|
+
ref memoStakeholders :>> stakeholders : MemoStakeholder[0..*];
|
|
34
|
+
}
|
|
30
35
|
|
|
31
36
|
concern def SafetyConcern :> MemoConcern {
|
|
32
37
|
@MemoIdentity { :>> providedId = "CNC-1"; }
|
|
@@ -136,7 +141,13 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
136
141
|
// A stakeholder holds concerns. These are the engineering and regulatory
|
|
137
142
|
// roles a viewpoint is written FOR; the clinical actors who operate the
|
|
138
143
|
// device are OperationalParticipants and are a different population.
|
|
139
|
-
|
|
144
|
+
//
|
|
145
|
+
// SysML v2 has no stakeholder definition to specialize: a stakeholder is a
|
|
146
|
+
// `Part` that a concern or viewpoint lists in `RequirementCheck::stakeholders`
|
|
147
|
+
// (declared with a `stakeholder` member). So the catalog is standard parts,
|
|
148
|
+
// not `MemoPart`s — MemoPart's lifecycle and dimension attributes describe
|
|
149
|
+
// model elements, not the people a viewpoint is written for.
|
|
150
|
+
abstract part def MemoStakeholder :> Parts::Part;
|
|
140
151
|
|
|
141
152
|
part def SystemArchitect :> MemoStakeholder {
|
|
142
153
|
@MemoIdentity { :>> providedId = "STK-1"; :>> label = "System Architect"; }
|
|
@@ -174,7 +185,7 @@ package memo_viewpoints_stakeholders_concerns {
|
|
|
174
185
|
|
|
175
186
|
// ─── The catalog, as usages ─────────────────────────────────────────
|
|
176
187
|
//
|
|
177
|
-
// A viewpoint's `
|
|
188
|
+
// A viewpoint's `memoStakeholders` and `framedConcerns`, and a quality
|
|
178
189
|
// attribute's `addressesConcerns`, are features. What a feature is bound to
|
|
179
190
|
// has to be a feature as well, not a definition, so each concern and each
|
|
180
191
|
// stakeholder above has exactly one usage for those bindings to name.
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows screen captures with the UI element tree laid out over them."; }
|
|
13
13
|
doc /* Frames the user interface spatially: a captured rendering of a screen, and the UIElement tree laid out over it by each element's bounds. Supports IEC 62366-1 use-related design review and the UI description in the software design specification, by making 'which control is this, and what does it do' answerable from the picture. There is one tree, not two — the elements carrying the geometry are the same elements carrying the requirements, functions, use errors, and risk controls. */
|
|
14
14
|
attribute :>> purpose = "Review the interface as the user sees it, with every functional area backed by a design record.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (usabilityEngineer, softwareArchitect, safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::architecture;
|
|
17
17
|
attribute :>> abstractionLevel = "implementation";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::documentSection);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_usability_usability_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the context and requirements layers for IEC 62366-1 usability engineering — actors, use contexts, identified use errors, and requirements tagged with the usability concern. Reuses existing context-layer elements (Actor, UseContext, UseError) rather than a separate usability layer. */
|
|
14
14
|
attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (usabilityEngineer, safetyEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::requirements;
|
|
17
17
|
attribute :>> abstractionLevel = "usability";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::documentSection);
|
|
@@ -12,7 +12,7 @@ package memo_viewpoints_verification_verification_viewpoint {
|
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements."; }
|
|
13
13
|
doc /* Default viewpoint derived from the requirements and assurance layers for V&V coverage — which requirements are verified/validated, by which case, and what evidence was produced, supporting ISO 13485 §7.3.6/§7.3.7 and IEC 62304 §5.7/§5.8. */
|
|
14
14
|
attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
|
|
15
|
-
ref :>>
|
|
15
|
+
ref :>> memoStakeholders = (verificationEngineer);
|
|
16
16
|
attribute :>> stage = WorkflowStageKind::verificationStage;
|
|
17
17
|
attribute :>> abstractionLevel = "verification";
|
|
18
18
|
attribute :>> outputKind = (ViewOutputKind::matrix);
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/examples/connected-patient-monitor/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_connected_patient_monitor_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_embedded_infusion_pump_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
package/examples/functional-logical-physical/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_functional_logical_physical_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_ivd_laboratory_system_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
package/examples/manual-surgical-instrument/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_manual_surgical_instrument_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
package/examples/multidimensional-layers/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_multidimensional_layers_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_reusable_instrument_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
package/examples/software-only-medical-device/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_software_only_medical_device_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|
package/examples/surgical-closure-workflow/model/catalog/viewpoints/unassigned/viewpoint.sysml
DELETED
|
@@ -1,9 +0,0 @@
|
|
|
1
|
-
// unassigned viewpoint.
|
|
2
|
-
//
|
|
3
|
-
// This project does not define its own viewpoint here; it binds the reusable
|
|
4
|
-
// MEMO viewpoint that frames these concerns. The views it governs sit beneath
|
|
5
|
-
// `views/`.
|
|
6
|
-
package memo_examples_surgical_closure_workflow_viewpoints_unassigned {
|
|
7
|
-
// The reusable package declaring unassigned could not be resolved during
|
|
8
|
-
// conversion. Import it here so the views beneath this viewpoint resolve.
|
|
9
|
-
}
|