TRAK-Community

Overview

The NSOV-2 Definitions subview is part of the NATO Service-Oriented 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.5 NATO Service-Oriented Views (NSOV) 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.6.3

The purpose of the Service Definitions subview is to strictly delineate and define services in order to understand the operational domain in terms of services supporting operational activities.

Covered by NATO release conditions.

Definition

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

The services in this subview are referenced in the NCV-7 and NSV-12 products.

Note - at NAF 3.1 the NCV-7 is now the NSOV-3.

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

The NSOV-2 view defines the properties of services and defines the interface of the service explicitly. NMM supports specific stereotypes to manage interfaces, ports as well as asynchronous messages and synchronous operations handling as part of the service interface. It should be noted that only one interface of a service may be exposed to the surrounding environment and that this is the interface that can be accessed by a service consumer.

Covered by NATO release conditions.

Data Objects*

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

The data in an NSOV-2 can include:

• Service (Operational, Information and Application Service)
• Service Interface
• Service Attribute
• Service interface definitions (required and provided) which may contain:
  • Service Interface Operations and
  • Asynchronous messages

Note: Service Attribute is missing from this diagram

Covered by NATO release conditions.

Presentation

Configuration History

• 3.1 Adds data objects list, removes Service Policy

Comments

The 3.0 text refers to service Policy being included but this isn’t listed in the data objects.

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

A definition of a service is broken apart into distinct segments:

• service outcome: defining the intended real world effects or information provided by the service;
• service identification: identifying and uniquely naming a service; describing the set of functionality offered;
• describing responsibilities; identifying the service’s consumers and the information consumed and provided;
• service properties: identifying specific properties of a service that may differ from one instance or implementation of a service to another. This includes quality of service properties, such as performance, security, availability, reliability, maintainability, latency, confidentiality, and integrity.
• service interfaces: specifying the interfaces through which the service consumer may exchange information with this service;
• service policies: specifying the policies regarding security, commercial conditions, applicable laws, etcetera, under which the service is provided.

Other Frameworks

See also:

• MODAF SOV-2 Service Interface Specification View but the MODAF view is more restricted - it only specifies the service interfaces (attributes are specified in MODAF SOV-1 Service Taxonomy View).

 

References

• Section 4.6.3 (page 224 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
• Section 5.2.5.2 (page 401 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
• Section 5.2.5.2 of AC/322(SC/1-WG/1)N(2009)0005-ADD2.  NATO Architecture Framework Version 3.1

 

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

Categories:

• Framework
  • View
• NAF
  • Subview
• Solution