View NAF:NTV-3 Standard Configurations Subview

NATO_logo.gif

Overview

The NTV-3 Standard Configurations subview is part of the NATO Technical View and one of the 47 NATO Architecture Framework subviews.

Version & Date

Version 3.0

See NAF Release History.

Purpose

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.8.3

The purpose of the Standard Configurations Description (NTV-3) is to describe standard configurations that are applied to or emerge from the architecture effort, used or encountered in any of the subviews developed in the architecture effort.

NTV-3 is intended to capture and explicitly describe configurations that are of value to the ongoing or to future architecture projects. It is also the intention of this subview to provide a single point to address and promote the use of standard configurations.

Covered by NATO release conditions.

Definition

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.8.3

The application of standard configurations shortens the architecture effort and provides for a better design by reusing readily available and already proven designs. The use of standard configurations is mandatory in NATO projects that involve software intensive systems, because it is intended to improve interoperability, which is one of the key requirements for NATO systems. New and improved configurations are recorded to help guide future architecture projects that may have to cope with similar issues or problems.

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.


Covered by NATO release conditions.

From the NATO Architecture Framework v3, CHAPTER 5, Section 5.2.7.3

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.


Covered by NATO release conditions.

Comments

A rather long-winded description of the value of ‘design pattern’ or ‘template’? Why not re-use the more common name rather than invent a new one?! The use of ‘standard’ in the subview name is confusing when the others refer to the Standard stereotype - something rather different.

Other Frameworks

See also:
• TRAK MVp-03 Requirements & Standards Viewpoint

References

•  Section 4.8.3 (page 271 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
•  Section 5.2.7.3 (page 443 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.

Category:Framework -> View
Category:NAF -> Subview
Category:Technical

Categories:

 

© 2010 Eclectica Systems Ltd.