View NAF:NOV-6c Operational Event-Trace Description Subview

NATO_logo.gif

Overview

The NOV-6c Operational Event-Trace Description 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.6.3

NOV-6c is valuable for moving to the next level of detail from the initial operational concepts. An NOV-6c product helps define node interactions and operational threads.

An NOV-6c product can also help ensure that each participating operational node has the necessary information at the right time in order to perform its assigned operational activity.

Covered by NATO release conditions.

Description*

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

The Operational Event-Trace Description provides a time-ordered examination of the information exchanges between participating operational nodes as a result of a particular scenario. Each event-trace diagram will have an accompanying description that defines the particular scenario or situation.

NOV-6c allows the tracing of actions in a scenario or critical sequence of events. NOV-6c can be used by itself or in conjunction with any other of the behavioural operational subviews (i.e. information exchanges in NOV-3, or flow of activity in NOV-5 or NOV-6b) to describe the dynamic behaviour of operational processes or a mission/operational thread. An operational thread is defined as a set of operational activities, with sequence and timing attributes of the activities, and includes the information needed to accomplish the activities. A particular operational thread may be used to depict a military capability. In this manner, a capability is defined in terms of the attributes required to accomplish a given mission objective by modelling the set of activities and their attributes. The sequence of activities forms the basis for defining and understanding the many factors that impact on the overall military capability.

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

The Operational Event-Trace Description provides a time-ordered examination of the information exchanges between participating Operational Nodes as a result of a particular scenario.

Service-Oriented Architectures

If the architect is developing a Service-Oriented Architecture (SOA), an NOV-6c product may be used to show the sequence of interactions required to support operational activities. An SOA NOV-5 product shows which services support which operational activities, however it may be useful to show how those services are required to interact in order to support operations. An SOA NOV-6c shows lifelines for services, and the sequence of interactions between those services:

Covered by NATO release conditions.

Data Objects

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

The data in a NOV-6c can include:

  • Lifelines (each associated with a Node)

Covered by NATO release conditions.

From The MODAF Operational Viewpoint p39:

MODAF_OV6c_mm_dataObjects_430.gif

Full size:File:MODAF OV6c mm dataObjects.gif

This diagram is taken from MODAF 1.2.004 MODAF::OV-6c Operational Event-Trace Description View as it is identical to that in NAF 3.1 with the following substitutions for view/subview number:

and remembering that the NOV-6c is only defined in terms of Information Exchanges.

Configuration History

Comments

References

Other Frameworks

See also:

 

 

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

Categories:

 

© 2010 Eclectica Systems Ltd.