@memoarchitect/ontology 0.16.2 → 0.16.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/examples/functional-logical-physical/model/catalog/functional_logical_physical.sysml +1 -1
- package/examples/gastric-bypass-variants/README.md +20 -0
- package/examples/gastric-bypass-variants/memo.identity.yaml +337 -0
- package/examples/gastric-bypass-variants/memo.package.yaml +5 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/NOTICE.md +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma.sysml +56 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_alimentary.sysml +1376 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_body_proper.sysml +45 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_material_anatomical_entity.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_segment_of_blood_vessel_tree_organ.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_cardiovascular_segment_of_hollow_tree_organ.sysml +21 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_boundary_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_cluster.sysml +45 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_set.sysml +30 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_space.sysml +60 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_structure.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_anatomical_surface.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_arborial_segment_of_arterial_tree_organ.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_arborial_segment_of_venous_tree_organ.sysml +23 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_blood_vessel.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_bona_fide_anatomical_surface.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cardinal_organ_part.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cardinal_tissue_part.sysml +16 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_cell_part_cluster.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_developmental_structure.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_immaterial_anatomical_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_material_anatomical_entity.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_nerve.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ.sysml +65 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component_layer.sysml +54 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_component_of_lymphatic_tree_organ.sysml +15 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_region.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_segment.sysml +46 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_organ_zone.sysml +34 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_physical_anatomical_entity.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_portion_of_tissue.sysml +106 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_postnatal_anatomical_structure.sysml +27 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_region_of_organ_component.sysml +55 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_region_of_surface_of_organ.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_blood_vessel_tree_organ.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_hollow_tree_organ.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_neural_tree_organ.sysml +10 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_segment_of_vascular_tree_organ.sysml +39 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_core_surface_of_organ_region.sysml +19 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_fascial.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_anatomical_structure.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_cardinal_organ_part.sysml +11 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_musculoskeletal_organ.sysml +7 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_anatomical_cluster.sysml +9 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_nerve.sysml +13 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_nervous_postnatal_anatomical_structure.sysml +8 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/gastric_bypass_variants_anatomy_fma_respiratory.sysml +14 -0
- package/examples/gastric-bypass-variants/memo_packages/gastric-bypass-variants-anatomy-fma/memo.package.yaml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +416 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/viewpoint.sysml +8 -0
- package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +53 -0
- package/examples/gastric-bypass-variants/model/methodology/project.sysml +26 -0
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +13 -20
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +1 -2
- package/examples/robot-cell-family/model/catalog/sos/chains.sysml +1 -2
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +1 -2
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/anatomy/LICENSES/CC-BY-4.0.txt +395 -0
- package/extensions/anatomy/NOTICE.md +20 -0
- package/extensions/anatomy/data/fma-index.json.gz +0 -0
- package/extensions/anatomy/memo.package.yaml +18 -0
- package/extensions/anatomy/src/anatomy_extension.sysml +9 -0
- package/extensions/anatomy/src/presets/memo_extension_anatomy_presets.sysml +12 -0
- package/extensions/anatomy/src/selector/memo_extension_anatomy_selector.sysml +17 -0
- package/extensions/anatomy/src/vocabulary/memo_extension_anatomy_vocabulary.sysml +115 -0
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/clinical/src/clinical_extension.sysml +3 -1
- package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +11 -5
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/ros/memo.package.yaml +1 -1
- package/memo.manifest.yaml +1 -0
- package/methodologies/default/memo.package.yaml +1 -1
- package/methodologies/gpca/memo.package.yaml +1 -1
- package/ontology/memo.package.yaml +1 -1
- package/package.json +1 -1
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/functions/memo_functions.sysml +10 -5
- package/src/architecture/operational/activities/memo_activities.sysml +20 -1
- package/src/architecture/operational/context/actors/memo_actors.sysml +3 -1
- package/src/architecture/operational/memo_architecture_operational.sysml +1 -0
- package/src/architecture/operational/rollups/memo_rollups.sysml +109 -0
- package/src/architecture/operational/scenarios/memo_scenarios.sysml +16 -5
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +11 -0
- package/src/architecture/operational/workflows/memo_workflows.sysml +62 -27
- package/src/assurance/requirements/needs/memo_needs.sysml +8 -0
- package/src/core/common/memo_common.sysml +19 -0
- package/src/core/relationships/memo_workspace_membership.sysml +1 -0
- package/src/core/stdlib/analysis/analysis.sysml +11 -0
- package/src/core/stdlib/functions/functions.sysml +2 -0
- package/src/core/stdlib/money/money.sysml +53 -0
- package/src/core/stdlib/quantities/quantities.sysml +2 -0
- package/src/memo_namespaces.sysml +16 -0
- package/src/methodology/profiles/memo_profiles.sysml +10 -9
- package/src/methodology/workflow/memo_workflow.sysml +16 -6
- package/src/rules/ontology/ontology_invariants.sysml +116 -0
- package/src/viewpoints/definitions/memo_view_layout.sysml +9 -0
- package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
- package/stage1/syside-f7095495f0f20200e0c34176.ids.gz +0 -0
- package/stage1/syside-f7095495f0f20200e0c34176.json.gz +0 -0
- package/stage1/opensysml-23e5a5f26f7b25370edc4f26.json.gz +0 -0
- package/stage1/syside-27179e19589cf7a97f4dd15a.ids.gz +0 -0
- package/stage1/syside-27179e19589cf7a97f4dd15a.json.gz +0 -0
- package/stage1/syside-67f92dc96ba75cd05b5c8d13.ids.gz +0 -0
- package/stage1/syside-67f92dc96ba75cd05b5c8d13.json.gz +0 -0
- package/stage1/syside-eb527547500a60b508b4578c.ids.gz +0 -0
- package/stage1/syside-eb527547500a60b508b4578c.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-container'
|
|
10
|
-
version: 0.16.
|
|
10
|
+
version: 0.16.4
|
|
11
11
|
description: OCI container images and container runtimes as deployment content
|
|
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/extension-messaging'
|
|
10
|
-
version: 0.16.
|
|
10
|
+
version: 0.16.4
|
|
11
11
|
description: Publish/subscribe messaging — topics, brokers, and delivery semantics
|
|
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/extension-ros'
|
|
10
|
-
version: 0.16.
|
|
10
|
+
version: 0.16.4
|
|
11
11
|
description: ROS 2 nodes, messages, topic/service/action interfaces, QoS, and containerized deployment
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
package/memo.manifest.yaml
CHANGED
|
@@ -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.16.
|
|
10
|
+
version: 0.16.4
|
|
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.16.
|
|
10
|
+
version: 0.16.4
|
|
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.16.
|
|
10
|
+
version: 0.16.4
|
|
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.16.
|
|
3
|
+
"version": "0.16.4",
|
|
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.16.
|
|
10
|
+
version: 0.16.4
|
|
11
11
|
description: Closure rules and viewpoints for medical device modeling
|
|
12
12
|
license: MIT
|
|
13
13
|
tags:
|
|
@@ -15,11 +15,16 @@
|
|
|
15
15
|
// a part, and a separate `action def OperativeAction` carried the behaviour with a
|
|
16
16
|
// `ref performedFunction` stapling the two back together — a reference used in
|
|
17
17
|
// ZERO example files. The ends are metaclass-neutral now (CR-ONT-060..073), so
|
|
18
|
-
// the split has no cause and is gone:
|
|
19
|
-
//
|
|
20
|
-
//
|
|
21
|
-
//
|
|
22
|
-
//
|
|
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.
|
|
22
|
+
//
|
|
23
|
+
// `OperativeAction` was NOT merged into the function family. It is a separate `action def` in
|
|
24
|
+
// the operational layer (memo_architecture_operational_activities): a step of the work, which a
|
|
25
|
+
// person or the system performs. The two are joined by native `perform`, not by a type: a
|
|
26
|
+
// system-performed level-2 activity `perform`s the `SystemFunction` that carries it out, and
|
|
27
|
+
// a function is performed only from such an activity or from a `FunctionalFlow` step.
|
|
23
28
|
//
|
|
24
29
|
// `functionCategory` and `actionKind` are NOT two spellings of one axis, and
|
|
25
30
|
// merging them would lose information. `actionKind` is the verb — sense,
|
|
@@ -6,6 +6,15 @@
|
|
|
6
6
|
// guidance) and it must trace to usability validation. Task difficulty belongs
|
|
7
7
|
// to an action performed in a context (TaskDifficultyAssessment), never to an
|
|
8
8
|
// instrument.
|
|
9
|
+
//
|
|
10
|
+
// An `OperativeAction` is a step at level 1 or an activity at level 2, by the use case whose
|
|
11
|
+
// scenario it is in (memo_architecture_operational_use_cases). A level-1 step is structure: what
|
|
12
|
+
// must happen to the patient, with `targets` at most, and no number. A level-2 activity is the
|
|
13
|
+
// tuple surgical process modelling attaches to an activity: who (native `perform` from a role or
|
|
14
|
+
// system part), what (the action), with what (`instruments`), on what (`targets`), and when
|
|
15
|
+
// (`expectedDuration`, `plannedSuccessProbability`). What the system does to carry out an
|
|
16
|
+
// activity is the `SystemFunction` it `perform`s. Measured values are evidence, not attributes
|
|
17
|
+
// here. The roll-ups of these numbers are in memo_architecture_operational_rollups.
|
|
9
18
|
package memo_architecture_operational_activities {
|
|
10
19
|
private import memo_core_stdlib_quantities::*;
|
|
11
20
|
private import Metaobjects::SemanticMetadata;
|
|
@@ -25,6 +34,11 @@ package memo_architecture_operational_activities {
|
|
|
25
34
|
enum extreme;
|
|
26
35
|
}
|
|
27
36
|
|
|
37
|
+
// A probability: a dimensionless quantity between 0 and 1.
|
|
38
|
+
attribute def ProbabilityValue :> DimensionOneValue {
|
|
39
|
+
assert constraint { self >= 0 [one] and self <= 1 [one] }
|
|
40
|
+
}
|
|
41
|
+
|
|
28
42
|
// One operational action / step. Who performs it — a human actor or the
|
|
29
43
|
// system — is a relationship (native `perform`), not a subtype, so an
|
|
30
44
|
// action can migrate from user- to system-performed (automation, as-is →
|
|
@@ -40,6 +54,12 @@ package memo_architecture_operational_activities {
|
|
|
40
54
|
attribute criticality : CriticalityKind;
|
|
41
55
|
attribute taskGoal : String;
|
|
42
56
|
attribute expectedDuration : DurationValue;
|
|
57
|
+
// The planned chance the step succeeds; a number, so level 2 only.
|
|
58
|
+
attribute plannedSuccessProbability : ProbabilityValue[0..1];
|
|
59
|
+
// With what, and on what: the resources the step uses and the parts it acts on, whatever
|
|
60
|
+
// they are (anatomy, a needle, a specimen, the instrument itself).
|
|
61
|
+
ref instruments : MemoResource[0..*];
|
|
62
|
+
ref targets : MemoPart[0..*];
|
|
43
63
|
attribute frequencyOfUse : String;
|
|
44
64
|
attribute potentialHarm : String[0..1];
|
|
45
65
|
attribute severityIfFailed : SeverityKind[0..1];
|
|
@@ -61,7 +81,6 @@ package memo_architecture_operational_activities {
|
|
|
61
81
|
attribute trainingDemand : DemandLevelKind;
|
|
62
82
|
attribute ergonomicDemand : DemandLevelKind;
|
|
63
83
|
attribute environmentalDemand : DemandLevelKind;
|
|
64
|
-
attribute expectedDuration : DurationValue;
|
|
65
84
|
attribute assessor : String;
|
|
66
85
|
attribute assessmentMethod : String;
|
|
67
86
|
|
|
@@ -3,6 +3,8 @@
|
|
|
3
3
|
// a native SysML notion (a Part in a stakeholder membership on a concern or
|
|
4
4
|
// viewpoint), not a separate MEMO type; the same Part may fill both roles.
|
|
5
5
|
// "User" is reserved for a human who interacts with the medical device.
|
|
6
|
+
// A User is also a `MemoResource`: staff are a resource with a capacity cost rate, and are already the
|
|
7
|
+
// performers, so there is no "personnel" resource kind, which would be a second spelling of User.
|
|
6
8
|
package memo_architecture_operational_context_actors {
|
|
7
9
|
private import ScalarValues::*;
|
|
8
10
|
|
|
@@ -19,7 +21,7 @@ package memo_architecture_operational_context_actors {
|
|
|
19
21
|
// The human actor. The specific role is given by actorKind
|
|
20
22
|
// (patient / clinician / caregiver / technician / administrator); the
|
|
21
23
|
// role-specific fields below are set only for the relevant actorKind.
|
|
22
|
-
part def User specializes OperationalParticipant {
|
|
24
|
+
part def User specializes OperationalParticipant, MemoResource {
|
|
23
25
|
attribute userPopulation : String;
|
|
24
26
|
attribute impairmentConsiderations : String;
|
|
25
27
|
attribute intendedTraining : String;
|
|
@@ -12,6 +12,7 @@ package memo_architecture_operational {
|
|
|
12
12
|
public import memo_architecture_operational_context_actors::*;
|
|
13
13
|
public import memo_architecture_operational_context_stakeholders::*;
|
|
14
14
|
public import memo_architecture_operational_context_use_context::*;
|
|
15
|
+
public import memo_architecture_operational_rollups::*;
|
|
15
16
|
public import memo_architecture_operational_scenarios::*;
|
|
16
17
|
public import memo_architecture_operational_structure::*;
|
|
17
18
|
public import memo_architecture_operational_use_cases::*;
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
// Roll-ups of a level-2 procedure flow (plan decision 9). A number is entered once, on an
|
|
2
|
+
// activity (`expectedDuration`, `plannedSuccessProbability`, the cost rates of its `instruments`),
|
|
3
|
+
// and every figure above it is derived here: a scenario, a procedure, a variant. A `TradeStudy`
|
|
4
|
+
// compares variants by these, so nothing a study reads is typed in twice.
|
|
5
|
+
//
|
|
6
|
+
// ─── Traversal ──────────────────────────────────────────────────────────
|
|
7
|
+
// `ActivitiesOf` is the one place that decides which activities count, and every roll-up reads
|
|
8
|
+
// it. It reads `enclosedPerformances`, which holds a step's composite `subactions`, the activities
|
|
9
|
+
// it `perform`s by reference (a scenario that performs activities declared once and used in
|
|
10
|
+
// several), and the `includedUseCases` of a use case, which are `enclosedPerformances` and not
|
|
11
|
+
// `subactions`, so a walk over `subactions` alone would miss every reusable system use case. It
|
|
12
|
+
// descends only into what can hold activities: an activity, a scenario or a use case. A
|
|
13
|
+
// `perform` of a `SystemFunction` is therefore never entered, which is the point of the stop:
|
|
14
|
+
// level 3 is how the system does its share, not more time, and following it would count the
|
|
15
|
+
// same work twice.
|
|
16
|
+
//
|
|
17
|
+
// ─── Sums ───────────────────────────────────────────────────────────────
|
|
18
|
+
// Sums and products use `QuantityCalculations`, so a cost, a duration and a probability stay
|
|
19
|
+
// quantities with units; money is `memo_core_stdlib_money`, in the project's one currency.
|
|
20
|
+
// A cost is the activity's duration times each instrument's capacity cost rate, plus each
|
|
21
|
+
// instrument's unit cost. Parallel branches are each paid for, because each resource used is
|
|
22
|
+
// paid for. Time is the sum along the path; a fork whose branches overlap in time is not yet
|
|
23
|
+
// reduced to its longest branch here.
|
|
24
|
+
//
|
|
25
|
+
// `memo evaluate` runs them from these bodies over the built model (memo-tools, analysis/calc), and a
|
|
26
|
+
// `TradeStudy` reads the results, so no figure is written twice. Units follow the SysML library's own
|
|
27
|
+
// conversions, so minutes and hours add and a rate times a duration is an amount.
|
|
28
|
+
package memo_architecture_operational_rollups {
|
|
29
|
+
private import ScalarValues::*;
|
|
30
|
+
private import memo_core_stdlib_functions::*;
|
|
31
|
+
private import memo_core_stdlib_quantities::*;
|
|
32
|
+
private import memo_core_stdlib_money::*;
|
|
33
|
+
private import memo_core_common::*;
|
|
34
|
+
private import memo_architecture_operational_activities::*;
|
|
35
|
+
private import memo_architecture_operational_scenarios::*;
|
|
36
|
+
private import memo_architecture_operational_workflows::*;
|
|
37
|
+
private import memo_architecture_operational_use_cases::*;
|
|
38
|
+
|
|
39
|
+
calc def ActivitiesOf {
|
|
40
|
+
in owner : MemoAction[1];
|
|
41
|
+
return activities : OperativeAction[0..*] = (
|
|
42
|
+
owner.enclosedPerformances->select { in inner : MemoAction[1]; inner istype OperativeAction },
|
|
43
|
+
owner.enclosedPerformances
|
|
44
|
+
->select { in inner : MemoAction[1];
|
|
45
|
+
inner istype OperativeAction or inner istype OperativeScenario or inner istype UseCase }
|
|
46
|
+
->collect { in inner : MemoAction[1]; ActivitiesOf(inner) });
|
|
47
|
+
}
|
|
48
|
+
|
|
49
|
+
calc def ActivityCost {
|
|
50
|
+
in activity : OperativeAction[1];
|
|
51
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum((
|
|
52
|
+
activity.instruments.capacityCostRate->collect { in rate : CostRateValue[1]; (rate * activity.expectedDuration) as MoneyValue },
|
|
53
|
+
activity.instruments.unitCost));
|
|
54
|
+
}
|
|
55
|
+
|
|
56
|
+
calc def ScenarioCost {
|
|
57
|
+
in scenario : MemoAction[1];
|
|
58
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum(
|
|
59
|
+
ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; ActivityCost(activity) });
|
|
60
|
+
}
|
|
61
|
+
|
|
62
|
+
calc def ScenarioDuration {
|
|
63
|
+
in scenario : MemoAction[1];
|
|
64
|
+
return duration : DurationValue[1] = QuantityCalculations::sum(
|
|
65
|
+
ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; activity.expectedDuration });
|
|
66
|
+
}
|
|
67
|
+
|
|
68
|
+
calc def ScenarioSuccess {
|
|
69
|
+
in scenario : MemoAction[1];
|
|
70
|
+
return success : ProbabilityValue[1] = QuantityCalculations::product(
|
|
71
|
+
ActivitiesOf(scenario).plannedSuccessProbability);
|
|
72
|
+
}
|
|
73
|
+
|
|
74
|
+
calc def ProcedureCost {
|
|
75
|
+
in workflow : OperationalWorkflow[1];
|
|
76
|
+
return cost : MoneyValue[1] = QuantityCalculations::sum((
|
|
77
|
+
workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
|
|
78
|
+
->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioCost(s)) as MoneyValue },
|
|
79
|
+
workflow.perProcedureCost));
|
|
80
|
+
}
|
|
81
|
+
|
|
82
|
+
calc def ProcedureDuration {
|
|
83
|
+
in workflow : OperationalWorkflow[1];
|
|
84
|
+
return duration : DurationValue[1] = QuantityCalculations::sum(
|
|
85
|
+
workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
|
|
86
|
+
->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioDuration(s)) as DurationValue });
|
|
87
|
+
}
|
|
88
|
+
|
|
89
|
+
calc def ScenarioWeight {
|
|
90
|
+
in scenario : OperativeScenario[1];
|
|
91
|
+
return weight : Real[1] = if scenario.scenarioKind == ScenarioKind::nominal ? 1.0 else scenario.likelihood;
|
|
92
|
+
}
|
|
93
|
+
|
|
94
|
+
calc def HighDemandCount {
|
|
95
|
+
in assessments : TaskDifficultyAssessment[0..*];
|
|
96
|
+
return count : Natural[1] = assessments->select { in a : TaskDifficultyAssessment[1];
|
|
97
|
+
a.overallDifficulty == DemandLevelKind::high or a.overallDifficulty == DemandLevelKind::extreme }->size();
|
|
98
|
+
}
|
|
99
|
+
|
|
100
|
+
calc def HighestDemand {
|
|
101
|
+
in assessments : TaskDifficultyAssessment[0..*];
|
|
102
|
+
return demand : DemandLevelKind[1] =
|
|
103
|
+
if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::extreme } ? DemandLevelKind::extreme
|
|
104
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::high } ? DemandLevelKind::high
|
|
105
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::moderate } ? DemandLevelKind::moderate
|
|
106
|
+
else if assessments->exists { in a : TaskDifficultyAssessment[1]; a.overallDifficulty == DemandLevelKind::low } ? DemandLevelKind::low
|
|
107
|
+
else DemandLevelKind::minimal;
|
|
108
|
+
}
|
|
109
|
+
}
|
|
@@ -1,8 +1,16 @@
|
|
|
1
|
-
// Scenario foundation. A scenario is
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
// scenario
|
|
1
|
+
// Scenario foundation. A scenario is the stepwise sequence of actions that
|
|
2
|
+
// completes a workflow's body of work, with its pre- and post-conditions: IEC
|
|
3
|
+
// 62366-1's use scenario, a sequence of tasks by a user in a use environment
|
|
4
|
+
// and the device's responses. It is where the steps are; the workflow it is
|
|
5
|
+
// nested in is the analysis of that work. A scenario is nominal or alternate,
|
|
6
|
+
// so a nominal scenario and its alternates are siblings in their workflow. A
|
|
7
|
+
// step used in several scenarios is one action def used in each, never copied.
|
|
8
|
+
// An actual or hypothetical execution is a native usage of the scenario, not a
|
|
9
|
+
// separate element.
|
|
10
|
+
//
|
|
11
|
+
// A scenario of a level-1 use case lists steps; a scenario of a level-2 use case lists activities
|
|
12
|
+
// (memo_architecture_operational_activities), and `likelihood` is per variant, so a robot and a
|
|
13
|
+
// laparoscopic tower have different conversion rates for the same alternate scenario.
|
|
6
14
|
package memo_architecture_operational_scenarios {
|
|
7
15
|
private import Metaobjects::SemanticMetadata;
|
|
8
16
|
private import ScalarValues::*;
|
|
@@ -36,6 +44,9 @@ package memo_architecture_operational_scenarios {
|
|
|
36
44
|
attribute expectedResult : String;
|
|
37
45
|
attribute postCondition : String;
|
|
38
46
|
attribute pathSummary : String;
|
|
47
|
+
// How likely this path is, among the workflow's scenarios, for the variant it belongs to
|
|
48
|
+
// (a robot and a laparoscopic tower do not convert to open at the same rate); level 2 only.
|
|
49
|
+
attribute likelihood : ProbabilityValue[0..1];
|
|
39
50
|
|
|
40
51
|
// The workflow this scenario belongs to is the one it is nested in
|
|
41
52
|
// (a `HasScenario` relation was removed for that reason); a
|
|
@@ -1,6 +1,17 @@
|
|
|
1
1
|
// Use cases (§5). A UseCase is a goal a person or organization wants to
|
|
2
2
|
// achieve with system support — there is no separate Goal class. Clinical,
|
|
3
3
|
// service, manufacturing, and development use cases specialize the same base.
|
|
4
|
+
//
|
|
5
|
+
// A use case is at one of two levels, and the level is its subject's type, not a field.
|
|
6
|
+
// Level 1 is clinical: the subject is an `OperationalEntity` (the care team, the setting), the
|
|
7
|
+
// use case names no product, and nothing on its workflow, scenarios or steps carries a number.
|
|
8
|
+
// Level 2 is a black box: the subject is a `System` or `SystemOfSystems`, one variant of a
|
|
9
|
+
// platform, and its procedure flow carries every number (time, cost, success, likelihood) for
|
|
10
|
+
// that variant. A level-2 activity refines the level-1 step it carries out by upward
|
|
11
|
+
// `#refinement`, so one level-1 use case is the shared baseline of every variant. Reusable
|
|
12
|
+
// services of the system (dock, teleoperate) are level-2 use cases that a procedure flow
|
|
13
|
+
// `include`s, never copies. The level below, how the system does its share, is the Functional
|
|
14
|
+
// layer, reached by `perform`.
|
|
4
15
|
package memo_architecture_operational_use_cases {
|
|
5
16
|
private import Metaobjects::SemanticMetadata;
|
|
6
17
|
private import ScalarValues::*;
|
|
@@ -1,29 +1,40 @@
|
|
|
1
|
-
// First-class operational workflows.
|
|
2
|
-
//
|
|
3
|
-
//
|
|
4
|
-
//
|
|
5
|
-
//
|
|
6
|
-
//
|
|
1
|
+
// First-class operational workflows. A use case is the user's goal; an
|
|
2
|
+
// OperationalWorkflow is the ANALYSIS of one body of work that pursues it: who
|
|
3
|
+
// does it, where, with what equipment, between which entry and completion
|
|
4
|
+
// conditions, and (from the needs that point at it) what is needed and what
|
|
5
|
+
// is not yet met. It may exist before any device is selected. It is not a
|
|
6
|
+
// sequence of steps: the steps are its scenarios' (memo_architecture_operational_scenarios),
|
|
7
|
+
// each one stepwise path with pre- and post-conditions, and an occurrence is
|
|
8
|
+
// one execution of a scenario.
|
|
9
|
+
//
|
|
10
|
+
// IEC 62366-1 is the guide: the workflow is the use specification (5.1) scoped
|
|
11
|
+
// to one body of work, with the UI characteristics related to safety (5.2) and
|
|
12
|
+
// the known use-related hazards (5.3) its analysis draws on; a scenario is the
|
|
13
|
+
// standard's use scenario, a sequence of tasks by a user in a use environment.
|
|
14
|
+
// The standard has no "workflow"; this is MEMO's.
|
|
15
|
+
//
|
|
16
|
+
// So a workflow is a part, not an action: an action's nested actions are all
|
|
17
|
+
// performed, and a workflow's scenarios are alternatives. It owns its scenarios
|
|
18
|
+
// as nested actions, the way a part owns what it can do.
|
|
19
|
+
//
|
|
20
|
+
// A workflow's equipment is `WorkflowResource` parts, each a `MemoResource` with its cost rate.
|
|
21
|
+
// A generic resource is specialized by the product that fills it (`part def ProductXStapler :>
|
|
22
|
+
// Stapler`), which is why there is no `resolvedProduct` reference: native specialization says it.
|
|
7
23
|
package memo_architecture_operational_workflows {
|
|
8
24
|
private import Metaobjects::SemanticMetadata;
|
|
9
25
|
private import ScalarValues::*;
|
|
10
26
|
|
|
27
|
+
private import memo_core_stdlib_quantities::*;
|
|
28
|
+
private import memo_core_stdlib_money::*;
|
|
29
|
+
|
|
11
30
|
private import memo_core_common::*;
|
|
12
31
|
private import memo_core_enumerations::*;
|
|
13
32
|
private import memo_core_relationships::*;
|
|
14
33
|
private import memo_architecture_operational_context_actors::*;
|
|
34
|
+
private import memo_architecture_operational_context_use_context::*;
|
|
15
35
|
private import memo_architecture_operational_activities::*;
|
|
16
36
|
private import memo_architecture_operational_use_cases::*;
|
|
17
37
|
|
|
18
|
-
// As-is vs. to-be vs. contingency is a typed dimension of the workflow,
|
|
19
|
-
// not a name suffix.
|
|
20
|
-
enum def WorkflowStateKind {
|
|
21
|
-
enum asIs;
|
|
22
|
-
enum toBe;
|
|
23
|
-
enum contingency;
|
|
24
|
-
enum deprecated;
|
|
25
|
-
}
|
|
26
|
-
|
|
27
38
|
enum def StepTransformationKind {
|
|
28
39
|
enum preserves;
|
|
29
40
|
enum automates;
|
|
@@ -31,13 +42,26 @@ package memo_architecture_operational_workflows {
|
|
|
31
42
|
enum eliminates;
|
|
32
43
|
}
|
|
33
44
|
|
|
34
|
-
|
|
35
|
-
|
|
45
|
+
part def OperationalWorkflow specializes MemoPart {
|
|
46
|
+
// Where the body of work starts and ends. A scenario's pre- and
|
|
47
|
+
// post-conditions are its own path's, inside these.
|
|
36
48
|
attribute entryCondition : String;
|
|
37
49
|
attribute completionCondition : String;
|
|
38
50
|
attribute recoveryPathSummary : String;
|
|
39
51
|
attribute timingConstraints : String;
|
|
40
|
-
|
|
52
|
+
// What one procedure costs apart from its activities (set-up, capital per case); a number,
|
|
53
|
+
// so it is set on a level-2 variant's workflow, never on level 1.
|
|
54
|
+
attribute perProcedureCost : MoneyValue[0..1];
|
|
55
|
+
// The context and environment of use (IEC 62366-1 5.1), as modelled
|
|
56
|
+
// elements rather than a sentence: the care setting, jurisdiction and
|
|
57
|
+
// connected use are UseContext's, lighting and noise UseEnvironment's.
|
|
58
|
+
ref useContext : UseContext[0..1];
|
|
59
|
+
ref useEnvironment : UseEnvironment[0..1];
|
|
60
|
+
// The equipment and other resources the work needs are the workflow's
|
|
61
|
+
// own `WorkflowResource` parts. Users are not listed: they are who
|
|
62
|
+
// `perform`s its scenarios' steps. Needs point here (Need.workflow);
|
|
63
|
+
// the workflow does not list them, because assurance may depend on
|
|
64
|
+
// architecture and not the reverse.
|
|
41
65
|
}
|
|
42
66
|
|
|
43
67
|
// The use case a workflow realizes. Many workflows may trace to one use
|
|
@@ -75,12 +99,22 @@ package memo_architecture_operational_workflows {
|
|
|
75
99
|
attribute informationTransferred : String[0..1];
|
|
76
100
|
}
|
|
77
101
|
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
102
|
+
enum def ResourceKind {
|
|
103
|
+
enum instrument;
|
|
104
|
+
enum equipment;
|
|
105
|
+
enum consumable;
|
|
106
|
+
enum material;
|
|
107
|
+
enum information;
|
|
108
|
+
enum space;
|
|
109
|
+
}
|
|
110
|
+
|
|
111
|
+
// Resources a workflow requires: instruments, equipment, consumables, materials, information
|
|
112
|
+
// or space, by reference. Owned by the workflow as its parts. A staff member is not one: that
|
|
113
|
+
// is a `User`, which is a `MemoResource` of its own.
|
|
114
|
+
part def WorkflowResource specializes MemoResource {
|
|
115
|
+
attribute resourceKind : ResourceKind;
|
|
116
|
+
attribute quantity : Natural;
|
|
117
|
+
attribute reprocessingDuration : DurationValue[0..1];
|
|
84
118
|
}
|
|
85
119
|
|
|
86
120
|
// ── Workflow-level relationships ─────────────────────────────
|
|
@@ -92,9 +126,10 @@ package memo_architecture_operational_workflows {
|
|
|
92
126
|
// that each implied a different target type are now two typed refs plus
|
|
93
127
|
// this one plain relation.
|
|
94
128
|
|
|
95
|
-
// ──
|
|
96
|
-
// Transforms
|
|
97
|
-
//
|
|
129
|
+
// ── Technique change ─────────────────────────────────────────
|
|
130
|
+
// Transforms relates a step of one level-1 technique variant of a workflow to the step of
|
|
131
|
+
// the other that preserves, automates, augments or eliminates it. Two platforms' activities
|
|
132
|
+
// correspond through the level-1 step both refine, not through this.
|
|
98
133
|
enum def TransformKind {
|
|
99
134
|
enum step;
|
|
100
135
|
enum workflow;
|
|
@@ -15,6 +15,7 @@ package memo_assurance_requirements_needs {
|
|
|
15
15
|
// elements. Assurance may depend on architecture; the reverse may not.
|
|
16
16
|
private import memo_architecture_operational_context_actors::*;
|
|
17
17
|
private import memo_architecture_operational_context_use_context::*;
|
|
18
|
+
private import memo_architecture_operational_workflows::*;
|
|
18
19
|
|
|
19
20
|
// The kind of need. Was a subclass branch (StakeholderNeed / UserNeed /
|
|
20
21
|
// ClinicalUserNeed / PatientUserNeed / BusinessNeed / ServiceNeed /
|
|
@@ -50,6 +51,13 @@ package memo_assurance_requirements_needs {
|
|
|
50
51
|
// carries the care setting, environment and jurisdiction that an
|
|
51
52
|
// `operationalContextReference` string could only describe.
|
|
52
53
|
ref useContext : UseContext[0..1];
|
|
54
|
+
// The body of work the need arises in: its workflow, the analysis of
|
|
55
|
+
// that work (IEC 62366-1 5.1). The need points at the workflow, never
|
|
56
|
+
// the reverse, so a workflow's needs are found upstream of it.
|
|
57
|
+
ref workflow : OperationalWorkflow[0..1];
|
|
58
|
+
// Whether current practice meets the need. False is an unmet need, the
|
|
59
|
+
// gap a device is for; unset is not yet assessed.
|
|
60
|
+
attribute metByCurrentPractice : Boolean[0..1];
|
|
53
61
|
// design-control need (ISO 13485 design input)
|
|
54
62
|
attribute sourceFolder : String;
|
|
55
63
|
}
|
|
@@ -22,6 +22,17 @@
|
|
|
22
22
|
// to the identifier they were already declared under. Display text is now
|
|
23
23
|
// `@MemoIdentity { label }` and prose is `doc`.
|
|
24
24
|
//
|
|
25
|
+
// ─── Resources ──────────────────────────────────────────────────────────
|
|
26
|
+
// `MemoResource` is here, beside `MemoPart`, because the operational layer's actors
|
|
27
|
+
// (`User`) and workflows (`WorkflowResource`) both specialize it, and so can the
|
|
28
|
+
// logical layer's platform (`part def SurgicalRobot :> System, MemoResource`); core is the one
|
|
29
|
+
// layer all of them import. Time-driven activity-based costing needs two numbers per
|
|
30
|
+
// resource: what an hour of its capacity costs (staff pay, or an instrument's purchase,
|
|
31
|
+
// service and practical capacity) and what one use costs (a consumable). The activity
|
|
32
|
+
// that uses the resource supplies the time. Both are money in the project's one currency
|
|
33
|
+
// (memo_core_stdlib_money) and, by the principle that level 1 carries no numbers, are set
|
|
34
|
+
// per variant on level 2.
|
|
35
|
+
//
|
|
25
36
|
// What remains on a base is domain semantics — `status`, and whatever that
|
|
26
37
|
// metaclass family genuinely needs.
|
|
27
38
|
//
|
|
@@ -36,6 +47,7 @@ package memo_core_common {
|
|
|
36
47
|
private import memo_core_dimensions::*;
|
|
37
48
|
private import memo_core_terminology::*;
|
|
38
49
|
private import memo_core_enumerations::*;
|
|
50
|
+
private import memo_core_stdlib_money::*;
|
|
39
51
|
|
|
40
52
|
// The metaclass-agnostic carrier for MEMO's identity fields.
|
|
41
53
|
//
|
|
@@ -136,6 +148,13 @@ package memo_core_common {
|
|
|
136
148
|
attribute revision : String[0..1];
|
|
137
149
|
}
|
|
138
150
|
|
|
151
|
+
// A resource a body of work spends: an instrument, a person, a consumable or the platform. It
|
|
152
|
+
// carries what an hour of its capacity costs and what one use of it costs.
|
|
153
|
+
abstract part def MemoResource specializes MemoPart {
|
|
154
|
+
attribute capacityCostRate : CostRateValue[0..1];
|
|
155
|
+
attribute unitCost : MoneyValue[0..1];
|
|
156
|
+
}
|
|
157
|
+
|
|
139
158
|
// ─── Role bases retained from the original kernel, re-founded on
|
|
140
159
|
// MemoPart so all existing content inherits the dimensions. ───
|
|
141
160
|
part def RequirementDriver specializes MemoPart;
|
|
@@ -289,6 +289,7 @@ package memo_core_relationships_workspace_membership {
|
|
|
289
289
|
|
|
290
290
|
// Neither: a step is not placed by the rule that says when it is done.
|
|
291
291
|
part membershipDoneWhen : WorkspaceMembershipEntry { attribute :>> relation = "doneWhen"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
292
|
+
part membershipLinkedWhen : WorkspaceMembershipEntry { attribute :>> relation = "linkedWhen"; attribute :>> direction = WorkspaceMembershipKind::neither; }
|
|
292
293
|
|
|
293
294
|
// A project follows the releases it feeds, as a device follows what it covers: a project that feeds releases
|
|
294
295
|
// of two systems is shared, and one that feeds none is Unassigned (work that reached nothing).
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
// Re-export-only wrapper. No new types.
|
|
2
|
+
//
|
|
3
|
+
// The trade-study framework (`TradeStudy`, `EvaluationFunction`, `MinimizeObjective`,
|
|
4
|
+
// `MaximizeObjective`) a comparison of alternatives is written with: current practice, ours and a
|
|
5
|
+
// competitor's are the alternatives, an evaluation function over their roll-ups scores each, and
|
|
6
|
+
// the objective says which score is best.
|
|
7
|
+
package memo_core_stdlib_analysis {
|
|
8
|
+
private import ScalarValues::*;
|
|
9
|
+
|
|
10
|
+
public import TradeStudies::*;
|
|
11
|
+
}
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
// Money as a quantity, the one stated exception to "a measurable value is ISQ".
|
|
2
|
+
//
|
|
3
|
+
// ISQ (ISO/IEC 80000) has no monetary quantity, and a cost kept as a bare `Real`
|
|
4
|
+
// or a `String` cannot be summed with `QuantityCalculations::sum` or multiplied
|
|
5
|
+
// by a duration into a cost. So money is a quantity of its own: a base quantity
|
|
6
|
+
// (`monetaryAmount`), a unit type for it (`CurrencyUnit`), and the rate that is
|
|
7
|
+
// money per time (`CostRateValue`, `CostRateUnit`), built exactly as ISQBase builds
|
|
8
|
+
// `DurationValue`/`DurationUnit` and `FrequencyUnit`. A sum of `MoneyValue`s then
|
|
9
|
+
// type-checks, and so does `capacityCostRate * expectedDuration`.
|
|
10
|
+
//
|
|
11
|
+
// One currency per project. The library declares no currency: a project declares
|
|
12
|
+
// the one it uses, once, as a `CurrencyUnit` (`attribute <EUR> euro : CurrencyUnit;`)
|
|
13
|
+
// and writes every amount in it. No conversion between currencies is modelled, so
|
|
14
|
+
// two currency units in one project is an error, checked by a consistency rule.
|
|
15
|
+
//
|
|
16
|
+
// Where it lives: `memo_core_stdlib_quantities` re-exports ISQ, SI and the SI prefixes
|
|
17
|
+
// and declares nothing, so a declaration does not go there. This package is the same
|
|
18
|
+
// kind of unit beside it, in core because both the operational layer (resource cost)
|
|
19
|
+
// and the realization layers (bill-of-material cost) price things, and core is the
|
|
20
|
+
// only layer every one of them may import. It imports the SysML quantity libraries
|
|
21
|
+
// and nothing of MEMO's.
|
|
22
|
+
package memo_core_stdlib_money {
|
|
23
|
+
private import ScalarValues::Real;
|
|
24
|
+
private import Quantities::*;
|
|
25
|
+
private import MeasurementReferences::*;
|
|
26
|
+
private import ISQ::DurationUnit;
|
|
27
|
+
private import ISQ::isq;
|
|
28
|
+
|
|
29
|
+
attribute def MoneyValue :> ScalarQuantityValue {
|
|
30
|
+
attribute :>> num: Real;
|
|
31
|
+
attribute :>> mRef: CurrencyUnit[1];
|
|
32
|
+
}
|
|
33
|
+
|
|
34
|
+
attribute monetaryAmount: MoneyValue[*] nonunique :> scalarQuantities;
|
|
35
|
+
|
|
36
|
+
attribute def CurrencyUnit :> SimpleUnit {
|
|
37
|
+
private attribute moneyPF: QuantityPowerFactor[1] { :>> quantity = monetaryAmount; :>> exponent = 1; }
|
|
38
|
+
attribute :>> quantityDimension { :>> quantityPowerFactors = moneyPF; }
|
|
39
|
+
}
|
|
40
|
+
|
|
41
|
+
attribute def CostRateValue :> ScalarQuantityValue {
|
|
42
|
+
attribute :>> num: Real;
|
|
43
|
+
attribute :>> mRef: CostRateUnit[1];
|
|
44
|
+
}
|
|
45
|
+
|
|
46
|
+
attribute costRate: CostRateValue[*] nonunique :> scalarQuantities;
|
|
47
|
+
|
|
48
|
+
attribute def CostRateUnit :> DerivedUnit {
|
|
49
|
+
private attribute moneyPF: QuantityPowerFactor[1] { :>> quantity = monetaryAmount; :>> exponent = 1; }
|
|
50
|
+
private attribute durationPF: QuantityPowerFactor[1] { :>> quantity = isq.T; :>> exponent = -1; }
|
|
51
|
+
attribute :>> quantityDimension { :>> quantityPowerFactors = (moneyPF, durationPF); }
|
|
52
|
+
}
|
|
53
|
+
}
|