@memoarchitect/ontology 0.22.0 → 0.23.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (60) hide show
  1. package/README.md +1 -1
  2. package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +17 -17
  3. package/examples/gpca-pump/model/catalog/gpca_operational.sysml +6 -12
  4. package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +2 -2
  5. package/examples/robot-cell-family/model/catalog/sos/chains.sysml +1 -1
  6. package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +1 -1
  7. package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +1 -1
  8. package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +1 -1
  9. package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +1 -1
  10. package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +2 -2
  11. package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +3 -3
  12. package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +5 -5
  13. package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +1 -1
  14. package/extensions/aadl/memo.package.yaml +1 -1
  15. package/extensions/anatomy/memo.package.yaml +1 -1
  16. package/extensions/clinical/memo.package.yaml +1 -1
  17. package/extensions/cloud/memo.package.yaml +1 -1
  18. package/extensions/container/memo.package.yaml +1 -1
  19. package/extensions/messaging/memo.package.yaml +1 -1
  20. package/extensions/ros/memo.package.yaml +1 -1
  21. package/methodologies/default/memo.package.yaml +1 -1
  22. package/methodologies/gpca/memo.package.yaml +1 -1
  23. package/ontology/memo.package.yaml +1 -1
  24. package/package.json +1 -1
  25. package/profile/memo.package.yaml +1 -1
  26. package/src/architecture/functional/functions/memo_functions.sysml +6 -1
  27. package/src/architecture/operational/rollups/memo_rollups.sysml +3 -3
  28. package/src/architecture/operational/use_cases/memo_use_cases.sysml +4 -4
  29. package/src/architecture/operational/workflows/memo_workflows.sysml +15 -16
  30. package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
  31. package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
  32. package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
  33. package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
  34. package/src/artifacts/templates/dhf/iec-62366/use-spec.md +1 -1
  35. package/src/assurance/requirements/needs/memo_needs.sysml +1 -1
  36. package/src/core/enumerations/memo_enumerations.sysml +10 -0
  37. package/src/core/relationships/memo_workspace_membership.sysml +4 -1
  38. package/src/methodology/profiles/memo_profiles.sysml +628 -73
  39. package/src/methodology/workflow/memo_workflow.sysml +57 -7
  40. package/src/rules/ontology/ontology_invariants.sysml +56 -12
  41. package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +28 -28
  42. package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +1 -1
  43. package/src/viewpoints/context/context_viewpoint.sysml +1 -1
  44. package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +1 -1
  45. package/src/viewpoints/definitions/memo_view_layout.sysml +19 -0
  46. package/src/viewpoints/functional/functional_viewpoint.sysml +1 -1
  47. package/src/viewpoints/logical/logical_viewpoint.sysml +1 -1
  48. package/src/viewpoints/operational/operational_viewpoint.sysml +1 -1
  49. package/src/viewpoints/physical/physical_viewpoint.sysml +1 -1
  50. package/src/viewpoints/requirements/requirements_viewpoint.sysml +1 -1
  51. package/src/viewpoints/risk/risk_viewpoint.sysml +1 -1
  52. package/src/viewpoints/software/software_viewpoint.sysml +1 -1
  53. package/src/viewpoints/usability/usability_viewpoint.sysml +1 -1
  54. package/src/viewpoints/verification/verification_viewpoint.sysml +1 -1
  55. package/stage1/opensysml-ad5ae1d762e9e7107282daa2.json.gz +0 -0
  56. package/stage1/syside-ff96456991e9f3c2ca352a54.ids.gz +0 -0
  57. package/stage1/syside-ff96456991e9f3c2ca352a54.json.gz +0 -0
  58. package/stage1/opensysml-38b58af8f1ce330053e05f1e.json.gz +0 -0
  59. package/stage1/syside-ca5c563522d5f99a57a61152.ids.gz +0 -0
  60. package/stage1/syside-ca5c563522d5f99a57a61152.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.22.0
28
+ pnpm add @memoarchitect/ontology@0.23.0
29
29
  ```
30
30
 
31
31
  > **Pre-1.0 notice:** ontology names, relationships, and package layout may
@@ -67,10 +67,10 @@ package memo_examples_gastric_bypass_variants {
67
67
  }
68
68
  part wfRouxEnY : ClinicalProcedureWorkflow {
69
69
  @MemoIdentity { :>> label = "Clinical workflow: Roux-en-Y gastric bypass"; }
70
- attribute :>> entryCondition = "patient prepared; time-out complete";
71
- attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
72
70
  action scNominal : OperativeScenario {
73
71
  @MemoIdentity { :>> label = "Nominal path"; }
72
+ attribute :>> postCondition = "pouch and anastomosis created and leak-tested";
73
+ attribute :>> preCondition = "patient prepared; time-out complete";
74
74
  action establishAccess : EstablishPneumoperitoneumAndAccess {
75
75
  @MemoIdentity { :>> label = "Establish access"; }
76
76
  }
@@ -171,15 +171,13 @@ package memo_examples_gastric_bypass_variants {
171
171
  allocate fnFireStapler to platform.ourRobot;
172
172
 
173
173
  // ── Tier 2: the system workflow, laparoscopic ──────────────────────
174
- use case ucRouxEnYLap : SystemUseCase {
174
+ use case ucRouxEnYLap : OperationalUseCase {
175
175
  attribute :>> useCaseKind = UseCaseKind::care;
176
176
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (laparoscopic)"; }
177
177
  subject :>> supportingSystem = platform.laparoscopicTower;
178
178
  }
179
- part wfRouxEnYLap : SystemWorkflow {
179
+ part wfRouxEnYLap : OperationalWorkflow {
180
180
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (laparoscopic)"; }
181
- attribute :>> entryCondition = "patient prepared; time-out complete";
182
- attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
183
181
  attribute :>> perProcedureCost = 450 [EUR];
184
182
  part staplerLap : Stapler {
185
183
  @MemoIdentity { :>> label = "Stapler (laparoscopic)"; }
@@ -188,6 +186,8 @@ package memo_examples_gastric_bypass_variants {
188
186
  }
189
187
  action scLapNominal : OperativeScenario {
190
188
  @MemoIdentity { :>> label = "Nominal path (laparoscopic)"; }
189
+ attribute :>> postCondition = "pouch and anastomosis created and leak-tested";
190
+ attribute :>> preCondition = "patient prepared; time-out complete";
191
191
  action establishAccess : EstablishPneumoperitoneumAndAccess {
192
192
  @MemoIdentity { :>> label = "Establish access"; }
193
193
  attribute :>> expectedDuration = 20 [min];
@@ -236,15 +236,13 @@ package memo_examples_gastric_bypass_variants {
236
236
  #refinement dependency wfRouxEnYLap::scLapConversion::convertToOpen to wfRouxEnY::scConversion::convertToOpen;
237
237
 
238
238
  // ── Tier 2: the system workflow, our robot ──────────────────────
239
- use case ucRouxEnYOur : SystemUseCase {
239
+ use case ucRouxEnYOur : OperationalUseCase {
240
240
  attribute :>> useCaseKind = UseCaseKind::care;
241
241
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (our robot)"; }
242
242
  subject :>> supportingSystem = platform.ourRobot;
243
243
  }
244
- part wfRouxEnYOur : SystemWorkflow {
244
+ part wfRouxEnYOur : OperationalWorkflow {
245
245
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (our robot)"; }
246
- attribute :>> entryCondition = "patient prepared; time-out complete";
247
- attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
248
246
  attribute :>> perProcedureCost = 900 [EUR];
249
247
  part staplerOur : Stapler {
250
248
  @MemoIdentity { :>> label = "Stapler (our robot)"; }
@@ -253,6 +251,8 @@ package memo_examples_gastric_bypass_variants {
253
251
  }
254
252
  action scOurNominal : OperativeScenario {
255
253
  @MemoIdentity { :>> label = "Nominal path (our robot)"; }
254
+ attribute :>> postCondition = "pouch and anastomosis created and leak-tested";
255
+ attribute :>> preCondition = "patient prepared; time-out complete";
256
256
  action establishAccess : EstablishPneumoperitoneumAndAccess {
257
257
  @MemoIdentity { :>> label = "Establish access"; }
258
258
  attribute :>> expectedDuration = 30 [min];
@@ -306,15 +306,13 @@ package memo_examples_gastric_bypass_variants {
306
306
  #refinement dependency wfRouxEnYOur::scOurConversion::convertToOpen to wfRouxEnY::scConversion::convertToOpen;
307
307
 
308
308
  // ── Tier 2: the system workflow, competitor robot ──────────────────────
309
- use case ucRouxEnYCmp : SystemUseCase {
309
+ use case ucRouxEnYCmp : OperationalUseCase {
310
310
  attribute :>> useCaseKind = UseCaseKind::care;
311
311
  @MemoIdentity { :>> label = "Perform Roux-en-Y gastric bypass (competitor robot)"; }
312
312
  subject :>> supportingSystem = platform.competitorRobot;
313
313
  }
314
- part wfRouxEnYCmp : SystemWorkflow {
314
+ part wfRouxEnYCmp : OperationalWorkflow {
315
315
  @MemoIdentity { :>> label = "System workflow: Roux-en-Y gastric bypass (competitor robot)"; }
316
- attribute :>> entryCondition = "patient prepared; time-out complete";
317
- attribute :>> completionCondition = "pouch and anastomosis created and leak-tested";
318
316
  attribute :>> perProcedureCost = 1100 [EUR];
319
317
  part staplerCmp : Stapler {
320
318
  @MemoIdentity { :>> label = "Stapler (competitor robot)"; }
@@ -323,6 +321,8 @@ package memo_examples_gastric_bypass_variants {
323
321
  }
324
322
  action scCmpNominal : OperativeScenario {
325
323
  @MemoIdentity { :>> label = "Nominal path (competitor robot)"; }
324
+ attribute :>> postCondition = "pouch and anastomosis created and leak-tested";
325
+ attribute :>> preCondition = "patient prepared; time-out complete";
326
326
  action establishAccess : EstablishPneumoperitoneumAndAccess {
327
327
  @MemoIdentity { :>> label = "Establish access"; }
328
328
  attribute :>> expectedDuration = 35 [min];
@@ -386,17 +386,17 @@ package memo_examples_gastric_bypass_variants {
386
386
  // procedure, which the roll-up derives from the activities' times, the resources' rates and the
387
387
  // alternate scenarios' likelihoods. The lowest wins.
388
388
  analysis bypassTradeStudy : TradeStudy {
389
- subject : OperationalWorkflow = (wfRouxEnYLap, wfRouxEnYOur, wfRouxEnYCmp);
389
+ subject : Workflow = (wfRouxEnYLap, wfRouxEnYOur, wfRouxEnYCmp);
390
390
  objective : MinimizeObjective;
391
391
 
392
392
  calc :>> evaluationFunction {
393
- in part aWorkflow :>> alternative : OperationalWorkflow;
393
+ in part aWorkflow :>> alternative : Workflow;
394
394
 
395
395
  calc procedureCost : ProcedureCost { in workflow = aWorkflow; return cost; }
396
396
 
397
397
  return :>> result : Real = procedureCost.cost.num;
398
398
  }
399
399
 
400
- return part :>> selectedAlternative : OperationalWorkflow;
400
+ return part :>> selectedAlternative : Workflow;
401
401
  }
402
402
  }
@@ -6,6 +6,7 @@ package memo_examples_gpca_pump_gpca_operational {
6
6
  private import memo_examples_gpca_pump_gpca_context::*;
7
7
  private import memo_examples_gpca_pump_gpca_system::*;
8
8
  private import memo_examples_gpca_pump_gpca_behavior_subsystems::*;
9
+ private import memo_examples_gpca_pump_gpca_architecture::gpcaPump;
9
10
 
10
11
  // ── Operational entities beyond the human actors ────────────
11
12
  part entityPharmacy : OperationalEntity {
@@ -136,14 +137,14 @@ package memo_examples_gpca_pump_gpca_operational {
136
137
  // The use case is the patient and clinician goal. It is supported by
137
138
  // several workflows, each of which owns multiple selected scenarios.
138
139
  // --8<-- [start:use-case]
139
- use case ucDeliverPcaTherapy : SystemUseCase {
140
+ use case ucDeliverPcaTherapy : OperationalUseCase {
140
141
  attribute :>> useCaseKind = UseCaseKind::care;
141
142
  @MemoIdentity { :>> providedId = "UC-001"; :>> label = "Deliver patient controlled analgesia"; }
142
143
  attribute :>> goalStatement = "Deliver prescribed analgesia safely while allowing patient-controlled bolus requests within configured limits.";
143
144
  attribute :>> trigger = "A clinician starts prescribed patient-controlled analgesia therapy.";
144
145
  attribute :>> successOutcome = "The patient receives prescribed analgesia without exceeding dose, lockout, or safety limits.";
145
146
  ref :>> useContext = hospitalWardContext;
146
- subject supportingSystem;
147
+ subject :>> supportingSystem = gpcaPump;
147
148
  actor nurseInitiator = actorNurse;
148
149
  actor patientActor = actorPatient;
149
150
  actor prescriberActor = actorPrescriber;
@@ -151,16 +152,11 @@ package memo_examples_gpca_pump_gpca_operational {
151
152
  }
152
153
  // --8<-- [end:use-case]
153
154
 
154
- part wfPrepareAndStartTherapy : SystemWorkflow {
155
+ part wfPrepareAndStartTherapy : OperationalWorkflow {
155
156
  @MemoIdentity { :>> label = "Prepare and start therapy"; }
156
- attribute :>> entryCondition = "A valid prescription and prepared reservoir are available.";
157
- attribute :>> completionCondition = "Therapy is started with confirmed prescription limits.";
158
-
159
157
  }
160
- part wfManageActiveTherapy : SystemWorkflow {
158
+ part wfManageActiveTherapy : OperationalWorkflow {
161
159
  @MemoIdentity { :>> label = "Manage active therapy"; }
162
- attribute :>> entryCondition = "Basal therapy is active.";
163
- attribute :>> completionCondition = "A bolus is handled or active therapy continues safely.";
164
160
  action osNominalTherapy : OperativeScenario {
165
161
  @MemoIdentity { :>> providedId = "OS-001"; :>> label = "Nominal therapy session"; }
166
162
  attribute :>> preCondition = "prescription issued, reservoir loaded";
@@ -191,10 +187,8 @@ package memo_examples_gpca_pump_gpca_operational {
191
187
  }
192
188
  // --8<-- [end:lockout-scenario]
193
189
  }
194
- part wfRespondToTherapyAlarm : SystemWorkflow {
190
+ part wfRespondToTherapyAlarm : OperationalWorkflow {
195
191
  @MemoIdentity { :>> label = "Respond to therapy alarm"; }
196
- attribute :>> entryCondition = "A therapy alarm or degraded condition is detected.";
197
- attribute :>> completionCondition = "The pump is safe and the clinician has resolved or escalated the condition.";
198
192
 
199
193
  action osOcclusionAlarm : OperativeScenario {
200
194
  attribute :>> scenarioKind = ScenarioKind::alternate;
@@ -31,10 +31,10 @@ package memo_examples_reusable_instrument {
31
31
  // --8<-- [start:workflow]
32
32
  part wfReprocess : ClinicalWorkflow {
33
33
  @MemoIdentity { :>> providedId = "RI-WF-001"; :>> label = "Instrument reprocessing workflow"; }
34
- attribute :>> entryCondition = "used instrument received in decontamination";
35
- attribute :>> completionCondition = "sterile pack released to storage";
36
34
  action scNominalCycle : OperativeScenario {
37
35
  @MemoIdentity { :>> providedId = "RI-SC-001"; :>> label = "Nominal reprocessing cycle"; }
36
+ attribute :>> postCondition = "sterile pack released to storage";
37
+ attribute :>> preCondition = "used instrument received in decontamination";
38
38
 
39
39
  perform actClean;
40
40
  perform actInspect;
@@ -10,7 +10,7 @@ package robot_cell_family_sos_chains {
10
10
  private import robot_cell_family_systems_manipulation_manipulation_system::*;
11
11
  private import robot_cell_family_systems_perception_perception_system::*;
12
12
 
13
- part wfMapGuidedPick : SystemWorkflow {
13
+ part wfMapGuidedPick : OperationalWorkflow {
14
14
  @MemoIdentity { :>> providedId = "RCF-FC-001"; :>> label = "Map-Guided Pick"; }
15
15
  doc /* Point clouds acquired by the perception system build the occupancy map; each grasp by the manipulator is tagged on that map. */
16
16
  action scMapGuidedPick : OperativeScenario {
@@ -8,7 +8,7 @@ package robot_cell_family_sos_use_cases {
8
8
  private import robot_cell_family_systems_manipulation_manipulation_system::*;
9
9
  private import robot_cell_family_systems_perception_perception_system::*;
10
10
 
11
- use case ucPerformPickAndPlace : SystemUseCase {
11
+ use case ucPerformPickAndPlace : OperationalUseCase {
12
12
  @MemoIdentity { :>> providedId = "RCF-UC-001"; :>> label = "Perform Pick And Place"; }
13
13
  attribute :>> useCaseKind = UseCaseKind::care;
14
14
  attribute :>> goalStatement = "Move a workpiece by mapping the cell and grasping it.";
@@ -29,7 +29,7 @@ package robot_cell_family_systems_manipulation_manipulation_system {
29
29
  attribute :>> outputDescription = "Grasp made within the set force and time limits, and the event that records it";
30
30
  }
31
31
 
32
- use case ucExecuteGrasp : SystemUseCase {
32
+ use case ucExecuteGrasp : OperationalUseCase {
33
33
  @MemoIdentity { :>> providedId = "RCF-MAN-UC-001"; :>> label = "Execute Grasp"; }
34
34
  attribute :>> useCaseKind = UseCaseKind::care;
35
35
  subject :>> supportingSystem : ManipulatorSystem;
@@ -37,7 +37,7 @@ package robot_cell_family_systems_navigation_navigation_system {
37
37
  }
38
38
 
39
39
  // A system use case: its subject is this system.
40
- use case ucAcquireMap : SystemUseCase {
40
+ use case ucAcquireMap : OperationalUseCase {
41
41
  @MemoIdentity { :>> providedId = "RCF-NAV-UC-001"; :>> label = "Acquire Occupancy Map"; }
42
42
  attribute :>> useCaseKind = UseCaseKind::care;
43
43
  subject :>> supportingSystem : NavigationSystem;
@@ -28,7 +28,7 @@ package robot_cell_family_systems_perception_perception_system {
28
28
  attribute :>> outputDescription = "Filtered, timestamped point clouds";
29
29
  }
30
30
 
31
- use case ucRecordRun : SystemUseCase {
31
+ use case ucRecordRun : OperationalUseCase {
32
32
  @MemoIdentity { :>> providedId = "RCF-PER-UC-001"; :>> label = "Record Run Data"; }
33
33
  attribute :>> useCaseKind = UseCaseKind::care;
34
34
  subject :>> supportingSystem : PerceptionSystem;
@@ -87,11 +87,11 @@ package memo_examples_surgical_closure_workflow {
87
87
  // --8<-- [start:workflow]
88
88
  part wfSleeveGastrectomy : ClinicalProcedureWorkflow {
89
89
  @MemoIdentity { :>> providedId = "LSG-WF-001"; :>> label = "Laparoscopic sleeve gastrectomy workflow"; }
90
- attribute :>> entryCondition = "patient prepared; time-out ready";
91
- attribute :>> completionCondition = "staple line assessed; postoperative handover complete";
92
90
  attribute :>> clinicalObjective = "create a gastric sleeve after controlled mobilisation and staple-line assessment";
93
91
  action scNominalSleeveProcedure : OperativeScenario {
94
92
  @MemoIdentity { :>> providedId = "LSG-SC-001"; :>> label = "Nominal sleeve gastrectomy"; }
93
+ attribute :>> postCondition = "staple line assessed; postoperative handover complete";
94
+ attribute :>> preCondition = "patient prepared; time-out ready";
95
95
  attribute :>> pathSummary = "Time-out, access, mobilisation, sleeve creation, staple-line assessment, closure, and handover complete without rework.";
96
96
 
97
97
  perform actTimeOutAndPosition;
@@ -34,19 +34,19 @@ package memo_examples_sysml_diagram_samples_samples_browser_view {
34
34
  @MemoIdentity { :>> label = "Remote Monitor"; }
35
35
  }
36
36
 
37
- use case startSystem : SystemUseCase {
37
+ use case startSystem : OperationalUseCase {
38
38
  @MemoIdentity { :>> providedId = "UC-BRW-1"; :>> label = "Start System"; }
39
39
  attribute :>> useCaseKind = UseCaseKind::care;
40
40
  subject controlSystem;
41
41
  actor operatorActor = systemOperator;
42
42
  }
43
- use case runDiagnostics : SystemUseCase {
43
+ use case runDiagnostics : OperationalUseCase {
44
44
  @MemoIdentity { :>> providedId = "UC-BRW-2"; :>> label = "Run Diagnostics"; }
45
45
  attribute :>> useCaseKind = UseCaseKind::service;
46
46
  subject controlSystem;
47
47
  actor engineerActor = maintenanceEngineer;
48
48
  }
49
- use case monitorStatus : SystemUseCase {
49
+ use case monitorStatus : OperationalUseCase {
50
50
  @MemoIdentity { :>> providedId = "UC-BRW-3"; :>> label = "Monitor Status"; }
51
51
  attribute :>> useCaseKind = UseCaseKind::care;
52
52
  subject controlSystem;
@@ -27,14 +27,14 @@ package memo_examples_sysml_diagram_samples_samples_use_case_view {
27
27
  @MemoIdentity { :>> label = "Nursing Staff"; }
28
28
  }
29
29
 
30
- use case reviewStatus : SystemUseCase {
30
+ use case reviewStatus : OperationalUseCase {
31
31
  @MemoIdentity { :>> providedId = "UC-SAMPLE-1"; :>> label = "Review Device Status"; }
32
32
  attribute :>> useCaseKind = UseCaseKind::care;
33
33
  include validateTherapySettings;
34
34
  subject supportingSystem;
35
35
  actor patientActor = patient;
36
36
  }
37
- use case configureTherapy : SystemUseCase {
37
+ use case configureTherapy : OperationalUseCase {
38
38
  @MemoIdentity { :>> providedId = "UC-SAMPLE-2"; :>> label = "Configure Therapy"; }
39
39
  attribute :>> useCaseKind = UseCaseKind::care;
40
40
  include reviewStatus;
@@ -42,20 +42,20 @@ package memo_examples_sysml_diagram_samples_samples_use_case_view {
42
42
  actor clinicianInitiator = clinician;
43
43
  actor patientActor = patient;
44
44
  }
45
- use case maintainDevice : SystemUseCase {
45
+ use case maintainDevice : OperationalUseCase {
46
46
  @MemoIdentity { :>> providedId = "UC-SAMPLE-3"; :>> label = "Maintain Device"; }
47
47
  attribute :>> useCaseKind = UseCaseKind::service;
48
48
  subject supportingSystem;
49
49
  actor serviceTechnicianActor = serviceTechnician;
50
50
  }
51
51
 
52
- use case documentTreatment : SystemUseCase {
52
+ use case documentTreatment : OperationalUseCase {
53
53
  @MemoIdentity { :>> providedId = "UC-SAMPLE-4"; :>> label = "Document Treatment"; }
54
54
  attribute :>> useCaseKind = UseCaseKind::care;
55
55
  }
56
56
 
57
57
  // L2 child of Review Device Status: makes L0 → L1 → L2 selectable.
58
- use case validateTherapySettings : SystemUseCase {
58
+ use case validateTherapySettings : OperationalUseCase {
59
59
  @MemoIdentity { :>> providedId = "UC-SAMPLE-5"; :>> label = "Validate Therapy Settings"; }
60
60
  attribute :>> useCaseKind = UseCaseKind::care;
61
61
  subject supportingSystem;
@@ -18,7 +18,7 @@ package memo_examples_temperature_alarm {
18
18
  attribute :>> actorKind = ActorKind::clinician;
19
19
  @MemoIdentity { :>> providedId = "TA-USR-001"; }
20
20
  }
21
- use case ucMonitorTemp : SystemUseCase {
21
+ use case ucMonitorTemp : OperationalUseCase {
22
22
  attribute :>> useCaseKind = UseCaseKind::care;
23
23
  @MemoIdentity { :>> providedId = "TA-UC-001"; :>> label = "Monitor patient temperature"; }
24
24
  attribute :>> goalStatement = "Continuously monitor core temperature and be alerted when it leaves the safe range.";
@@ -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.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
11
11
  description: Example methodology extension for clinical-procedure vocabulary
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-cloud'
10
- version: 0.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
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.22.0
10
+ version: 0.23.0
11
11
  description: "MEMO default medical-device methodology \u2014 selects viewpoints/views/DHF documents from @memoarchitect/ontology and adds rules, gates, patterns, profiles, and workflow."
12
12
  license: MIT
13
13
  tags:
@@ -7,7 +7,7 @@
7
7
  # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
8
8
  # removed at the native semantic flip and are now rejected if present.
9
9
  name: '@memoarchitect/methodology-gpca'
10
- version: 0.22.0
10
+ version: 0.23.0
11
11
  description: "GPCA infusion pump methodology \u2014 subtraction-based tailoring of @memoarchitect/methodology-default for the non-networked prototype variant. Excludes cybersecurity and SOUP."
12
12
  license: MIT
13
13
  tags:
@@ -7,7 +7,7 @@
7
7
  # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
8
8
  # removed at the native semantic flip and are now rejected if present.
9
9
  name: '@memoarchitect/ontology'
10
- version: 0.22.0
10
+ version: 0.23.0
11
11
  description: "MEMO \u2014 the single canonical medical-device ontology: core semantics, the Arcadia-inspired architecture layers (context, requirements, behavior, structure, interfaces, risk, cybersecurity,\
12
12
  \ assurance, \u2026), compliance, viewpoints, views, and invariant rules. One namespace (memo::), one src/ tree."
13
13
  license: MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@memoarchitect/ontology",
3
- "version": "0.22.0",
3
+ "version": "0.23.0",
4
4
  "packageManager": "pnpm@9.15.0",
5
5
  "description": "MEMO — Medical Engineering Modelling Ontology. Pure SysML v2 medical-device ontology with native constraints, portable to any conformant SysML v2 tool (SysIDE, SysON, sysand).",
6
6
  "scripts": {
@@ -7,7 +7,7 @@
7
7
  # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
8
8
  # removed at the native semantic flip and are now rejected if present.
9
9
  name: '@memoarchitect/medical-modeling-profile'
10
- version: 0.22.0
10
+ version: 0.23.0
11
11
  description: Closure rules and viewpoints for medical device modeling
12
12
  license: MIT
13
13
  tags:
@@ -75,6 +75,11 @@ package memo_architecture_functional_functions {
75
75
  private import memo_architecture_operational_activities::*;
76
76
  private import memo_architecture_operational_scenarios::*;
77
77
 
78
+ metadata def FunctionalRoot :> MemoTypedDependency {
79
+ doc /* The single top-level system function of a System or SystemOfSystems. Its native action decomposition describes that system's functional breakdown. */
80
+ @MemoIdentity { :>> label = "Functional root"; }
81
+ }
82
+
78
83
  abstract action def MemoFunction specializes MemoAction, MemoConstrainedOccurrence {
79
84
  @MemoIdentity { :>> label = "Function"; }
80
85
  attribute functionCategory : String;
@@ -135,7 +140,7 @@ package memo_architecture_functional_functions {
135
140
  // flows are part of functional architecture, never logical structure.
136
141
  //
137
142
  // An `action def`, like every other behaviour in MEMO. A route through
138
- // responsibilities is the same shape as the `OperationalWorkflow` and
143
+ // responsibilities is the same shape as the `Workflow` and
139
144
  // `OperativeScenario` it sits beside: the scenarios package calls a
140
145
  // scenario "a selected path through a workflow (or functional flow)",
141
146
  // naming the two as one kind of thing, and its steps are `action def`s
@@ -9,7 +9,7 @@
9
9
  // it. It reads `enclosedPerformances`, which holds a step's composite `subactions`, the activities
10
10
  // it `perform`s by reference (a scenario that performs activities declared once and used in
11
11
  // several), and the `includedUseCases` of a use case, which are `enclosedPerformances` and not
12
- // `subactions`, so a walk over `subactions` alone would miss every reusable system use case. It
12
+ // `subactions`, so a walk over `subactions` alone would miss every reusable operational use case. It
13
13
  // descends only into what can hold activities: an activity, a scenario or a use case. A
14
14
  // `perform` of a `SystemFunction` is therefore never entered, which is the point of the stop:
15
15
  // level 3 is how the system does its share, not more time, and following it would count the
@@ -88,7 +88,7 @@ package memo_architecture_operational_rollups {
88
88
  }
89
89
 
90
90
  calc def ProcedureCost {
91
- in workflow : OperationalWorkflow[1];
91
+ in workflow : Workflow[1];
92
92
  return cost : MoneyValue[1] = QuantityCalculations::sum((
93
93
  workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
94
94
  ->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioCost(s)) as MoneyValue },
@@ -96,7 +96,7 @@ package memo_architecture_operational_rollups {
96
96
  }
97
97
 
98
98
  calc def ProcedureDuration {
99
- in workflow : OperationalWorkflow[1];
99
+ in workflow : Workflow[1];
100
100
  return duration : DurationValue[1] = QuantityCalculations::sum(
101
101
  workflow.ownedActions->select { in s : MemoAction[1]; s istype OperativeScenario }
102
102
  ->collect { in s : OperativeScenario[1]; (ScenarioWeight(s) * ScenarioDuration(s)) as DurationValue });
@@ -3,7 +3,7 @@
3
3
  // manufacturing, and development use cases specialize the same base.
4
4
  //
5
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
+ // `OperationalUseCase`), kept in agreement with its subject by CR-ONT-093.
7
7
  // Level 1 is clinical: the subject is an `OperationalEntity` (the care team, the setting), the
8
8
  // use case names no product, and nothing on its workflow, scenarios or steps carries a number.
9
9
  // Level 2 is a black box: the subject is a `System` or `SystemOfSystems`, one variant of a
@@ -63,14 +63,14 @@ package memo_architecture_operational_use_cases {
63
63
 
64
64
  // The two levels are types, declared and not derived. A clinical use case has an
65
65
  // `OperationalEntity` (the care team, the setting) as its subject, names no product and carries
66
- // no number; a system use case has a `System` or `SystemOfSystems`, one variant of a platform.
66
+ // no number; an operational use case has a `System` or `SystemOfSystems`, one variant of a platform.
67
67
  // CR-ONT-093 keeps the declared type and the subject in agreement. `UseCase` is abstract: a
68
68
  // project states which level each use case is at.
69
69
  use case def ClinicalUseCase :> UseCase {
70
70
  @MemoIdentity { :>> label = "Clinical use case"; }
71
71
  }
72
- use case def SystemUseCase :> UseCase {
73
- @MemoIdentity { :>> label = "System use case"; }
72
+ use case def OperationalUseCase :> UseCase {
73
+ @MemoIdentity { :>> label = "Operational use case"; }
74
74
  }
75
75
 
76
76
  connection def Motivates :> MemoRelationship {
@@ -1,6 +1,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
1
+ // First-class workflows. A use case is the user's goal; a
2
+ // Workflow is the ANALYSIS of one body of work that pursues it: who
3
+ // does it, where, with what equipment, and
4
4
  // conditions, and (from the needs that point at it) what is needed and what
5
5
  // is not yet met. It may exist before any device is selected. It is not a
6
6
  // sequence of steps: the steps are its scenarios' (memo_architecture_operational_scenarios),
@@ -35,12 +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
- abstract part def OperationalWorkflow specializes MemoPart {
39
- @MemoIdentity { :>> label = "Operational workflow"; }
40
- // Where the body of work starts and ends. A scenario's pre- and
41
- // post-conditions are its own path's, inside these.
42
- attribute entryCondition : String;
43
- attribute completionCondition : String;
38
+ abstract part def Workflow specializes MemoPart {
39
+ @MemoIdentity { :>> label = "Workflow"; }
40
+ // A workflow has no pre- or postcondition: where a path starts and ends is its
41
+ // scenario's (`preCondition`, `postCondition`), because each path starts and ends
42
+ // on its own terms.
44
43
  // What one procedure costs apart from its activities (set-up, capital per case); a number,
45
44
  // so it is set on a level-2 variant's workflow, never on level 1.
46
45
  attribute perProcedureCost : MoneyValue[0..1];
@@ -57,13 +56,13 @@ package memo_architecture_operational_workflows {
57
56
  }
58
57
 
59
58
  // A workflow is at the level of the use case it realizes, and says so by its type: a
60
- // `ClinicalWorkflow` realizes a `ClinicalUseCase` (no product, no number); a `SystemWorkflow`
61
- // realizes a `SystemUseCase` (one variant, every number). CR-ONT-103 keeps the two in step.
62
- part def ClinicalWorkflow specializes OperationalWorkflow {
59
+ // `ClinicalWorkflow` realizes a `ClinicalUseCase` (no product, no number); an `OperationalWorkflow`
60
+ // realizes an `OperationalUseCase` (one variant, every number). CR-ONT-103 keeps the two in step.
61
+ part def ClinicalWorkflow specializes Workflow {
63
62
  @MemoIdentity { :>> label = "Clinical workflow"; }
64
63
  }
65
- part def SystemWorkflow specializes OperationalWorkflow {
66
- @MemoIdentity { :>> label = "System workflow"; }
64
+ part def OperationalWorkflow specializes Workflow {
65
+ @MemoIdentity { :>> label = "Operational workflow"; }
67
66
  }
68
67
 
69
68
  // The use case a workflow realizes. Many workflows may trace to one use
@@ -71,7 +70,7 @@ package memo_architecture_operational_workflows {
71
70
  // workflow → use case).
72
71
  connection def RealizesUseCase :> MemoRelationship {
73
72
  @MemoIdentity { :>> label = "Realizes use case"; }
74
- end realizingWorkflow : OperationalWorkflow :>> source;
73
+ end realizingWorkflow : Workflow :>> source;
75
74
  end realizedUseCase : UseCase :>> target;
76
75
  }
77
76
  abstract connection realizesUseCaseLinks : RealizesUseCase[*];
@@ -104,7 +103,7 @@ package memo_architecture_operational_workflows {
104
103
  // ── Workflow-level relationships ─────────────────────────────
105
104
  // An element supports (affords, enables) an action — e.g. a UI element that
106
105
  // affords a user task. Use-case and capability tracing are direct refs
107
- // (OperationalWorkflow.useCase, OperativeAction.contributesToCapabilities),
106
+ // (Workflow.useCase, OperativeAction.contributesToCapabilities),
108
107
  // so this is one plain relation.
109
108
 
110
109
  }
@@ -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: [ClinicalUseCase, SystemUseCase]
48
+ kind: [ClinicalUseCase, OperationalUseCase]
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: [ClinicalUseCase, SystemUseCase, ValidationCase]
34
+ kind: [ClinicalUseCase, OperationalUseCase, ValidationCase]
35
35
  display: table
36
36
  columns: name, layer, doc
37
37
  sort: name