MODAF

Configuration control

Configuration control policy and version history.

The MODAF documentation is version controlled. The link provides information on major, minor and editorial revisions.

Date: 3 Sep 09

Frequently asked questions

The following links provide information on ontologies and their use in the MOD Architecture Framework (MODAF), a glossary and abbreviations list and frequently asked questions.
Is there a MODAF manual?
Please be aware there is now a link under 'Related pages' to a PDF download version of this entire website, to act as a manual or reference guide fo the MODAF practitioner.

Date: 3 Sep 09

MODAF Meta Model

The MOD Architecture Framework (MODAF) Meta Model (M3) is the information model for MODAF, defining the structure of the underlying architectural information that is presented in the views. The goal is that MODAF tools are "model-driven" - ie the views that are presented to the user are snapshots of underlying architectural data which is stored in the tool or in a repository.

As well as an overview of the M3, there are three versions of the detailed M3 available to download in XMI, Sparx and HTML formats. For RLI users an online version of the M3 is provided under Applications & Tools/Information Policy & Services.
 
All of the below versions are links to v1.2.004 of the M3.

Date: 1 Sep 09

Use and examples of MODAF

General guidance for the architecting process and application of the MOD Architecture Framework (MODAF).

The MODAF Architecting Process
There are many different approaches to architecting which can be taken depending on the situation. MODAF does not prescribe an ‘official’ architecting process. 
However, for someone new to architecting with MODAF, some direction is helpful – this document suggests a way to go.

Uses and Examples
The other documents on this page present a number of examples of how MODAF can be used to support activities associated with the delivery of military capability.

Date: 27 Feb 09

Service oriented view (SOV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) Service Oriented View Viewpoint.

The Service-Oriented Views (SOVs) are a set of views that specify services that are to be used in a Service-Oriented Architecture (SOA). In MODAF terms, services are an implementation-independent specification of a packaged element of functionality. The views describe the specification of these services, how services are orchestrated together for a purpose, the capabilities that services deliver and how services are implemented. Note that the views do not focus on the detailed design of the service, rather on the requirement the service fulfils.

Date: 24 Feb 09

Acquisition view (AcV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) Acquisition View Viewpoint.

The Acquisition Views (AcVs) describe programmatic details, including dependencies between projects and capability integration across the Defence Lines of Development (DLODs). The Views identify interaction between programmes and projects, and integrate acquisition activities across all of the DLODs. The AcVs provide important programmatic information for those involved in capability management and acquisition. Since they also address the maturity across all of the DLODs to deliver an integrated military capability, the AcVs also form an important interface between the acquisition IPT and its Lead User community.

Date: 24 Feb 09

Technical standards view (TV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) Technical Standards View Viewpoint.

The Technical Standards Views (TVs) are tabular views containing standards, rules, policy and guidance applicable to aspects of the architecture. The contents of the TVs do not necessarily need to be of a technical nature and can apply just as much to operational activities (e.g.) doctrine, Standard Operating Procedures and Tactics, Techniques and Procdures) as they do to systems (e.g. standards and protocols). The content of TVs will come from a number of sources including the policy setting organisations in MOD and core interoperability standards from The Sponsor.

Date: 24 Feb 09

System view (SV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) System View Viewpoint.

The System Views (SVs) are a set of views that describe resources that realise capability. The Systems Views describe resource functions and interactions between resources and can also provide detailed system interface models. Note that these views address the involvement of humans in both the operation of systems and in carrying out functions in their own right. The SVs can be used to specify solutions to requirements specified in the Operational Viewpoints (OVs), or simply to provide more detail to the logical OV architecture.

Date: 24 Feb 09

Operational view (OV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) Operational View Viewpoint.

The Operational Views (OVs) define the logical aspects of the architecture. A suite of OV products may be used to describe a requirement for a to-be architecture in logical terms, or as a simplified description of the key behavioural and information aspects of an as-is architecture. The OVs re-use the capabilities defined in the StVs and put them in context of an operation or scenario. The OVs can be used at a number of points through the MOD lifecycle including the development of user requirements, capturing future concepts and supporting the operational planning process. A number of stakeholders will develop and exploit OVs during the MOD acquisition lifecycle.

More details on the OVs and Information Exchange Requirements (IERs) are contained in the document IERs in MODAF.

Date: 24 Feb 09

Strategic view (StV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) Strategic View Viewpoint.

Strategic Views (StVs) support the process of analysing and optimising the delivery of military capability in line with the MOD's strategic intent. The StVs achieve this by capturing the capability policy/concepts, decomposing this into a capability taxonomy supported by appropriate measures of effectiveness that can be used for capability audit and gap/overlap analysis.

Date: 24 Feb 09

All views (AV) viewpoint

A description of and guidance for the use of the MOD Architecture Framework (MODAF) All Views viewpoint.

The All Views (AVs) provide an overarching description of the architecture - its scope, ownership, timeframe and all of the other metadata that is required in order to effectively search and query architectural models. They also provide a place to record any findings arising from the architecturing process. The AVs include a dictionary of the terms used in the construction of the architecture - which helps others fully understand its meaning at a later date.

Date: 24 Feb 09

Views summary documents

Documents summarising the MOD Architecture Framework (MODAF) Views and Viewpoints.

View Summary is intended to help choose the most appropriate MODAF views. It provides a list of all views and details what each view is used for and what data elements they contain.

Layers and Viewpoint Linkages provides a top-level view of how MODAF views relate to each other.

There is also a downloadable version of the Viewpoints and Views homepage.

Date: 24 Feb 09