System Views (SV) [Physical, Specification or Solution Views]
SV-12 Service Provision v1.2
Version 1.2.001 ammendment
Version 1.2.001 fixes an error that this relationship was not symmetrical by introducing a ‘resource uses service’ relationship.
The Service Provision View (SV-12) specifies configurations of resources that can deliver a service, and the levels of service those resources can deliver in different environments.
h3. NAF V3 Equivalency
Note that this differs to the strict NAF definition in NSV-12 which only shows where systems contribute to services. In addition, certain parts of the NAF documentation refer to this view as NSV-13
Background:
The Service Oriented Views (SOVs) in MODAF provide a specification of what a service is to do and how it presents its functionality to service consumers. The SOVs deliberately avoid specifying how a service is to be implemented, so that maximum creative flexibility is available to service providers. However, when a service is implemented in an architecture, it is useful to know how that service is implemented. SV-12 provides the mapping from services to the resources that provide those services.
Usage:
- Service Implementation
- Resource Audit
- Tracing business processes to the resources that support them
Data objects:
The data in an SV-12 can include:
- Service
- Resource Type
Relationships Between Key Data Objects (Simplified from M3)
Representation:
- Mapping (Matrix)
- Diagram
- UML
Detailed Product Description:
An SV-12 maps a resource (which may be constructed of other resources) to the services it can provide. SV-12 products are usually presented as a structural model (e.g. a UML composite structure), with tracing relationships to services. It is also be possible to present an SV-12 as a table, with services on one axis and resources on the other. Care should be taken with this approach, however, as it tends to obfuscate any underlying structure the resources might have.
Version 1.2.001 also allows the SV-12 to show the inverse relationship of when a resources uses a service.
A given implementation may provide a different level of service depending on the environment in which is it used. The service attributes defined in SOV-1 can be given values in an SV-12 and related to the environment under which those values are true.
UML Representation of SV-12
Page version 1.2.001, dated 5th August 2008