The SvcV-1 “Services Interface Description” addresses the composition and interaction of Services. SvcV-1 incorporates human elements as types of Performers – Organizations and Personnel Types.
Guide: DoDAF Architecture Framework Version 2.02 – Page 171
The SvcV-1 links together the operational and services architecture models by depicting how resources are structured and interact to realize the logical architecture specified in an OV-2 “Operational Resource Flow Description”. A SvcV-1 may represent the realization of a requirement specified in an OV-2 (i.e., in a “To-Be” Architectural Description), and so there may be many alternative SvcV models that could realize the operational requirement. Alternatively, in an “As-Is” Architectural Description, the OV-2 may simply be a simplified, logical representation of the SvcV-1 to allow communication of key Resource Flows to non-technical stakeholders. [1]
It is important for the architect to recognize that the SvcV-1 focuses on the Resource Flow and the providing service. This differs from a SV-1 System Interface Description which focuses on the System-to-System point-to-point interface, for which the Source System and Target System have an agreed upon interface. For the SvcV-1, the focus on the provider and the data provided is a Net-Centric Data Strategy tenet appropriate for a publish/subscribe pattern. This pattern is not the only type of service that can be captured in the SvcV-1. [1]
Sub-services may be identified in SvcV-1 to any level (i.e., depth) of decomposition the architect sees fit. The SvcV-1 may also identify the Physical Assets (e.g., Platforms) at which Resources are deployed, and optionally overlay Operational Activities and Locations that utilize those Resources. In many cases, an operational activity and locations depicted in an OV-2 Operational Resource Flow Description may well be the logical representation of the resource that is shown in SvcV-1. [1]
The intended usage of the SvcV-1 includes: [1]
- Definition of service concepts
- Definition of service options
- Service Resource Flow requirements capture
- Capability integration planning
- Service integration management
- Operational planning (capability and performer definition)
The SvcV-1 is used in two complementary ways: [1]
- Describe the Resource Flows exchanged between resources in the architecture.
- Describe a solution, or solution option, in terms of the components of capability and their physical integration on platforms and other facilities.
| DoDAF Viewpoint Matrix | |||||||||||||
| AV | 1 | 2 | |||||||||||
| CV | 1 | 2 | 3 | 4 | 5 | 6 | 7 | ||||||
| DIV | 1 | 2 | 3 | ||||||||||
| OV | 1 | 2 | 3 | 4 | 5a | 5b | 6a | 6b | 6c | ||||
| PV | 1 | 2 | 3 | ||||||||||
| SvcV | 1 | 2 | 3a | 3b | 4 | 5 | 6 | 7 | 8 | 9 | 10a | 10b | 10c |
| StdV | 1 | 2 | |||||||||||
| SV | 1 | 2 | 3 | 4 | 5a | 5b | 6 | 7 | 8 | 9 | 10a | 10b | 10c |
AcqTips:
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
- [1] DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal
Updated: 6/26/2018