View NAF:NSOV-1 Service Taxonomy Subview

NATO_logo.gif

Overview

The NSOV-1 Service Taxonomy 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.2

The purpose of the Service Taxonomy subview is to organise knowledge according to the service perspective, and to facilitate harmonization of services across multiple domains (or across multiple architectures).

Covered by NATO release conditions.

Definition

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

A taxonomy, essentially, is a system of classification. The general purpose is to organise one’s knowledge of something into categories of similar things, in order to understand something better through comparison with other similar things. In the Service-Oriented View, the service taxonomy represents the operational domain’s knowledge, as described in the Operational View, in terms of services, structured in some useful way. The services themselves are defined in NSOV-2.

For the taxonomy to be efficient and useful, it needs to classify services according to some classification criterion. This criterion should reflect the purpose of the taxonomy itself. For example, if the purpose is to reduce design complexity, then services could be classified according to architecture aspects, views, perspectives or levels of abstraction, if these are the mechanisms used to reduce complexity (e.g. distinguishing application services from infrastructure services). If the purpose is to support programme management, then services could be classified according to organisational aspects (e.g. distinguishing functional services from core services). Criteria of purpose may also be combined (e.g. resulting in, using the previous two examples, functional application services and core infrastructure services).

The NNEC Service Framework is a good example of a service taxonomy. The NNEC Service Framework is a taxonomy of NNEC services that classifies NNEC services according to NNEC C4ISR objectives. This particular taxonomy is structured according to NNEC service areas, NNEC service groups and NNEC service categories, consecutively.

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

NSOV-1 is a service taxonomy, describing a specialisation hierarchy of services (note these are classes of services, rather than the service implementations). There is no prescribed representation for this view, other than the ability to show multiple inheritances. The view may optionally show properties (e.g. service availability) and constraints on those properties, though this is covered in detail in NSOV-2.

Covered by NATO release conditions.

Data Objects

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

The data in an NSOV-1 can include:

Note: Service Policy is not shown in the NSOV-3.

Covered by NATO release conditions.

From The MODAF Service Oriented Viewpoint p3:

MODAF_SOV-1_ServiceTaxonomy_mm.jpg

Subject to Crown Copyright

This diagram is taken from MODAF 1.2.004 MODAF::SOV-1 Service Taxonomy View as it is identical to that in NAF 3.1 with the following substitutions for view/subview number:

  • MODAF::SOV-1 equates to NAF::NSOV-1 Service Taxonomy Subview

Presentation

Configuration History

  • 3.1 Adds data objects

Comments

References

Other Frameworks

See also:

 

 

 


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

Categories:

 

© 2010 Eclectica Systems Ltd.