@memoarchitect/ontology 0.8.22 → 0.8.24

package/src/viewpoints/catalog/memo_viewpoint_catalog.sysml

@@ -13,154 +13,154 @@ package memo_viewpoints_catalog {
     // resolution to a standard SysML v2 view kind.
 
     // ── Content and context ─────────────────────────────────────
-    part vpModelContent : Viewpoint {
+    viewpoint vpModelContent : MemoViewpoint {
         attribute :>> id = "VP-CAT-001"; attribute :>> name = "ModelContentViewpoint";
         attribute :>> purpose = "Browse the model tree and package structure.";
         attribute :>> defaultViewKind = DiagramViewKind::browser;
     }
-    part vpSystemContext : Viewpoint {
+    viewpoint vpSystemContext : MemoViewpoint {
         attribute :>> id = "VP-CAT-002"; attribute :>> name = "SystemContextViewpoint";
         attribute :>> purpose = "System of interest, actors, external systems, and context exchanges.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
     // ── Operational world ───────────────────────────────────────
-    part vpUseCase : Viewpoint {
+    viewpoint vpUseCase : MemoViewpoint {
         attribute :>> id = "VP-CAT-003"; attribute :>> name = "UseCaseViewpoint";
         attribute :>> purpose = "Use cases, initiating users, supporting actors, and motivating needs.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpClinicalWorkflow : Viewpoint {
+    viewpoint vpClinicalWorkflow : MemoViewpoint {
         attribute :>> id = "VP-CAT-004"; attribute :>> name = "ClinicalWorkflowViewpoint";
         attribute :>> purpose = "Workflow steps, decisions, parallel work, handoffs, and roles.";
         attribute :>> defaultViewKind = DiagramViewKind::actionflow;
     }
-    part vpScenario : Viewpoint {
+    viewpoint vpScenario : MemoViewpoint {
         attribute :>> id = "VP-CAT-005"; attribute :>> name = "ScenarioViewpoint";
         attribute :>> purpose = "Selected paths through workflows: variants, conditions, variation points.";
         attribute :>> defaultViewKind = DiagramViewKind::actionflow;
     }
     // ── Functional ──────────────────────────────────────────────
-    part vpFunctionalArchitecture : Viewpoint {
+    viewpoint vpFunctionalArchitecture : MemoViewpoint {
         attribute :>> id = "VP-CAT-006"; attribute :>> name = "FunctionalArchitectureViewpoint";
         attribute :>> purpose = "System functions, capabilities, and functional exchanges.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpFunctionalFlow : Viewpoint {
+    viewpoint vpFunctionalFlow : MemoViewpoint {
         attribute :>> id = "VP-CAT-007"; attribute :>> name = "FunctionalFlowViewpoint";
         attribute :>> purpose = "Ordered functional flows and their steps.";
         attribute :>> defaultViewKind = DiagramViewKind::actionflow;
     }
     // ── Logical ─────────────────────────────────────────────────
-    part vpLogicalArchitecture : Viewpoint {
+    viewpoint vpLogicalArchitecture : MemoViewpoint {
         attribute :>> id = "VP-CAT-008"; attribute :>> name = "LogicalArchitectureViewpoint";
         attribute :>> purpose = "Logical components, channels, and allocations.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpSystemDecomposition : Viewpoint {
+    viewpoint vpSystemDecomposition : MemoViewpoint {
         attribute :>> id = "VP-CAT-009"; attribute :>> name = "SystemDecompositionViewpoint";
         attribute :>> purpose = "Composition hierarchy of the system of interest.";
         attribute :>> defaultViewKind = DiagramViewKind::browser;
     }
-    part vpInternalInterconnection : Viewpoint {
+    viewpoint vpInternalInterconnection : MemoViewpoint {
         attribute :>> id = "VP-CAT-010"; attribute :>> name = "InternalInterconnectionViewpoint";
         attribute :>> purpose = "Ports, connectors, and exchanges inside a component boundary.";
         attribute :>> defaultViewKind = DiagramViewKind::interconnection;
     }
     // ── Implementation ──────────────────────────────────────────
-    part vpSoftwareModule : Viewpoint {
+    viewpoint vpSoftwareModule : MemoViewpoint {
         attribute :>> id = "VP-CAT-011"; attribute :>> name = "SoftwareModuleViewpoint";
         attribute :>> purpose = "IEC 62304 module structure: systems, items, units, SOUP.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpSoftwareComponents : Viewpoint {
+    viewpoint vpSoftwareComponents : MemoViewpoint {
         attribute :>> id = "VP-CAT-012"; attribute :>> name = "SoftwareComponentViewpoint";
         attribute :>> purpose = "Runtime component-and-connector structure with concurrency and scheduling.";
         attribute :>> defaultViewKind = DiagramViewKind::interconnection;
     }
-    part vpHardwareArchitecture : Viewpoint {
+    viewpoint vpHardwareArchitecture : MemoViewpoint {
         attribute :>> id = "VP-CAT-013"; attribute :>> name = "HardwareArchitectureViewpoint";
         attribute :>> purpose = "Electronic/electrical structure and processing platform.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpPhysicalArchitecture : Viewpoint {
+    viewpoint vpPhysicalArchitecture : MemoViewpoint {
         attribute :>> id = "VP-CAT-014"; attribute :>> name = "PhysicalArchitectureViewpoint";
         attribute :>> purpose = "Mechanical, fluidic, optical, and other physical realization.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpDeviceComposition : Viewpoint {
+    viewpoint vpDeviceComposition : MemoViewpoint {
         attribute :>> id = "VP-CAT-015"; attribute :>> name = "DeviceCompositionViewpoint";
         attribute :>> purpose = "Device definitions, instances, accessories, and consumables.";
         attribute :>> defaultViewKind = DiagramViewKind::browser;
     }
-    part vpNetworkDeployment : Viewpoint {
+    viewpoint vpNetworkDeployment : MemoViewpoint {
         attribute :>> id = "VP-CAT-016"; attribute :>> name = "NetworkDeploymentViewpoint";
         attribute :>> purpose = "Deployment units on processing nodes and network topology.";
         attribute :>> defaultViewKind = DiagramViewKind::interconnection;
     }
     // ── Interaction and behavior ────────────────────────────────
-    part vpUiFlow : Viewpoint {
+    viewpoint vpUiFlow : MemoViewpoint {
         attribute :>> id = "VP-CAT-017"; attribute :>> name = "UiFlowViewpoint";
         attribute :>> purpose = "Interaction flows, UI states, and transitions.";
         attribute :>> defaultViewKind = DiagramViewKind::statetransition;
     }
-    part vpStateMode : Viewpoint {
+    viewpoint vpStateMode : MemoViewpoint {
         attribute :>> id = "VP-CAT-018"; attribute :>> name = "StateModeViewpoint";
         attribute :>> purpose = "System states, device modes, and transitions.";
         attribute :>> defaultViewKind = DiagramViewKind::statetransition;
     }
-    part vpSequenceInteraction : Viewpoint {
+    viewpoint vpSequenceInteraction : MemoViewpoint {
         attribute :>> id = "VP-CAT-019"; attribute :>> name = "SequenceInteractionViewpoint";
         attribute :>> purpose = "Ordered message exchanges between participants in a scenario.";
         attribute :>> defaultViewKind = DiagramViewKind::sequence;
     }
     // ── Assurance ───────────────────────────────────────────────
-    part vpRequirementsTraceability : Viewpoint {
+    viewpoint vpRequirementsTraceability : MemoViewpoint {
         attribute :>> id = "VP-CAT-020"; attribute :>> name = "RequirementsTraceabilityViewpoint";
         attribute :>> purpose = "Needs → requirements → architecture → verification trace matrix.";
         attribute :>> defaultViewKind = DiagramViewKind::grid;
     }
-    part vpRiskChain : Viewpoint {
+    viewpoint vpRiskChain : MemoViewpoint {
         attribute :>> id = "VP-CAT-021"; attribute :>> name = "RiskChainViewpoint";
         attribute :>> purpose = "ISO 14971 chain: hazard → hazardous situation → harm with controls.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpCybersecurity : Viewpoint {
+    viewpoint vpCybersecurity : MemoViewpoint {
         attribute :>> id = "VP-CAT-022"; attribute :>> name = "CybersecurityViewpoint";
         attribute :>> purpose = "Assets, threats, trust boundaries, and security controls.";
         attribute :>> defaultViewKind = DiagramViewKind::general;
     }
-    part vpHumanFactors : Viewpoint {
+    viewpoint vpHumanFactors : MemoViewpoint {
         attribute :>> id = "VP-CAT-023"; attribute :>> name = "HumanFactorsViewpoint";
         attribute :>> purpose = "Users, tasks, use errors, and hazard-related use scenarios.";
         attribute :>> defaultViewKind = DiagramViewKind::grid;
     }
-    part vpVerificationCoverage : Viewpoint {
+    viewpoint vpVerificationCoverage : MemoViewpoint {
         attribute :>> id = "VP-CAT-024"; attribute :>> name = "VerificationCoverageViewpoint";
         attribute :>> purpose = "Verification cases against requirements and functions.";
         attribute :>> defaultViewKind = DiagramViewKind::grid;
     }
-    part vpValidationCoverage : Viewpoint {
+    viewpoint vpValidationCoverage : MemoViewpoint {
         attribute :>> id = "VP-CAT-025"; attribute :>> name = "ValidationCoverageViewpoint";
         attribute :>> purpose = "Validation cases against use cases and critical tasks.";
         attribute :>> defaultViewKind = DiagramViewKind::grid;
     }
-    part vpEvidenceTraceability : Viewpoint {
+    viewpoint vpEvidenceTraceability : MemoViewpoint {
         attribute :>> id = "VP-CAT-026"; attribute :>> name = "EvidenceTraceabilityViewpoint";
         attribute :>> purpose = "Evidence records back to the cases and elements they support.";
         attribute :>> defaultViewKind = DiagramViewKind::grid;
     }
     // A software sequence diagram is a VIEW conforming to this viewpoint
     // (ISO/IEC/IEEE 42010): it frames the runtime message ordering between
-    // SoftwareComponents realizing a functional MemoScenario. The viewpoint is the
+    // SoftwareComponents realizing a functional OperativeScenario. The viewpoint is the
     // reusable spec; the diagram of a specific model is the view.
-    part vpSoftwareSequence : Viewpoint {
+    viewpoint vpSoftwareSequence : MemoViewpoint {
         attribute :>> id = "VP-CAT-027"; attribute :>> name = "SoftwareSequenceViewpoint";
         attribute :>> purpose = "Runtime message ordering between software components along a functional scenario.";
         attribute :>> defaultViewKind = DiagramViewKind::sequence;
     }
     // The first cataloged viewpoint to resolve to `geometry`: screen regions
     // carry authored RegionBounds, so a geometry view draws modelled facts.
-    part vpUILayout : Viewpoint {
+    viewpoint vpUILayout : MemoViewpoint {
         attribute :>> id = "VP-CAT-028"; attribute :>> name = "UILayoutViewpoint";
         attribute :>> purpose = "Captured screens with their marked regions and the UI elements those regions present.";
         attribute :>> defaultViewKind = DiagramViewKind::geometry;

package/src/viewpoints/clinical/clinical_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_clinical_clinical_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part clinicalViewpoint : Viewpoint {
+    viewpoint clinicalViewpoint : MemoViewpoint {
         attribute :>> id = "VP-CLIN";
         attribute :>> name = "ClinicalViewpoint";
-        attribute :>> title = "Clinical Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/context/context_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_context_context_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part contextViewpoint : Viewpoint {
+    viewpoint contextViewpoint : MemoViewpoint {
         attribute :>> id = "VP-CTX";
         attribute :>> name = "ContextViewpoint";
-        attribute :>> title = "System Context Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/context/views/system_context_view/system_context_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_context_views_system_context_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-CTX-001";
     attribute :>> name = "SystemContextView";
-    attribute :>> title = "System Context View";
     attribute :>> shortDescription = "Actors, use context, and system boundary.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::blockDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_context_views_system_context_view {
         attribute :>> includeLayers = ("context");
         attribute :>> rationaleText = "Auto-populate the system context view from the context layer.";
     }
-    part :>> viewpointDefinition = contextViewpoint;
+    ref :>> viewpointDefinition = contextViewpoint;
                 }
 }

package/src/viewpoints/cybersecurity/cybersecurity_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part cybersecurityViewpoint : Viewpoint {
+    viewpoint cybersecurityViewpoint : MemoViewpoint {
         attribute :>> id = "VP-CYB";
         attribute :>> name = "CybersecurityViewpoint";
-        attribute :>> title = "Cybersecurity Viewpoint";
         attribute :>> 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.";
@@ -20,9 +19,8 @@ package memo_viewpoints_cybersecurity_cybersecurity_viewpoint {
         attribute :>> includedLayers = ("cybersecurity", "software_structure", "hardware_structure", "interfaces", "risk", "assurance");
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 3;
-        attribute :>> allowedElementKinds = ("CybersecurityAsset", "Threat", "Vulnerability", "CyberHazard", "CyberRisk", "CyberMitigation", "SecurityRequirement", "TrustBoundary", "MemoScenario[scenarioKind=threat]");
+        attribute :>> allowedElementKinds = ("CybersecurityAsset", "Threat", "Vulnerability", "CyberHazard", "CyberRisk", "CyberMitigation", "SecurityRequirement", "TrustBoundary", "OperativeScenario[scenarioKind=threat]");
         attribute :>> allowedRelationshipKinds = ("ThreatenedBy", "Exploits", "RealizedByScenario", "Mitigates", "DerivesCyberRequirement", "ImpactsSafety", "CrossesTrustBoundary");
-        attribute :>> documentUsage = ("Secure Product Development", "Threat Model", "Cybersecurity Risk Assessment", "QMSR");
         attribute :>> userExtensible = true;
     }
 }

package/src/viewpoints/definitions/memo_viewpoint_definitions.sysml

@@ -1,12 +1,37 @@
+// MEMO's ISO/IEC/IEEE 42010 view apparatus, built on native SysML v2 — which
+// already models the whole stack: a View conforms to a Viewpoint, a Viewpoint
+// frames Concerns, Concerns are held by Stakeholders. MemoView extends the
+// native Views::View. Concerns are the native `concern def`; stakeholders are
+// native stakeholder memberships (any Part in the stakeholder role); MEMO adds
+// only the medical-device attributes on top, never a parallel type.
 package memo_viewpoints_definitions {
-    private import Metaobjects::SemanticMetadata;
     private import ScalarValues::*;
 
     private import memo_core_common::*;
     private import memo_core_enumerations::*;
+    private import memo_core_dimensions::*;
+    private import memo_core_terminology::*;
     private import memo_core_relationships::*;
 
-    part def Viewpoint specializes DocumentedElement {
+    // Extends the native SysML viewpoint (Views::ViewpointCheck, a
+    // RequirementCheck whose subject is a View) with MEMO's catalog
+    // attributes. The MEMO identity core is re-declared here because a
+    // viewpoint is native requirement-family, not a MemoPart — the same
+    // per-metaclass pattern MemoView and the other bases use.
+    viewpoint def MemoViewpoint :> Views::ViewpointCheck {
+        attribute id : String;
+        attribute uuid : String;
+        attribute name : String;
+        attribute shortDescription : String;
+        attribute description : String;
+        attribute rationale : String;
+        attribute sourceReference : String;
+        attribute status : ElementStatusKind;
+        attribute lifecycleState : LifecycleStateKind;
+        attribute realizationStage : RealizationStageKind[0..1];
+        attribute crossCuttingConcerns : CrossCuttingConcernKind[0..*];
+        attribute applicableStandards : ExternalReference[0..*];
+        attribute codes : TerminologyCode[0..*];
         attribute purpose : String;
         attribute audience : AudienceKind[*];
         attribute stage : WorkflowStageKind;
@@ -48,7 +73,24 @@ package memo_viewpoints_definitions {
         attribute rationaleText : String;
     }
 
-    view def MemoView :> Views::View, DocumentedElement {
+    view def MemoView :> Views::View {
+        // MEMO identity core, re-declared here rather than inherited: a view is
+        // native SysML and must stay one, so it does not mix in the MemoPart
+        // part hierarchy — same per-metaclass pattern the other MEMO bases use.
+        attribute id : String;
+        attribute uuid : String;
+        attribute name : String;
+        attribute shortDescription : String;
+        attribute description : String;
+        attribute rationale : String;
+        attribute sourceReference : String;
+        attribute status : ElementStatusKind;
+        attribute lifecycleState : LifecycleStateKind;
+        attribute realizationStage : RealizationStageKind[0..1];
+        attribute crossCuttingConcerns : CrossCuttingConcernKind[0..*];
+        attribute concerns : ConcernKind[0..*];
+        attribute applicableStandards : ExternalReference[0..*];
+        attribute codes : TerminologyCode[0..*];
         attribute outputKind : ViewOutputKind[*];
         attribute presentationKind : PresentationKind[*];
         attribute filterExpression : String;
@@ -57,7 +99,7 @@ package memo_viewpoints_definitions {
         attribute autoPopulate : Boolean;
         // ISO 42010 conformance is many-to-many: every view has one or more
         // viewpoints, and a viewpoint may be realized by many reusable views.
-        part viewpointDefinition : Viewpoint[1..*];
+        ref viewpointDefinition : MemoViewpoint[1..*];
         // Optional grouping within each viewpoint, interpreted by Architect.
         attribute group : String;
         ref subjectElement : MemoPart[*];

package/src/viewpoints/functional/functional_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_functional_functional_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part functionalViewpoint : Viewpoint {
+    viewpoint functionalViewpoint : MemoViewpoint {
         attribute :>> id = "VP-FUNC";
         attribute :>> name = "FunctionalViewpoint";
-        attribute :>> title = "Functional Viewpoint";
         attribute :>> 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.";
@@ -20,7 +19,7 @@ package memo_viewpoints_functional_functional_viewpoint {
         attribute :>> includedLayers = ("functions");
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 2;
-        attribute :>> allowedElementKinds = ("SystemFunction", "ComponentFunction", "FunctionalFlow", "FunctionalFlowStep", "MemoScenario[scenarioKind=functional]", "FunctionalExchange");
+        attribute :>> allowedElementKinds = ("SystemFunction", "ComponentFunction", "FunctionalFlow", "FunctionalFlowStep", "OperativeScenario[scenarioKind=functional]", "FunctionalExchange");
         attribute :>> userExtensible = true;
     }
 }

package/src/viewpoints/functional/views/function_allocation_view/function_allocation_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_functional_views_function_allocation_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-FUNC-002";
     attribute :>> name = "FunctionAllocationView";
-    attribute :>> title = "Function Allocation View";
     attribute :>> shortDescription = "Functions allocated to logical components.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::blockDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_functional_views_function_allocation_view {
         attribute :>> includeLayers = ("functions", "logical_structure");
         attribute :>> rationaleText = "Auto-populate function-to-component allocation from the functions and logical structure layers.";
     }
-    part :>> viewpointDefinition = functionalViewpoint;
+    ref :>> viewpointDefinition = functionalViewpoint;
                 }
 }

package/src/viewpoints/functional/views/system_functional_tree_view/system_functional_tree_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_functional_views_system_functional_tree_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-FUNC-001";
     attribute :>> name = "SystemFunctionalTreeView";
-    attribute :>> title = "System Functional Tree";
     attribute :>> shortDescription = "Hierarchical decomposition of system functions.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::activityDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_functional_views_system_functional_tree_view {
         attribute :>> includeLayers = ("functions");
         attribute :>> rationaleText = "Auto-populate the functional tree from the functions layer.";
     }
-    part :>> viewpointDefinition = functionalViewpoint;
+    ref :>> viewpointDefinition = functionalViewpoint;
                 }
 }

package/src/viewpoints/logical/logical_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_logical_logical_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part logicalArchitectureViewpoint : Viewpoint {
+    viewpoint logicalArchitectureViewpoint : MemoViewpoint {
         attribute :>> id = "VP-LOG";
         attribute :>> name = "LogicalArchitectureViewpoint";
-        attribute :>> title = "Logical Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/logical/views/logical_architecture_view/logical_architecture_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_logical_views_logical_architecture_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-LOG-001";
     attribute :>> name = "LogicalArchitectureView";
-    attribute :>> title = "Logical Architecture View";
     attribute :>> shortDescription = "Logical components and their interfaces.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::blockDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_logical_views_logical_architecture_view {
         attribute :>> includeLayers = ("logical_structure", "interfaces");
         attribute :>> rationaleText = "Auto-populate the logical architecture view from the logical structure and interfaces layers.";
     }
-    part :>> viewpointDefinition = logicalArchitectureViewpoint;
+    ref :>> viewpointDefinition = logicalArchitectureViewpoint;
                 }
 }

package/src/viewpoints/operational/operational_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_operational_operational_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part operationalViewpoint : Viewpoint {
+    viewpoint operationalViewpoint : MemoViewpoint {
         attribute :>> id = "VP-OPS";
         attribute :>> name = "OperationalViewpoint";
-        attribute :>> title = "Operational & Use-Case Viewpoint";
         attribute :>> 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.";
@@ -20,7 +19,7 @@ package memo_viewpoints_operational_operational_viewpoint {
         attribute :>> includedLayers = ("context", "operational", "system");
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 1;
-        attribute :>> allowedElementKinds = ("Actor", "UseContext", "OperationalActivity", "MemoScenario[scenarioKind=operative]");
+        attribute :>> allowedElementKinds = ("Actor", "UseContext", "OperativeAction", "OperativeScenario[scenarioKind=operative]");
         attribute :>> userExtensible = true;
     }
 }

package/src/viewpoints/operational/views/use_case_view/use_case_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_operational_views_use_case_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-OPS-001";
     attribute :>> name = "UseCaseView";
-    attribute :>> title = "Use Case Overview";
     attribute :>> shortDescription = "Actors connected to the operational scenarios and capabilities they invoke.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::custom);
@@ -20,10 +19,10 @@ package memo_viewpoints_operational_views_use_case_view {
     part :>> selectionQuery {
         attribute :>> id = "QRY-OPS-001";
         attribute :>> name = "UseCaseQuery";
-        attribute :>> includeElementKinds = ("Actor", "UseContext", "MemoScenario[scenarioKind=operative]");
+        attribute :>> includeElementKinds = ("Actor", "UseContext", "OperativeScenario[scenarioKind=operative]");
         attribute :>> includeLayers = ("context", "operational");
         attribute :>> rationaleText = "Auto-populate the use case view from the context and operational layers.";
     }
-    part :>> viewpointDefinition = operationalViewpoint;
+    ref :>> viewpointDefinition = operationalViewpoint;
                 }
 }

package/src/viewpoints/physical/physical_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_physical_physical_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part physicalViewpoint : Viewpoint {
+    viewpoint physicalViewpoint : MemoViewpoint {
         attribute :>> id = "VP-PHY";
         attribute :>> name = "PhysicalViewpoint";
-        attribute :>> title = "Physical Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/physical/views/network_topology_view/network_topology_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_physical_views_network_topology_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-PHY-002";
     attribute :>> name = "NetworkTopologyView";
-    attribute :>> title = "Network Topology View";
     attribute :>> shortDescription = "Physical interconnections and network ports between components.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::internalDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_physical_views_network_topology_view {
         attribute :>> includeLayers = ("physical");
         attribute :>> rationaleText = "Auto-populate the network topology view from the physical interfaces layer.";
     }
-    part :>> viewpointDefinition = physicalViewpoint;
+    ref :>> viewpointDefinition = physicalViewpoint;
                 }
 }

package/src/viewpoints/physical/views/physical_bom_view/physical_bom_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_physical_views_physical_bom_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-PHY-001";
     attribute :>> name = "PhysicalBOMView";
-    attribute :>> title = "Physical Bill of Materials View";
     attribute :>> shortDescription = "Physical and hardware components with their decomposition.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::blockDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_physical_views_physical_bom_view {
         attribute :>> includeLayers = ("hardware_structure", "physical");
         attribute :>> rationaleText = "Auto-populate the physical BOM view from the hardware and physical layers.";
     }
-    part :>> viewpointDefinition = physicalViewpoint;
+    ref :>> viewpointDefinition = physicalViewpoint;
                 }
 }

package/src/viewpoints/requirements/requirements_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_requirements_requirements_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part requirementsViewpoint : Viewpoint {
+    viewpoint requirementsViewpoint : MemoViewpoint {
         attribute :>> id = "VP-REQ";
         attribute :>> name = "RequirementsViewpoint";
-        attribute :>> title = "Requirements Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/requirements/views/requirements_traceability_view/requirements_traceability_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_requirements_views_requirements_traceability_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-REQ-001";
     attribute :>> name = "RequirementsTraceabilityView";
-    attribute :>> title = "Requirements Traceability View";
     attribute :>> shortDescription = "Stakeholder needs traced through system, software, and hardware requirements.";
     attribute :>> outputKind = (ViewOutputKind::matrix);
     attribute :>> presentationKind = (PresentationKind::traceMatrix);
@@ -24,6 +23,6 @@ package memo_viewpoints_requirements_views_requirements_traceability_view {
         attribute :>> includeLayers = ("requirements");
         attribute :>> rationaleText = "Auto-populate requirements traceability from the requirements layer.";
     }
-    part :>> viewpointDefinition = requirementsViewpoint;
+    ref :>> viewpointDefinition = requirementsViewpoint;
                 }
 }

package/src/viewpoints/risk/risk_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_risk_risk_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part riskViewpoint : Viewpoint {
+    viewpoint riskViewpoint : MemoViewpoint {
         attribute :>> id = "VP-RISK";
         attribute :>> name = "RiskViewpoint";
-        attribute :>> title = "Risk and Control Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/risk/views/risk_chain_view/risk_chain_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_risk_views_risk_chain_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-RISK-001";
     attribute :>> name = "RiskChainView";
-    attribute :>> title = "Risk Mitigation Chain View";
     attribute :>> shortDescription = "Hazards through harms with controls and verification.";
     attribute :>> outputKind = (ViewOutputKind::table);
     attribute :>> presentationKind = (PresentationKind::riskTable);
@@ -25,6 +24,6 @@ package memo_viewpoints_risk_views_risk_chain_view {
         attribute :>> includeConcerns = (ConcernKind::safety);
         attribute :>> rationaleText = "Auto-populate the risk chain view from the risk and assurance layers.";
     }
-    part :>> viewpointDefinition = riskViewpoint;
+    ref :>> viewpointDefinition = riskViewpoint;
                 }
 }

package/src/viewpoints/software/software_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_software_software_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part softwareViewpoint : Viewpoint {
+    viewpoint softwareViewpoint : MemoViewpoint {
         attribute :>> id = "VP-SW";
         attribute :>> name = "SoftwareViewpoint";
-        attribute :>> title = "Software Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/software/views/software_architecture_view/software_architecture_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_software_views_software_architecture_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-SW-001";
     attribute :>> name = "SoftwareArchitectureView";
-    attribute :>> title = "Software Architecture View";
     attribute :>> shortDescription = "Software systems, components, and SOUP with their decomposition.";
     attribute :>> outputKind = (ViewOutputKind::diagram);
     attribute :>> presentationKind = (PresentationKind::blockDiagram);
@@ -24,6 +23,6 @@ package memo_viewpoints_software_views_software_architecture_view {
         attribute :>> includeLayers = ("software_structure");
         attribute :>> rationaleText = "Auto-populate the software architecture view from the software structure layer.";
     }
-    part :>> viewpointDefinition = softwareViewpoint;
+    ref :>> viewpointDefinition = softwareViewpoint;
                 }
 }

package/src/viewpoints/ui_layout/ui_layout_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part uiLayoutViewpoint : Viewpoint {
+    viewpoint uiLayoutViewpoint : MemoViewpoint {
         attribute :>> id = "VP-UIL";
         attribute :>> name = "UILayoutViewpoint";
-        attribute :>> title = "UI Layout Viewpoint";
         attribute :>> 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.";