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

3. Introduction

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

5. MODEM is a descendent of work within the IDEAS group (International Defence Enterprise Architecture Specification)
: 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.

6. Why did we start?

7. For whom do we do it?

8. ISAF Contributing nations

9. Something about frameworks

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

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

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

13. There are a lot of different frameworks and standards
TOGAF
NAF 3.1
DoDAF v1.5
UPDM
SoaML
OASIS
DoDAF 2.0

14. Framework timeline
MODAF 1.0
MODAF 1.1
NAF 3.0
UPDM 1.0
DoDAF 1.0
DoDAF 1.5
MODAF 1.2
NAF 3.1
NAF 2.0
DoDAF 2.0
C4ISR 2.0
UPDM 2.0
C4ISR 1.0
1996
1997
1998
2003
2004
2005
2006
2007
2008
2009
2010
2011

15. MODAF Stack Strategic (StV) Acquisition Service (SOV) (AcV) Standards
Re-useable specifications
& strategic governance
Strategic (StV)
Acquisition
(AcV)
Service (SOV)
Standards
(TV)
Logical architecture:
Scenarios, requirements, etc.
Operational (OV)
Physical Architecture - Solutions.
Systems (SV)
Block diagram © Model Futures 2008

16. Overview of MODAF Meta-Model

17. The benefits of a EA based on a meta-model that defines the types of elements that can be used in an architecture model

18. 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 architectural “sentences”.
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.

19. 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)

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

21. Semantic technology

22. 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
IDEAS
UML

23. Build upon what already exists
There is a significant investment in MODAF
Harvest the relevant features
Winnow out the irrelevant technical features

24. Building a semantic foundation
implicit semantics
From a semantic perspective, it is like an iceberg, with visible ‘explicit semantic’ and hidden ‘implicit semantics’.
M3 was designed as a UML profile.
The goal is to:
Peel off the implementation structure, and
Make the implicit semantics explicit
semantic
foundation M3
UML Profile
implementation structure
explicit semantics
As a result it has both implementation structure and (explicit) semantics

25. super-sub-type

26. Recovering the supersubtype semantic structure
MODEM
Need to harvest where it matches, and
Refine where it does not.

27. An example of formal semantics
A UML State Machine
Figure Protocol state machine” (p UML Superstructure Specification, v2.3)

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

29. Removing Implementation Structure Combining state machines

30. Removing Implementation Structure Sub-typing state machines

31. Building in a ‘clear’ real world semantics
IDEAS
Real
World
UML
Formal

32. Patterns

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

34. Architect: I have a need to show roads that overlap as part of my architecture model

35. Architect: The actual intersection is of special interest

36. Tool support for EA

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

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

39. MOD statement and conclusions

40. MOD STATEMENT OF INTENT FOR THE IMPLEMENTATION OF MODEM
Patrick Gorman
Assistant Head Architecture Framework
MOD CIO

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

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

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

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

45. More details concerning MODEM can be found at:
SwAF-MODEM-Behaviour Analysis Report - March 2011.pdf