The StVs are intended primarily to support the Capability Management process, which involves the management of a wide variety of issues associated with the development of military capability, including:
· Measurement of capability / effectiveness
· Capability Audit process including the identification of capability gaps and overlaps
· Development of capability goals and requirements
· Identification and management of cross-capability dependencies
· Balance of investment analyses including affordability constraints
· Management of the acquisition process and capability delivery
· Capability integration including integration across all the lines of development
These activities are undertaken largely by the ECC, but with major contributions being made by a number of other MOD organisations, including the Front Line Commands and the various branches responsible for operational concepts and doctrine.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| MODAF Overview of Strategic Views.pdf | application/pdf | 289.92 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
The MOD Architectural Framework (MODAF) is being developed as a critical enabler of NEC1, which enables improved interoperability and should realise significant cost avoidance benefits through improved efficiency of the MOD acquisition processes and reduction in the amount of rework required to deliver interoperability and integration. The full rationale behind the development of MODAF and its expected benefits are described in more detail within the MODAF PID and its associated business case.
MODAF will be based largely upon best practice, which for defence acquisition is mainly the US Department of Defense Architectural Framework2 (DODAF). However, DODAF was developed over a number of years to meet the needs, organisational structure, doctrine and acquisition processes of the US armed forces and as a consequence is not always ideally suited to MOD needs. Therefore, although many DODAF views will be used as-is, some are likely to be dropped, as mandatory views at least, and others added to supplement the needs of the MOD processes and lifecycle.