Service-Orientated Views (SOV)
SOV-4c Service Interaction Specification v1.2
The purpose of the Service Interaction Specification View (SOV-4c) is to specify how a service interacts with external agents, and the sequence and dependencies of those interactions.
NAF V3 Equivalency
SOV-4c has no direct equivalent in NAF v3. NAF v3 does show sequence diagrams in NSOV-5, however these appear to show services being orchestrated – this would be shown in OV-6c in MODAF.
Background:
An SOV-4c product does not specify the sequencing of an orchestrated set of services (see OV-6c). It’s purpose is to specify the general sequence of interactions that are possible for a given service.
Usage:
- Service Specification
Data objects:
The data in an SOV-4c can include:
- Service(Operational, Information and Application Service)
- Service Interface
- Service Lifeline
- Service Consumer
Relationships Between Key Data Objects (Simplified from M3)
Representation:
- UML
Detailed Product Description:
SOV-4c specifies how a service interacts with any given agent that has compatible interfaces. The representation is usually a UML Sequence Diagram.
SOV-4c Sequence Diagram representation
The product shows a service and the interfaces it exposes – quite often the diagrams can be cluttered if all interfaces are shown, so it is advisable to consider producing multiple SOV-4c products for a given service. Each interface in an SOV-4c has a “lifeline” to which messages are shown passing. It is also possible to show timing constraints between messages.
Page version 1.2, dated 20th June 2008