nafv4-architecture-metadata
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Architecture Foundation/Metadata Viewpoints (A1-A8, Ar) in Sparx Enterprise Architect. Use when the user wants to create A1 (Meta-Data Definitions), A2 (Architecture Products), A3 (Architecture Correspondence), A4 (Methodology Used), A5 (Architecture Status), A6 (Architecture Version), A7 (Architecture Compliance), A8 (Standards), or Ar (Architecture Roadmap) diagrams, add architecture metadata elements, create associations between architecture descriptions, or work with NAF architecture foundation modeling. Also triggers on natural language like "architectural description", "view", "viewpoint", "concern", "standard", "protocol", "architecture correspondence", etc.
nafv4-assistant
NAF v4 / ADMBw modeling assistant providing convenience functions for common modeling tasks. Offers specialized utilities like requirement naming, batch operations, and modeling helpers. Automatically routes to appropriate function based on user request or allows browsing available functions. Integrates with nafv4-coordinator for all NAF modeling operations.
nafv4-concepts
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Concepts Viewpoints (C1-C8, Cr) in Sparx Enterprise Architect. Use when the user wants to create C1 (Capability Taxonomy), C2 (Enterprise Vision), C3 (Capability Dependencies), C4 (Standard Processes), C5 (Effects), C7 (Performance Parameters), C8 (Planning Assumptions), or Cr (Capability Roadmap) diagrams, add capability elements, create associations between capabilities, enterprises, activities, or work with NAF concepts modeling. Also triggers on natural language like "capability", "enterprise vision", "enduring task", "desired effect", "measure of effectiveness", etc.
nafv4-coordinator
Coordinate NAF v4 / ADMBw modeling across all viewpoint categories. Routes requests to specialized skills (Requirements, Architecture Metadata, Concepts, Logical Specification, Physical Resources, Service Specification) and handles cross-viewpoint relationships. Use when the user wants to work with multiple viewpoint categories, create relationships between different viewpoint types (e.g., Requirement → Capability, Capability → Service), or needs guidance on which viewpoint to use.
nafv4-logical-specification
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Logical Specification Viewpoints (L1-L8, Lr) in Sparx Enterprise Architect. Use when the user wants to create L1 (Node Types), L2 (Logical Scenario), L3 (Node Interactions), L4 (Logical Activities), L5 (Logical States), L6 (Logical Sequence), L7 (Information Model), L8 (Logical Constraints), or Lr (Lines of Development) diagrams, add logical elements, create flows and interactions, or work with NAF logical architecture modeling. Also triggers on natural language like "operational performer", "logical node", "operational activity", "information exchange", "logical flow", etc.
nafv4-physical-resources
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Physical Resource Specification Viewpoints (P1-P8, Pr) in Sparx Enterprise Architect. Use when the user wants to create P1 (Resource Types), P2 (Resource Structure), P3 (Resource Connectivity), P4 (Resource Functions), P5 (Resource States), P6 (Resource Sequence), P7 (Data Model), P8 (Resource Constraints), or Pr (Configuration Management) diagrams, add resource elements, create associations between resources, or work with NAF physical architecture modeling. Also triggers on natural language like "system", "resource type", "function", "interface", "protocol", "state machine", etc.
nafv4-requirements
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Requirements Viewpoints (R2-R6) in Sparx Enterprise Architect. Use when the user wants to create R2 (Requirement Catalogue), R3 (Requirement Dependencies), R4 (Requirement Conformance), R5 (Requirement Derivation), or R6 (Requirement Realization) diagrams, add requirements elements, create associations between requirements, or work with NAF requirements modeling. Also triggers on natural language like "functional requirement", "requirement category", "derived from", "conforms to standard", etc.
nafv4-service-specification
Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Service Specification Viewpoints (S1-S8, Sr) in Sparx Enterprise Architect. Use when the user wants to create S1 (Service Taxonomy), S2 (Service Structure), S3 (Service Interfaces), S4 (Service Functions), S5 (Service States), S6 (Service Interactions), S7 (Service Interface Parameters), S8 (Service Policy), or Sr (Service Roadmap) diagrams, add service elements, create service interfaces, model service functions, or work with NAF service modeling. Also triggers on natural language like "service specification", "service interface", "service function", "service policy", "service taxonomy", etc.