@memoarchitect/ontology 0.16.5 → 0.17.1

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.
Files changed (51) hide show
  1. package/README.md +1 -1
  2. package/examples/gastric-bypass-variants/memo.identity.yaml +6 -0
  3. package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +11 -11
  4. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/viewpoint.sysml +8 -0
  5. package/examples/gastric-bypass-variants/model/catalog/viewpoints/clinical_workflow/views/bypass_flow.sysml +20 -0
  6. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/viewpoint.sysml +8 -0
  7. package/examples/gastric-bypass-variants/model/catalog/viewpoints/functional/views/bypass_flows.sysml +20 -0
  8. package/examples/gastric-bypass-variants/model/catalog/viewpoints/operational/views/bypass_flows.sysml +3 -18
  9. package/examples/gastric-bypass-variants/model/methodology/project.sysml +1 -0
  10. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +5 -5
  11. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +3 -3
  12. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +1 -1
  13. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +2 -2
  14. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +2 -2
  15. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +2 -2
  16. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +2 -2
  17. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +2 -2
  18. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +5 -5
  19. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +9 -9
  20. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +2 -2
  21. package/extensions/aadl/memo.package.yaml +1 -1
  22. package/extensions/anatomy/memo.package.yaml +1 -1
  23. package/extensions/clinical/memo.package.yaml +1 -1
  24. package/extensions/clinical/src/procedures/memo_clinical_procedures.sysml +12 -1
  25. package/extensions/cloud/memo.package.yaml +1 -1
  26. package/extensions/container/memo.package.yaml +1 -1
  27. package/extensions/messaging/memo.package.yaml +1 -1
  28. package/extensions/ros/memo.package.yaml +1 -1
  29. package/methodologies/default/memo.package.yaml +1 -1
  30. package/methodologies/gpca/memo.package.yaml +1 -1
  31. package/ontology/memo.package.yaml +1 -1
  32. package/package.json +1 -1
  33. package/profile/memo.package.yaml +1 -1
  34. package/src/architecture/operational/rollups/memo_rollups.sysml +19 -4
  35. package/src/architecture/operational/use_cases/memo_use_cases.sysml +14 -3
  36. package/src/architecture/operational/workflows/memo_workflows.sysml +9 -53
  37. package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
  38. package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
  39. package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
  40. package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
  41. package/src/artifacts/templates/dhf/iec-62366/use-spec.md +1 -1
  42. package/src/core/relationships/memo_workspace_membership.sysml +0 -2
  43. package/src/memo_namespaces.sysml +6 -0
  44. package/src/methodology/profiles/memo_profiles.sysml +2 -2
  45. package/src/rules/ontology/ontology_invariants.sysml +44 -20
  46. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +25 -0
  47. package/src/viewpoints/definitions/memo_view_layout.sysml +2 -0
  48. package/stage1/opensysml-78b939a8e298313dd51f9813.json.gz +0 -0
  49. package/stage1/syside-d48ff8bfaf540531526ec21a.ids.gz +0 -0
  50. package/stage1/syside-d48ff8bfaf540531526ec21a.json.gz +0 -0
  51. package/stage1/opensysml-14b923f7fe63f4062aa23208.json.gz +0 -0
package/README.md CHANGED
@@ -25,7 +25,7 @@ pin an exact release; the package has no repository or runtime dependency on Mem
25
25
  Tools or Memo Architect.
26
26
 
27
27
  ```bash
28
- pnpm add @memoarchitect/ontology@0.16.5
28
+ pnpm add @memoarchitect/ontology@0.17.1
29
29
  ```
30
30
 
31
31
  > **Pre-1.0 notice:** ontology names, relationships, and package layout may
@@ -305,6 +305,12 @@ elements:
305
305
  "memo_examples_gastric_bypass_variants_project::upperGi":
306
306
  shortId: "UNK-1"
307
307
  uuid: "c999ccf2-0fe8-5257-9344-14f34de28d39"
308
+ "memo_examples_gastric_bypass_variants_viewpoints_clinical_workflow_views::bypassFlowClinical":
309
+ shortId: "MMX-13"
310
+ uuid: "ffa4edf9-165e-52e2-9bb6-2a755b8a5937"
311
+ "memo_examples_gastric_bypass_variants_viewpoints_functional_views::bypassFlowFunctional":
312
+ shortId: "MMX-12"
313
+ uuid: "09fbcf2f-f707-5560-8891-a183c140459b"
308
314
  "memo_examples_gastric_bypass_variants_viewpoints_operational_views::bypassFlowClinical":
309
315
  shortId: "MMX-7"
310
316
  uuid: "725383b1-e31a-518f-8ecf-319f9c596e2d"
@@ -73,8 +73,8 @@ package memo_examples_gastric_bypass_variants {
73
73
  }
74
74
 
75
75
  // ── Tier 1: the clinical workflow ───────────────────────────
76
- use case ucRouxEnY : UseCase {
77
- attribute :>> useCaseKind = UseCaseKind::clinical;
76
+ use case ucRouxEnY : ClinicalUseCase {
77
+ attribute :>> useCaseKind = UseCaseKind::care;
78
78
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass"; }
79
79
  attribute :>> goalStatement = "Create the gastric pouch and its anastomosis and confirm that it does not leak, whatever the platform.";
80
80
  subject :>> supportingSystem = surgicalTeam;
@@ -185,12 +185,12 @@ package memo_examples_gastric_bypass_variants {
185
185
  allocate fnFireStapler to platform.ourRobot;
186
186
 
187
187
  // ── Tier 2: the system workflow, laparoscopic ──────────────────────
188
- use case ucRouxEnYLap : UseCase {
189
- attribute :>> useCaseKind = UseCaseKind::clinical;
188
+ use case ucRouxEnYLap : SystemUseCase {
189
+ attribute :>> useCaseKind = UseCaseKind::care;
190
190
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (laparoscopic)"; }
191
191
  subject :>> supportingSystem = platform.laparoscopicTower;
192
192
  }
193
- part wfRouxEnYLap : OperationalWorkflow {
193
+ part wfRouxEnYLap : SystemWorkflow {
194
194
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (laparoscopic)"; }
195
195
  attribute :>> entryCondition = "patient prepared; time-out complete";
196
196
  attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
@@ -250,12 +250,12 @@ package memo_examples_gastric_bypass_variants {
250
250
  #refinement dependency wfRouxEnYLap::scLapConversion::convertToOpen to wfRouxEnY::scConversion::convertToOpen;
251
251
 
252
252
  // ── Tier 2: the system workflow, our robot ──────────────────────
253
- use case ucRouxEnYOur : UseCase {
254
- attribute :>> useCaseKind = UseCaseKind::clinical;
253
+ use case ucRouxEnYOur : SystemUseCase {
254
+ attribute :>> useCaseKind = UseCaseKind::care;
255
255
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (our robot)"; }
256
256
  subject :>> supportingSystem = platform.ourRobot;
257
257
  }
258
- part wfRouxEnYOur : OperationalWorkflow {
258
+ part wfRouxEnYOur : SystemWorkflow {
259
259
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (our robot)"; }
260
260
  attribute :>> entryCondition = "patient prepared; time-out complete";
261
261
  attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
@@ -320,12 +320,12 @@ package memo_examples_gastric_bypass_variants {
320
320
  #refinement dependency wfRouxEnYOur::scOurConversion::convertToOpen to wfRouxEnY::scConversion::convertToOpen;
321
321
 
322
322
  // ── Tier 2: the system workflow, competitor robot ──────────────────────
323
- use case ucRouxEnYCmp : UseCase {
324
- attribute :>> useCaseKind = UseCaseKind::clinical;
323
+ use case ucRouxEnYCmp : SystemUseCase {
324
+ attribute :>> useCaseKind = UseCaseKind::care;
325
325
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (competitor robot)"; }
326
326
  subject :>> supportingSystem = platform.competitorRobot;
327
327
  }
328
- part wfRouxEnYCmp : OperationalWorkflow {
328
+ part wfRouxEnYCmp : SystemWorkflow {
329
329
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (competitor robot)"; }
330
330
  attribute :>> entryCondition = "patient prepared; time-out complete";
331
331
  attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
@@ -0,0 +1,8 @@
1
+ // clinical workflow viewpoint.
2
+ //
3
+ // This project does not define its own viewpoint here; it binds the reusable
4
+ // MEMO viewpoint that frames these concerns. The views it governs sit beneath
5
+ // `views/`.
6
+ package memo_examples_gastric_bypass_variants_viewpoints_clinical_workflow {
7
+ public import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
8
+ }
@@ -0,0 +1,20 @@
1
+ // The clinical workflow of the example: what the care team does, with no product and no number.
2
+ // Each platform's system workflow refines it and is in the operational viewpoint.
3
+ package memo_examples_gastric_bypass_variants_viewpoints_clinical_workflow_views {
4
+ private import ScalarValues::*;
5
+
6
+ private import memo_viewpoints_definitions::*;
7
+ private import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
8
+ private import memo_core_enumerations::*;
9
+
10
+ private import memo_core_common::*;
11
+ private import memo_core_common::MemoIdentity;
12
+ view bypassFlowClinical : MemoDiagramView {
13
+ @MemoIdentity { :>> label = "Clinical workflow: Roux-en-Y gastric bypass"; }
14
+ expose memo_examples_gastric_bypass_variants::wfRouxEnY::scNominal::**;
15
+ attribute depth = 2;
16
+ attribute :>> viewKind = DiagramViewKind::actionflow;
17
+ attribute :>> diagramType = "ofd";
18
+ ref :>> viewpointDefinition = clinicalWorkflowViewpoint;
19
+ }
20
+ }
@@ -0,0 +1,8 @@
1
+ // functional viewpoint.
2
+ //
3
+ // This project does not define its own viewpoint here; it binds the reusable
4
+ // MEMO viewpoint that frames these concerns. The views it governs sit beneath
5
+ // `views/`.
6
+ package memo_examples_gastric_bypass_variants_viewpoints_functional {
7
+ public import memo_viewpoints_functional_functional_viewpoint::*;
8
+ }
@@ -0,0 +1,20 @@
1
+ // Our robot's functional workflow: the functions it performs, in order. Functions are inside the
2
+ // system, so this view belongs to the functional viewpoint, not the operational one.
3
+ package memo_examples_gastric_bypass_variants_viewpoints_functional_views {
4
+ private import ScalarValues::*;
5
+
6
+ private import memo_viewpoints_definitions::*;
7
+ private import memo_viewpoints_functional_functional_viewpoint::*;
8
+ private import memo_core_enumerations::*;
9
+
10
+ private import memo_core_common::*;
11
+ private import memo_core_common::MemoIdentity;
12
+ view bypassFlowFunctional : MemoDiagramView {
13
+ @MemoIdentity { :>> label = "Functional workflow: our robot"; }
14
+ expose memo_examples_gastric_bypass_variants::fcOurRobotProcedure::**;
15
+ attribute depth = 2;
16
+ attribute :>> viewKind = DiagramViewKind::actionflow;
17
+ attribute :>> diagramType = "ofd";
18
+ ref :>> viewpointDefinition = functionalViewpoint;
19
+ }
20
+ }
@@ -1,5 +1,6 @@
1
- // The five flow views of the gastric-bypass example, in one package: the clinical workflow, the
2
- // system workflow of each platform, and our robot's functional workflow. Each shows its nominal
1
+ // The three operational flow views of the gastric-bypass example: the system workflow of each
2
+ // platform (the clinical workflow is in the clinical workflow viewpoint). Operational stays a black box, so no function appears here;
3
+ // our robot's functional workflow is in the functional viewpoint. Each shows its nominal
3
4
  // scenario; the alternate scenario is one step and has no flow to draw.
4
5
  package memo_examples_gastric_bypass_variants_viewpoints_operational_views {
5
6
  private import ScalarValues::*;
@@ -10,14 +11,6 @@ package memo_examples_gastric_bypass_variants_viewpoints_operational_views {
10
11
 
11
12
  private import memo_core_common::*;
12
13
  private import memo_core_common::MemoIdentity;
13
- view bypassFlowClinical : MemoDiagramView {
14
- @MemoIdentity { :>> label = "Clinical workflow: Roux-en-Y gastric bypass"; }
15
- expose memo_examples_gastric_bypass_variants::wfRouxEnY::scNominal::**;
16
- attribute depth = 2;
17
- attribute :>> viewKind = DiagramViewKind::actionflow;
18
- attribute :>> diagramType = "ofd";
19
- ref :>> viewpointDefinition = operationalViewpoint;
20
- }
21
14
  view bypassFlowLaparoscopic : MemoDiagramView {
22
15
  @MemoIdentity { :>> label = "System workflow: laparoscopic"; }
23
16
  expose memo_examples_gastric_bypass_variants::wfRouxEnYLap::scLapNominal::**;
@@ -42,12 +35,4 @@ package memo_examples_gastric_bypass_variants_viewpoints_operational_views {
42
35
  attribute :>> diagramType = "ofd";
43
36
  ref :>> viewpointDefinition = operationalViewpoint;
44
37
  }
45
- view bypassFlowFunctional : MemoDiagramView {
46
- @MemoIdentity { :>> label = "Functional workflow: our robot"; }
47
- expose memo_examples_gastric_bypass_variants::fcOurRobotProcedure::**;
48
- attribute depth = 2;
49
- attribute :>> viewKind = DiagramViewKind::actionflow;
50
- attribute :>> diagramType = "ofd";
51
- ref :>> viewpointDefinition = operationalViewpoint;
52
- }
53
38
  }
@@ -8,6 +8,7 @@ package memo_examples_gastric_bypass_variants_project {
8
8
 
9
9
  private import memo_examples_gastric_bypass_variants::*;
10
10
  private import memo_examples_gastric_bypass_variants_viewpoints_operational_views::*;
11
+ private import memo_examples_gastric_bypass_variants_viewpoints_functional_views::*;
11
12
 
12
13
  // The clinical extension brings the anatomy extension with it. The anatomy the model uses is
13
14
  // generated from FMA into a library of its own (`memo anatomy generate`), from the selector below.
@@ -145,8 +145,8 @@ package memo_examples_gpca_pump_gpca_operational {
145
145
  // ── Scenario-driven operational model ──────────────────────
146
146
  // The use case is the patient and clinician goal. It is supported by
147
147
  // several workflows, each of which owns multiple selected scenarios.
148
- use case ucDeliverPcaTherapy : UseCase {
149
- attribute :>> useCaseKind = UseCaseKind::clinical;
148
+ use case ucDeliverPcaTherapy : SystemUseCase {
149
+ attribute :>> useCaseKind = UseCaseKind::care;
150
150
  @MemoIdentity { :>> providedId = "UC-001"; :>> label = "DeliverPatientControlledAnalgesia"; }
151
151
  attribute :>> goalStatement = "Deliver prescribed analgesia safely while allowing patient-controlled bolus requests within configured limits.";
152
152
  attribute :>> trigger = "A clinician starts prescribed patient-controlled analgesia therapy.";
@@ -159,13 +159,13 @@ package memo_examples_gpca_pump_gpca_operational {
159
159
  actor pharmacistActor = actorPharmacist;
160
160
  }
161
161
 
162
- part wfPrepareAndStartTherapy : OperationalWorkflow {
162
+ part wfPrepareAndStartTherapy : SystemWorkflow {
163
163
  @MemoIdentity { :>> label = "PrepareAndStartTherapy"; }
164
164
  attribute :>> entryCondition = "A valid prescription and prepared reservoir are available.";
165
165
  attribute :>> completionCondition = "Therapy is started with confirmed prescription limits.";
166
166
 
167
167
  }
168
- part wfManageActiveTherapy : OperationalWorkflow {
168
+ part wfManageActiveTherapy : SystemWorkflow {
169
169
  @MemoIdentity { :>> label = "ManageActiveTherapy"; }
170
170
  attribute :>> entryCondition = "Basal therapy is active.";
171
171
  attribute :>> completionCondition = "A bolus is handled or active therapy continues safely.";
@@ -197,7 +197,7 @@ package memo_examples_gpca_pump_gpca_operational {
197
197
  }
198
198
  }
199
199
  }
200
- part wfRespondToTherapyAlarm : OperationalWorkflow {
200
+ part wfRespondToTherapyAlarm : SystemWorkflow {
201
201
  @MemoIdentity { :>> label = "RespondToTherapyAlarm"; }
202
202
  attribute :>> entryCondition = "A therapy alarm or degraded condition is detected.";
203
203
  attribute :>> completionCondition = "The pump is safe and the clinician has resolved or escalated the condition.";
@@ -24,8 +24,8 @@ package memo_examples_reusable_instrument {
24
24
  attribute :>> serviceScope = "central sterile services department";
25
25
  }
26
26
 
27
- use case ucSterilize : UseCase {
28
- attribute :>> useCaseKind = UseCaseKind::clinical;
27
+ use case ucSterilize : ClinicalUseCase {
28
+ attribute :>> useCaseKind = UseCaseKind::care;
29
29
  @MemoIdentity { :>> providedId = "RI-UC-001"; :>> label = "SterilizeReusableInstrument"; }
30
30
  attribute :>> goalStatement = "Return a used instrument to sterile, functional condition for the next case.";
31
31
  attribute :>> preCondition = "instrument collected from the OR; gross soil removed at point of use";
@@ -35,7 +35,7 @@ package memo_examples_reusable_instrument {
35
35
  }
36
36
 
37
37
  // Reprocessing workflow: exists independently of any single instrument.
38
- part wfReprocess : OperationalWorkflow {
38
+ part wfReprocess : ClinicalWorkflow {
39
39
  @MemoIdentity { :>> providedId = "RI-WF-001"; :>> label = "InstrumentReprocessingWorkflow"; }
40
40
  attribute :>> entryCondition = "used instrument received in decontamination";
41
41
  attribute :>> completionCondition = "sterile pack released to storage";
@@ -15,7 +15,7 @@ package robot_cell_family_sos_chains {
15
15
  private import robot_cell_family_systems_manipulation_manipulation_system::*;
16
16
  private import robot_cell_family_systems_perception_perception_system::*;
17
17
 
18
- part wfMapGuidedPick : OperationalWorkflow {
18
+ part wfMapGuidedPick : SystemWorkflow {
19
19
  @MemoIdentity { :>> providedId = "RCF-FC-001"; :>> label = "Map-Guided Pick"; }
20
20
  doc /* Point clouds acquired by the perception system build the occupancy map; each grasp by the manipulator is tagged on that map. */
21
21
  action scMapGuidedPick : OperativeScenario {
@@ -11,9 +11,9 @@ package robot_cell_family_sos_use_cases {
11
11
  private import robot_cell_family_systems_manipulation_manipulation_system::*;
12
12
  private import robot_cell_family_systems_perception_perception_system::*;
13
13
 
14
- use case ucPerformPickAndPlace : UseCase {
14
+ use case ucPerformPickAndPlace : SystemUseCase {
15
15
  @MemoIdentity { :>> providedId = "RCF-UC-001"; :>> label = "Perform Pick And Place"; }
16
- attribute :>> useCaseKind = UseCaseKind::clinical;
16
+ attribute :>> useCaseKind = UseCaseKind::care;
17
17
  attribute :>> goalStatement = "Move a workpiece by mapping the cell and grasping it.";
18
18
  subject :>> supportingSystem = robotCell;
19
19
  actor operator = cellOperator;
@@ -34,9 +34,9 @@ package robot_cell_family_systems_manipulation_manipulation_system {
34
34
  attribute :>> outputDescription = "Grasp made within the set force and time limits, and the event that records it";
35
35
  }
36
36
 
37
- use case ucExecuteGrasp : UseCase {
37
+ use case ucExecuteGrasp : SystemUseCase {
38
38
  @MemoIdentity { :>> providedId = "RCF-MAN-UC-001"; :>> label = "Execute Grasp"; }
39
- attribute :>> useCaseKind = UseCaseKind::clinical;
39
+ attribute :>> useCaseKind = UseCaseKind::care;
40
40
  subject :>> supportingSystem : ManipulatorSystem;
41
41
  actor operator = cellOperator;
42
42
  }
@@ -42,9 +42,9 @@ package robot_cell_family_systems_navigation_navigation_system {
42
42
  }
43
43
 
44
44
  // A system use case: its subject is this system.
45
- use case ucAcquireMap : UseCase {
45
+ use case ucAcquireMap : SystemUseCase {
46
46
  @MemoIdentity { :>> providedId = "RCF-NAV-UC-001"; :>> label = "Acquire Occupancy Map"; }
47
- attribute :>> useCaseKind = UseCaseKind::clinical;
47
+ attribute :>> useCaseKind = UseCaseKind::care;
48
48
  subject :>> supportingSystem : NavigationSystem;
49
49
  actor operator = cellOperator;
50
50
  }
@@ -33,9 +33,9 @@ package robot_cell_family_systems_perception_perception_system {
33
33
  attribute :>> outputDescription = "Filtered, timestamped point clouds";
34
34
  }
35
35
 
36
- use case ucRecordRun : UseCase {
36
+ use case ucRecordRun : SystemUseCase {
37
37
  @MemoIdentity { :>> providedId = "RCF-PER-UC-001"; :>> label = "Record Run Data"; }
38
- attribute :>> useCaseKind = UseCaseKind::clinical;
38
+ attribute :>> useCaseKind = UseCaseKind::care;
39
39
  subject :>> supportingSystem : PerceptionSystem;
40
40
  actor operator = cellTechnician;
41
41
  }
@@ -49,8 +49,8 @@ package memo_examples_surgical_closure_workflow {
49
49
  @MemoIdentity { :>> providedId = "LSG-N-001"; }
50
50
  attribute :>> statement = "The surgical team needs to perform gastric resection with controlled anatomy, haemostasis, and a checked staple line.";
51
51
  }
52
- use case ucPerformSleeveGastrectomy : UseCase {
53
- attribute :>> useCaseKind = UseCaseKind::clinical;
52
+ use case ucPerformSleeveGastrectomy : ClinicalUseCase {
53
+ attribute :>> useCaseKind = UseCaseKind::care;
54
54
  @MemoIdentity { :>> providedId = "LSG-UC-001"; :>> label = "PerformLaparoscopicSleeveGastrectomy"; }
55
55
  attribute :>> goalStatement = "Complete the planned laparoscopic sleeve gastrectomy and transfer the patient with the staple line assessed.";
56
56
  attribute :>> trigger = "patient prepared and surgical time-out complete";
@@ -42,21 +42,21 @@ package memo_examples_sysml_diagram_samples_samples_browser_view {
42
42
  @MemoIdentity { :>> label = "Remote Monitor"; }
43
43
  }
44
44
 
45
- use case startSystem : UseCase {
45
+ use case startSystem : SystemUseCase {
46
46
  @MemoIdentity { :>> providedId = "UC-BRW-1"; :>> label = "Start System"; }
47
- attribute :>> useCaseKind = UseCaseKind::clinical;
47
+ attribute :>> useCaseKind = UseCaseKind::care;
48
48
  subject controlSystem;
49
49
  actor operatorActor = systemOperator;
50
50
  }
51
- use case runDiagnostics : UseCase {
51
+ use case runDiagnostics : SystemUseCase {
52
52
  @MemoIdentity { :>> providedId = "UC-BRW-2"; :>> label = "Run Diagnostics"; }
53
53
  attribute :>> useCaseKind = UseCaseKind::service;
54
54
  subject controlSystem;
55
55
  actor engineerActor = maintenanceEngineer;
56
56
  }
57
- use case monitorStatus : UseCase {
57
+ use case monitorStatus : SystemUseCase {
58
58
  @MemoIdentity { :>> providedId = "UC-BRW-3"; :>> label = "Monitor Status"; }
59
- attribute :>> useCaseKind = UseCaseKind::clinical;
59
+ attribute :>> useCaseKind = UseCaseKind::care;
60
60
  subject controlSystem;
61
61
  actor monitorActor = remoteMonitor;
62
62
  }
@@ -34,37 +34,37 @@ package memo_examples_sysml_diagram_samples_samples_use_case_view {
34
34
  @MemoIdentity { :>> label = "Nursing Staff"; }
35
35
  }
36
36
 
37
- use case reviewStatus : UseCase {
37
+ use case reviewStatus : SystemUseCase {
38
38
  @MemoIdentity { :>> providedId = "UC-SAMPLE-1"; :>> label = "Review Device Status"; }
39
- attribute :>> useCaseKind = UseCaseKind::clinical;
39
+ attribute :>> useCaseKind = UseCaseKind::care;
40
40
  include validateTherapySettings;
41
41
  subject supportingSystem;
42
42
  actor patientActor = patient;
43
43
  }
44
- use case configureTherapy : UseCase {
44
+ use case configureTherapy : SystemUseCase {
45
45
  @MemoIdentity { :>> providedId = "UC-SAMPLE-2"; :>> label = "Configure Therapy"; }
46
- attribute :>> useCaseKind = UseCaseKind::clinical;
46
+ attribute :>> useCaseKind = UseCaseKind::care;
47
47
  include reviewStatus;
48
48
  subject supportingSystem;
49
49
  actor clinicianInitiator = clinician;
50
50
  actor patientActor = patient;
51
51
  }
52
- use case maintainDevice : UseCase {
52
+ use case maintainDevice : SystemUseCase {
53
53
  @MemoIdentity { :>> providedId = "UC-SAMPLE-3"; :>> label = "Maintain Device"; }
54
54
  attribute :>> useCaseKind = UseCaseKind::service;
55
55
  subject supportingSystem;
56
56
  actor serviceTechnicianActor = serviceTechnician;
57
57
  }
58
58
 
59
- use case documentTreatment : UseCase {
59
+ use case documentTreatment : SystemUseCase {
60
60
  @MemoIdentity { :>> providedId = "UC-SAMPLE-4"; :>> label = "Document Treatment"; }
61
- attribute :>> useCaseKind = UseCaseKind::clinical;
61
+ attribute :>> useCaseKind = UseCaseKind::care;
62
62
  }
63
63
 
64
64
  // L2 child of Review Device Status: makes L0 → L1 → L2 selectable.
65
- use case validateTherapySettings : UseCase {
65
+ use case validateTherapySettings : SystemUseCase {
66
66
  @MemoIdentity { :>> providedId = "UC-SAMPLE-5"; :>> label = "Validate Therapy Settings"; }
67
- attribute :>> useCaseKind = UseCaseKind::clinical;
67
+ attribute :>> useCaseKind = UseCaseKind::care;
68
68
  subject supportingSystem;
69
69
  actor clinicianActor = clinician;
70
70
  }
@@ -36,8 +36,8 @@ package memo_examples_temperature_alarm {
36
36
  attribute :>> actorKind = ActorKind::clinician;
37
37
  @MemoIdentity { :>> providedId = "TA-USR-001"; }
38
38
  }
39
- use case ucMonitorTemp : UseCase {
40
- attribute :>> useCaseKind = UseCaseKind::clinical;
39
+ use case ucMonitorTemp : SystemUseCase {
40
+ attribute :>> useCaseKind = UseCaseKind::care;
41
41
  @MemoIdentity { :>> providedId = "TA-UC-001"; :>> label = "MonitorPatientTemperature"; }
42
42
  attribute :>> goalStatement = "Continuously monitor core temperature and be alerted when it leaves the safe range.";
43
43
  subject supportingSystem;
@@ -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-aadl'
10
- version: 0.16.5
10
+ version: 0.17.1
11
11
  description: AADL (SAE AS5506) correspondence profile and runtime component families
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-anatomy'
10
- version: 0.16.5
10
+ version: 0.17.1
11
11
  description: Human anatomy from the Foundational Model of Anatomy (FMA), selected per project
12
12
  license: MIT AND CC-BY-4.0
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/example-extension-clinical'
10
- version: 0.16.5
10
+ version: 0.17.1
11
11
  description: Example methodology extension for clinical-procedure vocabulary
12
12
  license: MIT
13
13
  tags:
@@ -14,10 +14,21 @@ package memo_extension_clinical_procedures {
14
14
 
15
15
  private import memo_core_terminology::*;
16
16
  private import memo_architecture_operational_workflows::*;
17
+ private import memo_viewpoints_rendering::*;
18
+ private import memo_core_common::MemoIdentity;
17
19
 
18
- part def ClinicalProcedureWorkflow specializes OperationalWorkflow {
20
+ part def ClinicalProcedureWorkflow specializes ClinicalWorkflow {
19
21
  attribute procedureCode : TerminologyCode[0..1];
20
22
  attribute clinicalObjective : String;
21
23
  attribute anesthesiaRequirement : String;
22
24
  }
25
+
26
+ // A package places its own kinds in the Model Explorer (the core ontology's classifications apply to the
27
+ // core's). Without this the procedure workflow is listed in no domain, outside the level it is declared at.
28
+ part explorerProceduresClassification : ExplorerClassification {
29
+ @MemoIdentity { :>> providedId = "EXPL-031"; :>> label = "proceduresExplorerClassification"; }
30
+ attribute :>> sourceNamespace = "procedures";
31
+ attribute :>> explorerDomain = "architecture";
32
+ attribute :>> explorerGroup = "operational";
33
+ }
23
34
  }
@@ -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-cloud'
10
- version: 0.16.5
10
+ version: 0.17.1
11
11
  description: Networked services and managed data stores
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-container'
10
- version: 0.16.5
10
+ version: 0.17.1
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.5
10
+ version: 0.17.1
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.5
10
+ version: 0.17.1
11
11
  description: ROS 2 nodes, messages, topic/service/action interfaces, QoS, and containerized deployment
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-default'
10
- version: 0.16.5
10
+ version: 0.17.1
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.5
10
+ version: 0.17.1
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.5
10
+ version: 0.17.1
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.5",
3
+ "version": "0.17.1",
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.5
10
+ version: 0.17.1
11
11
  description: Closure rules and viewpoints for medical device modeling
12
12
  license: MIT
13
13
  tags:
@@ -19,8 +19,8 @@
19
19
  // quantities with units; money is `memo_core_stdlib_money`, in the project's one currency.
20
20
  // A cost is the activity's duration times each instrument's capacity cost rate, plus each
21
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.
22
+ // paid for. Time is the longest path (`ScenarioDuration`), so a fork whose branches
23
+ // overlap takes its longest branch; a cost is still the sum, because each branch is paid for.
24
24
  //
25
25
  // `memo evaluate` runs them from these bodies over the built model (memo-tools, analysis/calc), and a
26
26
  // `TradeStudy` reads the results, so no figure is written twice. Units follow the SysML library's own
@@ -59,10 +59,25 @@ package memo_architecture_operational_rollups {
59
59
  ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; ActivityCost(activity) });
60
60
  }
61
61
 
62
+ // The time at which a step is done: its own duration after the latest of the steps before it.
63
+ // `predecessors` is the kernel library's (every earlier occurrence along the successions, not
64
+ // only the adjacent ones), which is enough because a step's finish time never falls short of
65
+ // the finish time of anything before it. A step with no succession to another is concurrent
66
+ // with it, as in the language, so two branches of a fork overlap and a scenario takes as long
67
+ // as its longest path, not the sum of its steps.
68
+ calc def FinishTime {
69
+ in activity : OperativeAction[1];
70
+ return finish : DurationValue[1] = QuantityCalculations::sum((
71
+ activity.expectedDuration,
72
+ activity.predecessors->collect { in before : OperativeAction[1]; FinishTime(before) }
73
+ ->reduce { in x : DurationValue[1]; in y : DurationValue[1]; NumericalFunctions::max(x, y) }));
74
+ }
75
+
62
76
  calc def ScenarioDuration {
63
77
  in scenario : MemoAction[1];
64
- return duration : DurationValue[1] = QuantityCalculations::sum(
65
- ActivitiesOf(scenario)->collect { in activity : OperativeAction[1]; activity.expectedDuration });
78
+ return duration : DurationValue[1] = ActivitiesOf(scenario)
79
+ ->collect { in activity : OperativeAction[1]; FinishTime(activity) }
80
+ ->reduce { in x : DurationValue[1]; in y : DurationValue[1]; NumericalFunctions::max(x, y) };
66
81
  }
67
82
 
68
83
  calc def ScenarioSuccess {
@@ -2,7 +2,8 @@
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
4
  //
5
- // A use case is at one of two levels, and the level is its subject's type, not a field.
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 clinical;
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;
@@ -62,6 +63,16 @@ package memo_architecture_operational_use_cases {
62
63
  // the actor's name, as the note on `Initiates` below says.
63
64
  }
64
65
 
66
+ // The two levels are types, declared and not derived. A clinical use case has an
67
+ // `OperationalEntity` (the care team, the setting) as its subject, names no product and carries
68
+ // no number; a system use case has a `System` or `SystemOfSystems`, one variant of a platform.
69
+ // CR-ONT-093 keeps the declared type and the subject in agreement. `UseCase` is abstract: a
70
+ // project states which level each use case is at.
71
+ use case def ClinicalUseCase :> UseCase {
72
+ }
73
+ use case def SystemUseCase :> UseCase {
74
+ }
75
+
65
76
  connection def Motivates :> MemoRelationship {
66
77
  end motivatingNeed : Need :>> source;
67
78
  end motivatedUseCase : UseCase :>> target;
@@ -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
- enum def StepTransformationKind {
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;
@@ -126,27 +105,4 @@ package memo_architecture_operational_workflows {
126
105
  // that each implied a different target type are now two typed refs plus
127
106
  // this one plain relation.
128
107
 
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
108
  }
@@ -45,7 +45,7 @@ empty: "No user need elements defined. Add Need or Requirement elements."
45
45
  Use cases describing how intended users interact with **{{project.product}}**, drawn from the model:
46
46
 
47
47
  ```memo-query
48
- kind: UseCase
48
+ kind: [ClinicalUseCase, SystemUseCase]
49
49
  display: table
50
50
  columns: name, layer, doc
51
51
  sort: name
@@ -31,7 +31,7 @@ _[TODO: Describe participant demographics, number, and selection criteria]_
31
31
  This section is generated from the system model. The table below lists the **Test Scenarios** elements currently defined:
32
32
 
33
33
  ```memo-query
34
- kind: [UseCase, ValidationCase]
34
+ kind: [ClinicalUseCase, SystemUseCase, ValidationCase]
35
35
  display: table
36
36
  columns: name, layer, doc
37
37
  sort: name
@@ -39,7 +39,7 @@ _[TODO: Describe all use environments: clinical, home, ambulatory, etc.]_
39
39
  This section is generated from the system model. The table below lists the **Use-Related Hazards** elements currently defined:
40
40
 
41
41
  ```memo-query
42
- kind: [UseCase, OperativeAction]
42
+ kind: [ClinicalUseCase, SystemUseCase, OperativeAction]
43
43
  display: table
44
44
  columns: name, layer, doc
45
45
  sort: name
@@ -23,7 +23,7 @@ This Use-Related Risk Analysis (URRA) identifies use errors and use-related haza
23
23
  This section is generated from the system model. The table below lists the **Use Scenarios** elements currently defined:
24
24
 
25
25
  ```memo-query
26
- kind: [UseCase, OperativeAction]
26
+ kind: [ClinicalUseCase, SystemUseCase, OperativeAction]
27
27
  display: table
28
28
  columns: name, layer, doc
29
29
  sort: name
@@ -39,7 +39,7 @@ _[TODO: Describe physical, social, technical environments where the device will
39
39
  Use cases describing how intended users interact with **{{project.product}}**, drawn from the model:
40
40
 
41
41
  ```memo-query
42
- kind: UseCase
42
+ kind: [ClinicalUseCase, SystemUseCase]
43
43
  display: table
44
44
  columns: name, layer, doc
45
45
  sort: name
@@ -76,8 +76,6 @@ package memo_core_relationships_workspace_membership {
76
76
  part membershipMotivates : WorkspaceMembershipEntry { attribute :>> relation = "motivates"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
77
77
  // A workflow follows the use case it realizes.
78
78
  part membershipRealizesUseCase : WorkspaceMembershipEntry { attribute :>> relation = "realizesUseCase"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
79
- // Neither: a transformation joins two actions.
80
- part membershipTransforms : WorkspaceMembershipEntry { attribute :>> relation = "transforms"; attribute :>> direction = WorkspaceMembershipKind::neither; }
81
79
  // A module follows the deployment unit it is built into.
82
80
  part membershipBuildsInto : WorkspaceMembershipEntry { attribute :>> relation = "buildsInto"; attribute :>> direction = WorkspaceMembershipKind::sourceFollowsTarget; }
83
81
  // The hardware or software follows the logical component it realizes: the logical component is
@@ -69,6 +69,7 @@ package memo {
69
69
  public import memo_viewpoints_cybersecurity_views_cybersecurity_assessment_view::*;
70
70
  public import memo_viewpoints_clinical_clinical_viewpoint::*;
71
71
  public import memo_viewpoints_clinical_views_clinical_evidence_view::*;
72
+ public import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
72
73
  public import memo_viewpoints_usability_usability_viewpoint::*;
73
74
  public import memo_viewpoints_usability_views_usability_engineering_view::*;
74
75
  public import memo_viewpoints_ui_layout_ui_layout_viewpoint::*;
@@ -304,6 +305,7 @@ package memo_namespace_rules {
304
305
  package memo_namespace_viewpoints {
305
306
  alias catalog for memo_namespace_viewpoints_catalog;
306
307
  alias clinical for memo_namespace_viewpoints_clinical;
308
+ alias clinical_workflow for memo_namespace_viewpoints_clinical_workflow;
307
309
  alias context for memo_namespace_viewpoints_context;
308
310
  alias cybersecurity for memo_namespace_viewpoints_cybersecurity;
309
311
  alias definitions for memo_namespace_viewpoints_definitions;
@@ -532,6 +534,10 @@ package memo_namespace_viewpoints_clinical {
532
534
  package views { alias clinical_evidence_view for memo_namespace_viewpoints_clinical_clinical_evidence_view; }
533
535
  }
534
536
 
537
+ package memo_namespace_viewpoints_clinical_workflow {
538
+ public import memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint::*;
539
+ }
540
+
535
541
  package memo_namespace_viewpoints_context {
536
542
  public import memo_viewpoints_context_context_viewpoint::*;
537
543
  package views { alias system_context_view for memo_namespace_viewpoints_context_system_context_view; }
@@ -16,7 +16,7 @@ package memo_methodology_profiles {
16
16
  private import memo_core_common::MemoIdentity;
17
17
  part mdCoreLibrary : MethodologyLibrary {
18
18
  @MemoIdentity { :>> providedId = "METHLIB-001"; :>> label = "MedicalDeviceMethodologyLibrary"; }
19
- attribute :>> version = "0.16.5";
19
+ attribute :>> version = "0.17.1";
20
20
  attribute :>> domain = "medical device modeling";
21
21
  doc /* Methodology layer for selecting, restricting, sequencing, tailoring, and lightly extending use of the medical-device ontology. */
22
22
  }
@@ -37,7 +37,7 @@ package memo_methodology_profiles {
37
37
  // second scope authority.
38
38
  part mdDefaultDefinition : MethodologyDefinition {
39
39
  @MemoIdentity { :>> providedId = "METH-MD-DEFAULT"; :>> label = "MedicalDeviceDefault"; }
40
- attribute :>> version = "0.16.5";
40
+ attribute :>> version = "0.17.1";
41
41
  attribute :>> domain = "medical device modeling";
42
42
  doc /* MEMO default medical-device methodology. Selects every layer, discipline, standard, artifact kind, and viewpoint the resolved ontology and extension packages provide. */
43
43
  attribute :>> scopeMode = ScopeModeKind::allAvailable;
@@ -4,15 +4,16 @@
4
4
  // Structural invariants (endpoint existence, cycle freedom) are expressed over
5
5
  // the typed relations introduced in 0.5 — typed references make them checkable.
6
6
  //
7
- // Operational levels (CR-ONT-093..101). A use case is at the level of its subject: an
8
- // `OperationalEntity` is level 1 (clinical, no product, no number), a `System` or `SystemOfSystems`
9
- // is level 2 (one variant of a platform, which carries every number). The level of a step is the
10
- // level of the use case its workflow `realizesUseCase`. The workflow is reached from the step by
11
- // `composes` (a step nested in a scenario) or through the scenario that `performs` it (a step
12
- // declared once and used in several); a step outside any workflow has no level and is judged by
13
- // no level rule.
14
- // Nothing here is a kind list: each rule reads the subject's type and the `performs` and
15
- // `realizes` edges the builder already produces. Rule 6 of the plan, that every variant of a `TradeStudy` refines every step compared (101),
7
+ // Operational levels (CR-ONT-093..103). A use case and a workflow are each declared at a level by
8
+ // their type: `ClinicalUseCase` and `ClinicalWorkflow` are level 1 (clinical, no product, no
9
+ // number), `SystemUseCase` and `SystemWorkflow` level 2 (one variant of a platform, which carries
10
+ // every number). 093 keeps a use case's type and subject in agreement, 103 a workflow's type and
11
+ // the use case it `realizesUseCase`. The level of a step is the type of the workflow it sits in,
12
+ // reached from the step by `composes` (a step nested in a scenario) or through the scenario that
13
+ // `performs` it (a step declared once and used in several); a step outside any workflow has no
14
+ // level and is judged by no level rule.
15
+ // Each rule reads a type and the `performs` and `realizes` edges the builder already produces.
16
+ // Rule 6 of the plan, that every variant of a `TradeStudy` refines every step compared (101),
16
17
  // reads the study's `hasSubject` edges: its subject is the alternatives it analyses.
17
18
  // The one-currency rule (098) counts the project's `CurrencyUnit` declarations: a unit declared at
18
19
  // package level is built as a model element, as ISQ and SI declare theirs.
@@ -55,10 +56,10 @@ package memo_rules_ontology {
55
56
  }
56
57
  // ─── Use case scope (plan O8) ─────────────────────────────────────────
57
58
  //
58
- // A use case is at the level of its subject: one whose subject is a SystemOfSystems is a clinical
59
- // procedure, one whose subject is a System is a system use case. There is no kind for either; the
60
- // level is read from the subject, and the subject from `hasSubject`. A use case with no subject
61
- // is at neither level and neither rule judges it.
59
+ // The level of a use case is its declared type (`ClinicalUseCase`, `SystemUseCase`), and
60
+ // CR-ONT-093 keeps it in agreement with the subject (`hasSubject`). Rule 085 reads the subject
61
+ // for what it says about composition, not for the level. A use case with no subject
62
+ // is judged by no rule on the subject.
62
63
 
63
64
  constraint def SosUseCaseIncludesSystemUseCaseRule :> MemoConsistencyRule {
64
65
  @MemoIdentity { :>> providedId = "CR-ONT-085"; }
@@ -697,8 +698,8 @@ package memo_rules_ontology {
697
698
  attribute obligation = RuleObligationKind::recommended;
698
699
  attribute appliesTo = "UseCase";
699
700
  attribute severity = RuleSeverityKind::error;
700
- attribute rationaleText = "A use case is at the level of its subject: an operational entity (the care team, the setting) is level 1, a system or a system of systems is level 2. A subject of any other type is at neither level, so the use case cannot say whether it may name a product or carry a number.";
701
- attribute predicateExpression = "downstream(hasSubject)->forAll(conformsTo(OperationalEntity) or conformsTo(System) or conformsTo(SystemOfSystems))";
701
+ attribute rationaleText = "A use case is declared at a level, and its subject agrees: a clinical use case has an operational entity (the care team, the setting) as its subject, a system use case a system or a system of systems. A use case of neither type does not say whether it may name a product or carry a number, and a subject of the other level makes the declared type false.";
702
+ attribute predicateExpression = "(conformsTo(ClinicalUseCase) and downstream(hasSubject)->forAll(conformsTo(OperationalEntity))) or (conformsTo(SystemUseCase) and downstream(hasSubject)->forAll(conformsTo(System) or conformsTo(SystemOfSystems)))";
702
703
  constraint { true }
703
704
  }
704
705
  constraint def LevelOneStepCarriesNoNumberRule :> MemoConsistencyRule {
@@ -709,7 +710,7 @@ package memo_rules_ontology {
709
710
  attribute appliesTo = "OperativeAction";
710
711
  attribute severity = RuleSeverityKind::error;
711
712
  attribute rationaleText = "A step of a level-1 workflow is the shared baseline of every variant and carries no planned number: a gastric pouch takes a different time and succeeds at a different rate on each platform, so a number on the step would belong to no variant. Time and success are set on the level-2 activity that refines it.";
712
- attribute predicateExpression = "(attributes.expectedDuration == '' and attributes.plannedSuccessProbability == '') or not((upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))))))";
713
+ attribute predicateExpression = "(attributes.expectedDuration == '' and attributes.plannedSuccessProbability == '') or not((upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))))))";
713
714
  constraint { true }
714
715
  }
715
716
  constraint def RealizerOfLevelOneStepIsLevelTwoRule :> MemoConsistencyRule {
@@ -720,7 +721,7 @@ package memo_rules_ontology {
720
721
  attribute appliesTo = "OperativeAction";
721
722
  attribute severity = RuleSeverityKind::error;
722
723
  attribute rationaleText = "Whatever refines a level-1 step is itself at level 2: a level-1 step refined by another level-1 step, or by an activity of no workflow at all, skips the level that names the variant.";
723
- attribute predicateExpression = "not(downstream(realizes)->exists((upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))))))) or (upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(System) or conformsTo(SystemOfSystems)))))))";
724
+ attribute predicateExpression = "not(downstream(realizes)->exists((upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))))))) or (upstream(composes)->exists(conformsTo(SystemWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(SystemWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(SystemWorkflow)))))";
724
725
  constraint { true }
725
726
  }
726
727
  constraint def InternalSystemActivityPerformsAFunctionRule :> MemoConsistencyRule {
@@ -742,7 +743,7 @@ package memo_rules_ontology {
742
743
  attribute appliesTo = "SystemFunction";
743
744
  attribute severity = RuleSeverityKind::error;
744
745
  attribute rationaleText = "A system function is performed from a level-2 activity or from a step of a functional flow, never from a level-1 step: level 1 names no product, and a function is what a product does.";
745
- attribute predicateExpression = "upstream(performs)->forAll(not(conformsTo(OperativeAction) and (upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))))))))";
746
+ attribute predicateExpression = "upstream(performs)->forAll(not(conformsTo(OperativeAction) and (upstream(composes)->exists(conformsTo(ClinicalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(ClinicalWorkflow)))))))";
746
747
  constraint { true }
747
748
  }
748
749
  constraint def ProjectDeclaresOneCurrencyRule :> MemoConsistencyRule {
@@ -764,7 +765,7 @@ package memo_rules_ontology {
764
765
  attribute appliesTo = "OperativeScenario";
765
766
  attribute severity = RuleSeverityKind::error;
766
767
  attribute rationaleText = "How likely a path is differs by platform (a robot and a laparoscopic tower do not convert to open at the same rate), so a scenario of a level-1 workflow carries no likelihood; it is set on the level-2 scenario of each variant.";
767
- attribute predicateExpression = "attributes.likelihood == '' or not(upstream(composes)->exists(conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity)))))";
768
+ attribute predicateExpression = "attributes.likelihood == '' or not(upstream(composes)->exists(conformsTo(ClinicalWorkflow)))";
768
769
  constraint { true }
769
770
  }
770
771
  constraint def LevelOneWorkflowCarriesNoCostRule :> MemoConsistencyRule {
@@ -775,7 +776,7 @@ package memo_rules_ontology {
775
776
  attribute appliesTo = "OperationalWorkflow";
776
777
  attribute severity = RuleSeverityKind::error;
777
778
  attribute rationaleText = "What a procedure costs apart from its activities (set-up, capital per case) depends on the platform, so a level-1 workflow carries no per-procedure cost; it is set on the workflow of each level-2 variant.";
778
- attribute predicateExpression = "attributes.perProcedureCost == '' or not(downstream(realizesUseCase)->exists(downstream(hasSubject)->exists(conformsTo(OperationalEntity))))";
779
+ attribute predicateExpression = "attributes.perProcedureCost == '' or not(conformsTo(ClinicalWorkflow))";
779
780
  constraint { true }
780
781
  }
781
782
  constraint def TradeStudyVariantRefinesEveryStepRule :> MemoConsistencyRule {
@@ -789,4 +790,27 @@ package memo_rules_ontology {
789
790
  attribute predicateExpression = "not(upstream(hasSubject)->exists(attributes.usageType == 'TradeStudy')) or upstream(hasSubject)->select(attributes.usageType == 'TradeStudy')->forAll(downstream(hasSubject)->forAll(downstream(composes)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))) and downstream(composes)->forAll(downstream(performs)->forAll(downstream(realizes)->forAll(upstream(realizes)->exists(upstream(composes)->exists(id == subject.id) or upstream(performs)->exists(upstream(composes)->exists(id == subject.id))))))))";
790
791
  constraint { true }
791
792
  }
793
+ constraint def WorkflowOwnsNoStepsOutsideScenariosRule :> MemoConsistencyRule {
794
+ @MemoIdentity { :>> providedId = "CR-ONT-102"; }
795
+ attribute tailoring = RuleTailoringKind::methodology;
796
+ attribute domain = RuleDomainKind::modelling;
797
+ attribute obligation = RuleObligationKind::recommended;
798
+ attribute appliesTo = "OperativeAction";
799
+ attribute severity = RuleSeverityKind::error;
800
+ attribute rationaleText = "A workflow is the analysis of a use case (its equipment, environment and needs); the steps that carry it out are the tasks of a use scenario (IEC 62366-1 5.4). A step owned by the workflow itself belongs to no scenario, so it has no pre- or post-condition and no path it is on.";
801
+ attribute predicateExpression = "not(upstream(composes)->exists(conformsTo(OperationalWorkflow))) or upstream(composes)->exists(conformsTo(OperativeScenario))";
802
+ constraint { true }
803
+ }
804
+ constraint def WorkflowRealizesUseCaseOfItsLevelRule :> MemoConsistencyRule {
805
+ @MemoIdentity { :>> providedId = "CR-ONT-103"; }
806
+ attribute tailoring = RuleTailoringKind::methodology;
807
+ attribute domain = RuleDomainKind::modelling;
808
+ attribute obligation = RuleObligationKind::recommended;
809
+ attribute appliesTo = "OperationalWorkflow";
810
+ attribute severity = RuleSeverityKind::error;
811
+ attribute rationaleText = "A workflow is the analysis of a use case and is at its level: a clinical workflow realizes a clinical use case, a system workflow a system use case. A workflow of the wrong level would carry a number the use case it serves may not, or hide a product from the baseline every variant is compared against.";
812
+ attribute predicateExpression = "(conformsTo(ClinicalWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(ClinicalUseCase))) or (conformsTo(SystemWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(SystemUseCase)))";
813
+ constraint { true }
814
+ }
815
+ #EnforcesClause dependency from WorkflowOwnsNoStepsOutsideScenariosRule to iec62366_1::iec62366_1Clause5::iec62366_1Clause5_4;
792
816
  }
@@ -0,0 +1,25 @@
1
+ package memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint {
2
+ private import ScalarValues::*;
3
+
4
+ private import memo_viewpoints_definitions::*;
5
+ private import memo_core_enumerations::*;
6
+ private import memo_viewpoints_stakeholders_concerns::*;
7
+
8
+ private import memo_core_common::*;
9
+ private import memo_core_common::MemoIdentity;
10
+ viewpoint clinicalWorkflowViewpoint : MemoViewpoint {
11
+ @MemoIdentity { :>> providedId = "VP-CLINWF"; :>> label = "ClinicalWorkflowViewpoint"; }
12
+ @MemoIdentity { :>> shortDescription = "Shows clinical use cases, workflows and scenarios: what must happen to the patient, with no product and no number."; }
13
+ doc /* Level 1 of the operational levels: the clinical use cases, their workflows and scenarios, and the steps the care team performs. It names no product and carries no number; the system workflows that refine it are the Operational viewpoint's. Not the Clinical viewpoint, which presents clinical evidence. */
14
+ attribute :>> purpose = "Communicate the clinical baseline every system variant is compared against.";
15
+ ref :>> memoStakeholders = (clinicalEngineer, systemArchitect);
16
+ attribute :>> stage = WorkflowStageKind::context;
17
+ attribute :>> abstractionLevel = "clinical";
18
+ attribute :>> outputKind = (ViewOutputKind::diagram);
19
+ attribute :>> presentationKind = (PresentationKind::activityDiagram);
20
+ ref :>> framedConcerns = (safetyConcern, clinicalConcern);
21
+ attribute :>> explorerLane = "architecture";
22
+ attribute :>> explorerOrder = 0;
23
+ attribute :>> userExtensible = true;
24
+ }
25
+ }
@@ -133,6 +133,8 @@ package memo_viewpoints_definitions_layout {
133
133
  attribute labelVisible : Boolean[0..1];
134
134
  attribute lineStyle : MemoLayoutLineStyle[0..1];
135
135
  attribute route : Real[0..*] ordered;
136
+ /** A short token for the connector's ends, so a route is kept only while it still joins what it was drawn between. */
137
+ attribute attachment : String[0..1];
136
138
  attribute sourceElement : String[0..1];
137
139
  attribute targetElement : String[0..1];
138
140
  attribute sourcePortId : String[0..1];