View NAF:NOV-3 Operational Information Requirements Subview

NATO_logo.gif

Overview

The NOV-3 Operational Information Requirements subview is part of the NATO Operational View and one of the 49 NATO Architecture Framework subviews*.

Version & Date

Version 3.1

* =  changed at 3.1

+ =  new at 3.1

The change history is derived from the definition of each NATO Architecture view within section 5.2.4 NATO Operational View (NOV) in AC/322(SC/1-WG/1)N(2009)0005-ADD2.  NATO Architecture Framework Version 3.1 document from http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3_1 .

See NAF Release History.

Purpose

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

The purpose of the Operational Information Requirements subview is to identify and describe all information exchanges that make up all information needlines between operational nodes, as identified in NOV-2. The NOV-3 subview identifies who exchanges what information, with whom, why the information is necessary, and with what quality the information exchange must occur.

Covered by NATO release conditions.

Description

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

The NOV-3 subview expresses the relationships across the NATO Operational View’s three basic entities: operational activity (operational task), (operational) node, and information exchange. Operational activities are addressed in NOV-5; nodes in NOV-2.

The emphasis in this product is on the operational characteristics of the information. It is important to note that NOV-3 is not intended to be an exhaustive listing of all the details contained in every information exchange of every operational node associated with the architecture in question. Nor will the production of such a listing be considered sufficient to replace an integrated architecture development effort. Rather, this product is intended to capture the most important aspects of selected information exchanges.

There is not always a one-to-one mapping of NOV-3 information exchanges to NOV-2 needlines; rather, many individual information exchanges may be associated with one needline.

The information media type (i.e. data, voice and video), quality (i.e. frequency, timeliness and security), and quantity (i.e. volume and speed) are attributes of the information and information exchange that must be included in the requirements description. For example, if the subject architecture concerns tactical battlefield targeting, then the timeliness of the enemy target information is a significant attribute of the information exchange.

Required properties such as availability, secure communications, latency, and reliability may also be captured for each exchange. Required properties may be extended to capture other needs such as personnel skills or facilities. The specific mission/scenario and the related operational tasks and activities can be noted as an attribute of the information exchange.

The identification and description of an information exchange, together with the identification and specification of its information attributes and information exchange attributes, form the Information Exchange Requirement (IER).

Covered by NATO release conditions.

Data Objects

From the NATO Architecture Framework v3.1, CHAPTER 5, Section 5.2.4.3

The data in an NOV-3 can include:

Covered by NATO release conditions.

From The MODAF Operational Viewpoint p21:

MODAF_OV-3_dataObjects_mm_430.gif

Full size:File:MODAF OV-3 dataObjects mm.gif

Subject to Crown Copyright

Note: Although fragment of simplified metamodel in the NOV-3 is different to that in MODAF 1.2.004 for the MODAF::OV-3 Operational Information Exchange Matrix View the NOV-3 is the same if you restrict it to information flows only.

The following substitutions need to be made for view/subview number:

Presentation

Configuration History

Comments

The NOV-3 is restricted to describing information exchanges and yet the metamodel at 3.1 includes the ability to describe energy exchanges, materiel exchanges and movement of people. It is therefore inconsistent with the NOV-2 which does cover all the exchanges in the NAF metamodel.  If it is extended to include all exchanges the title would need to be changed to be consistent with the subject of the view.

References

Other Frameworks

See also:

 

 

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

Categories:

 

© 2010 Eclectica Systems Ltd.