Service-Orientated Views (SOV)

SOV-5 Service Functionality v1.2

The Service Functionality View (SOV-5) defines the behaviour of a service in terms of the functions it is expected to perform

NAF v3 Equivalency

The NAF v3 equivalent view is NSOV-5

Background:

SOV-5 is the key behavioural specification for services. Equivalent in nature to OV-5 and SV-4, it specifies a set of functions that a service implementation is expected to perform.

Usage:

Data objects:

The data in an SOV-5 can include:



Relationships Between Key Data Objects (Simplified from M3)

Representation:

Detailed Product Description:

An SOV-5 specifies the required functionality that an implementation of a service is expected to have – the implementation is represented in SV-1 and SV-4. An SOV-5 is usually presented as a functional diagram, with optional flows. An SOV-5 product should also show which service the functions correspond to.



Representation of SOV-5

Note that an SOV-5 should be a statement of what a service implementation is to do rather than how it is to do it. The functions specified in an SOV-5 should be essential to the service rather than an attempt to steer a particular implementation approach.

Page version 1.2, dated 20th June 2008

Top of Page