@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
|
@@ -3,18 +3,13 @@
|
|
|
3
3
|
//
|
|
4
4
|
// ─── A component exchange is an interface ────────────────────────────────
|
|
5
5
|
//
|
|
6
|
-
// `ComponentExchange` is an `interface def`: the edge between two ports IS
|
|
7
|
-
//
|
|
8
|
-
// refs named the ports, beside a separate `flow` or `bind` naming them again,
|
|
9
|
-
// and CR-ONT-076 existed only to keep the two representations in step. It
|
|
10
|
-
// also lost information: the builder stored a dotted ref value as its first
|
|
11
|
-
// segment only, so every endpoint read as the enclosing device, and
|
|
12
|
-
// CR-ONT-072/073 checked the device instead of the port.
|
|
6
|
+
// `ComponentExchange` is an `interface def`: the edge between two ports IS the
|
|
7
|
+
// exchange.
|
|
13
8
|
//
|
|
14
|
-
// Its ends are the ports, and they are ports, never components:
|
|
15
|
-
//
|
|
16
|
-
//
|
|
17
|
-
//
|
|
9
|
+
// Its ends are the ports, and they are ports, never components: an exchange
|
|
10
|
+
// needs an actual boundary port, and a rule (CR-ONT-072/073) says so because
|
|
11
|
+
// the compiler does not — it accepts a part at an interface end even when the
|
|
12
|
+
// definition types its ends.
|
|
18
13
|
//
|
|
19
14
|
// ─── Transport, delegation, and the choice between them ──────────────────
|
|
20
15
|
//
|
|
@@ -43,14 +38,14 @@ package memo_architecture_logical_interfaces {
|
|
|
43
38
|
private import memo_architecture_functional_functions::*;
|
|
44
39
|
|
|
45
40
|
// ─── One Interface definition ────────────────────────────────────
|
|
46
|
-
// Realization domain (hardware vs software), signaling family
|
|
47
|
-
//
|
|
48
|
-
//
|
|
49
|
-
//
|
|
50
|
-
//
|
|
51
|
-
//
|
|
52
|
-
//
|
|
53
|
-
//
|
|
41
|
+
// Realization domain (hardware vs software), signaling family (digital /
|
|
42
|
+
// analog / synchronous / asynchronous) and concrete protocol (SPI, CAN,
|
|
43
|
+
// Ethernet, 4-20mA, REST, gRPC, message-queue …) are captured by
|
|
44
|
+
// `interfaceKind` + `protocol`, NOT by a class branch. Every descriptive
|
|
45
|
+
// attribute below is optional, so an interface carries only the ones that
|
|
46
|
+
// apply to it. There is no HardwareInterface / DigitalInterface /
|
|
47
|
+
// SPIInterface / RestInterface … hierarchy: such classes would differ only
|
|
48
|
+
// in the value of `protocol`.
|
|
54
49
|
|
|
55
50
|
// The common contract of an interface, whatever layer it is on: what
|
|
56
51
|
// crosses, which way, under what timing, and how much it matters to
|
|
@@ -154,16 +149,15 @@ package memo_architecture_logical_interfaces {
|
|
|
154
149
|
// data port), modeled as a first-class element so exchanges can
|
|
155
150
|
// reference it and views can render the system boundary.
|
|
156
151
|
//
|
|
157
|
-
// A `port def`
|
|
158
|
-
//
|
|
159
|
-
//
|
|
160
|
-
// `portKind` is duplicated on both ports instead of hoisted onto a base.
|
|
152
|
+
// A `port def` — see PhysicalPort in memo_architecture_realization_physical
|
|
153
|
+
// for why `direction` is native and why `portKind` is declared on both
|
|
154
|
+
// ports instead of on a base.
|
|
161
155
|
port def SoftwarePort specializes MemoPort {
|
|
162
156
|
attribute portKind : InterfaceKind;
|
|
163
|
-
// AADL port category
|
|
164
|
-
//
|
|
165
|
-
//
|
|
166
|
-
//
|
|
157
|
+
// AADL port category. Sampled vs. queued delivery decides whether a
|
|
158
|
+
// missed deadline drops a sample or grows a queue, which the timing
|
|
159
|
+
// analysis and the safety case both need. `portKind` says what crosses;
|
|
160
|
+
// this says how.
|
|
167
161
|
attribute portCategory : PortCategoryKind;
|
|
168
162
|
attribute dataTypeName : String;
|
|
169
163
|
}
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
// Logical architecture
|
|
2
|
-
//
|
|
1
|
+
// Logical architecture. Technology-independent structure: what parts of the
|
|
2
|
+
// solution exist and how they interact, before committing to software,
|
|
3
3
|
// electronics, or mechanics. Redundancy is expressed by typed channel roles
|
|
4
4
|
// plus independence constraints — never by duplicating identically named
|
|
5
5
|
// components.
|
|
@@ -13,7 +13,7 @@ package memo_architecture_logical_structure {
|
|
|
13
13
|
private import memo_architecture_logical_interfaces::Interface;
|
|
14
14
|
|
|
15
15
|
// What a logical connection carries: information and control, but also
|
|
16
|
-
// energy, material, fluid, and mechanical force
|
|
16
|
+
// energy, material, fluid, and mechanical force.
|
|
17
17
|
enum def FlowContentKind {
|
|
18
18
|
enum information;
|
|
19
19
|
enum command;
|
|
@@ -190,19 +190,16 @@ package memo_architecture_logical_structure {
|
|
|
190
190
|
// attribute :>> contentKind = FlowContentKind::measurement;
|
|
191
191
|
// }
|
|
192
192
|
//
|
|
193
|
-
//
|
|
194
|
-
//
|
|
195
|
-
//
|
|
196
|
-
// and its payload the item feature on them. `direction` is not carried
|
|
197
|
-
// over: the ports say `in` and `out`, and a second writable direction is
|
|
198
|
-
// the duplicate §8 of the architecture plan forbids.
|
|
193
|
+
// The flow's ends are those ports, and its payload the item feature on
|
|
194
|
+
// them. It declares no `direction`: the ports say `in` and `out`, and a
|
|
195
|
+
// second writable direction would be a duplicate.
|
|
199
196
|
//
|
|
200
|
-
// The ends are not restricted to `LogicalPort`.
|
|
201
|
-
//
|
|
202
|
-
//
|
|
203
|
-
//
|
|
204
|
-
//
|
|
205
|
-
//
|
|
197
|
+
// The ends are not restricted to `LogicalPort`. A flow may move a specimen
|
|
198
|
+
// or a force between hardware parts, and a flow def that named
|
|
199
|
+
// `LogicalPort` ends would refuse it. `payload` is not declared either: `of
|
|
200
|
+
// <type>` on a usage of a flow def that declares a feature is not
|
|
201
|
+
// distinguishable (namespace distinguishability) from the library's own
|
|
202
|
+
// `payload`, so the payload lives on the ports.
|
|
206
203
|
abstract flow def LogicalExchange {
|
|
207
204
|
attribute contentKind : FlowContentKind;
|
|
208
205
|
attribute latencyRequirement : String;
|
|
@@ -222,7 +219,7 @@ package memo_architecture_logical_structure {
|
|
|
222
219
|
attribute executionSemantics : String;
|
|
223
220
|
}
|
|
224
221
|
|
|
225
|
-
// Isolation, fault containment, and trust boundaries
|
|
222
|
+
// Isolation, fault containment, and trust boundaries.
|
|
226
223
|
part def IsolationBoundary specializes MemoPart {
|
|
227
224
|
attribute boundaryKind : String;
|
|
228
225
|
attribute isolationMechanism : String;
|
|
@@ -243,7 +240,7 @@ package memo_architecture_logical_structure {
|
|
|
243
240
|
:> annotatedElement : SysML::ConnectionUsage;
|
|
244
241
|
:>> baseType = independentOfLinks meta SysML::Usage;
|
|
245
242
|
}
|
|
246
|
-
//
|
|
247
|
-
// `dependency <monitorChannel> to <monitoredComponent
|
|
243
|
+
// A channel monitoring a component is a native `dependency`: write
|
|
244
|
+
// `dependency <monitorChannel> to <monitoredComponent>;`.
|
|
248
245
|
|
|
249
246
|
}
|
|
@@ -68,8 +68,8 @@ package memo_architecture_operational_activities {
|
|
|
68
68
|
attribute feedbackExpected : String;
|
|
69
69
|
}
|
|
70
70
|
|
|
71
|
-
// Difficulty of a task in a particular context
|
|
72
|
-
//
|
|
71
|
+
// Difficulty of a task in a particular context. Associated by typed
|
|
72
|
+
// references, not inheritance; assessments are evidence-bearing.
|
|
73
73
|
part def TaskDifficultyAssessment specializes MemoPart {
|
|
74
74
|
attribute overallDifficulty : DemandLevelKind;
|
|
75
75
|
attribute physicalDemand : DemandLevelKind;
|
|
@@ -1,10 +1,11 @@
|
|
|
1
|
-
// Operational participants
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
//
|
|
6
|
-
//
|
|
7
|
-
// performers, so there is no "personnel" resource kind, which would
|
|
1
|
+
// Operational participants interact with the system. A stakeholder — someone
|
|
2
|
+
// with a concern about the system who need not interact with it — is a native
|
|
3
|
+
// SysML notion (a Part in a stakeholder membership on a concern or viewpoint),
|
|
4
|
+
// not a separate MEMO type; the same Part may fill both roles. "User" is
|
|
5
|
+
// reserved for a human who interacts with the medical device. A User is also a
|
|
6
|
+
// `MemoResource`: staff are a resource with a capacity cost rate, and are
|
|
7
|
+
// already the performers, so there is no "personnel" resource kind, which would
|
|
8
|
+
// be a second spelling of User.
|
|
8
9
|
package memo_architecture_operational_context_actors {
|
|
9
10
|
private import ScalarValues::*;
|
|
10
11
|
|
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
// ISO/IEC/IEEE 42010 architecture-description core
|
|
1
|
+
// ISO/IEC/IEEE 42010 architecture-description core: ArchitectureDescription,
|
|
2
2
|
// ModelKind, and CorrespondenceRule below. Stakeholders and concerns — 42010's
|
|
3
3
|
// other cornerstones — are native SysML v2 constructs (stakeholder memberships
|
|
4
4
|
// and `concern def`), used directly rather than reinvented as MEMO types. A
|
|
@@ -2,13 +2,12 @@
|
|
|
2
2
|
// reasonably foreseeable misuse are assurance requirements/risk inputs and
|
|
3
3
|
// live in memo_assurance_requirements.
|
|
4
4
|
//
|
|
5
|
-
//
|
|
6
|
-
// flow
|
|
7
|
-
//
|
|
8
|
-
//
|
|
9
|
-
//
|
|
10
|
-
//
|
|
11
|
-
// `flow`, ch. 12 delegates across a boundary with `bind`.
|
|
5
|
+
// Directional context-level data flow between boundary entities is SysML v2's
|
|
6
|
+
// own `flow`, because `of <ItemDef>` says WHAT moves and two untyped connection
|
|
7
|
+
// ends cannot. Delegation between a boundary port and the interior it stands
|
|
8
|
+
// for is `bind` — identity, not transport. SysML v2 keeps the two apart the
|
|
9
|
+
// same way: training ch. 13 wires components with `flow`, ch. 12 delegates
|
|
10
|
+
// across a boundary with `bind`.
|
|
12
11
|
package memo_architecture_operational_context_use_context {
|
|
13
12
|
private import Metaobjects::SemanticMetadata;
|
|
14
13
|
private import ScalarValues::*;
|
|
@@ -66,12 +65,9 @@ package memo_architecture_operational_context_use_context {
|
|
|
66
65
|
:>> baseType = interactsInContextLinks meta SysML::Usage;
|
|
67
66
|
}
|
|
68
67
|
|
|
69
|
-
//
|
|
70
|
-
// `connection connect <
|
|
71
|
-
//
|
|
72
|
-
// `ConnectsPhysically` is native `connect` (R10-S6): write
|
|
73
|
-
// `connection connect source ::> <a> to target ::> <b>;` — the ordinary
|
|
74
|
-
// untyped binary connection — instead of a connection def for it.
|
|
68
|
+
// An interaction between participants, or a physical connection, is native
|
|
69
|
+
// `connect`: write `connection connect <a> to <b>;`, the ordinary untyped
|
|
70
|
+
// binary connection.
|
|
75
71
|
connection def AppliesInContext :> MemoRelationship {
|
|
76
72
|
end useContext : UseContext :>> source;
|
|
77
73
|
end subjectElement : MemoPart :>> target;
|
|
@@ -1,7 +1,8 @@
|
|
|
1
|
-
// Roll-ups of a level-2 procedure flow
|
|
2
|
-
// activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of
|
|
3
|
-
// and every figure above it is derived here: a scenario, a
|
|
4
|
-
// compares variants by these, so nothing a
|
|
1
|
+
// Roll-ups of a level-2 procedure flow. A number is entered once, on an
|
|
2
|
+
// activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of
|
|
3
|
+
// its `instruments`), and every figure above it is derived here: a scenario, a
|
|
4
|
+
// procedure, a variant. A `TradeStudy` compares variants by these, so nothing a
|
|
5
|
+
// study reads is typed in twice.
|
|
5
6
|
//
|
|
6
7
|
// ─── Traversal ──────────────────────────────────────────────────────────
|
|
7
8
|
// `ActivitiesOf` is the one place that decides which activities count, and every roll-up reads
|
|
@@ -19,8 +20,8 @@
|
|
|
19
20
|
// quantities with units; money is `memo_core_stdlib_money`, in the project's one currency.
|
|
20
21
|
// A cost is the activity's duration times each instrument's capacity cost rate, plus each
|
|
21
22
|
// instrument's unit cost. Parallel branches are each paid for, because each resource used is
|
|
22
|
-
// paid for. Time is the
|
|
23
|
-
//
|
|
23
|
+
// paid for. Time is the longest path (`ScenarioDuration`), so a fork whose branches
|
|
24
|
+
// overlap takes its longest branch; a cost is still the sum, because each branch is paid for.
|
|
24
25
|
//
|
|
25
26
|
// `memo evaluate` runs them from these bodies over the built model (memo-tools, analysis/calc), and a
|
|
26
27
|
// `TradeStudy` reads the results, so no figure is written twice. Units follow the SysML library's own
|
|
@@ -59,10 +60,25 @@ package memo_architecture_operational_rollups {
|
|
|
59
60
|
ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; ActivityCost(activity) });
|
|
60
61
|
}
|
|
61
62
|
|
|
63
|
+
// The time at which a step is done: its own duration after the latest of the steps before it.
|
|
64
|
+
// `predecessors` is the kernel library's (every earlier occurrence along the successions, not
|
|
65
|
+
// only the adjacent ones), which is enough because a step's finish time never falls short of
|
|
66
|
+
// the finish time of anything before it. A step with no succession to another is concurrent
|
|
67
|
+
// with it, as in the language, so two branches of a fork overlap and a scenario takes as long
|
|
68
|
+
// as its longest path, not the sum of its steps.
|
|
69
|
+
calc def FinishTime {
|
|
70
|
+
in activity : OperativeAction[1];
|
|
71
|
+
return finish : DurationValue[1] = QuantityCalculations::sum((
|
|
72
|
+
activity.expectedDuration,
|
|
73
|
+
activity.predecessors->collect { in before : OperativeAction[1]; FinishTime(before) }
|
|
74
|
+
->reduce { in x : DurationValue[1]; in y : DurationValue[1]; NumericalFunctions::max(x, y) }));
|
|
75
|
+
}
|
|
76
|
+
|
|
62
77
|
calc def ScenarioDuration {
|
|
63
78
|
in scenario : MemoAction[1];
|
|
64
|
-
return duration : DurationValue[1] =
|
|
65
|
-
|
|
79
|
+
return duration : DurationValue[1] = ActivitiesOf(scenario)
|
|
80
|
+
->collect { in activity : OperativeAction[1]; FinishTime(activity) }
|
|
81
|
+
->reduce { in x : DurationValue[1]; in y : DurationValue[1]; NumericalFunctions::max(x, y) };
|
|
66
82
|
}
|
|
67
83
|
|
|
68
84
|
calc def ScenarioSuccess {
|
|
@@ -48,11 +48,10 @@ package memo_architecture_operational_scenarios {
|
|
|
48
48
|
// (a robot and a laparoscopic tower do not convert to open at the same rate); level 2 only.
|
|
49
49
|
attribute likelihood : ProbabilityValue[0..1];
|
|
50
50
|
|
|
51
|
-
// The workflow this scenario belongs to is the one it is nested in
|
|
52
|
-
// (a `HasScenario` relation was removed for that reason); a
|
|
51
|
+
// The workflow this scenario belongs to is the one it is nested in; a
|
|
53
52
|
// nominal/alternate pair are scenarios of the same workflow,
|
|
54
|
-
// distinguished by scenarioKind — no baseScenario back-ref.
|
|
55
|
-
//
|
|
53
|
+
// distinguished by scenarioKind — no baseScenario back-ref. Actors are
|
|
54
|
+
// derived from `perform` on the nested steps, not listed.
|
|
56
55
|
ref useContext : UseContext[0..1];
|
|
57
56
|
// threat scenario
|
|
58
57
|
attribute actorDescription : String;
|
|
@@ -69,6 +68,6 @@ package memo_architecture_operational_scenarios {
|
|
|
69
68
|
}
|
|
70
69
|
|
|
71
70
|
// A workflow is composed of one or more scenarios (nominal + alternate
|
|
72
|
-
// paths).
|
|
73
|
-
//
|
|
71
|
+
// paths). An actual execution is a native SysML *usage* of the scenario,
|
|
72
|
+
// not a separate def + relation.
|
|
74
73
|
}
|
|
@@ -10,11 +10,9 @@ package memo_architecture_operational_structure {
|
|
|
10
10
|
// IEC 62366-1 / ISO 14971 intended use: the medical device's declared
|
|
11
11
|
// purpose and the root of the operational spine. A MemoMission, because
|
|
12
12
|
// "mission" has no medical-device meaning — intended use is what a device
|
|
13
|
-
// exists to do.
|
|
14
|
-
//
|
|
15
|
-
//
|
|
16
|
-
// 5.2 asks for it to be documented as the starting point of risk analysis.
|
|
17
|
-
// It was a `part def`, which made it a structural thing.
|
|
13
|
+
// exists to do. It is a `requirement def`: the intended use is the top
|
|
14
|
+
// obligation the device's design inputs derive from, and ISO 14971 5.2 asks
|
|
15
|
+
// for it to be documented as the starting point of risk analysis.
|
|
18
16
|
requirement def IntendedUse :> MemoMission {
|
|
19
17
|
attribute indication : String;
|
|
20
18
|
attribute contraindication : String;
|
|
@@ -1,8 +1,9 @@
|
|
|
1
|
-
// Use cases
|
|
2
|
-
//
|
|
3
|
-
//
|
|
1
|
+
// Use cases. A UseCase is a goal a person or organization wants to achieve with
|
|
2
|
+
// system support — there is no separate Goal class. Clinical, service,
|
|
3
|
+
// manufacturing, and development use cases specialize the same base.
|
|
4
4
|
//
|
|
5
|
-
// A use case is at one of two levels, and the level is its
|
|
5
|
+
// A use case is at one of two levels, and the level is its own type (`ClinicalUseCase` or
|
|
6
|
+
// `SystemUseCase`), kept in agreement with its subject by CR-ONT-093.
|
|
6
7
|
// Level 1 is clinical: the subject is an `OperationalEntity` (the care team, the setting), the
|
|
7
8
|
// use case names no product, and nothing on its workflow, scenarios or steps carries a number.
|
|
8
9
|
// Level 2 is a black box: the subject is a `System` or `SystemOfSystems`, one variant of a
|
|
@@ -24,7 +25,7 @@ package memo_architecture_operational_use_cases {
|
|
|
24
25
|
private import memo_assurance_requirements_needs::*;
|
|
25
26
|
|
|
26
27
|
enum def UseCaseKind {
|
|
27
|
-
enum
|
|
28
|
+
enum care;
|
|
28
29
|
enum service;
|
|
29
30
|
enum manufacturing;
|
|
30
31
|
enum development;
|
|
@@ -36,7 +37,7 @@ package memo_architecture_operational_use_cases {
|
|
|
36
37
|
// subject/actor features below had to be re-declared by hand instead of
|
|
37
38
|
// being inherited. The wrapper survives only to carry the display label and
|
|
38
39
|
// lifecycle status; identity comes from `@MemoIdentity`.
|
|
39
|
-
use case def UseCase :> MemoUseCase, UseCases::UseCase {
|
|
40
|
+
abstract use case def UseCase :> MemoUseCase, UseCases::UseCase {
|
|
40
41
|
// Text of this use case's goal; this is not a separate Goal element.
|
|
41
42
|
attribute goalStatement : String;
|
|
42
43
|
attribute trigger : String;
|
|
@@ -48,21 +49,29 @@ package memo_architecture_operational_use_cases {
|
|
|
48
49
|
attribute useCaseKind : UseCaseKind;
|
|
49
50
|
|
|
50
51
|
// The device or system under consideration supports the goal. Native
|
|
51
|
-
// `subject`, not `ref
|
|
52
|
-
//
|
|
53
|
-
//
|
|
54
|
-
//
|
|
55
|
-
// waiting to surface once `actor` needed a subject to attach to.
|
|
52
|
+
// `subject`, not `ref`: a use case needs an explicit subject before it
|
|
53
|
+
// can declare `actor` (the subject parameter comes first), and "the
|
|
54
|
+
// device/system under consideration" is exactly what a case's subject
|
|
55
|
+
// means.
|
|
56
56
|
subject supportingSystem : MemoPart[0..1];
|
|
57
57
|
ref useContext : UseContext[0..1];
|
|
58
58
|
// Who takes part is native `actor` (`actor <role> = <participant>;`),
|
|
59
|
-
// inherited from `UseCases::UseCase`.
|
|
60
|
-
//
|
|
61
|
-
|
|
62
|
-
|
|
59
|
+
// inherited from `UseCases::UseCase`. Which actor initiates is carried
|
|
60
|
+
// by the actor's name, as the note below says.
|
|
61
|
+
}
|
|
62
|
+
|
|
63
|
+
// The two levels are types, declared and not derived. A clinical use case has an
|
|
64
|
+
// `OperationalEntity` (the care team, the setting) as its subject, names no product and carries
|
|
65
|
+
// no number; a system use case has a `System` or `SystemOfSystems`, one variant of a platform.
|
|
66
|
+
// CR-ONT-093 keeps the declared type and the subject in agreement. `UseCase` is abstract: a
|
|
67
|
+
// project states which level each use case is at.
|
|
68
|
+
use case def ClinicalUseCase :> UseCase {
|
|
69
|
+
}
|
|
70
|
+
use case def SystemUseCase :> UseCase {
|
|
63
71
|
}
|
|
64
72
|
|
|
65
73
|
connection def Motivates :> MemoRelationship {
|
|
74
|
+
attribute :>> isTrace = true;
|
|
66
75
|
end motivatingNeed : Need :>> source;
|
|
67
76
|
end motivatedUseCase : UseCase :>> target;
|
|
68
77
|
}
|
|
@@ -72,15 +81,12 @@ package memo_architecture_operational_use_cases {
|
|
|
72
81
|
:> annotatedElement : SysML::ConnectionUsage;
|
|
73
82
|
:>> baseType = motivatesLinks meta SysML::Usage;
|
|
74
83
|
}
|
|
75
|
-
//
|
|
76
|
-
//
|
|
77
|
-
//
|
|
78
|
-
//
|
|
79
|
-
//
|
|
80
|
-
//
|
|
81
|
-
//
|
|
82
|
-
//
|
|
83
|
-
// has no use-case `extend` (the textual BNF defines IncludeUseCaseUsage
|
|
84
|
-
// and nothing for extend), and MEMO does not add one: an optional path
|
|
85
|
-
// through a use case is an alternate scenario, not a second use case.
|
|
84
|
+
// Who initiates or takes part in a use case is native `actor`: write `actor
|
|
85
|
+
// <role> = <existingElement>;` inside the use case. Native `actor` does not
|
|
86
|
+
// distinguish an initiating actor from a participating one; that is in how
|
|
87
|
+
// the actor is named on the use case. UML use-case decomposition is native
|
|
88
|
+
// `include use case` / `include`. SysML v2 has no use-case `extend` (the
|
|
89
|
+
// textual BNF defines IncludeUseCaseUsage and nothing for extend), and MEMO
|
|
90
|
+
// does not add one: an optional path through a use case is an alternate
|
|
91
|
+
// scenario, not a second use case.
|
|
86
92
|
}
|
|
@@ -35,20 +35,11 @@ package memo_architecture_operational_workflows {
|
|
|
35
35
|
private import memo_architecture_operational_activities::*;
|
|
36
36
|
private import memo_architecture_operational_use_cases::*;
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
enum preserves;
|
|
40
|
-
enum automates;
|
|
41
|
-
enum augments;
|
|
42
|
-
enum eliminates;
|
|
43
|
-
}
|
|
44
|
-
|
|
45
|
-
part def OperationalWorkflow specializes MemoPart {
|
|
38
|
+
abstract part def OperationalWorkflow specializes MemoPart {
|
|
46
39
|
// Where the body of work starts and ends. A scenario's pre- and
|
|
47
40
|
// post-conditions are its own path's, inside these.
|
|
48
41
|
attribute entryCondition : String;
|
|
49
42
|
attribute completionCondition : String;
|
|
50
|
-
attribute recoveryPathSummary : String;
|
|
51
|
-
attribute timingConstraints : String;
|
|
52
43
|
// What one procedure costs apart from its activities (set-up, capital per case); a number,
|
|
53
44
|
// so it is set on a level-2 variant's workflow, never on level 1.
|
|
54
45
|
attribute perProcedureCost : MoneyValue[0..1];
|
|
@@ -64,6 +55,14 @@ package memo_architecture_operational_workflows {
|
|
|
64
55
|
// architecture and not the reverse.
|
|
65
56
|
}
|
|
66
57
|
|
|
58
|
+
// A workflow is at the level of the use case it realizes, and says so by its type: a
|
|
59
|
+
// `ClinicalWorkflow` realizes a `ClinicalUseCase` (no product, no number); a `SystemWorkflow`
|
|
60
|
+
// realizes a `SystemUseCase` (one variant, every number). CR-ONT-103 keeps the two in step.
|
|
61
|
+
part def ClinicalWorkflow specializes OperationalWorkflow {
|
|
62
|
+
}
|
|
63
|
+
part def SystemWorkflow specializes OperationalWorkflow {
|
|
64
|
+
}
|
|
65
|
+
|
|
67
66
|
// The use case a workflow realizes. Many workflows may trace to one use
|
|
68
67
|
// case; the use case does not own its workflows (the trace points upward,
|
|
69
68
|
// workflow → use case).
|
|
@@ -79,26 +78,6 @@ package memo_architecture_operational_workflows {
|
|
|
79
78
|
}
|
|
80
79
|
|
|
81
80
|
|
|
82
|
-
// decision / fork / join / handoff.
|
|
83
|
-
enum def ControlNodeKind {
|
|
84
|
-
enum decision;
|
|
85
|
-
enum 'fork';
|
|
86
|
-
enum 'join';
|
|
87
|
-
enum handoff;
|
|
88
|
-
}
|
|
89
|
-
|
|
90
|
-
// A workflow control node. The role is given by controlKind; the
|
|
91
|
-
// kind-specific fields below are set only for the relevant controlKind.
|
|
92
|
-
// handoff = transfer of responsibility between roles (shift change, room-to-lab).
|
|
93
|
-
action def WorkflowControlNode specializes MemoAction {
|
|
94
|
-
attribute controlKind : ControlNodeKind;
|
|
95
|
-
attribute decisionQuestion : String[0..1];
|
|
96
|
-
attribute decisionCriteria : String[0..1];
|
|
97
|
-
attribute parallelismRationale : String[0..1];
|
|
98
|
-
attribute joinCondition : String[0..1];
|
|
99
|
-
attribute informationTransferred : String[0..1];
|
|
100
|
-
}
|
|
101
|
-
|
|
102
81
|
enum def ResourceKind {
|
|
103
82
|
enum instrument;
|
|
104
83
|
enum equipment;
|
|
@@ -118,35 +97,9 @@ package memo_architecture_operational_workflows {
|
|
|
118
97
|
}
|
|
119
98
|
|
|
120
99
|
// ── Workflow-level relationships ─────────────────────────────
|
|
121
|
-
// An element supports (affords, enables) an action — e.g. a UI element
|
|
122
|
-
//
|
|
123
|
-
//
|
|
124
|
-
//
|
|
125
|
-
// SupportKind discriminator is gone: what used to be three enum values
|
|
126
|
-
// that each implied a different target type are now two typed refs plus
|
|
127
|
-
// this one plain relation.
|
|
100
|
+
// An element supports (affords, enables) an action — e.g. a UI element that
|
|
101
|
+
// affords a user task. Use-case and capability tracing are direct refs
|
|
102
|
+
// (OperationalWorkflow.useCase, OperativeAction.contributesToCapabilities),
|
|
103
|
+
// so this is one plain relation.
|
|
128
104
|
|
|
129
|
-
// ── Technique change ─────────────────────────────────────────
|
|
130
|
-
// Transforms relates a step of one level-1 technique variant of a workflow to the step of
|
|
131
|
-
// the other that preserves, automates, augments or eliminates it. Two platforms' activities
|
|
132
|
-
// correspond through the level-1 step both refine, not through this.
|
|
133
|
-
enum def TransformKind {
|
|
134
|
-
enum step;
|
|
135
|
-
enum workflow;
|
|
136
|
-
enum replacesWorkflow;
|
|
137
|
-
}
|
|
138
|
-
connection def Transforms :> MemoRelationship {
|
|
139
|
-
attribute transformKind : TransformKind;
|
|
140
|
-
attribute transformation : StepTransformationKind[0..1];
|
|
141
|
-
attribute transformationRationale : String[0..1];
|
|
142
|
-
end source : MemoAction;
|
|
143
|
-
end target : MemoAction;
|
|
144
|
-
}
|
|
145
|
-
abstract connection transformsLinks : Transforms[*];
|
|
146
|
-
metadata def <transforms> TransformsMetadata :> SemanticMetadata {
|
|
147
|
-
:> annotatedElement : SysML::ConnectionDefinition;
|
|
148
|
-
:> annotatedElement : SysML::ConnectionUsage;
|
|
149
|
-
:>> baseType = transformsLinks meta SysML::Usage;
|
|
150
|
-
}
|
|
151
|
-
// The device or system whose introduction enables a workflow.
|
|
152
105
|
}
|
|
@@ -2,12 +2,10 @@
|
|
|
2
2
|
// SoftwareDeploymentUnit deploysTo ProcessingNode. Software deploys only to capable
|
|
3
3
|
// execution nodes (rules/crosslayer).
|
|
4
4
|
//
|
|
5
|
-
// `HostedBy` is NOT part of that chain
|
|
6
|
-
//
|
|
7
|
-
//
|
|
8
|
-
//
|
|
9
|
-
// other way and between different things. Software reaches a node through
|
|
10
|
-
// DeploysTo.
|
|
5
|
+
// `HostedBy` is NOT part of that chain. It is `processingNode : ProcessingNode
|
|
6
|
+
// -> hostAssembly : PhysicalAssembly`: physical hosting of a node by the
|
|
7
|
+
// assembly it is mounted in, running the other way and between different
|
|
8
|
+
// things. Software reaches a node through DeploysTo.
|
|
11
9
|
package memo_architecture_realization_deployment {
|
|
12
10
|
private import memo_core_stdlib_quantities::*;
|
|
13
11
|
private import Metaobjects::SemanticMetadata;
|
|
@@ -41,7 +39,7 @@ package memo_architecture_realization_deployment {
|
|
|
41
39
|
attribute certificationEvidence : String;
|
|
42
40
|
}
|
|
43
41
|
|
|
44
|
-
|
|
42
|
+
// A module BUILDS INTO a deployment unit: that is an allocation, and the
|
|
45
43
|
// language has one. Rooted like MemoryBinding / ConnectionBinding below,
|
|
46
44
|
// so the whole deployment family spells allocation the same way.
|
|
47
45
|
allocation def BuildsInto :> MemoRelationship, Allocations::Allocation {
|
|
@@ -72,8 +70,7 @@ package memo_architecture_realization_deployment {
|
|
|
72
70
|
:> annotatedElement : SysML::AllocationUsage;
|
|
73
71
|
:>> baseType = realizedByLinks meta SysML::Usage;
|
|
74
72
|
}
|
|
75
|
-
|
|
76
|
-
// to b;` -- the declaration was the only part still saying `connection`.
|
|
73
|
+
// Written `allocation x : DeploysTo allocate a to b;`.
|
|
77
74
|
allocation def DeploysTo :> MemoRelationship, Allocations::Allocation {
|
|
78
75
|
attribute deploymentKind : DeploymentKind;
|
|
79
76
|
end deploymentUnit : SoftwareDeploymentUnit :>> source;
|
|
@@ -96,24 +93,21 @@ package memo_architecture_realization_deployment {
|
|
|
96
93
|
:>> baseType = providesEnvironmentLinks meta SysML::Usage;
|
|
97
94
|
}
|
|
98
95
|
|
|
99
|
-
// ─── AADL bindings (SAE AS5506)
|
|
96
|
+
// ─── AADL bindings (SAE AS5506) ────────────────────────────
|
|
100
97
|
//
|
|
101
98
|
// AADL's analytic power is that EVERYTHING is bound to something, and the
|
|
102
|
-
// binding is where latency, bandwidth and fault propagation accrue.
|
|
103
|
-
//
|
|
104
|
-
//
|
|
105
|
-
//
|
|
106
|
-
//
|
|
107
|
-
// the model could not perform.
|
|
99
|
+
// binding is where latency, bandwidth and fault propagation accrue.
|
|
100
|
+
// `DeploysTo` is `actual_processor_binding`. Without the other two,
|
|
101
|
+
// `SoftwareComponent.memoryBudget` is unanalysable and
|
|
102
|
+
// `EndToEndFlow.latencyBudgetMs` cannot be checked against the media the
|
|
103
|
+
// flow traverses.
|
|
108
104
|
//
|
|
109
105
|
// Both are `allocation def`s rooted on the standard's
|
|
110
106
|
// `Allocations::Allocation`, because a binding IS an allocation and the
|
|
111
107
|
// language says so. The double specialization keeps MEMO's identification
|
|
112
108
|
// core from `MemoRelationship` while adding the standard's allocation
|
|
113
109
|
// semantics; both root on `Connections::BinaryConnection`, so this is a
|
|
114
|
-
// diamond and not a conflict.
|
|
115
|
-
// negative control (a non-existent supertype is reported), so the clean
|
|
116
|
-
// result is the checker agreeing rather than the checker skipping.
|
|
110
|
+
// diamond and not a conflict.
|
|
117
111
|
|
|
118
112
|
// AADL `actual_memory_binding`. Which memory a software component's code
|
|
119
113
|
// and data occupy — what makes a memory budget a claim about a device
|
|
@@ -134,10 +128,10 @@ package memo_architecture_realization_deployment {
|
|
|
134
128
|
// interface: a network medium under a component exchange, a cable or
|
|
135
129
|
// harness under a hardware `Interface`, a connector, a tube. The source is
|
|
136
130
|
// the interface usage rather than a link, because the interface is the
|
|
137
|
-
// ELEMENT that owns the budget
|
|
138
|
-
//
|
|
139
|
-
//
|
|
140
|
-
//
|
|
131
|
+
// ELEMENT that owns the budget and a link instance is not something the
|
|
132
|
+
// graph can bind to; it is also exactly where the latency the medium
|
|
133
|
+
// contributes has to be accounted. Ends are the two bases (MemoInterface,
|
|
134
|
+
// PhysicalComponent) so one binding serves every layer.
|
|
141
135
|
allocation def ConnectionBinding :> MemoRelationship, Allocations::Allocation {
|
|
142
136
|
attribute allocatedBandwidth : String;
|
|
143
137
|
attribute mediumLatencyMs : DurationValue;
|
|
@@ -198,7 +192,7 @@ package memo_architecture_realization_deployment {
|
|
|
198
192
|
:>> baseType = flowComprisesSpecLinks meta SysML::Usage;
|
|
199
193
|
}
|
|
200
194
|
// The flow traverses a software→hardware binding; latency accrues here.
|
|
201
|
-
|
|
195
|
+
// A binding IS an allocation, exactly as MemoryBinding and
|
|
202
196
|
// ConnectionBinding already declare.
|
|
203
197
|
allocation def FlowTraversesBinding :> MemoRelationship, Allocations::Allocation {
|
|
204
198
|
end endToEndFlow : EndToEndFlow :>> source;
|