Jump to content

MODAF

Edit links
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 67.98.115.178 (talk) at 14:35, 1 May 2007. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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. As of 10th April 2007, MODAF version 1.1 was released. 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.

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 (Lines of Development / DOTMLPF) and programmatic aspects such as project dependencies.

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) - see http://www.modaf.org.uk/m3. 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.

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 architecting 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 architecting activities across Defence.

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 and 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.

Viewpoints and Views

A MODAF model is organised into six viewpoints:

All Viewpoint (AV)

The All Viewpoint (AV) consists of views that provide information pertinent to the entire architecture. They represent supporting information rather than architectural models.

  • AV-1 -- Overview and Summary Information
  • AV-2 -- Integrated Dictionary

Strategic Viewpoint (StV)

The Strategic Viewpoint (StV) consists of views that articulate high level requirements for enterprise change over time - capabilities, goals and enduring tasks.

  • StV-1 -- Enterprise Vision
  • StV-2 -- Capability Taxonomy
  • StV-3 -- Capability Phasing
  • StV-4 -- Capability Dependencies
  • StV-5 -- Capability to Organisation Deployment Mapping
  • StV-6 -- Operational Activity to Capability

Operational Viewpoint (OV)

The Operational Viewpoint (OV) consists of views that describe the tasks and activities, operational elements, and information exchanges required to conduct operations.

  • OV-1a -- High Level Operational Concept Graphic
  • OV-1b -- Operational Concept Description
  • OV-1c -- Operational Performance Attributes
  • OV-2 -- Operational Node Relationships Description
  • OV-3 -- Operational Information Exchange Matrix
  • OV-4 -- Organisational Relationships Chart
  • OV-5 -- Operational Activity Model
  • OV-6a -- Operational Rules Model
  • OV-6b -- Operational State Transition Description
  • OV-6c -- Operational Event Trace Description
  • OV-7 -- Information Model

System Viewpoint (SV)

The System Viewpoint (SV) consists of views that articulate the solution specification - resources, functions and interactions. The System Views in MODAF Version 1.1 are now, in the most part, significantly changed from DoDAF. In particular, they specifically allow for human factors in solution specifications, rather than only depicting technical systems.

  • SV-1 -- Resource Interaction Specification
  • SV-2a -- System Port Specification
  • SV-2b -- System Port Connectivity Description
  • SV-2c -- System Connectivity Clusters
  • SV-3 -- Resource Interaction Matrix
  • SV-4 -- Functionality Description
  • SV-5 -- Function to Operational Activity Traceability Matrix
  • SV-6 -- Systems Data Exchange Matrix
  • SV-7 -- Resource Performance Parameters Matrix
  • SV-8 -- Capability Configuration Management
  • SV-9 -- Technology and Skills Forecast
  • SV-10a -- Resource Constraints Specification
  • SV-10b -- Resource State Transition Description
  • SV-10c -- Resource Event-Trace Description
  • SV-11 -- Physical Schema


Technical Standards Viewpoint (TV)

The Technical Standards Viewpoint (TV) consists of views that articulate policy, standards, guidance, constraints and forecasts.

  • TV-1 -- Technical Standards Profile
  • TV-2 -- Technical Standards Forecast

Acquisition Viewpoint (AcV)

The Acquisition Viewpoint (AcV) consists of views that describe programmatic details, including dependencies between projects and capability integration across all the DLODs. These views guide the acquisition and fielding processes.

  • AcV-1 -- Acquisition Clusters
  • AcV-2 -- Programme Timelines

Origins

MODAF is based on the US Department of Defense Architectural Framework (DoDAF), extending it by two additional viewpoints - strategic and acquisition. The MODAF CoI deskbooks provide lists of views that individual communities would be particularly interested in.

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.

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.

Retrieved from "https://en.wikipedia.org/w/index.php?title=MODAF&oldid=127425753"