DoDAF Viewpoints and Models
SvcV-4: Services Functionality Description
The SvcV-4 DoDAF-described Model addresses human and service functionality.
The primary purpose of SvcV-4 is to:
- Develop a clear description of the necessary data flows that are input (consumed) by and output (produced) by each resource.
- Ensure that the service functional connectivity is complete (i.e., that a resource's required inputs are all satisfied).
- Ensure that the functional decomposition reaches an appropriate level of detail.
The Services Functionality Description provides detailed information regarding the:
- Allocation of service functions to resources.
- Flow of resources between service functions.
The SvcV-4 is the Services Viewpoint counterpart to the OV-5b Operational Activity Model of the Operational Viewpoint.
The intended usage of the SvcV-4 includes:
- Description of task workflow.
- Identification of functional service requirements.
- Functional decomposition of Services.
- Relate human and service functions.
It is important to note that one usage of the SvcV-4 can support a net-centric (service-oriented) implementation in describing the producing services and consuming services. The Services Functionality Description information can support the registration of services in net-centric (service-oriented) implementation.
The SvcV-4 is used to specify the service functionality of resources in the architecture. The SvcV-4 is the behavioral counterpart to the SvcV-1 Services Context Description (in the same way that OV-5b Operational Activity Model is the behavioral counterpart to OV-2 Operational Resource Flow Description).
The scope of this model may be capability wide, without regard to which resources perform which service functions, or it may be resource-specific. Variations may focus on intra- or inter-resource data flows, or may simply allocate service functions to resources.
There are two basic ways to depict a SvcV-4:
- The Taxonomic Service Functional Hierarchy shows a decomposition of service functions depicted in a tree structure and is typically used where tasks are concurrent but dependent, such as a production line, for example.
- The Data Flow Diagram shows service functions connected by data flow arrows and data stores.
Within an Architectural Description, the SvcV-4 document service functions, the Resource Flows between those service functions, the internal system data repositories or service data stores, and the external sources and sinks for the service data flows, but not external to the Architectural Description's scope. They may also show how users behave in relation to those services.
SvcV-1 Services Context Description
SvcV-2 Services Resource Flow Description
SvcV-3a Systems-Services Matrix
SvcV-3b Services-Services Matrix
SvcV-4 Services Functionality Description
SvcV-5 Operational Activity to Services Traceability Matrix
SvcV-6 Services Resource Flow Matrix
SvcV-7 Services Measures Matrix
SvcV-8 Services Evolution Description
SvcV-9 Services Technology & Skills Forecast
SvcV-10abc Introduction to SvcV-10a, SvcV-10b and SvcV-10c
SvcV-10a Services Rules Model
SvcV-10b Services State Transition Description
SvcV-10c Services Event-Trace Description