@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.
- package/README.md +1 -1
- package/examples/gastric-bypass-variants/model/catalog/gastric_bypass_variants.sysml +17 -17
- package/examples/gpca-pump/model/catalog/gpca_operational.sysml +6 -12
- package/examples/reusable-instrument/model/catalog/reusable_instrument.sysml +2 -2
- package/examples/robot-cell-family/model/catalog/sos/chains.sysml +1 -1
- package/examples/robot-cell-family/model/catalog/sos/use_cases.sysml +1 -1
- package/examples/robot-cell-family/model/catalog/systems/manipulation/manipulation_system.sysml +1 -1
- package/examples/robot-cell-family/model/catalog/systems/navigation/navigation_system.sysml +1 -1
- package/examples/robot-cell-family/model/catalog/systems/perception/perception_system.sysml +1 -1
- package/examples/surgical-closure-workflow/model/catalog/surgical_closure_workflow.sysml +2 -2
- package/examples/sysml-diagram-samples/model/catalog/samples/browser_view.sysml +3 -3
- package/examples/sysml-diagram-samples/model/catalog/samples/use_case_view.sysml +5 -5
- package/examples/temperature-alarm/model/catalog/temperature_alarm.sysml +1 -1
- package/extensions/aadl/memo.package.yaml +1 -1
- package/extensions/anatomy/memo.package.yaml +1 -1
- package/extensions/clinical/memo.package.yaml +1 -1
- package/extensions/cloud/memo.package.yaml +1 -1
- package/extensions/container/memo.package.yaml +1 -1
- package/extensions/messaging/memo.package.yaml +1 -1
- package/extensions/ros/memo.package.yaml +1 -1
- package/methodologies/default/memo.package.yaml +1 -1
- package/methodologies/gpca/memo.package.yaml +1 -1
- package/ontology/memo.package.yaml +1 -1
- package/package.json +1 -1
- package/profile/memo.package.yaml +1 -1
- package/src/architecture/functional/functions/memo_functions.sysml +6 -1
- package/src/architecture/operational/rollups/memo_rollups.sysml +3 -3
- package/src/architecture/operational/use_cases/memo_use_cases.sysml +4 -4
- package/src/architecture/operational/workflows/memo_workflows.sysml +15 -16
- package/src/artifacts/templates/dhf/21cfr820/user-needs.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/summative-eval.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/ue-plan.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/urra.md +1 -1
- package/src/artifacts/templates/dhf/iec-62366/use-spec.md +1 -1
- package/src/assurance/requirements/needs/memo_needs.sysml +1 -1
- package/src/core/enumerations/memo_enumerations.sysml +10 -0
- package/src/core/relationships/memo_workspace_membership.sysml +4 -1
- package/src/methodology/profiles/memo_profiles.sysml +628 -73
- package/src/methodology/workflow/memo_workflow.sysml +57 -7
- package/src/rules/ontology/ontology_invariants.sysml +56 -12
- package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml +28 -28
- package/src/viewpoints/clinical_workflow/clinical_workflow_viewpoint.sysml +1 -1
- package/src/viewpoints/context/context_viewpoint.sysml +1 -1
- package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml +1 -1
- package/src/viewpoints/definitions/memo_view_layout.sysml +19 -0
- package/src/viewpoints/functional/functional_viewpoint.sysml +1 -1
- package/src/viewpoints/logical/logical_viewpoint.sysml +1 -1
- package/src/viewpoints/operational/operational_viewpoint.sysml +1 -1
- package/src/viewpoints/physical/physical_viewpoint.sysml +1 -1
- package/src/viewpoints/requirements/requirements_viewpoint.sysml +1 -1
- package/src/viewpoints/risk/risk_viewpoint.sysml +1 -1
- package/src/viewpoints/software/software_viewpoint.sysml +1 -1
- package/src/viewpoints/usability/usability_viewpoint.sysml +1 -1
- package/src/viewpoints/verification/verification_viewpoint.sysml +1 -1
- package/stage1/opensysml-ad5ae1d762e9e7107282daa2.json.gz +0 -0
- package/stage1/syside-ff96456991e9f3c2ca352a54.ids.gz +0 -0
- package/stage1/syside-ff96456991e9f3c2ca352a54.json.gz +0 -0
- package/stage1/opensysml-38b58af8f1ce330053e05f1e.json.gz +0 -0
- package/stage1/syside-ca5c563522d5f99a57a61152.ids.gz +0 -0
- package/stage1/syside-ca5c563522d5f99a57a61152.json.gz +0 -0
|
@@ -21,13 +21,18 @@ package memo_methodology_workflow {
|
|
|
21
21
|
// order and says which step feeds which; it never holds a step back. Teams work
|
|
22
22
|
// each layer independently and link their work as the other side appears.
|
|
23
23
|
//
|
|
24
|
-
// What makes a step DONE is stated, not assumed, in two parts
|
|
25
|
-
//
|
|
26
|
-
// every
|
|
27
|
-
//
|
|
28
|
-
// rule
|
|
29
|
-
//
|
|
30
|
-
//
|
|
24
|
+
// What makes a step DONE is stated, not assumed, in two parts
|
|
25
|
+
// judged apart:
|
|
26
|
+
// own work every `outputKinds` kind has an element in the workspace, and every
|
|
27
|
+
// rule the step `#DoneWhen`s has a subject there and no finding on it;
|
|
28
|
+
// links every rule the step `#LinkedWhen`s has no finding. A link rule with
|
|
29
|
+
// no subject yet waits for the step that produces its subjects: that
|
|
30
|
+
// is another team's work, not this one's.
|
|
31
|
+
// A step that states none of these has no done criterion and is never reported as done.
|
|
32
|
+
//
|
|
33
|
+
// A step is read by people as its `@MemoIdentity` label, a verb phrase ("Connect the components");
|
|
34
|
+
// `objectiveDescription` says how it is done and `exitCriteria` when. Its row on the method map is
|
|
35
|
+
// the `MethodLayer` that names its `stage`.
|
|
31
36
|
action def MethodologyWorkflowStep :> MemoAction {
|
|
32
37
|
@MemoIdentity { :>> label = "Methodology workflow step"; }
|
|
33
38
|
attribute stage : WorkflowStageKind;
|
|
@@ -47,6 +52,51 @@ package memo_methodology_workflow {
|
|
|
47
52
|
ref guideViewpoint : MemoViewpoint[0..1];
|
|
48
53
|
}
|
|
49
54
|
|
|
55
|
+
// A row of the method map: a layer of the architecture, or an assurance discipline. Its label is
|
|
56
|
+
// what the map calls it ("Logical"), its doc the question it answers ("How the system will work").
|
|
57
|
+
// Rows are listed in the order the methodology declares them, each side apart. A row holds the steps
|
|
58
|
+
// whose `stage` it names, at whichever level is being worked, numbered in the methodology's order: a
|
|
59
|
+
// step names its stage, never its row, so the grouping has one authority. The row's viewpoints are
|
|
60
|
+
// the ones its views are made in, in the order they are offered.
|
|
61
|
+
enum def MethodTaskKind {
|
|
62
|
+
enum decomposition;
|
|
63
|
+
enum sequence;
|
|
64
|
+
enum realization;
|
|
65
|
+
}
|
|
66
|
+
part def MethodWorkTask :> MemoPart {
|
|
67
|
+
attribute taskKind : MethodTaskKind;
|
|
68
|
+
attribute primary : Boolean;
|
|
69
|
+
attribute taskSubjectKind : String;
|
|
70
|
+
attribute taskReferenceKind : String[0..1];
|
|
71
|
+
attribute taskLevel : String[0..1];
|
|
72
|
+
attribute taskWorkflowKind : String[0..1];
|
|
73
|
+
attribute taskScenarioKind : String[0..1];
|
|
74
|
+
attribute taskStepKind : String[0..1];
|
|
75
|
+
attribute taskImplementationKind : String[0..1];
|
|
76
|
+
attribute taskAllocationKind : String[0..1];
|
|
77
|
+
attribute taskRelationshipKind : String[0..1];
|
|
78
|
+
attribute objectiveDescription : String;
|
|
79
|
+
attribute reviewDescription : String;
|
|
80
|
+
ref taskViewpoint : MemoViewpoint[0..1];
|
|
81
|
+
}
|
|
82
|
+
|
|
83
|
+
part def MethodLayer :> MemoPart {
|
|
84
|
+
attribute workbench : String[0..1];
|
|
85
|
+
ref workTasks : MethodWorkTask[0..*];
|
|
86
|
+
attribute axis : MethodAxisKind;
|
|
87
|
+
attribute stages : WorkflowStageKind[1..*];
|
|
88
|
+
ref layerViewpoints : MemoViewpoint[0..*];
|
|
89
|
+
// Kinds worked in this row, including their specializations; independent of step completion criteria.
|
|
90
|
+
attribute elementKinds : String[0..*];
|
|
91
|
+
// For a discipline: the standard it is worked to, as the map writes it ("ISO 14971").
|
|
92
|
+
attribute standardReference : String[0..1];
|
|
93
|
+
// For a discipline: how its work links to the layers, as one line.
|
|
94
|
+
attribute linkDescription : String[0..1];
|
|
95
|
+
// True when its work often exists already in another tool and is imported (CSV, ReqIF), per system;
|
|
96
|
+
// a re-import flags the links to review.
|
|
97
|
+
attribute importable : Boolean[0..1];
|
|
98
|
+
}
|
|
99
|
+
|
|
50
100
|
metadata def DoneWhen :> MemoTypedDependency {
|
|
51
101
|
doc /* `#DoneWhen dependency from <step> to <rule>, <rule>;` The step's own work is done when each of these rules has a subject in the workspace and no finding on it. */
|
|
52
102
|
@MemoIdentity { :>> label = "Done when"; }
|
|
@@ -6,8 +6,8 @@
|
|
|
6
6
|
//
|
|
7
7
|
// Operational levels (CR-ONT-093..103). A use case and a workflow are each
|
|
8
8
|
// declared at a level by their type: `ClinicalUseCase` and `ClinicalWorkflow`
|
|
9
|
-
// are level 1 (clinical, no product, no number), `
|
|
10
|
-
// `
|
|
9
|
+
// are level 1 (clinical, no product, no number), `OperationalUseCase` and
|
|
10
|
+
// `OperationalWorkflow` level 2 (one variant of a platform, which carries every
|
|
11
11
|
// number). 093 keeps a use case's type and subject in agreement, 103 a
|
|
12
12
|
// workflow's type and the use case it `realizesUseCase`. The level of a step is
|
|
13
13
|
// the type of the workflow it sits in, reached from the step by `composes` (a
|
|
@@ -55,9 +55,53 @@ package memo_rules_ontology {
|
|
|
55
55
|
attribute predicateExpression = "allOfKind('System')->exists(isDefinition == 'true')";
|
|
56
56
|
constraint { true }
|
|
57
57
|
}
|
|
58
|
+
// ─── Where systems are declared ─────────────────────────────
|
|
59
|
+
//
|
|
60
|
+
// A model's systems are its products, and a workspace starts at a system's definition. All of
|
|
61
|
+
// them are defined in one package, so one file lists every product and system of systems the
|
|
62
|
+
// model has. A package is declared in exactly one file, so comparing packages compares files.
|
|
63
|
+
// Their usages, subsystems, components and connections stay in the packages that describe them.
|
|
64
|
+
// The System and SystemOfSystems extents are compared separately: both kinds specialize
|
|
65
|
+
// LogicalComponent, so neither extent holds the other. A usage carries no `isDefinition`, so
|
|
66
|
+
// the test is `!= 'true'`, never `== 'false'`.
|
|
67
|
+
constraint def SystemDefinitionsInOnePackageRule :> MemoConsistencyRule {
|
|
68
|
+
@MemoIdentity { :>> providedId = "CR-ONT-106"; }
|
|
69
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
70
|
+
attribute domain = RuleDomainKind::modelling;
|
|
71
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
72
|
+
attribute appliesTo = "System";
|
|
73
|
+
attribute severity = RuleSeverityKind::warning;
|
|
74
|
+
attribute rationaleText = "Every System and SystemOfSystems definition of a model is declared in one package, so one file lists the products the model describes. Usages, subsystems, components and connections stay in the packages that describe them and import that package.";
|
|
75
|
+
attribute predicateExpression = "isDefinition != 'true' or (allOfKind('System')->forAll(isDefinition != 'true' or package == subject.package) and allOfKind('SystemOfSystems')->forAll(isDefinition != 'true' or package == subject.package))";
|
|
76
|
+
constraint { true }
|
|
77
|
+
}
|
|
78
|
+
// A usage typed by the System or SystemOfSystems kind itself states a system the model never
|
|
79
|
+
// defines. It is valid SysML, but no workspace starts at it and nothing else can be typed by it.
|
|
80
|
+
constraint def SystemUsageHasDefinitionRule :> MemoConsistencyRule {
|
|
81
|
+
@MemoIdentity { :>> providedId = "CR-ONT-107"; }
|
|
82
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
83
|
+
attribute domain = RuleDomainKind::modelling;
|
|
84
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
85
|
+
attribute appliesTo = "System";
|
|
86
|
+
attribute severity = RuleSeverityKind::warning;
|
|
87
|
+
attribute rationaleText = "A system is defined before it is used: a part typed by System itself names a product the model never defines, so no workspace starts at it. Declare a part def that specializes System and type the usage by it.";
|
|
88
|
+
attribute predicateExpression = "isDefinition == 'true' or usageType != 'System'";
|
|
89
|
+
constraint { true }
|
|
90
|
+
}
|
|
91
|
+
constraint def SystemOfSystemsUsageHasDefinitionRule :> MemoConsistencyRule {
|
|
92
|
+
@MemoIdentity { :>> providedId = "CR-ONT-108"; }
|
|
93
|
+
attribute tailoring = RuleTailoringKind::methodology;
|
|
94
|
+
attribute domain = RuleDomainKind::modelling;
|
|
95
|
+
attribute obligation = RuleObligationKind::recommended;
|
|
96
|
+
attribute appliesTo = "SystemOfSystems";
|
|
97
|
+
attribute severity = RuleSeverityKind::warning;
|
|
98
|
+
attribute rationaleText = "A system of systems is defined before it is used: a part typed by SystemOfSystems itself names a system of systems the model never defines, so no workspace starts at it. Declare a part def that specializes SystemOfSystems and type the usage by it.";
|
|
99
|
+
attribute predicateExpression = "isDefinition == 'true' or usageType != 'SystemOfSystems'";
|
|
100
|
+
constraint { true }
|
|
101
|
+
}
|
|
58
102
|
// ─── Use case scope ─────────────────────────────────────────
|
|
59
103
|
//
|
|
60
|
-
// The level of a use case is its declared type (`ClinicalUseCase`, `
|
|
104
|
+
// The level of a use case is its declared type (`ClinicalUseCase`, `OperationalUseCase`), and
|
|
61
105
|
// CR-ONT-093 keeps it in agreement with the subject (`hasSubject`). Rule 085 reads the subject
|
|
62
106
|
// for what it says about composition, not for the level. A use case with no subject
|
|
63
107
|
// is judged by no rule on the subject.
|
|
@@ -699,8 +743,8 @@ package memo_rules_ontology {
|
|
|
699
743
|
attribute obligation = RuleObligationKind::recommended;
|
|
700
744
|
attribute appliesTo = "UseCase";
|
|
701
745
|
attribute severity = RuleSeverityKind::error;
|
|
702
|
-
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,
|
|
703
|
-
attribute predicateExpression = "(conformsTo(ClinicalUseCase) and downstream(hasSubject)->forAll(conformsTo(OperationalEntity))) or (conformsTo(
|
|
746
|
+
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, an operational 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.";
|
|
747
|
+
attribute predicateExpression = "(conformsTo(ClinicalUseCase) and downstream(hasSubject)->forAll(conformsTo(OperationalEntity))) or (conformsTo(OperationalUseCase) and downstream(hasSubject)->forAll(conformsTo(System) or conformsTo(SystemOfSystems)))";
|
|
704
748
|
constraint { true }
|
|
705
749
|
}
|
|
706
750
|
constraint def LevelOneStepCarriesNoNumberRule :> MemoConsistencyRule {
|
|
@@ -722,7 +766,7 @@ package memo_rules_ontology {
|
|
|
722
766
|
attribute appliesTo = "OperativeAction";
|
|
723
767
|
attribute severity = RuleSeverityKind::error;
|
|
724
768
|
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.";
|
|
725
|
-
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(
|
|
769
|
+
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(OperationalWorkflow)) or upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow))) or upstream(composes)->exists(upstream(performs)->exists(upstream(composes)->exists(conformsTo(OperationalWorkflow)))))";
|
|
726
770
|
constraint { true }
|
|
727
771
|
}
|
|
728
772
|
constraint def InternalSystemActivityPerformsAFunctionRule :> MemoConsistencyRule {
|
|
@@ -774,7 +818,7 @@ package memo_rules_ontology {
|
|
|
774
818
|
attribute tailoring = RuleTailoringKind::invariant;
|
|
775
819
|
attribute domain = RuleDomainKind::modelling;
|
|
776
820
|
attribute obligation = RuleObligationKind::recommended;
|
|
777
|
-
attribute appliesTo = "
|
|
821
|
+
attribute appliesTo = "Workflow";
|
|
778
822
|
attribute severity = RuleSeverityKind::error;
|
|
779
823
|
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.";
|
|
780
824
|
attribute predicateExpression = "attributes.perProcedureCost == '' or not(conformsTo(ClinicalWorkflow))";
|
|
@@ -785,7 +829,7 @@ package memo_rules_ontology {
|
|
|
785
829
|
attribute tailoring = RuleTailoringKind::methodology;
|
|
786
830
|
attribute domain = RuleDomainKind::modelling;
|
|
787
831
|
attribute obligation = RuleObligationKind::recommended;
|
|
788
|
-
attribute appliesTo = "
|
|
832
|
+
attribute appliesTo = "Workflow";
|
|
789
833
|
attribute severity = RuleSeverityKind::error;
|
|
790
834
|
attribute rationaleText = "Every alternative of a trade study refines every level-1 step that any alternative of it refines, whether its activities are nested in its scenarios or performed by them. An alternative with a step missing reads as zero time and zero cost for it, so the study would prefer it for doing less.";
|
|
791
835
|
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))))))))";
|
|
@@ -799,7 +843,7 @@ package memo_rules_ontology {
|
|
|
799
843
|
attribute appliesTo = "OperativeAction";
|
|
800
844
|
attribute severity = RuleSeverityKind::error;
|
|
801
845
|
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.";
|
|
802
|
-
attribute predicateExpression = "not(upstream(composes)->exists(conformsTo(
|
|
846
|
+
attribute predicateExpression = "not(upstream(composes)->exists(conformsTo(Workflow))) or upstream(composes)->exists(conformsTo(OperativeScenario))";
|
|
803
847
|
constraint { true }
|
|
804
848
|
}
|
|
805
849
|
constraint def WorkflowRealizesUseCaseOfItsLevelRule :> MemoConsistencyRule {
|
|
@@ -807,10 +851,10 @@ package memo_rules_ontology {
|
|
|
807
851
|
attribute tailoring = RuleTailoringKind::methodology;
|
|
808
852
|
attribute domain = RuleDomainKind::modelling;
|
|
809
853
|
attribute obligation = RuleObligationKind::recommended;
|
|
810
|
-
attribute appliesTo = "
|
|
854
|
+
attribute appliesTo = "Workflow";
|
|
811
855
|
attribute severity = RuleSeverityKind::error;
|
|
812
|
-
attribute rationaleText = "A workflow is the analysis of a use case and is at its level: a clinical workflow realizes a clinical use case,
|
|
813
|
-
attribute predicateExpression = "(conformsTo(ClinicalWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(ClinicalUseCase))) or (conformsTo(
|
|
856
|
+
attribute rationaleText = "A workflow is the analysis of a use case and is at its level: a clinical workflow realizes a clinical use case, an operational workflow an operational 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.";
|
|
857
|
+
attribute predicateExpression = "(conformsTo(ClinicalWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(ClinicalUseCase))) or (conformsTo(OperationalWorkflow) and downstream(realizesUseCase)->forAll(conformsTo(OperationalUseCase)))";
|
|
814
858
|
constraint { true }
|
|
815
859
|
}
|
|
816
860
|
#EnforcesClause dependency from WorkflowOwnsNoStepsOutsideScenariosRule to iec62366_1::iec62366_1Clause5::iec62366_1Clause5_4;
|
|
@@ -14,138 +14,138 @@ package memo_viewpoints_catalog {
|
|
|
14
14
|
|
|
15
15
|
// ── Content and context ─────────────────────────────────────
|
|
16
16
|
viewpoint vpModelContent : MemoViewpoint {
|
|
17
|
-
@MemoIdentity { :>> providedId = "VP-CAT-001"; :>> label = "
|
|
17
|
+
@MemoIdentity { :>> providedId = "VP-CAT-001"; :>> label = "Model content"; }
|
|
18
18
|
attribute :>> purpose = "Browse the model tree and package structure.";
|
|
19
19
|
attribute :>> defaultViewKind = DiagramViewKind::browser;
|
|
20
20
|
}
|
|
21
21
|
viewpoint vpSystemContext : MemoViewpoint {
|
|
22
|
-
@MemoIdentity { :>> providedId = "VP-CAT-002"; :>> label = "
|
|
22
|
+
@MemoIdentity { :>> providedId = "VP-CAT-002"; :>> label = "System context"; }
|
|
23
23
|
attribute :>> purpose = "System of interest, actors, external systems, and context exchanges.";
|
|
24
24
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
25
25
|
}
|
|
26
26
|
// ── Operational world ───────────────────────────────────────
|
|
27
27
|
viewpoint vpUseCase : MemoViewpoint {
|
|
28
|
-
@MemoIdentity { :>> providedId = "VP-CAT-003"; :>> label = "
|
|
28
|
+
@MemoIdentity { :>> providedId = "VP-CAT-003"; :>> label = "Use case"; }
|
|
29
29
|
attribute :>> purpose = "Use cases, initiating users, supporting actors, and motivating needs.";
|
|
30
30
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
31
31
|
}
|
|
32
32
|
viewpoint vpClinicalWorkflow : MemoViewpoint {
|
|
33
|
-
@MemoIdentity { :>> providedId = "VP-CAT-004"; :>> label = "
|
|
33
|
+
@MemoIdentity { :>> providedId = "VP-CAT-004"; :>> label = "Clinical workflow"; }
|
|
34
34
|
attribute :>> purpose = "Workflow steps, decisions, parallel work, handoffs, and roles.";
|
|
35
35
|
attribute :>> defaultViewKind = DiagramViewKind::actionflow;
|
|
36
36
|
}
|
|
37
37
|
viewpoint vpScenario : MemoViewpoint {
|
|
38
|
-
@MemoIdentity { :>> providedId = "VP-CAT-005"; :>> label = "
|
|
38
|
+
@MemoIdentity { :>> providedId = "VP-CAT-005"; :>> label = "Scenario"; }
|
|
39
39
|
attribute :>> purpose = "Selected paths through workflows: variants, conditions, variation points.";
|
|
40
40
|
attribute :>> defaultViewKind = DiagramViewKind::actionflow;
|
|
41
41
|
}
|
|
42
42
|
// ── Functional ──────────────────────────────────────────────
|
|
43
43
|
viewpoint vpFunctionalArchitecture : MemoViewpoint {
|
|
44
|
-
@MemoIdentity { :>> providedId = "VP-CAT-006"; :>> label = "
|
|
44
|
+
@MemoIdentity { :>> providedId = "VP-CAT-006"; :>> label = "Functional architecture"; }
|
|
45
45
|
attribute :>> purpose = "System functions, capabilities, and functional exchanges.";
|
|
46
46
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
47
47
|
}
|
|
48
48
|
viewpoint vpFunctionalFlow : MemoViewpoint {
|
|
49
|
-
@MemoIdentity { :>> providedId = "VP-CAT-007"; :>> label = "
|
|
49
|
+
@MemoIdentity { :>> providedId = "VP-CAT-007"; :>> label = "Functional flow"; }
|
|
50
50
|
attribute :>> purpose = "Ordered functional flows and their steps.";
|
|
51
51
|
attribute :>> defaultViewKind = DiagramViewKind::actionflow;
|
|
52
52
|
}
|
|
53
53
|
// ── Logical ─────────────────────────────────────────────────
|
|
54
54
|
viewpoint vpLogicalArchitecture : MemoViewpoint {
|
|
55
|
-
@MemoIdentity { :>> providedId = "VP-CAT-008"; :>> label = "
|
|
55
|
+
@MemoIdentity { :>> providedId = "VP-CAT-008"; :>> label = "Logical architecture"; }
|
|
56
56
|
attribute :>> purpose = "Logical components, channels, and allocations.";
|
|
57
57
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
58
58
|
}
|
|
59
59
|
viewpoint vpSystemDecomposition : MemoViewpoint {
|
|
60
|
-
@MemoIdentity { :>> providedId = "VP-CAT-009"; :>> label = "
|
|
60
|
+
@MemoIdentity { :>> providedId = "VP-CAT-009"; :>> label = "System decomposition"; }
|
|
61
61
|
attribute :>> purpose = "Composition hierarchy of the system of interest.";
|
|
62
62
|
attribute :>> defaultViewKind = DiagramViewKind::browser;
|
|
63
63
|
}
|
|
64
64
|
viewpoint vpInternalInterconnection : MemoViewpoint {
|
|
65
|
-
@MemoIdentity { :>> providedId = "VP-CAT-010"; :>> label = "
|
|
65
|
+
@MemoIdentity { :>> providedId = "VP-CAT-010"; :>> label = "Internal interconnection"; }
|
|
66
66
|
attribute :>> purpose = "Ports, connectors, and exchanges inside a component boundary.";
|
|
67
67
|
attribute :>> defaultViewKind = DiagramViewKind::interconnection;
|
|
68
68
|
}
|
|
69
69
|
// ── Implementation ──────────────────────────────────────────
|
|
70
70
|
viewpoint vpSoftwareModule : MemoViewpoint {
|
|
71
|
-
@MemoIdentity { :>> providedId = "VP-CAT-011"; :>> label = "
|
|
71
|
+
@MemoIdentity { :>> providedId = "VP-CAT-011"; :>> label = "Software module"; }
|
|
72
72
|
attribute :>> purpose = "IEC 62304 module structure: systems, items, units, SOUP.";
|
|
73
73
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
74
74
|
}
|
|
75
75
|
viewpoint vpSoftwareComponents : MemoViewpoint {
|
|
76
|
-
@MemoIdentity { :>> providedId = "VP-CAT-012"; :>> label = "
|
|
76
|
+
@MemoIdentity { :>> providedId = "VP-CAT-012"; :>> label = "Software components"; }
|
|
77
77
|
attribute :>> purpose = "Runtime component-and-connector structure with concurrency and scheduling.";
|
|
78
78
|
attribute :>> defaultViewKind = DiagramViewKind::interconnection;
|
|
79
79
|
}
|
|
80
80
|
viewpoint vpHardwareArchitecture : MemoViewpoint {
|
|
81
|
-
@MemoIdentity { :>> providedId = "VP-CAT-013"; :>> label = "
|
|
81
|
+
@MemoIdentity { :>> providedId = "VP-CAT-013"; :>> label = "Hardware architecture"; }
|
|
82
82
|
attribute :>> purpose = "Electronic/electrical structure and processing platform.";
|
|
83
83
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
84
84
|
}
|
|
85
85
|
viewpoint vpPhysicalArchitecture : MemoViewpoint {
|
|
86
|
-
@MemoIdentity { :>> providedId = "VP-CAT-014"; :>> label = "
|
|
86
|
+
@MemoIdentity { :>> providedId = "VP-CAT-014"; :>> label = "Physical architecture"; }
|
|
87
87
|
attribute :>> purpose = "Mechanical, fluidic, optical, and other physical realization.";
|
|
88
88
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
89
89
|
}
|
|
90
90
|
viewpoint vpDeviceComposition : MemoViewpoint {
|
|
91
|
-
@MemoIdentity { :>> providedId = "VP-CAT-015"; :>> label = "
|
|
91
|
+
@MemoIdentity { :>> providedId = "VP-CAT-015"; :>> label = "Device composition"; }
|
|
92
92
|
attribute :>> purpose = "Device definitions, instances, accessories, and consumables.";
|
|
93
93
|
attribute :>> defaultViewKind = DiagramViewKind::browser;
|
|
94
94
|
}
|
|
95
95
|
viewpoint vpNetworkDeployment : MemoViewpoint {
|
|
96
|
-
@MemoIdentity { :>> providedId = "VP-CAT-016"; :>> label = "
|
|
96
|
+
@MemoIdentity { :>> providedId = "VP-CAT-016"; :>> label = "Network deployment"; }
|
|
97
97
|
attribute :>> purpose = "Deployment units on processing nodes and network topology.";
|
|
98
98
|
attribute :>> defaultViewKind = DiagramViewKind::interconnection;
|
|
99
99
|
}
|
|
100
100
|
// ── Interaction and behavior ────────────────────────────────
|
|
101
101
|
viewpoint vpUiFlow : MemoViewpoint {
|
|
102
|
-
@MemoIdentity { :>> providedId = "VP-CAT-017"; :>> label = "
|
|
102
|
+
@MemoIdentity { :>> providedId = "VP-CAT-017"; :>> label = "UI flow"; }
|
|
103
103
|
attribute :>> purpose = "Interaction flows, UI states, and transitions.";
|
|
104
104
|
attribute :>> defaultViewKind = DiagramViewKind::statetransition;
|
|
105
105
|
}
|
|
106
106
|
viewpoint vpStateMode : MemoViewpoint {
|
|
107
|
-
@MemoIdentity { :>> providedId = "VP-CAT-018"; :>> label = "
|
|
107
|
+
@MemoIdentity { :>> providedId = "VP-CAT-018"; :>> label = "State and mode"; }
|
|
108
108
|
attribute :>> purpose = "System states, device modes, and transitions.";
|
|
109
109
|
attribute :>> defaultViewKind = DiagramViewKind::statetransition;
|
|
110
110
|
}
|
|
111
111
|
viewpoint vpSequenceInteraction : MemoViewpoint {
|
|
112
|
-
@MemoIdentity { :>> providedId = "VP-CAT-019"; :>> label = "
|
|
112
|
+
@MemoIdentity { :>> providedId = "VP-CAT-019"; :>> label = "Sequence interaction"; }
|
|
113
113
|
attribute :>> purpose = "Ordered message exchanges between participants in a scenario.";
|
|
114
114
|
attribute :>> defaultViewKind = DiagramViewKind::sequence;
|
|
115
115
|
}
|
|
116
116
|
// ── Assurance ───────────────────────────────────────────────
|
|
117
117
|
viewpoint vpRequirementsTraceability : MemoViewpoint {
|
|
118
|
-
@MemoIdentity { :>> providedId = "VP-CAT-020"; :>> label = "
|
|
118
|
+
@MemoIdentity { :>> providedId = "VP-CAT-020"; :>> label = "Requirements traceability"; }
|
|
119
119
|
attribute :>> purpose = "Needs → requirements → architecture → verification trace matrix.";
|
|
120
120
|
attribute :>> defaultViewKind = DiagramViewKind::grid;
|
|
121
121
|
}
|
|
122
122
|
viewpoint vpRiskChain : MemoViewpoint {
|
|
123
|
-
@MemoIdentity { :>> providedId = "VP-CAT-021"; :>> label = "
|
|
123
|
+
@MemoIdentity { :>> providedId = "VP-CAT-021"; :>> label = "Risk chain"; }
|
|
124
124
|
attribute :>> purpose = "ISO 14971 chain: hazard → hazardous situation → harm with controls.";
|
|
125
125
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
126
126
|
}
|
|
127
127
|
viewpoint vpCybersecurity : MemoViewpoint {
|
|
128
|
-
@MemoIdentity { :>> providedId = "VP-CAT-022"; :>> label = "
|
|
128
|
+
@MemoIdentity { :>> providedId = "VP-CAT-022"; :>> label = "Cybersecurity"; }
|
|
129
129
|
attribute :>> purpose = "Assets, threats, trust boundaries, and security controls.";
|
|
130
130
|
attribute :>> defaultViewKind = DiagramViewKind::general;
|
|
131
131
|
}
|
|
132
132
|
viewpoint vpHumanFactors : MemoViewpoint {
|
|
133
|
-
@MemoIdentity { :>> providedId = "VP-CAT-023"; :>> label = "
|
|
133
|
+
@MemoIdentity { :>> providedId = "VP-CAT-023"; :>> label = "Human factors"; }
|
|
134
134
|
attribute :>> purpose = "Users, tasks, use errors, and hazard-related use scenarios.";
|
|
135
135
|
attribute :>> defaultViewKind = DiagramViewKind::grid;
|
|
136
136
|
}
|
|
137
137
|
viewpoint vpVerificationCoverage : MemoViewpoint {
|
|
138
|
-
@MemoIdentity { :>> providedId = "VP-CAT-024"; :>> label = "
|
|
138
|
+
@MemoIdentity { :>> providedId = "VP-CAT-024"; :>> label = "Verification coverage"; }
|
|
139
139
|
attribute :>> purpose = "Verification cases against requirements and functions.";
|
|
140
140
|
attribute :>> defaultViewKind = DiagramViewKind::grid;
|
|
141
141
|
}
|
|
142
142
|
viewpoint vpValidationCoverage : MemoViewpoint {
|
|
143
|
-
@MemoIdentity { :>> providedId = "VP-CAT-025"; :>> label = "
|
|
143
|
+
@MemoIdentity { :>> providedId = "VP-CAT-025"; :>> label = "Validation coverage"; }
|
|
144
144
|
attribute :>> purpose = "Validation cases against use cases and critical tasks.";
|
|
145
145
|
attribute :>> defaultViewKind = DiagramViewKind::grid;
|
|
146
146
|
}
|
|
147
147
|
viewpoint vpEvidenceTraceability : MemoViewpoint {
|
|
148
|
-
@MemoIdentity { :>> providedId = "VP-CAT-026"; :>> label = "
|
|
148
|
+
@MemoIdentity { :>> providedId = "VP-CAT-026"; :>> label = "Evidence traceability"; }
|
|
149
149
|
attribute :>> purpose = "Evidence records back to the cases and elements they support.";
|
|
150
150
|
attribute :>> defaultViewKind = DiagramViewKind::grid;
|
|
151
151
|
}
|
|
@@ -154,14 +154,14 @@ package memo_viewpoints_catalog {
|
|
|
154
154
|
// SoftwareComponents realizing a functional OperativeScenario. The viewpoint is the
|
|
155
155
|
// reusable spec; the diagram of a specific model is the view.
|
|
156
156
|
viewpoint vpSoftwareSequence : MemoViewpoint {
|
|
157
|
-
@MemoIdentity { :>> providedId = "VP-CAT-027"; :>> label = "
|
|
157
|
+
@MemoIdentity { :>> providedId = "VP-CAT-027"; :>> label = "Software sequence"; }
|
|
158
158
|
attribute :>> purpose = "Runtime message ordering between software components along a functional scenario.";
|
|
159
159
|
attribute :>> defaultViewKind = DiagramViewKind::sequence;
|
|
160
160
|
}
|
|
161
161
|
// The first cataloged viewpoint to resolve to `geometry`: screen regions
|
|
162
162
|
// carry authored RegionBounds, so a geometry view draws modelled facts.
|
|
163
163
|
viewpoint vpUILayout : MemoViewpoint {
|
|
164
|
-
@MemoIdentity { :>> providedId = "VP-CAT-028"; :>> label = "
|
|
164
|
+
@MemoIdentity { :>> providedId = "VP-CAT-028"; :>> label = "UI layout"; }
|
|
165
165
|
attribute :>> purpose = "Captured screens with their marked regions and the UI elements those regions present.";
|
|
166
166
|
attribute :>> defaultViewKind = DiagramViewKind::geometry;
|
|
167
167
|
}
|
|
@@ -8,7 +8,7 @@ package memo_viewpoints_clinical_workflow_clinical_workflow_viewpoint {
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint clinicalWorkflowViewpoint : MemoViewpoint {
|
|
10
10
|
@MemoIdentity { :>> providedId = "VP-CLINWF"; :>> label = "ClinicalWorkflowViewpoint"; }
|
|
11
|
-
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
|
|
11
|
+
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 operational workflows that realize it are the Operational viewpoint's. Not the Clinical viewpoint, which presents clinical evidence. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows clinical use cases, workflows and scenarios: what must happen to the patient, with no product and no number."; }
|
|
13
13
|
attribute :>> purpose = "Communicate the clinical baseline every system variant is compared against.";
|
|
14
14
|
ref :>> memoStakeholders = (clinicalEngineer, systemArchitect);
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_context_context_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint contextViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-CTX"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-CTX"; :>> label = "Context views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the context layer to communicate who interacts with the device, under which use conditions, and where trust or safety boundaries exist. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use context, and system boundary."; }
|
|
13
13
|
attribute :>> purpose = "Communicate operational context and boundaries.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint cybersecurityViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-CYB"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-CYB"; :>> label = "Cybersecurity views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the cybersecurity layer, using STRIDE-style threat categories by default while allowing safety and privacy impacts to be traced into the broader model. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows assets, trust boundaries, threats, vulnerabilities, cyber hazards, cyber risks, and mitigations."; }
|
|
13
13
|
attribute :>> purpose = "Communicate cybersecurity design, threat analysis, and cyber risk posture.";
|
|
@@ -44,6 +44,12 @@ package memo_viewpoints_definitions_layout {
|
|
|
44
44
|
enum bottom;
|
|
45
45
|
}
|
|
46
46
|
|
|
47
|
+
/** Which way a label's text runs: across the page, or turned a quarter to read bottom to top. */
|
|
48
|
+
enum def MemoLayoutTextOrientation {
|
|
49
|
+
enum horizontal;
|
|
50
|
+
enum vertical;
|
|
51
|
+
}
|
|
52
|
+
|
|
47
53
|
/** The view-wide choices. One per view, absent when the view keeps every default. */
|
|
48
54
|
metadata def MemoLayout {
|
|
49
55
|
:> annotatedElement : SysML::ViewUsage;
|
|
@@ -98,6 +104,7 @@ package memo_viewpoints_definitions_layout {
|
|
|
98
104
|
attribute fontWeight : Real[0..1];
|
|
99
105
|
attribute textAlign : MemoLayoutAlign[0..1];
|
|
100
106
|
attribute verticalAlign : MemoLayoutVerticalAlign[0..1];
|
|
107
|
+
attribute textOrientation : MemoLayoutTextOrientation[0..1];
|
|
101
108
|
attribute opacity : Real[0..1];
|
|
102
109
|
}
|
|
103
110
|
|
|
@@ -113,6 +120,11 @@ package memo_viewpoints_definitions_layout {
|
|
|
113
120
|
/** A port nested in a port: how far along its parent, and whether it faces out. */
|
|
114
121
|
attribute alongOffset : Real[0..1];
|
|
115
122
|
attribute faceOuter : Boolean[0..1];
|
|
123
|
+
/** How the port's name is drawn. */
|
|
124
|
+
attribute textColor : String[0..1];
|
|
125
|
+
attribute fontSize : Real[0..1];
|
|
126
|
+
attribute fontWeight : Real[0..1];
|
|
127
|
+
attribute textOrientation : MemoLayoutTextOrientation[0..1];
|
|
116
128
|
}
|
|
117
129
|
|
|
118
130
|
/**
|
|
@@ -159,6 +171,13 @@ package memo_viewpoints_definitions_layout {
|
|
|
159
171
|
/** Where the connector's label sits, on the board. */
|
|
160
172
|
attribute labelX : Real[0..1];
|
|
161
173
|
attribute labelY : Real[0..1];
|
|
174
|
+
/** True once a person has placed the label, so routing leaves it where they put it. */
|
|
175
|
+
attribute manualLabel : Boolean[0..1];
|
|
176
|
+
/** How the connector's label is drawn. */
|
|
177
|
+
attribute textColor : String[0..1];
|
|
178
|
+
attribute fontSize : Real[0..1];
|
|
179
|
+
attribute fontWeight : Real[0..1];
|
|
180
|
+
attribute textOrientation : MemoLayoutTextOrientation[0..1];
|
|
162
181
|
/** Where each end leaves its box, relative to the box, and on which wall. */
|
|
163
182
|
attribute sourceOffsetX : Real[0..1];
|
|
164
183
|
attribute sourceOffsetY : Real[0..1];
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_functional_functional_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint functionalViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-FUNC"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-FUNC"; :>> label = "Functional views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the functions layer for what the system does, independent of how it is structured — function trees, function allocation, and behavior triggers. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows system functions, their decomposition, and allocation."; }
|
|
13
13
|
attribute :>> purpose = "Describe the system's functional decomposition and behavior.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_logical_logical_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint logicalArchitectureViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-LOG"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-LOG"; :>> label = "Logical architecture views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the logical architecture layer for subsystem structure, responsibilities, and major interactions, independent of physical realization. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows logical decomposition and interfaces."; }
|
|
13
13
|
attribute :>> purpose = "Describe the system's logical decomposition.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_operational_operational_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint operationalViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-OPS"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-OPS"; :>> label = "Operational views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the context, operational, and system layers for how actors use the device — operational scenarios, capabilities, and the functional chains that realize them. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows actors, use contexts, operational scenarios, and system capabilities."; }
|
|
13
13
|
attribute :>> purpose = "Communicate how actors interact with the system and which capabilities they invoke.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_physical_physical_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint physicalViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-PHY"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-PHY"; :>> label = "Physical views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the physical and hardware structure layers for bill-of-materials, hardware decomposition, physical interfaces, and network/connectivity topology. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows physical components, hardware structure, and their interconnections."; }
|
|
13
13
|
attribute :>> purpose = "Describe the system's physical realization and interconnections.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_requirements_requirements_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint requirementsViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-REQ"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-REQ"; :>> label = "Requirements views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the requirements layer for requirements traceability — the chain from stakeholder need through system, software, and hardware requirements, supporting IEC 62304 §5.1.1 and ISO 13485 §7.3.3. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows stakeholder needs and their decomposition into system, software, and hardware requirements."; }
|
|
13
13
|
attribute :>> purpose = "Communicate requirements decomposition and traceability.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_risk_risk_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint riskViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-RISK"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-RISK"; :>> label = "Risk views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the risk layer for ISO 14971-style reasoning across hazard, hazardous situation, harm, control, and verification evidence. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows hazards, risks, controls, and assurance links."; }
|
|
13
13
|
attribute :>> purpose = "Communicate safety risk chains and controls.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_software_software_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint softwareViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-SW"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-SW"; :>> label = "Software views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the software structure layer for IEC 62304 software architecture description — software item decomposition, SOUP inventory, and software-to-software interfaces, distinct from system-level logical decomposition. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows software systems, components, SOUP, and software interfaces."; }
|
|
13
13
|
attribute :>> purpose = "Describe the software architecture for IEC 62304 design documentation.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_usability_usability_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint usabilityViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-USE"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-USE"; :>> label = "Human factors views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the context and requirements layers for IEC 62366-1 usability engineering — actors, use contexts, identified use errors, and requirements tagged with the usability concern. Reuses existing context-layer elements (Actor, UseContext, UseError) rather than a separate usability layer. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements."; }
|
|
13
13
|
attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
|
|
@@ -7,7 +7,7 @@ package memo_viewpoints_verification_verification_viewpoint {
|
|
|
7
7
|
|
|
8
8
|
private import memo_core_common::*;
|
|
9
9
|
viewpoint verificationViewpoint : MemoViewpoint {
|
|
10
|
-
@MemoIdentity { :>> providedId = "VP-VER"; :>> label = "
|
|
10
|
+
@MemoIdentity { :>> providedId = "VP-VER"; :>> label = "Verification views"; }
|
|
11
11
|
doc /* Default viewpoint derived from the requirements and assurance layers for V&V coverage — which requirements are verified/validated, by which case, and what evidence was produced, supporting ISO 13485 §7.3.6/§7.3.7 and IEC 62304 §5.7/§5.8. */
|
|
12
12
|
@MemoIdentity { :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements."; }
|
|
13
13
|
attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
Binary file
|