Service-Orientated Views (SOV)

SOV-4a Service Constraints v1.2

The purpose of the Service Constraints View (SOV-4a) is to specifies constraints that apply to implementations of services.

NAF V3 Equivalency

SOV-4a has no direct equivalent in NAF v3, though Service Policy constraints can be shown in NSOV-1.

Background:

To better enable consistency and re-use of service specifications, it is important to set constraints on how a service should behave. An SOV-4a product specifies constraints against services to which implementations of must conform.

Usage:

Data objects:

The data in an SOV-4a can include:



Relationships Between Key Data Objects (Simplified from M3)

Representation:

Detailed Product Description:

SOV-4a products are usually tabular, with services as rows and constraints as columns.



SOV-4a tabular representation

It is also possible to present the constraints as adornments to services in a diagram (e.g. a compartment in a UML class).



SOV-4a UML representation

Page version 1.2, dated 20th June 2008

Top of Page