TRAK Community :: Wiki :: MODAF:SOV-4b Service State Model View

Overview

The SOV-4a Service Constraints View is part of the MODAF Service Oriented Viewpoint* and one of the 47 MODAF views*.

Version & Date

Version 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 p13:

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.

Subject to Crown Copyright

Background

From The MODAF Service Oriented Viewpoint p13:

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.

Subject to Crown Copyright

Description

From The MODAF Service Oriented Viewpoint p14:

SOV-4b products are usually UML (or similar) state transition models.

An SOV-4b may also specify performance constraints (ie the maximum duration a service may be in a particular state.

Subject to Crown Copyright

Data Objects

From The MODAF Service Oriented Viewpoint p13:

The data in an SOV-4b can include:
Service (Operational, Information and Application Service)

Service State Machine

Full size:File:MODAF SOV4 ServiceConstraints simplifiedMM.jpg