Presentation on theme: "HEADQUARTERS MODEM Building a Semantic Foundation for EA: Reengineering the MODAF Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo,"— Presentation transcript:
HEADQUARTERS MODEM Building a Semantic Foundation for EA: Reengineering the MODAF Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo, Swedish Armed Forces Lars-Olof Kihlström, Generic Systems Sweden AB, Ian Bailey, Model Futures Limited, Chris Partridge, BORO Solutions Limited
HEADQUARTERS Introduction MODEM is an enterprise architecture framework that provides a vocabulary for describing an enterprise, its structure as well as its behaviour in a unified manner. There are several architecture frameworks and this presentation starts with a brief description of how they relate to one another and how they differ. MODEM is an evolution of the framework definied by the Ministry of Defence in the UK called MODAF. The reengineering effort adds value since the semantics of the elements within the framework end up being defined properly, thereby enabling exchange of architecture models. MODEM is based on work performed by the IDEAS group.
HEADQUARTERS MODEM is a descendent of work within the IDEAS group (International Defence Enterprise Architecture Specification) 2005-2009: Development of a Model (IDEAS Foundation) for Coalition Architecture Interoperability. IDEAS is based on semantics in order to deal with semantic heterogeneity between the nations national Architecture Frameworks by the use of an approach based on Business Objects Reference Ontology (BORO) Methodology. IDEAS Foundation has been exploited by US DoD for DODAF 2. MODEM (MODAF Ontological Data Exchange Model) is the result of a Swedish led effort within IDEAS aiming for an evolution of M3 by exploiting the IDEAS foundation.
HEADQUARTERS Defence Enterprise Architecture Military operations are complex – Large, hierarchical organisations – Small, agile organisations – Thousands of interacting processes – Complex, data-intensive systems Enterprise architecture provides a way to plan and organise information about: – Structures – Behaviour – Capability Image Crown Copyright
HEADQUARTERS EA is Just Diagrams, Right ? First generation enterprise architecture really was just about pictures Things have moved on since then – EA is now considered a decision-support tool – Providing the right information, at the right level of abstraction to business and technical stakeholders The frameworks have had to adapt accordingly – Increasing use of meta-models – Some are even looking at ontologies
HEADQUARTERS MODAF The UK Ministry of Defence Architecture Framework – Originally based on DoDAF – MODAF extensions now adopted by DoDAF – NATO Architecture Framework *is* MODAF MODAF Meta-Model (M3) – An extension of the UML 2.1 Meta-Model – i.e. a UML profile
HEADQUARTERS There are a lot of different frameworks and standards TOGAFNAF 3.1DoDAF v1.5 UPDM SoaML OASIS DoDAF 2.0
HEADQUARTERS The benefits of a EA based on a meta- model that defines the types of elements that can be used in an architecture model
HEADQUARTERS What does a meta-model for an architecture framework provide? It could be said that the MODAF/ NAF/ UPDM meta-model provides a grammar for speaking architecture in accordance with a framework. It defines the type of words that may be used and how they can be combined (related) to form architecturalsentences. In the case of MODAF the meta-model was created using UML (Unified Modelling Language) where all types of elements to be used in an architecture model are extensions of standardised UML concepts.
HEADQUARTERS What does give us that MODAF M3 does not ? Consider the following text: 'Twas brillig, and the slithy toves Did gyre and gimble in the wabe; All mimsy were the borogoves, And the mome raths outgrabe. A portion of Jabberwocky: A poem by Lewis Carroll published as part of: Through the looking-glass, and what Alice found there (1872)
HEADQUARTERS An analogy..... While the grammar of the poem is sound, i.e. adjectives, nouns and verbs can be identified and they seem to relate to one another as they should, the meaning is less than clear. The difference between MODAF M3 and MODEM could be visualised by saying that in MODAF M3 the Jabberwocky poem would be accepted as correct as it only checks the grammar, whereas MODEM would also provide the semantic meaning.
HEADQUARTERS Building in a real world semantics The real problem in speech is not precise language. The problem is clear language. Richard Feynmann Formal Semantics Real World UML IDEAS
HEADQUARTERS There is a significant investment in MODAF Build upon what already exists Winnow out the irrelevant technical features Harvest the relevant features
HEADQUARTERS M3 UML Profile Building a semantic foundation M3 was designed as a UML profile. implementation structure explicit semantics As a result it has both implementation structure and (explicit) semantics implicit semantics From a semantic perspective, it is like an iceberg, with visible explicit semantic and hidden implicit semantics. The goal is to: Peel off the implementation structure, and Make the implicit semantics explicit semantic foundation
HEADQUARTERS MODEM Recovering the supersubtype semantic structure M3 Need to harvest where it matches, and Refine where it does not.
HEADQUARTERS An example of formal semantics Figure 15.12 - Protocol state machine (p. 552 - UML Superstructure Specification, v2.3) A UML State Machine
HEADQUARTERS What is state in the real world? You can know the name of a bird in all the languages of the world, but when you're finished, you'll know absolutely nothing whatever about the bird... So let's look at the bird and see what it's doing that's what counts. I learned very early the difference between knowing the name of something and knowing something. Richard Feynmann
HEADQUARTERS Removing Implementation Structure Combining state machines
HEADQUARTERS Removing Implementation Structure Sub-typing state machines
HEADQUARTERS Building in a clear real world semantics Formal Semantics Real World UML IDEAS
HEADQUARTERS MODEM relies heavily on the use of patterns The basic set of patterns include: –Overlap and intersection –Behaviour –Agent –Process –Exchange These patterns are then specialised in order to be used in a variety of places, some examples are shown here.
HEADQUARTERS Architect: I have a need to show roads that overlap as part of my architecture model
HEADQUARTERS Architect: The actual intersection is of special interest
HEADQUARTERS So why is MODEM needed? Current tool and architecture framework use situation Different tools are used in different domains. GenEA: General EA tools (ARIS, MEGA, SA, MooD etc.) UML tools with EA plugins (Magic Draw, Sparx, Rhapsody, Artisan etc.) They are islands on their own with no direct communication in between tools. They can not be used to enhance each other. Implementation Specification Strategy and planning Operational processes GenEA a UML EA a UML EA b UML EA c UML EA d UML EA e GenEA b GenEA c GenEA d GenEA e
HEADQUARTERS Possible tool situation based on MODEM A seamless transfer between tools without importing other tool conventions can be achieved if they are based on MODEM as an underlying basis. This will expand the usage as well as market for all tools. The interconnection ability will dramatically increase the use of each tool. The strengths of the different tools can be used to enhance the overall use of all tools. This will provide an benefits to all areas of use and to all tools. MODEM basis Implementation Specification Strategy and planning Operational processes GenEA a UML EA a UML EA b UML EA c UML EA d UML EA e GenEA b GenEA c GenEA d GenEA e e.g. RDF
Chief Information Officer MOD STATEMENT OF INTENT FOR THE IMPLEMENTATION OF MODEM Patrick Gorman Assistant Head Architecture Framework MOD CIO
Future MODAF – What We Want To Do On completion of MODEM (c. Sep 2012): Look to retire M3 Update Policy for use of: UPDM2 (UML / SysML Tools) MODEM (Non-UML Tools) Ensure alignment of MODEM and UPDM Offer MODEM to NATO to support convergence of frameworks
Future MODAF – What We Need To Do To Get There Primarily Stakeholder Engagement: UK Defence Stakeholders – MOD and Partners. Software Tool Vendors. NATO and Nations.
HEADQUARTERS The MODEM re-engineering aims to: Harvest the relevant semantic features of UML and the MODAF meta-model and migrate them to MODEM, Winnow out the irrelevant technical implementation features – particularly the constraints that were stove piping the UML meta-model and the MODAF meta-model built upon it, Provide a clearer picture of the enterprise – one which reveals the common underlying business patterns across what previously appeared as very different areas, and Provide a migration path for the existing MODAF models.
HEADQUARTERS Rationale on one slide MODEM has been developed to be used by the tool vendors in order to create a means of unification, reusability and exchange of architectural artefacts between different tools. MODEM is an evolution of M3 based on IDEAS work. MODEM will, together with the national architecture frameworks in the IDEAS nations, be a building block for a future common defence standard. NATO is invited to make use of MODEM for NAF. MODEM is not in not in any way defence specific and thus not limited to defence use only.
HEADQUARTERS More details concerning MODEM can be found at: http://www.borosolutions.co.uk/research/content/files/ SwAF-MODEM-Behaviour Analysis Report - March 2011.pdfhttp://www.borosolutions.co.uk/research/content/files/ http://dl.dropbox.com/u/823291/MODAF_M3_and_IDEAS_integration_phase%201%20and%202%20version_1.00.pdf http://dl.dropbox.com/u/823291/MODAF_M3_and_IDEAS_integration_examplification_version_1.00.pdf