DoDAF Viewpoints and Models
Standards Viewpoint
StdV-1: Standards Profile
The StdV-1 defines the technical, operational, and business standards, guidance, and policy applicable to the architecture being described. As well as identifying applicable technical standards, the DoDAF V2.0 StdV-1 also documents the policies and standards that apply to the operational or business context. The DISR is an architecture resource for technical standards that can be used in the generation of the StdV-1 and StdV-2 Standards Forecast.
In most cases, building a Standards Profile consists of identifying and listing the applicable portions of existing and emerging documentation. A StdV-1 should identify both existing guidelines, as well as any areas lacking guidance. As with other models, each profile is assigned a specific timescale (e.g., "As-Is", "To-Be", or transitional). Linking the profile to a defined timescale enables the profile to consider both emerging technologies and any current technical standards that are expected to be updated or become obsolete. If more than one emerging standard time-period is applicable to an architecture, then a StdV-2 Standards Forecast should be completed as well as a StdV-1.
The intended usage of the StdV-1 includes:
- Application of standards (informing project strategy).
- Standards compliance.
Detailed Description:
The StdV-1 collates the various systems and services, standards, and rules that implement and constrain the choices that can be or were made in the design and implementation of an Architectural Description. It delineates the systems, services, Standards, and rules that apply. The technical standards govern what hardware and software may be implemented and on what system. The standards that are cited may be international such as ISO standards, national standards, or organizational specific standards.
With associated standards with other elements of the architecture, a distinction is made between applicability and conformance. If a standard is applicable to a given architecture, that architecture need not be fully conformant with the standard. The degree of conformance to a given standard may be judged based on a risk assessment at each approval point.
Note that an association between a Standard and an architectural element should not be interpreted as indicating that the element is fully compliant with that Standard. Further detail would be needeed to confirm the level of compliance.
Standards Profiles for a particular architecture must maintain full compatibility with the root standards they have been derived from. In addition, the StdV-1 model may state a particular method of implementation for a Standard, as compliance with a Standard does not ensure interoperability. The Standards cited are referenced as relationships to the systems, services, system functions, service functions, system data, service data, hardware/software items or communication protocols, where applicable, in:
That is, each standard listed in the profile is associated with the elements that implement or use the standard.
The protocols referred to Resource Flow descriptions (see SV-2 Systems Resource Flow Description or SvcV-2 Services Resource Flow Description) are examples of Standards and these should also be included in the StdV-1 listing, irrespective of which models they appear in or are referred from.