MODAF
From Wikipedia, the free encyclopedia
The UK Ministry of Defence Architectural Framework (MODAF) defines a standardised way of conducting Enterprise Architecture and provides a means to model, understand, analyze and specify Capabilities, Systems, Systems of Systems, and Business Processes. The purpose of MODAF is to provide a rigorous systems of systems definition when procuring and integrating defence systems. The latest revision as of 2 September 2008 is v1.2[1]. The documentation for MODAF and its meta-model can be found at http://www.modaf.org.uk. There is also a website serving the MODAF community at http://www.modaf.com, acting as the publication hub for the MODAF news and white papers.
Contents |
[edit] Scope
MODAF defines architectural views covering the strategic goals of the enterprise, and the people, processes and systems that deliver those goals. It also includes Capability Management (Defence Lines of Development, termed DLoDs in the UK, and DOTMLPF in the US) and programmatic aspects such as project dependencies.
[edit] Methodology & Models
There is no methodology associated with MODAF. Recommended practice is specified for five Communities of Interest (CoI) in the MODAF CoI Deskbooks. Neither does MODAF specify a modelling technique. For example, OV-5 products (activity models) could be represented as IDEF0, BPMN, UML Activity Diagrams, or any other commonly used process modelling syntax.
The key aspect of MODAF is that it encourages a data-driven approach to architecture. The specification is underpinned by the MODAF Meta-Model (M3)[2]. The M3 defines types of architectural elements and the relationships between them - e.g. organizations, operational nodes, systems, capabilities, etc. MODAF-compliant architectures are contiguous, coherent models of the enterprise which conform to the M3. The MODAF views are a set of standard specifications for presenting those architectures to different communities of interest.
[edit] Who Uses MODAF ?
Although originally developed by the UK Ministry of Defence, MODAF is the standard architecture framework for other organisations, such as:
- GCHQ
- Swedish Armed Forces
- National Air Traffic Services
- BAE Systems use MODAF on a number of internal programmes, most notably their TRAiDE environment
- EADS use MODAF as part of the Modelling and Simulation process for NetCOS their Synthetic Environment
- Thales Group use MODAF in their work for UK MOD
- Niteworks use MODAF extensively on problem solving and warfighter experimentation for the UK MOD
In addition, revision 3 of the NATO Architecture Framework (NAF) is identical to MODAF at its core, but extends the framework by adding views for Bandwidth Analysis, SOA and standard configurations.
[edit] Policy
MoD DG Info published a document on Enterprise Architecture Policy on 23rd Nov 2006. The document was endorsed by the DIRGE on January 2007 as policy, and in due course will be promulgated through the MoD DIN process. The MoD architectural approach is underpinned by the following policy statements:
- a. The delivery of architecture products to conform to MODAF.
- b. MODAF will be extended incrementally to support all formal architecture activities.
- c. Ownership and management of MODAF and its enablers (views, meta-model, controlled terminology and model exchange standards) resides in DG Info.
- d. DG Info will establish and manage a governance regime that includes representation from the user communities.
- e. MOD architectural design will take a federalist and tool-agnostic approach.
- f. Defence Process Owners (DPO) have responsibility for definition of boundaries, scope and baseline of their process and ensuring interfaces with other processes are managed appropriately.
- g. The policy also supports the delivery of MoD's NEC CIS Interoperability Assurance policy; DEC CCII, supported by the IA, will define across acquisition the operational and system of system boundaries so that the coherence of both requirement and solution can be assured.
- h. The IA is the lead for Interoperability and Compliance Assurance (IOCA) process and will specify architectural information required to support CIS interoperability assurance.
- i. DG Info will publish and maintain a view of architectural design activities across Defence.
[edit] Terminology
An "architectural framework" or "architecture framework" is a specification of how to organise and present architectural models. An architectural framework consists of a standard set of views, which each have a specific purpose.
An "architectural description" is a contiguous, coherent model of an enterprise. An architectural description comprises "architectural products". MODAF is not an architectural description.
A "view" is a specification of a way to present an aspect of the enterprise. Views are defined with one or more purposes in mind - e.g., showing the logical topology of the enterprise, describing a process model, defining a data model, etc.
An "architectural product" is a model of some aspect of the enterprise. An architectural product conforms to a "view"
A "viewpoint" is a collection of "views." Viewpoints are usually categorized by domain - e.g., in MODAF there are six viewpoints described below.
[edit] Viewpoints and Views
The MOD Architecture Framework has six viewpoints (categories of views), compared to DoDAF's four. For a detailed description of these views, see http://www.modaf.org.uk, the official MODAF site.
[edit] Origins
MODAF was originally based on the US Department of Defense Architectural Framework (DoDAF), extending it by two additional viewpoints - strategic and acquisition. The release of MODAF v1.1 has seen further changes - especially those emphasising the logical nature of the Operational Views. Although the original intent of DoDAF was that OVs were purely logical, the framework has not always been used in that way. Further changes in MODAF v1.1 introduced human aspects to the Systems views.
MODAF was initially developed for the MOD by MODAF Partners, a consortium of Cornwell Management Consulting (now Serco Group) and PA Consulting Group with Model Futures providing the technical input, and extended by other key suppliers such as Logica and Vega through work for the MoD Intergration Authority.
[edit] Representation of Views
MODAF does not mandate a particular notation for its views, however it does specify XMI 2.1 (for UML 2.0) as its standard for data exchange.
[edit] Primers, Tutorials & Training
An official MODAF Primer is currently being developed by the UK Ministry of Defence and Swedish Defence Materiel Administration. This should be available mid-2008.
modaf.com maintains a list of companies that provide MODAF training. This is by no means an exhaustive list, nor does it imply a recommendation for any of the companies - see http://www.modaf.com/Training.
[edit] Harmonization Between National Architecture Frameworks
There is an OMG effort to standardise a UML Profile for military architecture frameworks UPDM (UML Profile for DoDAF and MODAF). In addition, the IDEAS Group is a four nation (Australia, Canada, UK, USA + NATO as observers) effort to standardise a conceptual model for military architecture frameworks.
