View MODAF:SOV-3 Capability to Service Mapping View

mod_logo_60.jpg

Overview

The SOV-3 Capability to Service Mapping View is part of the MODAF Service Oriented Viewpoint* and one of the 47 MODAF views*.

Version & Date

Version 1.2.004.

* =  changed at 1.2.004

+ =  new at 1.2.004

The change history is derived from the definition of each MODAF view within the The MODAF Service Oriented Viewpoint viewpoint defining document from www.mod.uk/modaf.

See MODAF Release History.

Purpose*

From The MODAF Service Oriented Viewpoint p9:

The SOV-3 specifies the capabilities that services provide.

Subject to Crown Copyright

Background

From The MODAF Service Oriented Viewpoint p9:

An SOV-3 presents a simple mapping of services to capabilities, showing which capabilities a given service provides.

Note that in MODAF v1.2.003, the semantics of the relationship between services and capabilities was unclear. If more than one service mapped to a given capability, it was not clear if each of those services provided the capability in and of itself, or if all the services were required together in order to deliver the capability.

From v1.2.004, the relationship between capability and service indicates that the service provides the capability. If more than one service maps to a capability, each of those services provides the capability in and of itself. Should the architect wish to express the need to bring together multiple services to deliver a capability, this should be expressed in OV-2, Operational Node Relationship Description, (mapping the capability to a node) and OV-5, Operational Activity Model (orchestrating the services against the activities performed by the node).

Subject to Crown Copyright

Description

From The MODAF Service Oriented Viewpoint p10:

The relationship between capability and service is many-to-many. A given service may provide one or more capabilities, or a given capability may be provided by more than one service. Note that if a combination of services are required deliver a certain capability, this should be modelled using a combination of OV-2 (to map the capability to a node) and OV-5 (to orchestrate the services against activities performed by the node).

Subject to Crown Copyright

Data Objects

From The MODAF Service Oriented Viewpoint p9:

The data in an SOV-3 can include:

  • Service
  • Capability
  • Service Aims to Achieve (relationship from Service to Capability).

*

MODAF_SOV3CapabilityService_simplified.jpg

Subject to Crown Copyright

Presentation

From The MODAF Service Oriented Viewpoint p10:

  • Tabular
  • UML

From The MODAF Service Oriented Viewpoint p10:

An SOV-3 can be presented as a matrix with capabilities on one axis and services on the other.

Alternatively, SOV-3 can be presented as a diagram showing tracing relationships from capabilities to services.

Subject to Crown Copyright

Configuration History

Comments

As the text suggests this mapping could be achieved using a combination of OV-2 and OV-5.

Other Frameworks

From The MODAF Service Oriented Viewpoint 26th April 2010 p9:

The NAF v3 equivalent view is NCV-7, Capability to Service Mapping.

Note - the NCV-7 is now the NSOV-3 Capability to Service Mapping Subview at NAF v 3.1

From The MODAF Service Oriented View (SOV) Viewpoint 27th November 2008 p9:

The NAF v3 equivalent view is NCV-7. The use of services in Strategic Views in MODAF is inappropriate, as Capabilities are supposed to be defined independently of how they are to be achieved; hence the mapping to capabilities sits more comfortably in the SOA Views.

Note - the NSOV-4 Service to Operational Activity Subview was removed at NAF v 3.1

Subject to Crown Copyright

See also:

References


Category:Framework -> View
Category:MODAF -> View
Category:Service

Categories:

 

© 2010 Eclectica Systems Ltd.