About Defence

MODAF – Guidance

Documentation supporting the MOD Architecture Framework (MODAF).

Team announcement

This site replaces www.modaf.org.uk. We are keen to ensure that this new site is as user-friendly and useful as possible. Please e-mail any comments or suggestions for improving this site to the contact address shown.
MOD Architecture Framework

MOD Architecture Framework

Looking for guidance on MODAF? Below is an overview and guidance on MODAF.

From here you can navigate back to the home page or down for more information.

Guidance on MODAF

MODAF provides a coherent set of rules and templates, known as Views that, when populated, provide a graphical and textual visualisation of the business area being investigated. Each View offers a different perspective on the business to support different stakeholder interests. The Views are divided into seven categories:

  • Strategic Views (StVs) define the desired business outcome, and what capabilities are required to achieve it
  • Operational Views (OVs) define (in abstract rather than physical terms) the processes, information and entities needed to fulfil the capability requirements
  • Service Oriented Views (SOVs) describe the services, (i.e. units of work supplied by providers to consumers), required to support the processes described in the operational Views
  • Systems Views (SVs) describe the physical implementation of the Operational and Service Orientated Views and, thereby, define the solution
  • Acquisition Views (AcVs) describe the dependencies and timelines of the projects that will deliver the solution
  • Technical Views (TVs) define the standards that are to be applied to the solution
  • All Views (AVs) provide a description and glossary of the contents of the architecture

To ensure the coherence between the Views, MODAF is underpinned by a model which defines the relationship between all the data in all the Views. This model is called the MODAF Meta Model, also known as the "M3". The M3 also provides a technical standard to enable the exchange of data between architectures developed in different modelling (software) applications.

MODAF supports the application of rigour to requirements capture

The use of MODAF provides a de-facto element of rigour to requirements capture because the population of the Views requires the application of a structured analytical approach that leads the user from desired outcome to solution options.

MODAF supports the modelling of options

There are a number of commercially available tools that support the use of MODAF. As well as allowing the presentation of the Views, these tools also provide a repository in which the architecture can be stored and enable the modelling of different change options to support decision making.

MODAF supports interoperability

The use of MODAF as the standard architecture framework enables the coherent sharing of architectural information which helps identify gaps and overlaps between operating processes and the systems that support them.

MODAF has pedigree

MODAF was developed by MOD from the US Department of Defense Architecture Framework (DoDAF) version 1.0, but has been extended and modified to meet MOD requirements. MODAF is now itself internationally recognised as a best practice for enterprise architecting, and provided the template against which NATO Architecture Framework version 3.0 was developed.

MODAF has been adopted by organisations outside MOD

As well as MOD, MODAF is widely used by its industry partners, such as BAE Systems, Thales, Lockheed Martin, Boeing and Serco. It is also used by other government departments, such as GCHQ, and external bodies, such as the National Air Traffic Services. MODAF was recently adopted for use by the Swedish Armed Forces.


 





MODAF Version History

Aug 2005 - MODAF V1.0 Released

Apr 2007 - MODAF V1.1 Released

Apr 2008 - MODAF V1.2.003 Released

May 2010 - MODAF V1.2.004 Released

Page rated 31 times
This page has an average rating of 1/5