Nato Architecture Framework (NAF) - 4.7 - NATO Meta Model - NTV
NATO Technical Views (NTV)
NTV-1 Technical Standards Profile。
NTV-1 defines the technical and non-technical standards, guidance and policy applicable to the architecture.
The data in an NTV-1 can include:
- Standard
- Protocol
Nato Architecture Framework (NAF) - 3.6 - NATO Technical View#NTV-1.2C_Technical_Standards_Profile
NTV-2 Technical Standards Forecast。
The Standards Forecast contains expected changes in technology-related standards and conventions, which are documented in the NTV-2 Product.
The data in an NTV-2 can include:
- Standard (evolution over time)
Nato Architecture Framework (NAF) - 3.6 - NATO Technical View#NTV-2.2C_Technical_Standards_Forecast
NTV-3 Standards configuration。
The application of standard configurations shortens the architecture effort and provides for a better design by reusing readily available and already proven designs.
The architectures themselves must explicitly mention and describe standard configurations, or else they will not be recognized as such, and consequently, will not be available for future projects or recognized by future architects.
Nato Architecture Framework (NAF) - 3.6 - NATO Technical View#NTV-3.2C_Standard_Configurations
NTV metamodel diagrams。
- NTV-1&2&3 Technical standards profile, standards forecast and standard configuration
NTV metamodel glossary
| Element | Definition |
|---|---|
| Attribute | A defined property of an <<Entity>>. |
| DataModel | A structural specification of data, showing classifications of data elements and relationships between them. [ABSTRACT] |
| Entity | A definition (type) of an item of interest. |
| EntityRelationship | Asserts that there is a relationship between two entities. |
| ImplementsProtocol | An assertion that a <<ProtocolImplementation>> implements a <<Protocol>> |
| Protocol | A <<Standard>> for communication. <<Protocol>>s may be composite (i.e. a stack). |
| ProtocolImplementation | An element that can implement a <<Protocol>>. |
| ProtocolStack | Asserts that a <<Protocol>> (upperLayer) uses another <<Protocol>> (lowerLayer). |
| RatificationBody | Asserts than an <<ActualOrganisation>> is responsible for the ratification of a standard. |
| SpectrumAllocation | A <<Standard>> specifying a particular frequency range of the electromagnetic spectrum that is allotted to a particular usage. |
| StandardConfiguration | A UML::Comment that when attached to a <<CapabilityConfiguration>> indicates that it is a standard pattern for reuse in the architecture. |
| SubtypeRelationship | Asserts that one <<Entity>> (subtype) is a specialization of the other (supertype). |
