An SvcV-4 addresses human and service functionality.
The primary purposes of SvcV-4 are to:
- Develop a clear description of the necessary data flows that are input (consumed) by an 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.
Usage
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.
Product Description
The SV-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 diagrams to depict activity models, as explained below.
Systems Functionality Description
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.
Systems Functionality Flow Description
The functional 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 flow, but not external to the Architectural Description’s scope. They may also show how users behave in relation to those services.
Creating a Services Functionality Description
To create a Services Functionality Description:
- Click on Services Functionality Description in the Action Artifact area, and then select Create New Diagram.
- Type the diagram name and press Enter.
- A blank diagram is created and you can start constructing the view. Create ServiceFunctions through the tool under the diagram toolbar.
Creating a Services Functionality Flow Description (diagram)
To create a Services Functionality Flow Description (diagram):
- Click on Services Functionality Flow Description in the Action Artifact area, and then select Create New Diagram.
- Type the diagram name and press Enter.
- A blank diagram is created and you can start constructing the view. Create the activity flows with ServiceFunctionActions and other flow elements (e.g. Control Flows, Decision Nodes, etc).
Services Functionality Description
Services Functionality Flow Description
DoDAF in Visual Paradigm
The DoDAF is brought to you by Visual Paradigm, a full-featured development platform. Visual Paradigm provides an easy-to-use, model-driven DoDAF tool that supports the development of DoDAF 2.02 views and models. You can create integrated DoDAF products and generate architectural documents that facilitate organizations to efficiently coordinate enterprise architecture initiatives.