View NAF:NOV-5 Operational Activity Model Subview

NATO_logo.gif

Overview

The NOV-5 Operational Activity Model 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.5

The purpose of an Operational Activity Model is to:

  • Clearly delineate lines of responsibility for operational activities when coupled with NOV-2;
  • Uncover unnecessary operational activity redundancy;
  • Make decisions about streamlining, combining, or omitting activities;
  • Define or flag issues, opportunities, or operational activities and their interactions (information flows among the activities) that need to be scrutinized further; and
  • Provide a necessary foundation for depicting activity sequencing and timing in NOV-6a, NOV-6b, and NOV-6c.
  • Provide a clear picture of how operations are performed and thereby support analysis and design of services and systems.

Covered by NATO release conditions.

Description

From the NATO Architecture Framework v3, Chapter 4, Section 4.5.5

The Operational Activity Model describes the operations that are normally conducted in the course of achieving a mission or an operational objective. It describes operational activities (or operational tasks) and Input/Output (I/O) flows between activities.

I/Os of operational activities relate to information elements of NOV-3 and are further characterized by the information exchange attributes described in NOV-3. I/Os that are produced or consumed by leaf operational activities that cross operational node boundaries are carried by needlines of NOV-2.

From the NATO Architecture Framework v3.1,Chapter 5, Section 5.2.4.5

Service-Oriented Architectures

If the architect is developing a Service-Oriented Architecture (SOA), an NOV-5 product may be used to show which services are required to support the conduct of operational activities. This type of product is commonly termed a service orchestration diagram, because it helps define what services are needed to support an operation and when they are needed.

Covered by NATO release conditions.

Data Objects*

From the NATO Architecture Framework v3.1,Chapter 5, Section 5.2.4.5

The data in an NOV-3 can include:

Covered by NATO release conditions.

From The MODAF Operational Viewpoint (OV) p28:

MODAF_OV5_mm_dataObjects_430.gif

Full size:File:MODAF OV5 mm dataObjects.gif

Subject to Crown Copyright

This diagram is taken from MODAF 1.2.004 OV-5 Operational Activity Model as it is identical to that in NAF 3.1 with the following substitutions for view/subview number:

Note the data objects ought also to include those needed for the service orchestration form.

Presentation

Configuration History

  • 3.1 removes Swimlanes (each associated with a Node) from the data objects.

Comments

Standard Operational Activity is not defined in the NATO Architecture Framework Metamodel (NMM) glossary for the NATO Operational View. It is assumed to be identical to the MODAF::Standard Operational Activity.

References

Other Frameworks

See also:

 

 


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

Categories:

 

© 2010 Eclectica Systems Ltd.