Product Detailed Description - The TV-1 view consists of the set of Systems, Standards, and Rules that govern systems implementation and operation of that architecture. MODAF does not set or impose new or revised Standards; it simply represents the extant Standards, Rules, Doctrine and Policies in a coherent manner.
The technical standards govern what hardware and software may be implemented and on what system. Identified standards may require tailoring to fulfill the needs of the system being represented within the architectural framework; this tailoring is called creating a Standards Profile.
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 should 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).
Replaced/Superseded by document(s)
|File||MIME type||Size (KB)||Language||Download|
|MODAF White Paper on Technical View 1.pdf||application/pdf||56.25 KB||English||DOWNLOAD!|
The purpose of this paper is to describe the initial content and layout of the Technical Standards Profile (TV-1) view in a way, which would allow peer review from stakeholders. With the exception of this section, the rest of the paper follows the layout of the DODAF volume II document. The intention is that this format will be retained and used in the final MODAF documentation, currently scheduled for publication in July 2005.
The MOD Architecture Framework (MODAF) is being developed with the intention of providing a rigorous way to specify systems of systems, and is a key enabler to NEC1. The framework will predominantly be used for acquisition purposes, and a key driver for its adoption is the need to improve interoperability between systems. However, the MODAF could equally well be used to analyse existing, operational systems and better enable their integration with other systems (both new and existing).
An architectural framework defines a set of key business and technical information for describing a system of systems architecture. The purpose of an architectural framework is to define the operational context (organizations, locations, processes, information flows, etc.), the system architecture (interfaces, data specifications, protocols, etc.), and the supporting standards and documents that are necessary to describe the system of systems. The information presented in an architectural framework is split into logical groupings – usually known as views. The same system and business elements may be present in more than one view, but the purpose of each view is different and so each provides a different viewpoint on the information.