The System View (SV)-7 “Systems Measures Matrix” depicts the measures (metrics) of resources. The Systems Measures Matrix expands on the information presented in a SV-1 “Systems Interface Description” by depicting the characteristics of the resources in the SV-1.
The intended usage of the SV-7 includes:
- Definition of performance characteristics and measures (metrics).
- Identification of non-functional requirements.
The SV-7 specifies qualitative and quantitative measures (metrics) of resources; it specifies all of the measures. The measures are selected by the end user community and described by the architect. Performance parameters include all performance characteristics for which requirements can be developed and specifications defined. The complete set of performance parameters may not be known at the early stages of Architectural Description, so it is to be expected that this model is updated throughout the specification, design, development, testing, and possibly even its deployment and operations lifecycle phases. The performance characteristics are captured in the Measures Meta-model group.
One of the primary purposes of SV-7 is to communicate which measures are considered most crucial for the successful achievement of the mission goals assigned and how those performance parameters will be met. These particular measures can often be the deciding factors in acquisition and deployment decisions, and figures strongly in systems analysis and simulations done to support the acquisition decision processes and system design refinement. Measures of Effectiveness (MOE) and Measures of Performers (MOP) are measures that can be captured and presented in the Services Measures Matrix model.
The SV-7 is typically a table listing user defined measures (metrics) with a time period association. It is sometimes useful to analyze evolution by comparing measures (metrics) for current and future resources. For this reason, a hybrid SV-7 model which spans architectures across multiple phases may be useful.
- 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