Service-Orientated Views (SOV)
SOV-4b Service State Model v1.2
The purpose of the Service State Model View (SOV-4b) is to specify the possible states a service may have, and the possible transitions between those states.
NAF V3 Equivalency
SOV-4b has no direct equivalent in NAF v3.
Background:
It is generally considered good practice to make services stateless – i.e. consumers of a service are not aware of what state the service is in. However, in specifying a service, it is often necessary to specify the allowable states so as to constrain how implementations of the service will behave. SOV-4b is a specification of those states, and the possible transitions between them.
Usage:
- Service Specification
Data objects:
The data in an SOV-4a can include:
- Service(Operational, Information and Application Service)
- Service State Machine
Relationships Between Key Data Objects (Simplified from M3)
Representation:
- UML
- Other state transition models
Detailed Product Description:
SOV-4b products are usually UML (or similar) state transition models.
SOV-4b state transion model representation
An SOV-4b may also specify performance constraints (i.e. the maximum duration a service may be in a particular state):
SOV-4b showing performance constraints
Page version 1.2, dated 20th June 2008