View DNDAF:TV-2 Standards Forecast Subview

dnd.gif

Title

TV-2 Technical Standards Forecast Subview

Version & Date

1.7 See DNDAF Release History

* =  changed at 1.7

+ =  new at 1.7

Introduction +

One of the 2 subviews in the DNDAF Technical View. There are in 36 subviews defined in the DNDAF.

From DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views, 3.32:

The Technical View-2 (TV-2) : Standards Forecast contains expected changes in standards which are documented in TV-1. A standards forecast is a detailed description of emerging standards relevant to the systems and business processes covered by the architecture. TV-2 will identify emerging standards that may not yet be required, but will be required during the life cycle of the system being developed (i.e. IPv6).

A TV-2 complements and expands on the Standards Profile (TV-1) sub-view and should be used when more than one standard is expected to be change over time.

Purpose +

From DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views, 3.32:

The purpose of this sub-view is to identify technology standards, their fragility, and the impact of these standards on the future development and maintainability of the systems components. A forecast addressing emerging standards will give insight into the direction of the architecture project. The intended usage of TV-2 is for forecasting future changes in standards.

Description +

Definition +

From DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views, 3.32:

The Standards Forecast contains anticipated changes in technology-related standards which are documented in the TV-1 sub-view.

Detailed Description +

From DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views, 3.32:

TV-2 lists emerging or evolving standards relevant to the systems covered by the architecture. It contains predictions about the availability of emerging standards, and relates these predictions to the System view elements and the time periods that are listed in the SV-8 and SV-9.

The specific time periods selected (e.g. 6-month, 12-month intervals) and the standards being tracked will be coordinated with architecture transition plans (see SV-8). That is, insertion of new capabilities and upgrading of existing systems may depend on, or be driven by the availability of new standards and products incorporating those standards. The forecast specifies potential standards and thus impacts current architectures and influences the development of transition and target architectures. The forecast will be tailored to focus on standards areas that are related to the purpose for which a given architecture is being described and should identify potential standards affecting that architecture. If interface standards are an integral part of the technologies important to the evolution of a given architecture, then it may be convenient to combine TV-2 with SV-9.

TV-2 delineates the standards that will potentially impact the relevant system elements (from the sub-views where applicable) and relates them to the time periods that are listed in the SV-8 and SV-9. A system’s evolution, specified in SV-8, may be tied to a future standard listed in TV-2. A timed technology forecast from SV-9 is related to a TV-2 standards forecast in the following manner : a certain technology may be dependent on a TV-2 standard (i.e., a standard listed in TV-2 may not be adopted until a certain technology becomes available). This is how a prediction on the adoption of a future standard, as applicable to systems elements from the sub-views where applicable, may be related to standards listed in TV-1 through the SV- 9.

Subview DADM Elements +

From DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views, 3.32:

The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:

Note: TV-1 is also responsible for creating TECHNICAL-STANDARD, TIME-PERIOD, EMERGING-STANDARD, SYSTEM-STANDARD, ARCHITECTURE-STANDARD.

Presentation +

  • Tabular

Examples +

See:

  • No examples provided in current documentation.

Prerequisites +

Version 1.7 no longer defines pre-requisites for any subview.

See DNDAF Subview Dependencies

Configuration History

1.7 - new subview

Comments

 

Other Frameworks

See also:

References


Category:Framework -> Specification
Category:Framework -> Subview

Categories:

 

© 2010 Eclectica Systems Ltd.