Ministry of Defence Architectural Framework (MODAF)

Ministry of DefenceArchitectural Framework(MODAF) Institute of Electrical Engineers Commander Bill Biggs Royal Navy 17th February 2005

Why Enterprise Architecture? “The committee believes that the absence of an enterprise architecture has been a major contributor to the problems faced by the implementers of the [FBI's] Trilogy program. That is, the lack of an architecture to guide the planning of an information and communication infrastructure has resulted in improvisation that has virtually no chance of resulting in a well-ordered infrastructure for the enterprise to build upon. In fact, merely providing parts (e.g., computers and accessories, piece-part applications, and so on) is like buying brick, mortar, and lumber and expecting a builder to produce a functional building without benefit of building codes, blueprints, or an understanding of how people will use the building.” National Research Council, “A Review of the FBI’s Trilogy Information Technology Modernization Program”, Computer Science and Telecommunications Board, National Academies Press, Washington, D.C., 2004

MODAF • The business requirement for MODAF • MODAF explained • What is it? • How will it work? • How is it being delivered? • MODAF Meta Model • Technical enablers for MODAF

Network Enabled Capability • “NEC is the linking of sensors, decision makers and weapon systems so that information can be translated into synchronised and overwhelming military effect at optimum tempo.” General Fulton, CM(IS), July 2002 • NEC is about joining up the business and battlespace • Enables us to federate systems, sensors, effectors and hence improve military effectiveness

What is wrong with current situation? • Life has become too complicated for ad-hoc acquisition. • Projects and programmes now link and overlap. • Multiple operational, technical and service boundaries emerging, which must be managed coherently. • Overlapping functionality in subsystems, eg BISA’s. • The GII – not to mention NEC – requires key end-to-end properties to be assured whilst delivering “more for less” • Security, safety, performance, scalability, ease of upgrade. • Without change, we run the risk: • at best of inefficiency - project activities wrongly phased, reproduced or repeated. • at worst of major performance gaps overlooked, or emerging late in acquisition, requiring expensive remedial action.

… and we could improve acquisition House of Commons Defence Committee Defence Procurement, Sixth report of session 2003-04 “The performance of the Defence Procurement Agency in 2002–03 can only be described as woeful.” “The substantial in-year cost increases of some £3.1billion will have a major impact on the current equipment plan and must inevitably lead to cancellations or cuts in equipment projects, or delays in ordering equipment.” “…a key underlying cause of poor performance, in terms of delivering projects to time and cost, has been MoD’s failure to invest enough money and time to sufficiently de-risk projects in the Assessment Phase.”

Architectures: “A formal description of a system … at component level to guide its implementation” “The structure of components and their interrelationships” A set of views that describe system(s) of interest at a certain point in time Architectural Frameworks: “A tool which can be used for developing a broad range of different architectures.” “Provides a common vocabulary” Provides a basis for comparing and analysing architectures Architectures and Architectural Frameworks

Why are we using MODAF? • By providing a common “language” to describe MoD business it: • Gives a means of managing across all lines of development / through life • Allows the identification of overlap, duplication, gaps • Enables unambiguous requirements that enhance interoperability • Provides commonality and rigour to MoD processes • Provides improved contextual information on the systems to the approving authorities • All of which allow more efficient use of the budget and delivery of enhanced capability Essential enabler for NEC

Foundations of MoD Architecture MODAF Style guide for building architectures Enterprise Architecture MODAF Meta Model Object Taxonomy Language for describing EA and its elements Meta-data for categorising EA elements

Harmonising multiple perspectives

Architectural Framework - DoDAF “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time” Applied to the Enterprise across:

MODAF Views • MODAF is based upon DoDAF but with tailoring to MoD lifecycle / processes and as a result of US and UK lessons learned • Most DoDAF views will be incorporated largely as-is with tailoring to MoD terminology, ERM, etc • Some DoDAF views may be modified to incorporate lessons learned • Two new viewpoints included: • Strategic Views – mainly support capability management • Acquisition Views – support the acquisition lifecycle

NEC Use Cases SAG Scenarios IERs … Gap User Requirements Use Cases OV OV-1 OV-2 OV-3 … URD JSP DEF STAN STANAG ISO … Standards Assurance TV TV-1 TV-2 ARP SRD Acquisition Architecture Coordination SV-1 SV-2 SV-3 … SV-8 SV-9 Architecture Repository SV TDPs AcV Research & Technology AcV-2 CIP Fielding Outline MODAF Concept of Use (AcquisitionProcesses) Capability Management StV SCV-2 SCV-3 SCV-4 … CRD

Development of MODAF Initial views & consensus work on meta-model Initial MARS paper & selection of XMI MODAF Full piloting View Development MODAF validation Meta-model update XMI & MARS update

MODAF Development • Will utilise existing DoDAF products where possible • Similar documentation approach to DoDAF –executive summary, handbook, desk book • Will develop progressively with multi-stage stakeholder reviews to minimise surprises and volume of new material at each stage • Using white papers as discussion documents prior to integrating the full MODAF product set

MODAF Change Programme • Central equipment customer is overall project manager • Core funding for framework, enablers and aspects of governance • Training & population activity costs outside scope • Federated approach to change • Approved target is validated MODAF by Jun 05

Piloting Objectives • Validation of framework and enabling elements • Testing the ease of implementing MODAF views • Understanding the relationship between MODAF and project processes • Develop populated MODAF example views for use in COI Deskbooks • Proving tool interchange • Assess benefits realisation

Enterprise Architecture MODAF Meta Model Architectural, model-based approach Enterprise Architecture is a architectural, model-based approach to understanding, analysing and resolving enterprise issues Good, focused modelling • Consistent models • Rich diagrams and views • Integrated Repository Better descriptions understanding, analysing and resolving EA queries & views

MODAF & UML/SysML • Underlying architecture and consistency are key factors • 20 of 33 views will have UML representation • Significant UML ‘back catalogue’ & user community • Choice of XMI for tool interchange • Majority of tool support will be UML based • International & industrial dimensions

MODAF Meta Model • SysML • Modelling language for systems engineering • Key Concepts: • Activity: concept for modelling behaviour • Assembly: concept for modelling structures which have behaviour • MODAF Meta Model • Consistently models a complex system of systems • Extends SysML with concepts applicable to modelling an enterprise • Focused modelling of operational, system, implementation and programme viewpoints

MODAF Meta Model (M3) & UML Meta Object Facility (MOF) UML 2 Meta-Model SysML Profile M3 Profile

Example

MODAF • The business requirement for MODAF • MODAF explained • What is it? • How will it work? • How is it being delivered? • Architectural Modelling Language • Technical enablers for MODAF

MODAF Dependencies • Architectural Repository • M3 & Toolset Interchange Mechanism • Taxonomy • Tool interchange & vendor support

Conclusions • Business need & high level commitment strong • Intense development to date • Potent mix of AFs and UML • Plan for validated framework by Jun 05 with many more deliverables by April • More information from MODAF.com website.

Ministry of DefenceArchitectural Framework(MODAF) Institute of Electrical Engineers Commander Bill Biggs Royal Navy 17th February 2005

Ministry of Defence Architectural Framework (MODAF)