@memoarchitect/ontology 0.7.0 → 0.8.24

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.";
@@ -21,7 +20,7 @@ package memo_viewpoints_ui_layout_ui_layout_viewpoint {
         attribute :>> explorerLane = "architecture";
         attribute :>> explorerOrder = 4;
         attribute :>> allowedElementKinds = ("ScreenCapture", "UIElement", "UserInterface");
-        attribute :>> allowedRelationshipKinds = ("CapturesScreen", "NavigatesTo", "Composes", "SatisfiedBy", "ElementTriggersAction");
+        attribute :>> allowedRelationshipKinds = ("CapturesScreen", "NavigatesTo", "Composes", "satisfy", "ElementTriggersAction");
         attribute :>> defaultViewKind = DiagramViewKind::geometry;
         attribute :>> userExtensible = true;
     }

package/src/viewpoints/usability/usability_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_usability_usability_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part usabilityViewpoint : Viewpoint {
+    viewpoint usabilityViewpoint : MemoViewpoint {
         attribute :>> id = "VP-USE";
         attribute :>> name = "UsabilityViewpoint";
-        attribute :>> title = "Usability Viewpoint";
         attribute :>> 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.";

package/src/viewpoints/verification/verification_viewpoint.sysml

@@ -4,10 +4,9 @@ package memo_viewpoints_verification_verification_viewpoint {
     private import memo_viewpoints_definitions::*;
     private import memo_core_enumerations::*;
 
-    part verificationViewpoint : Viewpoint {
+    viewpoint verificationViewpoint : MemoViewpoint {
         attribute :>> id = "VP-VER";
         attribute :>> name = "VerificationViewpoint";
-        attribute :>> title = "Verification & Validation Viewpoint";
         attribute :>> 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.";
@@ -20,7 +19,7 @@ package memo_viewpoints_verification_verification_viewpoint {
         attribute :>> includedLayers = ("requirements", "assurance");
         attribute :>> explorerLane = "assurance";
         attribute :>> explorerOrder = 5;
-        attribute :>> allowedElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "Evidence", "TestArtifact");
+        attribute :>> allowedElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "MemoEvidence");
         attribute :>> userExtensible = true;
     }
 }

package/src/viewpoints/verification/views/verification_coverage_view/verification_coverage_view.sysml

@@ -10,7 +10,6 @@ package memo_viewpoints_verification_views_verification_coverage_view {
                     attribute depth = 2;
     attribute :>> id = "VIEW-VER-001";
     attribute :>> name = "VerificationCoverageView";
-    attribute :>> title = "Verification & Validation Coverage View";
     attribute :>> shortDescription = "Requirements with their verification cases, validation cases, and evidence.";
     attribute :>> outputKind = (ViewOutputKind::matrix);
     attribute :>> presentationKind = (PresentationKind::traceMatrix);
@@ -20,10 +19,10 @@ package memo_viewpoints_verification_views_verification_coverage_view {
     part :>> selectionQuery {
         attribute :>> id = "QRY-VER-001";
         attribute :>> name = "VerificationCoverageQuery";
-        attribute :>> includeElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "Evidence");
+        attribute :>> includeElementKinds = ("Requirement", "VerificationCase", "ValidationCase", "MemoEvidence");
         attribute :>> includeLayers = ("requirements", "assurance");
         attribute :>> rationaleText = "Auto-populate V&V coverage from the requirements and assurance layers.";
     }
-    part :>> viewpointDefinition = verificationViewpoint;
+    ref :>> viewpointDefinition = verificationViewpoint;
                 }
 }

package/templates/connected-device/memo.package.yaml

@@ -7,5 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
+entrypoint: model/catalog/project.sysml
+include: [model]
 version: 0.1.0
 description: MEMO connected device model

package/templates/default/memo.package.yaml

@@ -7,5 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
+entrypoint: model/catalog/project.sysml
+include: [model]
 version: 0.1.0
 description: MEMO architecture and assurance model

package/templates/infusion-pump/memo.package.yaml

@@ -7,5 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
+entrypoint: model/catalog/project.sysml
+include: [model]
 version: 0.1.0
 description: MEMO infusion pump model

package/templates/monitoring-device/memo.package.yaml

@@ -7,5 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
+entrypoint: model/catalog/project.sysml
+include: [model]
 version: 0.1.0
 description: MEMO monitoring device model

package/templates/samd/memo.package.yaml

@@ -7,5 +7,7 @@
 # (`type`, `extends`, `usage`, `ontologies`, `methodology`, `modules`) were
 # removed at the native semantic flip and are now rejected if present.
 name: '{{name}}'
+entrypoint: model/catalog/project.sysml
+include: [model]
 version: 0.1.0
 description: MEMO software as a medical device model

package/examples/extensions/README.md

@@ -1,16 +0,0 @@
-# Extension examples
-
-An extension is a regular SysML package selected by a MEMO methodology. MEMO
-does not define a separate extension metaclass. `MethodologyDefinition` and
-`ProjectMethodBinding` already accept packages through `includedModule`.
-
-- `template/` is the starting structure for an extension.
-- `clinical/` specializes `OperationalWorkflow` with clinical procedure data.
-
-Extensions specialize or reference base types. They do not redefine
-activities, workflows, architecture elements, relationships, or constraints
-already expressed by the base ontology.
-
-Extension packages remain outside `src/` and outside the `memo::` namespace.
-Projects import an extension package directly and include it in their selected
-methodology.

package/examples/extensions/template/src/extension.sysml

@@ -1,15 +0,0 @@
-// Replace the package name and included module with extension-specific names.
-package memo_extension_template {
-    private import ScalarValues::*;
-    private import memo_methodology_core::*;
-
-    part extensionMethod : MethodologyDefinition {
-        attribute :>> id = "EXT-METH-001";
-        attribute :>> name = "ExtensionMethod";
-        attribute :>> version = "0.1.0";
-        attribute :>> domain = "project extension";
-        attribute :>> description = "Adds a project or domain package to the selected MEMO methodology.";
-        attribute :>> baseMethodName = "MedicalDeviceLightDefault";
-        attribute :>> includedModule = "replace_with_extension_package";
-    }
-}