@memoarchitect/ontology 0.16.5 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/examples/connected-patient-monitor/model/catalog/connected_patient_monitor.sysml +11 -18
- package/examples/connected-patient-monitor/model/catalog/viewpoints/logical/views/connected_patient_monitor_overview.sysml +1 -3
- package/examples/connected-patient-monitor/model/methodology/project.sysml +2 -6
- package/examples/embedded-infusion-pump/model/catalog/embedded_infusion_pump.sysml +35 -47
- package/examples/embedded-infusion-pump/model/catalog/viewpoints/logical/views/embedded_infusion_pump_overview.sysml +1 -3
- package/examples/embedded-infusion-pump/model/methodology/project.sysml +2 -6
- package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +24 -36
- package/examples/functional-logical-physical/model/catalog/viewpoints/logical/views/functional_logical_physical_overview.sysml +1 -3
- package/examples/functional-logical-physical/model/methodology/project.sysml +2 -6
- package/examples/gastric-bypass-variants/memo.identity.yaml +6 -0
- package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +16 -30
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +16 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +16 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +4 -23
- package/examples/gastric-bypass-variants/model/methodology/project.sysml +3 -6
- package/examples/gpca-pump/methodology/gpca_methodology.sysml +2 -4
- package/examples/gpca-pump/methodology/gpca_profiles.sysml +1 -10
- package/examples/gpca-pump/model/catalog/gpca_analysis.sysml +27 -30
- package/examples/gpca-pump/model/catalog/gpca_architecture.sysml +125 -136
- package/examples/gpca-pump/model/catalog/gpca_behavior_actions.sysml +1 -5
- package/examples/gpca-pump/model/catalog/gpca_behavior_modes.sysml +40 -44
- package/examples/gpca-pump/model/catalog/gpca_behavior_subsystems.sysml +36 -45
- package/examples/gpca-pump/model/catalog/gpca_context.sysml +14 -26
- package/examples/gpca-pump/model/catalog/gpca_cybersecurity.sysml +21 -29
- package/examples/gpca-pump/model/catalog/gpca_devices.sysml +4 -7
- package/examples/gpca-pump/model/catalog/gpca_formal_behavior.sysml +21 -28
- package/examples/gpca-pump/model/catalog/gpca_interfaces.sysml +14 -22
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +50 -60
- package/examples/gpca-pump/model/catalog/gpca_physical.sysml +7 -11
- package/examples/gpca-pump/model/catalog/gpca_requirements.sysml +211 -215
- package/examples/gpca-pump/model/catalog/gpca_risk.sysml +87 -106
- package/examples/gpca-pump/model/catalog/gpca_standards.sysml +44 -53
- package/examples/gpca-pump/model/catalog/gpca_system.sysml +15 -22
- package/examples/gpca-pump/model/catalog/gpca_trace.sysml +301 -322
- package/examples/gpca-pump/model/catalog/gpca_verification.sysml +38 -41
- package/examples/gpca-pump/model/catalog/viewpoints/context/views/context_system_context_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/cybersecurity_cybersecurity_view.sysml +2 -16
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_cyber_assessment_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/cybersecurity/views/document_threat_model_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_allocation_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/functional/views/functional_function_browser_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/behavior_action_flow_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_device_interconnect_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_logical_architecture_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_mode_state_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/logical/views/logical_system_decomposition_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_scenario_sequence_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/operational/views/operational_use_case_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/physical/views/physical_physical_bom_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/requirements/views/requirements_requirements_trace_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_hazard_analysis_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/document_rmf_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_fmea_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/risk/views/risk_risk_chain_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_architecture_description_view.sysml +3 -10
- package/examples/gpca-pump/model/catalog/viewpoints/shared/views/document_dhf_index_view.sysml +3 -10
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/document_sdd_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/software/views/software_software_architecture_view.sysml +2 -15
- package/examples/gpca-pump/model/catalog/viewpoints/usability/views/document_usability_view.sysml +3 -9
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/document_vv_view.sysml +3 -8
- package/examples/gpca-pump/model/catalog/viewpoints/verification/views/verification_verification_coverage_view.sysml +2 -15
- package/examples/gpca-pump/model/methodology/project.sysml +1 -4
- package/examples/ivd-laboratory-system/model/catalog/ivd_laboratory_system.sysml +10 -19
- package/examples/ivd-laboratory-system/model/catalog/viewpoints/logical/views/ivd_laboratory_system_overview.sysml +1 -3
- package/examples/ivd-laboratory-system/model/methodology/project.sysml +2 -6
- package/examples/manual-surgical-instrument/model/catalog/manual_surgical_instrument.sysml +3 -8
- package/examples/manual-surgical-instrument/model/catalog/viewpoints/logical/views/manual_surgical_instrument_overview.sysml +1 -3
- package/examples/manual-surgical-instrument/model/methodology/project.sysml +2 -6
- package/examples/multidimensional-layers/model/catalog/multidimensional_layers.sysml +10 -20
- package/examples/multidimensional-layers/model/catalog/viewpoints/logical/views/multidimensional_layers_overview.sysml +1 -3
- package/examples/multidimensional-layers/model/methodology/project.sysml +2 -6
- package/examples/nested-architecture-dsm/README.md +5 -5
- package/examples/nested-architecture-dsm/model/catalog/architecture/functional/functions.sysml +19 -24
- package/examples/nested-architecture-dsm/model/catalog/architecture/logical/structure.sysml +19 -24
- package/examples/nested-architecture-dsm/model/catalog/architecture/operational/context.sysml +3 -7
- package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/needs.sysml +20 -24
- package/examples/nested-architecture-dsm/model/catalog/assurance/requirements/requirements.sysml +15 -19
- package/examples/nested-architecture-dsm/model/catalog/assurance/verification_validation/verification_validation.sysml +25 -29
- package/examples/nested-architecture-dsm/model/catalog/traces.sysml +1 -2
- package/examples/nested-architecture-dsm/model/methodology/project.sysml +2 -6
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +21 -30
- package/examples/reusable-instrument/model/catalog/viewpoints/logical/views/reusable_instrument_overview.sysml +1 -3
- package/examples/reusable-instrument/model/methodology/project.sysml +2 -6
- package/examples/robot-cell-family/model/catalog/shared/shared.sysml +1 -6
- package/examples/robot-cell-family/model/catalog/sos/chains.sysml +3 -8
- package/examples/robot-cell-family/model/catalog/sos/icds.sysml +1 -4
- package/examples/robot-cell-family/model/catalog/sos/sos.sysml +1 -3
- package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +3 -6
- package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +6 -11
- package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +6 -11
- package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +6 -11
- package/examples/robot-cell-family/model/methodology/project.sysml +2 -6
- package/examples/robot-platform/model/platform.sysml +1 -3
- package/examples/ros-mobile-robot/model/catalog/ros_mobile_robot.sysml +43 -56
- package/examples/ros-mobile-robot/model/catalog/viewpoints/logical/views/ros_mobile_robot_overview.sysml +1 -3
- package/examples/ros-mobile-robot/model/methodology/project.sysml +2 -6
- package/examples/software-only-medical-device/model/catalog/software_only_medical_device.sysml +16 -26
- package/examples/software-only-medical-device/model/catalog/viewpoints/logical/views/software_only_medical_device_overview.sysml +1 -3
- package/examples/software-only-medical-device/model/methodology/project.sysml +2 -6
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +34 -45
- package/examples/surgical-closure-workflow/model/catalog/viewpoints/logical/views/surgical_closure_workflow_overview.sysml +1 -3
- package/examples/surgical-closure-workflow/model/methodology/project.sysml +2 -6
- package/examples/surgical-robot/model/catalog/surgical_robot.sysml +9 -16
- package/examples/surgical-robot/model/catalog/viewpoints/logical/views/surgical_robot_overview.sysml +1 -3
- package/examples/surgical-robot/model/methodology/project.sysml +2 -6
- package/examples/sysml-diagram-samples/model/catalog/samples/action_flow_view.sysml +7 -17
- package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +13 -21
- package/examples/sysml-diagram-samples/model/catalog/samples/context_view.sysml +4 -12
- package/examples/sysml-diagram-samples/model/catalog/samples/drill_down_view.sysml +9 -15
- package/examples/sysml-diagram-samples/model/catalog/samples/functional_flow_view.sysml +11 -19
- package/examples/sysml-diagram-samples/model/catalog/samples/grid_view.sysml +4 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/interconnection_view.sysml +10 -20
- package/examples/sysml-diagram-samples/model/catalog/samples/operational_behaviour_view.sysml +3 -12
- package/examples/sysml-diagram-samples/model/catalog/samples/package_view.sysml +8 -15
- package/examples/sysml-diagram-samples/model/catalog/samples/requirements_view.sysml +15 -23
- package/examples/sysml-diagram-samples/model/catalog/samples/sequence_view.sysml +2 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/standard_activity_view.sysml +1 -6
- package/examples/sysml-diagram-samples/model/catalog/samples/state_transition_view.sysml +4 -10
- package/examples/sysml-diagram-samples/model/catalog/samples/tree_view.sysml +7 -14
- package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +14 -21
- package/examples/sysml-diagram-samples/model/catalog/viewpoints/shared/views/diagram_samples.sysml +1 -25
- package/examples/sysml-diagram-samples/model/methodology/project.sysml +2 -6
- package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +45 -65
- package/examples/temperature-alarm/model/catalog/viewpoints/logical/views/temperature_alarm_overview.sysml +1 -3
- package/examples/temperature-alarm/model/methodology/project.sysml +2 -6
- package/examples/ui-screen-regions/model/catalog/architecture/functional/functions.sysml +10 -28
- package/examples/ui-screen-regions/model/catalog/architecture/implementation/ui.sysml +14 -36
- package/examples/ui-screen-regions/model/catalog/artifacts/assets/catalog.sysml +4 -19
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/comments.sysml +4 -19
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/notes.sysml +2 -15
- package/examples/ui-screen-regions/model/catalog/artifacts/reviews/rationales.sysml +2 -15
- package/examples/ui-screen-regions/model/catalog/assurance/human_factors/human_factors.sysml +8 -25
- package/examples/ui-screen-regions/model/catalog/assurance/requirements/needs.sysml +3 -15
- package/examples/ui-screen-regions/model/catalog/assurance/requirements/requirements.sysml +25 -37
- package/examples/ui-screen-regions/model/catalog/assurance/safety_risk/risk.sysml +31 -48
- package/examples/ui-screen-regions/model/catalog/assurance/verification_validation/verification_validation.sysml +7 -19
- package/examples/ui-screen-regions/model/catalog/traces.sysml +53 -64
- package/examples/ui-screen-regions/model/catalog/viewpoints/functional/views/ui_functional_tree.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/requirements/views/ui_requirements_trace.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/risk/views/ui_risk_chain.sysml +2 -17
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/main_screen_layout.sysml +1 -15
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/settings_screen_layout.sysml +1 -15
- package/examples/ui-screen-regions/model/catalog/viewpoints/ui_layout/views/ui_region_trace.sysml +1 -15
- package/examples/ui-screen-regions/model/methodology/project.sysml +1 -5
- package/extensions/README.md +2 -2
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/aadl/src/correspondence/memo_aadl_correspondence.sysml +2 -2
- package/extensions/aadl/src/runtime/memo_aadl_runtime.sysml +9 -13
- package/extensions/anatomy/memo.package.yaml +1 -1
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +12 -1
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/cloud/src/cloud_extension.sysml +2 -4
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/container/src/container_extension.sysml +2 -5
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/messaging/src/messaging_extension.sysml +4 -5
- package/extensions/ros/memo.package.yaml +1 -1
- package/extensions/ros/src/ros_extension.sysml +5 -10
- package/methodologies/default/memo.package.yaml +1 -1
- package/methodologies/gpca/memo.package.yaml +1 -1
- package/ontology/memo.package.yaml +1 -1
- package/package.json +1 -1
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/behavior/memo_behavior.sysml +15 -27
- package/src/architecture/functional/functions/memo_functions.sysml +31 -44
- package/src/architecture/implementation/hardware/common/memo_hardware_common.sysml +1 -1
- package/src/architecture/implementation/hardware/electrical/memo_hardware_electrical.sysml +3 -3
- package/src/architecture/implementation/hardware/fluidic/memo_hardware_fluidic.sysml +3 -2
- package/src/architecture/implementation/hardware/mechanical/memo_hardware_mechanical.sysml +2 -2
- package/src/architecture/implementation/hardware/optical/memo_hardware_optical.sysml +2 -2
- package/src/architecture/implementation/hardware/sensing/memo_hardware_sensing.sysml +2 -2
- package/src/architecture/implementation/hardware/structure/memo_hardware_structure.sysml +5 -4
- package/src/architecture/implementation/software/runtime/memo_software_runtime.sysml +17 -20
- package/src/architecture/implementation/software/structure/memo_software_structure.sysml +2 -2
- package/src/architecture/implementation/ui/memo_ui.sysml +33 -43
- package/src/architecture/logical/interfaces/memo_interfaces.sysml +21 -27
- package/src/architecture/logical/structure/memo_logical_structure.sysml +15 -18
- package/src/architecture/operational/activities/memo_activities.sysml +2 -2
- package/src/architecture/operational/context/actors/memo_actors.sysml +8 -7
- package/src/architecture/operational/context/stakeholders/memo_stakeholders.sysml +1 -1
- package/src/architecture/operational/context/use_context/memo_use_context.sysml +9 -13
- package/src/architecture/operational/rollups/memo_rollups.sysml +24 -8
- package/src/architecture/operational/scenarios/memo_scenarios.sysml +5 -6
- package/src/architecture/operational/structure/memo_operational.sysml +3 -5
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +32 -26
- package/src/architecture/operational/workflows/memo_workflows.sysml +13 -60
- package/src/architecture/realization/deployment/memo_deployment.sysml +18 -24
- package/src/architecture/realization/physical/memo_physical_architecture.sysml +16 -19
- package/src/artifacts/configuration_management/memo_configuration_management.sysml +30 -22
- package/src/artifacts/standards/cfr_21_820.sysml +0 -1
- package/src/artifacts/standards/fda_cybersecurity_2023.sysml +2 -5
- package/src/artifacts/standards/iec_60601_1.sysml +0 -1
- package/src/artifacts/standards/iec_60601_1_2.sysml +0 -1
- package/src/artifacts/standards/iec_60812.sysml +0 -1
- package/src/artifacts/standards/iec_62304.sysml +0 -1
- package/src/artifacts/standards/iec_62366_1.sysml +0 -1
- package/src/artifacts/standards/iec_81001_5_1.sysml +1 -2
- package/src/artifacts/standards/iso_13485.sysml +0 -1
- package/src/artifacts/standards/iso_14971.sysml +0 -1
- package/src/artifacts/standards/iso_iec_ieee_42010.sysml +0 -1
- package/src/artifacts/standards/memo_artifacts_standards_traceability.sysml +2 -0
- package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/use-spec.md +1 -1
- package/src/assurance/cybersecurity/memo_cybersecurity.sysml +1 -0
- package/src/assurance/human_factors/memo_human_factors.sysml +9 -6
- package/src/assurance/requirements/memo_requirements.sysml +6 -11
- package/src/assurance/requirements/needs/memo_needs.sysml +4 -5
- package/src/assurance/safety_risk/analysis/memo_fmea.sysml +1 -0
- package/src/assurance/safety_risk/memo_risk.sysml +19 -22
- package/src/assurance/verification_validation/memo_assurance.sysml +14 -18
- package/src/core/annotations/memo_annotations.sysml +2 -2
- package/src/core/common/memo_common.sysml +40 -56
- package/src/core/dimensions/dimensions.sysml +9 -12
- package/src/core/enumerations/memo_enumerations.sysml +4 -12
- package/src/core/methodology_scope/methodology_scope.sysml +3 -6
- package/src/core/relationships/memo_relationships.sysml +54 -85
- package/src/core/relationships/memo_workspace_membership.sysml +0 -2
- package/src/memo_namespaces.sysml +9 -0
- package/src/methodology/archetypes/memo_archetypes.sysml +0 -1
- package/src/methodology/core/memo_core.sysml +12 -12
- package/src/methodology/profiles/memo_profiles.sysml +9 -10
- package/src/methodology/workflow/memo_workflow.sysml +7 -8
- package/src/rules/closure/closure_rules.sysml +7 -9
- package/src/rules/crosslayer/cross_layer_rules.sysml +0 -1
- package/src/rules/ontology/ontology_invariants.sysml +97 -105
- package/src/rules/quantitative/quantitative_rules.sysml +0 -1
- package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +5 -6
- package/src/viewpoints/clinical/clinical_viewpoint.sysml +0 -1
- package/src/viewpoints/clinical/views/clinical_evidence_view/clinical_evidence_view.sysml +8 -8
- package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +24 -0
- package/src/viewpoints/context/context_viewpoint.sysml +0 -1
- package/src/viewpoints/context/views/system_context_view/system_context_view.sysml +19 -20
- package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +0 -1
- package/src/viewpoints/cybersecurity/views/cybersecurity_assessment_view/cybersecurity_assessment_view.sysml +8 -8
- package/src/viewpoints/cybersecurity/views/threat_model_view/threat_model_view.sysml +8 -8
- package/src/viewpoints/definitions/memo_view_layout.sysml +27 -3
- package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml +8 -12
- package/src/viewpoints/functional/functional_viewpoint.sysml +0 -1
- package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml +19 -20
- package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml +19 -20
- package/src/viewpoints/logical/logical_viewpoint.sysml +0 -1
- package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml +19 -20
- package/src/viewpoints/operational/operational_viewpoint.sysml +0 -1
- package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml +19 -20
- package/src/viewpoints/physical/physical_viewpoint.sysml +0 -1
- package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml +19 -20
- package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml +19 -20
- package/src/viewpoints/rendering/memo_rendering.sysml +5 -8
- package/src/viewpoints/requirements/requirements_viewpoint.sysml +0 -1
- package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml +19 -20
- package/src/viewpoints/risk/risk_viewpoint.sysml +0 -1
- package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml +20 -21
- package/src/viewpoints/software/software_viewpoint.sysml +0 -1
- package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml +19 -20
- package/src/viewpoints/stakeholders_concerns/memo_stakeholders_concerns.sysml +7 -16
- package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml +0 -1
- package/src/viewpoints/ui_layout/views/screen_layout_view/screen_layout_view.sysml +0 -1
- package/src/viewpoints/usability/usability_viewpoint.sysml +0 -1
- package/src/viewpoints/usability/views/usability_engineering_view/usability_engineering_view.sysml +8 -8
- package/src/viewpoints/verification/verification_viewpoint.sysml +0 -1
- package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml +19 -20
- package/stage1/opensysml-ddad9e2794141c08532910cf.json.gz +0 -0
- package/stage1/syside-8176a62528c701f2f2e0fc7f.ids.gz +0 -0
- package/stage1/syside-8176a62528c701f2f2e0fc7f.json.gz +0 -0
- package/templates/default/model/catalog/assurance/requirements.sysml +1 -1
- package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/extension-messaging'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: Publish/subscribe messaging — topics, brokers, and delivery semantics
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -2,11 +2,10 @@
|
|
|
2
2
|
// It specializes native item, port, and interface families; publication and
|
|
3
3
|
// subscription are expressed by port direction plus native flows/messages.
|
|
4
4
|
//
|
|
5
|
-
//
|
|
6
|
-
//
|
|
7
|
-
//
|
|
8
|
-
//
|
|
9
|
-
// have delivery semantics, the channel it publishes over does.
|
|
5
|
+
// `deliverySemantics` and `topicStructure` are here because neither is a
|
|
6
|
+
// property of a component: a component does not have a topic, a publication
|
|
7
|
+
// does; a component does not have delivery semantics, the channel it publishes
|
|
8
|
+
// over does.
|
|
10
9
|
package memo_extension_messaging {
|
|
11
10
|
private import memo_core_stdlib_quantities::*;
|
|
12
11
|
private import ScalarValues::*;
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/extension-ros'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: ROS 2 nodes, messages, topic/service/action interfaces, QoS, and containerized deployment
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -1,8 +1,7 @@
|
|
|
1
1
|
// ROS 2 (Robot Operating System 2).
|
|
2
2
|
//
|
|
3
|
-
// The acceptance test for MEMO's extension point
|
|
4
|
-
//
|
|
5
|
-
// actions, and
|
|
3
|
+
// The acceptance test for MEMO's extension point: a whole technology stack —
|
|
4
|
+
// nodes, messages, topics, quality of service, services, actions, and
|
|
6
5
|
// containerized deployment — landing without a single change to a base
|
|
7
6
|
// relation. `BuildsInto`, `DeploysTo`, and `ProvidesEnvironment` are reused
|
|
8
7
|
// exactly as the base declares them.
|
|
@@ -29,13 +28,9 @@ package memo_extension_ros {
|
|
|
29
28
|
|
|
30
29
|
// ── Quality of service ──────────────────────────────────────────────
|
|
31
30
|
//
|
|
32
|
-
//
|
|
33
|
-
//
|
|
34
|
-
//
|
|
35
|
-
// `PropertySet` stub, which was one String field and could not say what a
|
|
36
|
-
// reliability setting is. A typed profile can be validated, compared
|
|
37
|
-
// between a publisher and a subscriber, and read by a tool; a property bag
|
|
38
|
-
// cannot. `PropertySet` is deleted in this session for that reason.
|
|
31
|
+
// Per-technology properties live in a typed `attribute def` on the
|
|
32
|
+
// extension's own types. A typed profile can be validated, compared between
|
|
33
|
+
// a publisher and a subscriber, and read by a tool; a property bag cannot.
|
|
39
34
|
|
|
40
35
|
// TRANSIENT_LOCAL replays the last samples to a late-joining subscriber;
|
|
41
36
|
// VOLATILE does not. The difference decides whether a node that restarts
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/methodology-default'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: "MEMO default medical-device methodology \u2014 selects viewpoints/views/DHF documents from @memoarchitect/ontology and adds rules, gates, patterns, profiles, and workflow."
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/methodology-gpca'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: "GPCA infusion pump methodology \u2014 subtraction-based tailoring of @memoarchitect/methodology-default for the non-networked prototype variant. Excludes cybersecurity and SOUP."
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/ontology'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: "MEMO \u2014 the single canonical medical-device ontology: core semantics, the Arcadia-inspired architecture layers (context, requirements, behavior, structure, interfaces, risk, cybersecurity,\
|
|
12
12
|
\ assurance, \u2026), compliance, viewpoints, views, and invariant rules. One namespace (memo::), one src/ tree."
|
|
13
13
|
license: MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@memoarchitect/ontology",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.18.0",
|
|
4
4
|
"packageManager": "pnpm@9.15.0",
|
|
5
5
|
"description": "MEMO — Medical Engineering Modelling Ontology. Pure SysML v2 medical-device ontology with native constraints, portable to any conformant SysML v2 tool (SysIDE, SysON, sysand).",
|
|
6
6
|
"scripts": {
|
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
# (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
|
|
8
8
|
# removed at the native semantic flip and are now rejected if present.
|
|
9
9
|
name: '@memoarchitect/medical-modeling-profile'
|
|
10
|
-
version: 0.
|
|
10
|
+
version: 0.18.0
|
|
11
11
|
description: Closure rules and viewpoints for medical device modeling
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -52,12 +52,10 @@ package memo_architecture_functional_behavior {
|
|
|
52
52
|
attribute sourceReference : String;
|
|
53
53
|
}
|
|
54
54
|
|
|
55
|
-
// A behavioural obligation, such as an invariant, transition rule,
|
|
56
|
-
//
|
|
57
|
-
//
|
|
58
|
-
//
|
|
59
|
-
// VerifiableElement, which made a property a structural thing and left
|
|
60
|
-
// native `verify` unable to name it.
|
|
55
|
+
// A behavioural obligation, such as an invariant, transition rule, temporal
|
|
56
|
+
// claim, assumption, or guarantee. It is a `requirement def` because that
|
|
57
|
+
// is what it is: a claim the design must meet and a verification case can
|
|
58
|
+
// `verify`.
|
|
61
59
|
//
|
|
62
60
|
// `formalExpression` holds the property in the language `languageKind` names: natural language,
|
|
63
61
|
// a pseudo-formal text, AGREE, LTL or CTL. None of those is a SysML expression (the expression
|
|
@@ -72,34 +70,24 @@ package memo_architecture_functional_behavior {
|
|
|
72
70
|
// An assume/guarantee contract on one component, AGREE's shape one to one:
|
|
73
71
|
// the component is the `subject`, each assumption an `assume` member and
|
|
74
72
|
// each guarantee a `require` member naming a BehaviorProperty. The subject
|
|
75
|
-
//
|
|
76
|
-
// and could not be navigated.
|
|
73
|
+
// is a reference, so a contract can be navigated to its component.
|
|
77
74
|
//
|
|
78
75
|
// This is not the procurement contract of a deliverable; that is a
|
|
79
76
|
// different definition.
|
|
80
77
|
requirement def Contract :> MemoRequirementElement {
|
|
81
78
|
subject component : MemoPart;
|
|
82
79
|
}
|
|
83
|
-
// `part def PropertySet specializes VerifiableElement { attribute
|
|
84
|
-
// propertySetScope : String; }` stood here and is DELETED (plan C3,
|
|
85
|
-
// open question §14.6). It was AADL's property-set idea imported as a
|
|
86
|
-
// name: one String field, no typed content, no binding to whatever it
|
|
87
|
-
// annotated, and zero usages anywhere in the tree.
|
|
88
|
-
//
|
|
89
80
|
// Per-technology properties belong on the extension type that owns them,
|
|
90
|
-
// typed. ROS QoS
|
|
91
|
-
//
|
|
92
|
-
//
|
|
93
|
-
//
|
|
94
|
-
//
|
|
95
|
-
//
|
|
96
|
-
//
|
|
97
|
-
//
|
|
98
|
-
//
|
|
99
|
-
//
|
|
100
|
-
// `part def specializes MemoPart`, the same A0 residue `FunctionalFlow`
|
|
101
|
-
// carried, and a behaviour cannot specialize a structure, so nothing could
|
|
102
|
-
// have performed one.
|
|
81
|
+
// typed. ROS QoS shows the shape: `attribute def RosQosProfile` has
|
|
82
|
+
// reliability, durability, deadline, liveliness and history depth as typed
|
|
83
|
+
// fields, so a publisher's offer and a subscriber's request can be
|
|
84
|
+
// compared. Where an extension needs to annotate a BASE element rather than
|
|
85
|
+
// declare its own type, the SysML- native answer is `metadata def` +
|
|
86
|
+
// `Metaobjects::SemanticMetadata`, which is what every MEMO relation
|
|
87
|
+
// carries. An `action def`: every field it carries — what it does, what
|
|
88
|
+
// goes in and out, its worst-case execution time — describes behaviour. A
|
|
89
|
+
// behaviour cannot specialize a structure, so as a part nothing could
|
|
90
|
+
// perform one.
|
|
103
91
|
action def ActivityAction specializes FunctionalAction {
|
|
104
92
|
attribute actionKind : ActionKind;
|
|
105
93
|
attribute outputDescription : String;
|
|
@@ -1,30 +1,24 @@
|
|
|
1
|
-
// Functional architecture
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
1
|
+
// Functional architecture. A function is a responsibility: what the system, or
|
|
2
|
+
// one of its components, is answerable for. A FunctionalExchange is a typed
|
|
3
|
+
// transfer between functions. A function may be realized by human action,
|
|
4
|
+
// mechanical design, electrical hardware, software, or a combination —
|
|
5
5
|
// allocation to the system's own parts is what ComponentFunction records, and
|
|
6
6
|
// it never assumes software.
|
|
7
7
|
//
|
|
8
8
|
// ─── A function is a behaviour ───────────────────────────────────────────
|
|
9
9
|
//
|
|
10
|
-
// `MemoFunction` and both its specializations are `action def`s
|
|
11
|
-
//
|
|
12
|
-
//
|
|
13
|
-
//
|
|
14
|
-
//
|
|
15
|
-
// a part, and a separate `action def OperativeAction` carried the behaviour with a
|
|
16
|
-
// `ref performedFunction` stapling the two back together — a reference used in
|
|
17
|
-
// ZERO example files. The ends are metaclass-neutral now (CR-ONT-060..073), so
|
|
18
|
-
// the function's split from a part has no cause and is gone: `MemoFunction` is an `action def`,
|
|
19
|
-
// and `actionKind` sits on it, where it was always describing the function. `FunctionalFlow`
|
|
20
|
-
// was the one element A0 left behind on the part side; it is an `action def` now, for the same
|
|
21
|
-
// reason and on the same evidence.
|
|
10
|
+
// `MemoFunction` and both its specializations are `action def`s: a function is
|
|
11
|
+
// a behaviour. Relation ends are metaclass-neutral (CR-ONT-060..073), so a
|
|
12
|
+
// function can be satisfied, verified and allocated as one. `actionKind` sits
|
|
13
|
+
// on it because it describes the function. `FunctionalFlow` is an `action def`
|
|
14
|
+
// for the same reason.
|
|
22
15
|
//
|
|
23
|
-
// `OperativeAction`
|
|
24
|
-
// the operational layer (memo_architecture_operational_activities): a
|
|
25
|
-
// person or the system performs. The two are joined
|
|
26
|
-
//
|
|
27
|
-
//
|
|
16
|
+
// `OperativeAction` is NOT in the function family. It is a separate `action
|
|
17
|
+
// def` in the operational layer (memo_architecture_operational_activities): a
|
|
18
|
+
// step of the work, which a person or the system performs. The two are joined
|
|
19
|
+
// by native `perform`, not by a type: a system-performed level-2 activity
|
|
20
|
+
// `perform`s the `SystemFunction` that carries it out, and a function is
|
|
21
|
+
// performed only from such an activity or from a `FunctionalFlow` step.
|
|
28
22
|
//
|
|
29
23
|
// `functionCategory` and `actionKind` are NOT two spellings of one axis, and
|
|
30
24
|
// merging them would lose information. `actionKind` is the verb — sense,
|
|
@@ -35,12 +29,9 @@
|
|
|
35
29
|
// ─── A functional exchange is a flow ─────────────────────────────────────
|
|
36
30
|
//
|
|
37
31
|
// `FunctionalExchange` is an `abstract flow def`, and an exchange is a typed
|
|
38
|
-
// named `flow` between function parameters: the edge IS the exchange.
|
|
39
|
-
//
|
|
40
|
-
//
|
|
41
|
-
// target of an allocation or a trace. A named flow now carries a qualified id
|
|
42
|
-
// that `allocate`, `satisfy` and the rest resolve, so the part reached no
|
|
43
|
-
// rule, query or diagram and existed only to be kept in step with its edge.
|
|
32
|
+
// named `flow` between function parameters: the edge IS the exchange. A named
|
|
33
|
+
// flow carries a qualified id that `allocate`, `satisfy` and the rest resolve,
|
|
34
|
+
// so no separate part is needed.
|
|
44
35
|
//
|
|
45
36
|
// It is `abstract` because a flow definition specializes the association
|
|
46
37
|
// `Flows::MessageAction`, and a concrete association must declare its two
|
|
@@ -71,8 +62,8 @@
|
|
|
71
62
|
//
|
|
72
63
|
// Decomposition and allocation reuse the existing relations and need no new
|
|
73
64
|
// ones — `Composes` for the function tree, `AllocatedTo` for the component.
|
|
74
|
-
// Both
|
|
75
|
-
//
|
|
65
|
+
// Both are metaclass-neutral, which is what makes an action-def function
|
|
66
|
+
// usable.
|
|
76
67
|
package memo_architecture_functional_functions {
|
|
77
68
|
private import memo_core_stdlib_quantities::*;
|
|
78
69
|
private import Metaobjects::SemanticMetadata;
|
|
@@ -88,9 +79,10 @@ package memo_architecture_functional_functions {
|
|
|
88
79
|
attribute functionCategory : String;
|
|
89
80
|
attribute actionKind : ActionKind;
|
|
90
81
|
attribute trigger : String;
|
|
91
|
-
// What the function produces, in words: the part the typed `out`
|
|
92
|
-
// names the item, not that it is
|
|
93
|
-
//
|
|
82
|
+
// What the function produces, in words: the part the typed `out`
|
|
83
|
+
// parameters cannot say (their type names the item, not that it is
|
|
84
|
+
// debounced, range-checked or timestamped). It does not restate the
|
|
85
|
+
// parameters, and what goes in is the `in` parameters alone.
|
|
94
86
|
attribute outputDescription : String;
|
|
95
87
|
attribute concernKind : ConcernKind;
|
|
96
88
|
attribute criticality : CriticalityKind;
|
|
@@ -135,17 +127,12 @@ package memo_architecture_functional_functions {
|
|
|
135
127
|
// A reusable functional route through system responsibilities. Functional
|
|
136
128
|
// flows are part of functional architecture, never logical structure.
|
|
137
129
|
//
|
|
138
|
-
// An `action def`, like every other behaviour in MEMO.
|
|
139
|
-
//
|
|
140
|
-
//
|
|
141
|
-
// KerML forbids a behaviour from specializing one — and it was the single
|
|
142
|
-
// element A0 did not carry across when that reason went away. A route
|
|
143
|
-
// through responsibilities is the same shape as the `OperationalWorkflow`
|
|
144
|
-
// and `OperativeScenario` it sits beside: the scenarios package calls a
|
|
130
|
+
// An `action def`, like every other behaviour in MEMO. A route through
|
|
131
|
+
// responsibilities is the same shape as the `OperationalWorkflow` and
|
|
132
|
+
// `OperativeScenario` it sits beside: the scenarios package calls a
|
|
145
133
|
// scenario "a selected path through a workflow (or functional flow)",
|
|
146
134
|
// naming the two as one kind of thing, and its steps are `action def`s
|
|
147
|
-
// already.
|
|
148
|
-
// has not been allowed to say so.
|
|
135
|
+
// already.
|
|
149
136
|
action def FunctionalFlow specializes MemoAction {
|
|
150
137
|
attribute flowCategory : FunctionalFlowKind;
|
|
151
138
|
attribute endToEndLatencyBudgetMs : DurationValue;
|
|
@@ -170,7 +157,7 @@ package memo_architecture_functional_functions {
|
|
|
170
157
|
// between two steps' parameters. A step's parameters redefine its
|
|
171
158
|
// function's by position.
|
|
172
159
|
|
|
173
|
-
// `
|
|
174
|
-
//
|
|
175
|
-
//
|
|
160
|
+
// A `FunctionalFlow` involves a function by native `perform`: it performs
|
|
161
|
+
// the function each of its steps subsets, and a flow with no steps performs
|
|
162
|
+
// its functions directly.
|
|
176
163
|
}
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// Physical realization taxonomy
|
|
1
|
+
// Physical realization taxonomy — shared roots. "Physical" encompasses
|
|
2
2
|
// hardware, mechanical, fluidic, pneumatic, optical, acoustic, and thermal
|
|
3
3
|
// realization — not only electronics. Assemblies compose components; patient-
|
|
4
4
|
// contacting parts must declare contact characteristics (ISO 10993-1;
|
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
// Electrical / electronic realization subgroup
|
|
2
|
-
//
|
|
3
|
-
//
|
|
1
|
+
// Electrical / electronic realization subgroup. Electrical power and signal
|
|
2
|
+
// parts, plus cabling and connectivity media, specialize the physical roots in
|
|
3
|
+
// memo_architecture_implementation_hardware_common.
|
|
4
4
|
package memo_architecture_implementation_hardware_electrical {
|
|
5
5
|
private import ScalarValues::*;
|
|
6
6
|
private import memo_architecture_implementation_hardware_common::*;
|
|
@@ -1,5 +1,6 @@
|
|
|
1
|
-
// Fluidic / pneumatic realization subgroup
|
|
2
|
-
// specialize the physical roots in
|
|
1
|
+
// Fluidic / pneumatic realization subgroup. Fluid- and gas-path parts
|
|
2
|
+
// specialize the physical roots in
|
|
3
|
+
// memo_architecture_implementation_hardware_common.
|
|
3
4
|
package memo_architecture_implementation_hardware_fluidic {
|
|
4
5
|
private import ScalarValues::*;
|
|
5
6
|
private import memo_architecture_implementation_hardware_common::*;
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
// Mechanical realization subgroup
|
|
2
|
-
//
|
|
1
|
+
// Mechanical realization subgroup. Structural and housing parts specialize the
|
|
2
|
+
// physical roots in memo_architecture_implementation_hardware_common.
|
|
3
3
|
package memo_architecture_implementation_hardware_mechanical {
|
|
4
4
|
private import ScalarValues::*;
|
|
5
5
|
private import memo_architecture_implementation_hardware_common::*;
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
// Optical realization subgroup
|
|
2
|
-
//
|
|
1
|
+
// Optical realization subgroup. Light-path parts specialize the physical roots
|
|
2
|
+
// in memo_architecture_implementation_hardware_common.
|
|
3
3
|
package memo_architecture_implementation_hardware_optical {
|
|
4
4
|
private import ScalarValues::*;
|
|
5
5
|
private import memo_architecture_implementation_hardware_common::*;
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
// Sensing / actuation realization subgroup
|
|
2
|
-
//
|
|
1
|
+
// Sensing / actuation realization subgroup. Transducers that measure or act on
|
|
2
|
+
// the physical world specialize the physical roots in
|
|
3
3
|
// memo_architecture_implementation_hardware_common.
|
|
4
4
|
package memo_architecture_implementation_hardware_sensing {
|
|
5
5
|
private import ScalarValues::*;
|
|
@@ -1,7 +1,8 @@
|
|
|
1
|
-
// Physical realization taxonomy
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
// `memo_architecture_implementation_hardware_structure`, so importers see one
|
|
1
|
+
// Physical realization taxonomy — aggregator. The hardware subgroup is split by
|
|
2
|
+
// technology domain into nested packages; this package re-exports the shared
|
|
3
|
+
// roots plus every domain subgroup under the historical name
|
|
4
|
+
// `memo_architecture_implementation_hardware_structure`, so importers see one
|
|
5
|
+
// flat surface.
|
|
5
6
|
package memo_architecture_implementation_hardware_structure {
|
|
6
7
|
public import memo_architecture_implementation_hardware_common::*;
|
|
7
8
|
public import memo_architecture_implementation_hardware_electrical::*;
|
|
@@ -1,15 +1,15 @@
|
|
|
1
|
-
// Software runtime (component-and-connector) view
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
1
|
+
// Software runtime (component-and-connector) view, matching the SEI Views and
|
|
2
|
+
// Beyond distinction between runtime components and implementation modules.
|
|
3
|
+
// Runtime structure carries concurrency, scheduling, health monitoring, fault
|
|
4
|
+
// containment, and update/rollback semantics. Module structure lives in
|
|
5
5
|
// memo_architecture_implementation_software_structure; allocation in
|
|
6
6
|
// memo_architecture_realization_deployment.
|
|
7
7
|
//
|
|
8
|
-
// Detailed AADL categories live in the AADL correspondence profile, which is
|
|
9
|
-
//
|
|
10
|
-
//
|
|
11
|
-
//
|
|
12
|
-
//
|
|
8
|
+
// Detailed AADL categories live in the AADL correspondence profile, which is an
|
|
9
|
+
// extension package: `extensions/aadl`. It carries the process / thread /
|
|
10
|
+
// virtual-processor families and a correspondence rule per mapped name and
|
|
11
|
+
// property. This comment pointed at `examples/aadl-mapping` for a long time and
|
|
12
|
+
// that directory never existed; the pointer above resolves.
|
|
13
13
|
package memo_architecture_implementation_software_runtime {
|
|
14
14
|
private import memo_core_stdlib_quantities::*;
|
|
15
15
|
private import Metaobjects::SemanticMetadata;
|
|
@@ -56,12 +56,9 @@ package memo_architecture_implementation_software_runtime {
|
|
|
56
56
|
attribute auditable : Boolean;
|
|
57
57
|
attribute updatePolicy : String;
|
|
58
58
|
attribute rollbackPolicy : String;
|
|
59
|
-
//
|
|
60
|
-
//
|
|
61
|
-
//
|
|
62
|
-
// no business asserting. They are gone; every one of them now lives on
|
|
63
|
-
// a type in an extension, where it is unconditional and therefore
|
|
64
|
-
// checkable (plan §10.3 D3, extensions/README.md):
|
|
59
|
+
// An attribute that applies to only one `runtimeKind` lives on a type
|
|
60
|
+
// in an extension, where it is unconditional and therefore checkable
|
|
61
|
+
// (extensions/README.md):
|
|
65
62
|
//
|
|
66
63
|
// addressSpaceIsolated, owningProcessName,
|
|
67
64
|
// partitionBudget, isolationMechanism -> extensions/aadl
|
|
@@ -70,13 +67,13 @@ package memo_architecture_implementation_software_runtime {
|
|
|
70
67
|
// imageReference, orchestrationPlatform -> extensions/container
|
|
71
68
|
// deliverySemantics, topicStructure -> extensions/messaging
|
|
72
69
|
//
|
|
73
|
-
// The last two
|
|
74
|
-
// have a topic, a publication does.
|
|
70
|
+
// The last two are not component properties at all: a component does
|
|
71
|
+
// not have a topic, a publication does.
|
|
75
72
|
//
|
|
76
|
-
// What
|
|
73
|
+
// What is here is what is true of EVERY runtime component in every
|
|
77
74
|
// regulated project — the AADL thread properties above and the
|
|
78
|
-
// assurance ones — plus `runtimeKind` itself, which says which family
|
|
79
|
-
//
|
|
75
|
+
// assurance ones — plus `runtimeKind` itself, which says which family a
|
|
76
|
+
// component belongs to without claiming to describe it.
|
|
80
77
|
}
|
|
81
78
|
|
|
82
79
|
// A runtime service or process that exists only because an OTS module is
|
|
@@ -141,8 +141,8 @@ package memo_architecture_implementation_software_structure {
|
|
|
141
141
|
part sbomEntry : SBOMEntry[0..*];
|
|
142
142
|
}
|
|
143
143
|
|
|
144
|
-
//
|
|
145
|
-
//
|
|
144
|
+
// One module using another is a native `dependency`: write `dependency
|
|
145
|
+
// <usingModule> to <usedModule>;`.
|
|
146
146
|
|
|
147
147
|
// ── Relations owned by this package ─────────────────────────────
|
|
148
148
|
// Moved out of memo_core_relationships: their ends are typed against
|
|
@@ -1,9 +1,9 @@
|
|
|
1
|
-
// User interface and interaction
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
// from device modes (memo_architecture_logical_structure::LogicalMode).
|
|
5
|
-
//
|
|
6
|
-
//
|
|
1
|
+
// User interface and interaction. A small semantic hierarchy: concrete widget
|
|
2
|
+
// forms (button, knob, chart …) are enum classifications, not classes. UI state
|
|
3
|
+
// is distinct from system state (memo_architecture_functional_behavior) and
|
|
4
|
+
// from device modes (memo_architecture_logical_structure::LogicalMode). UI is
|
|
5
|
+
// an implementation concern (rendered UI is software; physical controls are
|
|
6
|
+
// hardware), so it lives in the implementation layer, not operational.
|
|
7
7
|
package memo_architecture_implementation_ui {
|
|
8
8
|
private import Metaobjects::SemanticMetadata;
|
|
9
9
|
private import ScalarValues::*;
|
|
@@ -93,7 +93,7 @@ package memo_architecture_implementation_ui {
|
|
|
93
93
|
enum imported;
|
|
94
94
|
}
|
|
95
95
|
|
|
96
|
-
// The interaction intents a step or action can carry
|
|
96
|
+
// The interaction intents a step or action can carry.
|
|
97
97
|
enum def InteractionIntentKind {
|
|
98
98
|
enum userInput;
|
|
99
99
|
enum feedback;
|
|
@@ -115,15 +115,10 @@ package memo_architecture_implementation_ui {
|
|
|
115
115
|
attribute uiTechnology : String;
|
|
116
116
|
}
|
|
117
117
|
|
|
118
|
-
// `
|
|
119
|
-
//
|
|
120
|
-
//
|
|
121
|
-
//
|
|
122
|
-
// IEC 62366-1 puts the whole means of interaction in scope — a mis-keyed
|
|
123
|
-
// connector, a moulded marking on a housing, a tube routed backwards are
|
|
124
|
-
// use errors at parts that were never interaction elements and so could
|
|
125
|
-
// not be named. `ErrorAtElement` and `ElementTriggersAction` now take
|
|
126
|
-
// `MemoPart`; the attributes moved to whichever type actually set them.
|
|
118
|
+
// `ErrorAtElement` and `ElementTriggersAction` take `MemoPart`: IEC 62366-1
|
|
119
|
+
// puts the whole means of interaction in scope, and a mis-keyed connector,
|
|
120
|
+
// a moulded marking on a housing, a tube routed backwards are use errors at
|
|
121
|
+
// parts that are not interface elements.
|
|
127
122
|
|
|
128
123
|
// One UIElement — the single UI part type. The widget form — holding
|
|
129
124
|
// (screen/panel/dialog), acting (button/knob/slider), presenting
|
|
@@ -204,10 +199,9 @@ package memo_architecture_implementation_ui {
|
|
|
204
199
|
// device shows back — because a front panel is one interface, not two.
|
|
205
200
|
//
|
|
206
201
|
// It is a PhysicalComponent, so it inherits part number, material, and the
|
|
207
|
-
// ISO 10993-1 patient-contact characterization that a touched surface
|
|
208
|
-
//
|
|
209
|
-
//
|
|
210
|
-
// were software items with no way to state any of it.
|
|
202
|
+
// ISO 10993-1 patient-contact characterization that a touched surface needs
|
|
203
|
+
// and that software can never have. That inheritance is why these forms are
|
|
204
|
+
// not UIElement forms: a UIElement is software and cannot state any of it.
|
|
211
205
|
enum def OperatorInterfaceFormKind {
|
|
212
206
|
// ── actuated by the operator ──
|
|
213
207
|
enum knob;
|
|
@@ -275,11 +269,9 @@ package memo_architecture_implementation_ui {
|
|
|
275
269
|
|
|
276
270
|
// Clicking a button IS an operative action: it has a trigger, a
|
|
277
271
|
// precondition, a criticality, a potential harm and a frequency of use,
|
|
278
|
-
// exactly as turning a knob does.
|
|
279
|
-
//
|
|
280
|
-
//
|
|
281
|
-
// (source end: OperativeAction) would not accept it, so a use error
|
|
282
|
-
// committed by a click was unmodellable.
|
|
272
|
+
// exactly as turning a knob does. So UIAction specializes OperativeAction:
|
|
273
|
+
// it carries those attributes, and `CommitsUseError` (source end:
|
|
274
|
+
// OperativeAction) accepts a use error committed by a click.
|
|
283
275
|
//
|
|
284
276
|
// The three attributes here are what a UI action adds on top: what the
|
|
285
277
|
// user meant by it, what came back, and whether it asks first.
|
|
@@ -296,14 +288,11 @@ package memo_architecture_implementation_ui {
|
|
|
296
288
|
attribute exitPoint : String;
|
|
297
289
|
}
|
|
298
290
|
|
|
299
|
-
// `
|
|
300
|
-
//
|
|
301
|
-
//
|
|
302
|
-
//
|
|
303
|
-
// `
|
|
304
|
-
// state"). Free deletion rather than a migration — nothing referenced
|
|
305
|
-
// it, so nothing to preserve. If `UIState` is ever restructured onto a
|
|
306
|
-
// real state machine, `exhibit state` becomes available then.
|
|
291
|
+
// `UIState` is a `part def` with plain string attributes, not a `state
|
|
292
|
+
// def`, so `exhibit state` cannot name it: a SysML v2 compiler rejects
|
|
293
|
+
// `exhibit` referencing anything that does not conform to
|
|
294
|
+
// `States::StateAction`. If `UIState` is restructured onto a real state
|
|
295
|
+
// machine, `exhibit state` becomes available.
|
|
307
296
|
|
|
308
297
|
// ── Screen layout relations ──────────────────────────────────
|
|
309
298
|
// Which modelled screen an image is a rendering of.
|
|
@@ -319,14 +308,13 @@ package memo_architecture_implementation_ui {
|
|
|
319
308
|
}
|
|
320
309
|
|
|
321
310
|
// Activating this element opens another screen. This is NAVIGATION, not
|
|
322
|
-
// containment — the opened screen is not laid out inside the element, so
|
|
323
|
-
//
|
|
324
|
-
//
|
|
325
|
-
//
|
|
326
|
-
// from here, and only this relation says so.
|
|
311
|
+
// containment — the opened screen is not laid out inside the element, so it
|
|
312
|
+
// is not a Composes child and the geometric rules do not relate them.
|
|
313
|
+
// "Clicking takes you to a child view" is not spatial nesting: it is a
|
|
314
|
+
// separate frame reached from here, and only this relation says so.
|
|
327
315
|
//
|
|
328
|
-
//
|
|
329
|
-
//
|
|
316
|
+
// connection goToSettings : NavigatesTo connect homeScreen.settingsButton
|
|
317
|
+
// to settingsScreen;
|
|
330
318
|
//
|
|
331
319
|
// A screen is a UIElement whose `formKind` is `screen`; the end says UIElement because the form is an
|
|
332
320
|
// attribute, not a subtype.
|
|
@@ -341,7 +329,7 @@ package memo_architecture_implementation_ui {
|
|
|
341
329
|
:>> baseType = navigatesToLinks meta SysML::Usage;
|
|
342
330
|
}
|
|
343
331
|
|
|
344
|
-
// ──
|
|
332
|
+
// ── Traceability ─────────────────────────────────────────
|
|
345
333
|
// Source is `MemoPart`, not a UI-specific base: a foot pedal and a
|
|
346
334
|
// rendered button trigger the same kind of action, and the two are a
|
|
347
335
|
// PhysicalComponent and a SoftwareElement whose only common ancestor is
|
|
@@ -357,8 +345,8 @@ package memo_architecture_implementation_ui {
|
|
|
357
345
|
:> annotatedElement : SysML::ConnectionUsage;
|
|
358
346
|
:>> baseType = elementTriggersActionLinks meta SysML::Usage;
|
|
359
347
|
}
|
|
360
|
-
//
|
|
361
|
-
//
|
|
348
|
+
// A UI action invokes a function by native `perform`: write `perform
|
|
349
|
+
// <systemFunction>;` inside the `UIAction` usage.
|
|
362
350
|
connection def FlowServesUseCase :> MemoRelationship {
|
|
363
351
|
end interactionFlow : InteractionFlow :>> source;
|
|
364
352
|
end useCase : UseCase :>> target;
|
|
@@ -377,6 +365,7 @@ package memo_architecture_implementation_ui {
|
|
|
377
365
|
// backwards — not only on a control. Narrowing this to an interaction
|
|
378
366
|
// base made those unmodellable.
|
|
379
367
|
connection def ErrorAtElement :> MemoRelationship {
|
|
368
|
+
attribute :>> isTrace = true;
|
|
380
369
|
end useError : UseError :>> source;
|
|
381
370
|
end element : MemoPart :>> target;
|
|
382
371
|
}
|
|
@@ -389,6 +378,7 @@ package memo_architecture_implementation_ui {
|
|
|
389
378
|
// A risk control implemented by a UI element or by task design
|
|
390
379
|
// (confirmation dialog, lockout, guarded control).
|
|
391
380
|
connection def ControlImplementedBy :> MemoRelationship {
|
|
381
|
+
attribute :>> isTrace = true;
|
|
392
382
|
end riskControl : RiskControlMeasure :>> source;
|
|
393
383
|
end implementingElement :>> target;
|
|
394
384
|
}
|