The System View (SV)-1 “Systems Interface Description” addresses the composition and interaction of Systems. The SV-1 incorporates the human elements as types of Performers – Organizations and Personnel Types.
The SV-1 links together the operational and systems 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 SV-1 may represent the realization of a requirement specified in an OV-2 and so there may be many alternative SV models that could realize the operational requirement. Alternatively, in an “As-Is” architecture, the OV-2 may simply be a simplified, logical representation of the SV-1 to allow communication of key Resource Flows to non-technical stakeholders.
A System Resource Flow is a simplified representation of a pathway or network pattern, usually depicted graphically as a connector (i.e., a line with possible amplifying information). The SV-1 depicts all System Resource Flows between Systems that are of interest.
Sub-System assemblies may be identified in SV-1 to any level of decomposition the architect sees fit. SV-1 may also identify the Physical Assets 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 model may well be the logical representation of the resource that is shown in SV-1.
The intended usage of the SV-1 includes:
- Definition of System concepts.
- Definition of System options. System Resource Flow requirements capture.
- Capability integration planning.
- System integration management.
- Operational planning (capability and performer definition).
The SV-1 is used in two complementary ways:
- 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.
- 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:
-  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