@memoarchitect/ontology 0.12.1 → 0.13.2

package/examples/sysml-diagram-samples/model/catalog/viewpoints/unassigned/views/use_case_view.sysml

@@ -1,4 +1,5 @@
-package diagram_samples {
+package memo_examples_sysml_diagram_samples_viewpoints_unassigned_views_use_case_view {
+    private import memo_examples_sysml_diagram_samples_viewpoints_unassigned::*;
     private import ScalarValues::*;
     private import memo_architecture_operational_context_actors::*;
     private import memo_architecture_operational_use_cases::*;
@@ -89,25 +90,4 @@ package diagram_samples {
     // Status — the general case is browsing status; configuring therapy is a
     // more specific variant.
     connection : Specialization connect configureTherapy to reviewStatus;
-
-    view deviceUseCases : MemoDiagramView {
-        expose patient;
-        expose clinician;
-        expose serviceTechnician;
-        expose nursingStaff;
-        expose reviewStatus;
-        expose configureTherapy;
-        expose maintainDevice;
-        expose documentTreatment;
-        expose validateTherapySettings;
-        @MemoIdentity { :>> shortDescription = "Actors outside a device boundary with include, extend, generalization, hierarchy-level, and orthogonal-routing presentation."; }
-        attribute :>> viewKind = DiagramViewKind::general;
-        attribute :>> diagramType = "ucd";
-        ref :>> viewpointDefinition = useCaseViewpoint;
-        part :>> selectionQuery {
-            attribute :>> includeElementKinds = ("User", "UseCase");
-            attribute :>> includeRelationshipKinds = ("ParticipatesIn", "IncludesStep", "Extends", "Specialization");
-        }
-        attribute :>> layoutHint = "usecase:level=all;edge=rounded";
-    }
 }

package/extensions/aadl/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-aadl'
-version: 0.12.1
+version: 0.13.2
 description: AADL (SAE AS5506) correspondence profile and runtime component families
 license: MIT
 tags:

package/extensions/cloud/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-cloud'
-version: 0.12.1
+version: 0.13.2
 description: Networked services and managed data stores
 license: MIT
 tags:

package/extensions/container/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-container'
-version: 0.12.1
+version: 0.13.2
 description: OCI container images and container runtimes as deployment content
 license: MIT
 tags:

package/extensions/messaging/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-messaging'
-version: 0.12.1
+version: 0.13.2
 description: Publish/subscribe messaging — topics, brokers, and delivery semantics
 license: MIT
 tags:

package/extensions/ros/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/extension-ros'
-version: 0.12.1
+version: 0.13.2
 description: ROS 2 nodes, messages, topic/service/action interfaces, QoS, and containerized deployment
 license: MIT
 tags:

package/methodologies/default/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/methodology-default'
-version: 0.12.1
+version: 0.13.2
 description: "MEMO default medical-device methodology \u2014 selects viewpoints/views/DHF documents from @memoarchitect/ontology and adds rules, gates, patterns, profiles, and workflow."
 license: MIT
 tags:

package/methodologies/gpca/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/methodology-gpca'
-version: 0.12.1
+version: 0.13.2
 description: "GPCA infusion pump methodology \u2014 subtraction-based tailoring of @memoarchitect/methodology-default for the non-networked prototype variant. Excludes cybersecurity and SOUP."
 license: MIT
 tags:

package/ontology/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/ontology'
-version: 0.12.1
+version: 0.13.2
 description: "MEMO \u2014 the single canonical medical-device ontology: core semantics, the Arcadia-inspired architecture layers (context, requirements, behavior, structure, interfaces, risk, cybersecurity,\
   \ assurance, \u2026), compliance, viewpoints, views, and invariant rules. One namespace (memo::), one src/ tree."
 license: MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@memoarchitect/ontology",
-  "version": "0.12.1",
+  "version": "0.13.2",
   "packageManager": "pnpm@9.15.0",
   "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).",
   "scripts": {

package/profile/memo.package.yaml

@@ -7,7 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '@memoarchitect/medical-modeling-profile'
-version: 0.12.1
+version: 0.13.2
 description: Closure rules and viewpoints for medical device modeling
 license: MIT
 tags:

package/src/viewpoints/clinical/clinical_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_clinical_clinical_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows clinical context, users, use environment, and clinical evidence."; }
         attribute :>> description = "Default viewpoint derived from the context and assurance layers for clinical stakeholders — intended use, patient/clinician interaction, clinical evidence, and clinical safety claims.";
         attribute :>> purpose = "Communicate clinical use context and clinical evidence for the device.";
-        ref :>> stakeholders = (ClinicalEngineer, RegulatoryEngineer);
+        ref :>> stakeholders = (clinicalEngineer, regulatoryEngineer);
         attribute :>> stage = WorkflowStageKind::context;
         attribute :>> abstractionLevel = "clinical";
         attribute :>> outputKind = (ViewOutputKind::documentSection, ViewOutputKind::table);
         attribute :>> presentationKind = (PresentationKind::narrativeSection);
-        ref :>> framedConcerns = (SafetyConcern, ClinicalConcern);
+        ref :>> framedConcerns = (safetyConcern, clinicalConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 4;
         attribute :>> userExtensible = true;

package/src/viewpoints/context/context_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_context_context_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows actors, use context, and system boundary."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate operational context and boundaries.";
-        ref :>> stakeholders = (SystemArchitect);
+        ref :>> stakeholders = (systemArchitect);
         attribute :>> stage = WorkflowStageKind::context;
         attribute :>> abstractionLevel = "system";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::blockDiagram);
-        ref :>> framedConcerns = (SafetyConcern, InteroperabilityConcern);
+        ref :>> framedConcerns = (safetyConcern, interoperabilityConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 0;
         // UseEnvironment (IEC 62366-1 3.20) is what the device sits inside —

package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows assets, trust boundaries, threats, vulnerabilities, cyber hazards, cyber risks, and mitigations."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate cybersecurity design, threat analysis, and cyber risk posture.";
-        ref :>> stakeholders = (SecurityEngineer);
+        ref :>> stakeholders = (securityEngineer);
         attribute :>> stage = WorkflowStageKind::risk;
         attribute :>> abstractionLevel = "analysis";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::custom);
-        ref :>> framedConcerns = (CybersecurityConcern, PrivacyConcern, SafetyConcern);
+        ref :>> framedConcerns = (cybersecurityConcern, privacyConcern, safetyConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 3;
         attribute :>> userExtensible = true;

package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml

@@ -37,7 +37,9 @@ package memo_viewpoints_definitions {
          * requirement, and extensible by a project without editing the
          * ontology, which `AudienceKind` and `ConcernKind` were not.
          */
-        ref stakeholders : MemoStakeholder[*];
+        // Redefines the standard library's `RequirementCheck::stakeholders`,
+        // which a viewpoint inherits through `ViewpointCheck`.
+        ref :>> stakeholders : MemoStakeholder[0..*];
         attribute stage : WorkflowStageKind;
         attribute abstractionLevel : String;
         attribute outputKind : ViewOutputKind[*];

package/src/viewpoints/functional/functional_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_functional_functional_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows system functions, their decomposition, and allocation."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Describe the system's functional decomposition and behavior.";
-        ref :>> stakeholders = (SystemArchitect);
+        ref :>> stakeholders = (systemArchitect);
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> abstractionLevel = "functional";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::activityDiagram);
-        ref :>> framedConcerns = (SafetyConcern, PerformanceConcern);
+        ref :>> framedConcerns = (safetyConcern, performanceConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 2;
         attribute :>> userExtensible = true;

package/src/viewpoints/logical/logical_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_logical_logical_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows logical decomposition and interfaces."; }
         attribute :>> description = "Default viewpoint derived from the logical architecture layer for subsystem structure, responsibilities, and major interactions, independent of physical realization.";
         attribute :>> purpose = "Describe the system's logical decomposition.";
-        ref :>> stakeholders = (SystemArchitect);
+        ref :>> stakeholders = (systemArchitect);
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> abstractionLevel = "logical";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::blockDiagram);
-        ref :>> framedConcerns = (SafetyConcern, PerformanceConcern);
+        ref :>> framedConcerns = (safetyConcern, performanceConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 3;
         attribute :>> userExtensible = true;

package/src/viewpoints/operational/operational_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_operational_operational_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows actors, use contexts, operational scenarios, and system capabilities."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate how actors interact with the system and which capabilities they invoke.";
-        ref :>> stakeholders = (ProjectLead, SystemArchitect);
+        ref :>> stakeholders = (projectLead, systemArchitect);
         attribute :>> stage = WorkflowStageKind::context;
         attribute :>> abstractionLevel = "operational";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::custom);
-        ref :>> framedConcerns = (PerformanceConcern, InteroperabilityConcern);
+        ref :>> framedConcerns = (performanceConcern, interoperabilityConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 1;
         attribute :>> userExtensible = true;

package/src/viewpoints/physical/physical_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_physical_physical_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows physical components, hardware structure, and their interconnections."; }
         attribute :>> description = "Default viewpoint derived from the physical and hardware structure layers for bill-of-materials, hardware decomposition, physical interfaces, and network/connectivity topology.";
         attribute :>> purpose = "Describe the system's physical realization and interconnections.";
-        ref :>> stakeholders = (HardwareEngineer);
+        ref :>> stakeholders = (hardwareEngineer);
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> abstractionLevel = "physical";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::blockDiagram);
-        ref :>> framedConcerns = (ReliabilityConcern, InteroperabilityConcern);
+        ref :>> framedConcerns = (reliabilityConcern, interoperabilityConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 5;
         attribute :>> userExtensible = true;

package/src/viewpoints/requirements/requirements_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_requirements_requirements_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows stakeholder needs and their decomposition into system, software, and hardware requirements."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate requirements decomposition and traceability.";
-        ref :>> stakeholders = (RegulatoryEngineer, SystemArchitect);
+        ref :>> stakeholders = (regulatoryEngineer, systemArchitect);
         attribute :>> stage = WorkflowStageKind::requirements;
         attribute :>> abstractionLevel = "requirements";
         attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::matrix);
         attribute :>> presentationKind = (PresentationKind::traceMatrix);
-        ref :>> framedConcerns = (RegulatoryConcern, SafetyConcern);
+        ref :>> framedConcerns = (regulatoryConcern, safetyConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 1;
         attribute :>> userExtensible = true;

package/src/viewpoints/risk/risk_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_risk_risk_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows hazards, risks, controls, and assurance links."; }
         attribute :>> description = "Default viewpoint derived from the risk layer for ISO 14971-style reasoning across hazard, hazardous situation, harm, control, and verification evidence.";
         attribute :>> purpose = "Communicate safety risk chains and controls.";
-        ref :>> stakeholders = (SafetyEngineer);
+        ref :>> stakeholders = (safetyEngineer);
         attribute :>> stage = WorkflowStageKind::risk;
         attribute :>> abstractionLevel = "analysis";
         attribute :>> outputKind = (ViewOutputKind::table);
         attribute :>> presentationKind = (PresentationKind::riskTable);
-        ref :>> framedConcerns = (SafetyConcern, RegulatoryConcern);
+        ref :>> framedConcerns = (safetyConcern, regulatoryConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 2;
         attribute :>> userExtensible = true;

package/src/viewpoints/software/software_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_software_software_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows software systems, components, SOUP, and software interfaces."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Describe the software architecture for IEC 62304 design documentation.";
-        ref :>> stakeholders = (SoftwareArchitect);
+        ref :>> stakeholders = (softwareArchitect);
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> abstractionLevel = "software";
         attribute :>> outputKind = (ViewOutputKind::diagram);
         attribute :>> presentationKind = (PresentationKind::blockDiagram);
-        ref :>> framedConcerns = (SafetyConcern, ReliabilityConcern);
+        ref :>> framedConcerns = (safetyConcern, reliabilityConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 4;
         attribute :>> userExtensible = true;

package/src/viewpoints/{definitions → stakeholders_concerns}/memo_stakeholders_concerns.sysml

@@ -98,43 +98,43 @@ package memo_viewpoints_stakeholders_concerns {
     part def Availability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-1"; }
         attribute :>> name = "Availability";
-        ref :>> addressesConcerns = (SafetyConcern, ReliabilityConcern, ClinicalConcern);
+        ref :>> addressesConcerns = (safetyConcern, reliabilityConcern, clinicalConcern);
         attribute :>> measure = "Proportion of scheduled procedure time the function is delivered, and time to recover after a fault.";
     }
     part def Performance :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-2"; }
         attribute :>> name = "Performance";
-        ref :>> addressesConcerns = (PerformanceConcern, ClinicalConcern);
+        ref :>> addressesConcerns = (performanceConcern, clinicalConcern);
         attribute :>> measure = "Latency and throughput under the arrival pattern the procedure produces.";
     }
     part def Security :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-3"; }
         attribute :>> name = "Security";
-        ref :>> addressesConcerns = (CybersecurityConcern, PrivacyConcern, SafetyConcern);
+        ref :>> addressesConcerns = (cybersecurityConcern, privacyConcern, safetyConcern);
         attribute :>> measure = "Resistance to a stated threat, and time to detect and recover from a compromise.";
     }
     part def Modifiability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-4"; }
         attribute :>> name = "Modifiability";
-        ref :>> addressesConcerns = (RegulatoryConcern);
+        ref :>> addressesConcerns = (regulatoryConcern);
         attribute :>> measure = "Cost and blast radius of a stated change, including the re-verification it forces.";
     }
     part def Testability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-5"; }
         attribute :>> name = "Testability";
-        ref :>> addressesConcerns = (RegulatoryConcern, SafetyConcern);
+        ref :>> addressesConcerns = (regulatoryConcern, safetyConcern);
         attribute :>> measure = "Probability that a fault present is revealed by the next test, and the effort to observe it.";
     }
     part def Usability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-6"; }
         attribute :>> name = "Usability";
-        ref :>> addressesConcerns = (UsabilityConcern, SafetyConcern, ClinicalConcern);
+        ref :>> addressesConcerns = (usabilityConcern, safetyConcern, clinicalConcern);
         attribute :>> measure = "Task success and use-error rate for the intended user under use conditions (IEC 62366-1).";
     }
     part def Interoperability :> MemoQualityAttribute {
         @MemoIdentity { :>> providedId = "QA-7"; }
         attribute :>> name = "Interoperability";
-        ref :>> addressesConcerns = (InteroperabilityConcern, ClinicalConcern);
+        ref :>> addressesConcerns = (interoperabilityConcern, clinicalConcern);
         attribute :>> measure = "Proportion of exchanges with a named partner system that are correctly understood.";
     }
 
@@ -189,4 +189,31 @@ package memo_viewpoints_stakeholders_concerns {
         @MemoIdentity { :>> providedId = "STK-11"; }
         attribute :>> name = "Usability Engineer";
     }
+
+    // ─── The catalog, as usages ─────────────────────────────────────────
+    //
+    // A viewpoint's `stakeholders` and `framedConcerns`, and a quality
+    // attribute's `addressesConcerns`, are features. What a feature is bound to
+    // has to be a feature as well, not a definition, so each concern and each
+    // stakeholder above has exactly one usage for those bindings to name.
+    concern safetyConcern : SafetyConcern;
+    concern usabilityConcern : UsabilityConcern;
+    concern cybersecurityConcern : CybersecurityConcern;
+    concern performanceConcern : PerformanceConcern;
+    concern interoperabilityConcern : InteroperabilityConcern;
+    concern reliabilityConcern : ReliabilityConcern;
+    concern privacyConcern : PrivacyConcern;
+    concern regulatoryConcern : RegulatoryConcern;
+    concern clinicalConcern : ClinicalConcern;
+    part systemArchitect : SystemArchitect;
+    part softwareArchitect : SoftwareArchitect;
+    part hardwareEngineer : HardwareEngineer;
+    part safetyEngineer : SafetyEngineer;
+    part verificationEngineer : VerificationEngineer;
+    part regulatoryEngineer : RegulatoryEngineer;
+    part projectLead : ProjectLead;
+    part securityEngineer : SecurityEngineer;
+    part privacyEngineer : PrivacyEngineer;
+    part clinicalEngineer : ClinicalEngineer;
+    part usabilityEngineer : UsabilityEngineer;
 }

package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows screen captures with the UI element tree laid out over them."; }
         attribute :>> description = "Frames the user interface spatially: a captured rendering of a screen, and the UIElement tree laid out over it by each element's bounds. Supports IEC 62366-1 use-related design review and the UI description in the software design specification, by making 'which control is this, and what does it do' answerable from the picture. There is one tree, not two — the elements carrying the geometry are the same elements carrying the requirements, functions, use errors, and risk controls.";
         attribute :>> purpose = "Review the interface as the user sees it, with every functional area backed by a design record.";
-        ref :>> stakeholders = (UsabilityEngineer, SoftwareArchitect, SafetyEngineer);
+        ref :>> stakeholders = (usabilityEngineer, softwareArchitect, safetyEngineer);
         attribute :>> stage = WorkflowStageKind::architecture;
         attribute :>> abstractionLevel = "implementation";
         attribute :>> outputKind = (ViewOutputKind::diagram, ViewOutputKind::documentSection);
         attribute :>> presentationKind = (PresentationKind::screenLayout);
-        ref :>> framedConcerns = (UsabilityConcern, SafetyConcern);
+        ref :>> framedConcerns = (usabilityConcern, safetyConcern);
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 4;
         attribute :>> defaultViewKind = DiagramViewKind::geometry;

package/src/viewpoints/usability/usability_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_usability_usability_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows use contexts, actors, use errors, and usability requirements."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate use-related hazards and usability requirements for the device.";
-        ref :>> stakeholders = (UsabilityEngineer, SafetyEngineer);
+        ref :>> stakeholders = (usabilityEngineer, safetyEngineer);
         attribute :>> stage = WorkflowStageKind::requirements;
         attribute :>> abstractionLevel = "usability";
         attribute :>> outputKind = (ViewOutputKind::documentSection);
         attribute :>> presentationKind = (PresentationKind::narrativeSection);
-        ref :>> framedConcerns = (UsabilityConcern, SafetyConcern);
+        ref :>> framedConcerns = (usabilityConcern, safetyConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 4;
         attribute :>> userExtensible = true;

package/src/viewpoints/verification/verification_viewpoint.sysml

@@ -13,12 +13,12 @@ package memo_viewpoints_verification_verification_viewpoint {
         @MemoIdentity { :>> shortDescription = "Shows verification cases, validation cases, and the evidence they produce, traced to requirements."; }
         attribute :>> description = "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.";
         attribute :>> purpose = "Communicate verification and validation coverage against requirements.";
-        ref :>> stakeholders = (VerificationEngineer);
+        ref :>> stakeholders = (verificationEngineer);
         attribute :>> stage = WorkflowStageKind::verificationStage;
         attribute :>> abstractionLevel = "verification";
         attribute :>> outputKind = (ViewOutputKind::matrix);
         attribute :>> presentationKind = (PresentationKind::traceMatrix);
-        ref :>> framedConcerns = (SafetyConcern, RegulatoryConcern);
+        ref :>> framedConcerns = (safetyConcern, regulatoryConcern);
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 5;
         attribute :>> userExtensible = true;