| Modaf |
Articles about Modaf |
Information AboutModaf |
| CATEGORIES ABOUT MODAF | |
| enterprise architecture | |
|
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 IDEF 0, 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:
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. 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. 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. 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. SEE ALSO |
|
|