Technical Standards Views (TV) [Standards Views]

TV-1 Standards Profile

TV-1 defines the technical and non-technical standards, guidance and policy applicable to the architecture.

As well as identifying applicable technical standards, TV-1 may document the policies and standards that apply to the operational or business context.

Note: the name of this MODAF view was changed from ‘Technical Standards Profile’ following the MODAF Technical Group meeting on 9 February 2007.

Background:

In most cases “building” an Architecture Profile will consist of identifying and listing the applicable portions of existing and emerging technical documentation. A TV-1 should identify both existing guidelines as well as any areas lacking guidance. As with other products, each profile is assigned a specific timescale (eg as-is, to-be or transitional). Linking the profile to a defined timescale allows the profile to consider both emerging technologies and any current technologies or standards that are expected to be updated or become obsolete. If more than one emerging standard time-period is applicable to your architecture, then you should complete a Standards Forecast (TV-2) as well as a TV-1.

Usage:

Data objects:

The data in an TV-1 can include:

Representation:

Detailed Product Description:

The Standards Profile (TV-1) collates the various systems, Standards and rules that implement and constrain the choices that can be made in the design and implementation of an Architectural Framework.

The TV-1 View delineates the systems, Standards and rules that apply to architectural implementations.


Example Standards Profile (Technical)

The TV-1 View consists of the set of systems, Standards, and rules that govern systems implementation and operation of that Architecture. 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 organisational specific standards such as a CONOP, a CONEMP or a CONUSE.


Example Standards Profile (Operational)

When 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 on a risk basis at an approval point.

Any Standards cited in TV-1 View shall, where appropriate, be in accordance with the trend towards open Architectures – i.e. standards which encourage stove-piped systems will not be used. Identified standards may require tailoring to fulfil the needs of the system being represented within the Architectural Framework; this tailoring is called creating a Standards Profile.

Note that an association between a Standard and an architectural element should not be interpreted as stating the element is fully compliant with that Standard. Further detail would need to be given (outside MODAF) 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 TV-1 View 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, system functions, system data, hardware/software items or communication protocols in SV-1, SV-2, SV-4, SV-6, OV-7, and SV-11 Products, where applicable. That is, each standard listed in the profile will be associated with the SV elements that implement or use the standard (e.g., SV-1, SV-2, SV-4, SV-6, OV-7 and SV-11 element standards, where applicable).

The Protocols referred to interface and communications descriptions (see SV-2) are examples of Standards and these should also be included in the TV-1 listing, irrespective of which views they appear in, or are referred from.

Page version 1.1, dated 4th April 2007

Top of Page