S5 – Service States

NAF v3: NSOV-4b MODAF: SOV-4b

TaxonomyStructureConnectivityProcessesStatesSequencesInformationConstraintsRoadmap
C1-S1 (NSOV-3)
Service
Specifications
S1
Service Taxonomy
NAV-2, NSOV-1
AV-2, SOV-1
S3
Service Interfaces
NSOV-2
SOV-2
S4
Service Functions
NSOV-3
SOV-5
S5
Service States
NSOV-4b
SOV-4b
S6
Service Interactions
NSOV-4c
SOV-4c
S7
Service I/F Parameters
NSOV-2
SOV-2
S8
Service Policy
NSOV-4a
SOV-4a
Sr
Service Roadmap

The purpose of the Service States View (S5) is to specify the possible states a service may have, and the possible transitions between those states.

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. S5 is a specification of those states, and the possible transitions between them.

Usage

Representation

Detailed View Description

s5-example-1

Key Elements and Their Relationships

s5-hlmm

Meta-Model

The detailed meta-model for S5 can be viewed here

Leave a Reply