Institute Of Electrical Engineers

645 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
645
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
22
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Institute Of Electrical Engineers

  1. 1. Ministry of Defence Architectural Framework (MODAF) Institute of Electrical Engineers Commander Bill Biggs Royal Navy 17th February 2005
  2. 2. Why Enterprise Architecture? <ul><li>“ 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.” </li></ul><ul><li>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 </li></ul>
  3. 3. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  4. 4. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  5. 5. <ul><li>“ 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.” </li></ul><ul><li>General Fulton, CM(IS), July 2002 </li></ul><ul><li>NEC is about joining up the business and battlespace </li></ul><ul><li>Enables us to federate systems, sensors, effectors and hence improve military effectiveness </li></ul>Network Enabled Capability
  6. 6. What is wrong with current situation? <ul><li>Life has become too complicated for ad-hoc acquisition. </li></ul><ul><ul><li>Projects and programmes now link and overlap. </li></ul></ul><ul><ul><li>Multiple operational, technical and service boundaries emerging, which must be managed coherently. </li></ul></ul><ul><ul><li>Overlapping functionality in subsystems, eg BISA’s. </li></ul></ul><ul><li>The GII – not to mention NEC – requires key end-to-end properties to be assured whilst delivering “more for less” </li></ul><ul><ul><li>Security, safety, performance, scalability, ease of upgrade. </li></ul></ul><ul><li>Without change, we run the risk: </li></ul><ul><ul><li>at best of inefficiency - project activities wrongly phased, reproduced or repeated. </li></ul></ul><ul><ul><li>at worst of major performance gaps overlooked, or emerging late in acquisition, requiring expensive remedial action. </li></ul></ul>
  7. 7. … and we could improve acquisition <ul><li>House of Commons Defence Committee </li></ul><ul><li>Defence Procurement, Sixth report of session 2003-04 </li></ul><ul><li>“ The performance of the Defence Procurement Agency in 2002–03 can only be described as woeful.” </li></ul><ul><li>“ 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.” </li></ul><ul><li>“… 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.” </li></ul>
  8. 8. Architectures and Architectural Frameworks <ul><li>Architectures: </li></ul><ul><li>“ A formal description of a system … at component level to guide its implementation” </li></ul><ul><li>“ The structure of components and their interrelationships” </li></ul><ul><li>A set of views that describe system(s) of interest at a certain point in time </li></ul><ul><li>Architectural Frameworks: </li></ul><ul><li>“ A tool which can be used for developing a broad range of different architectures.” </li></ul><ul><li>“ Provides a common vocabulary” </li></ul><ul><li>Provides a basis for comparing and analysing architectures </li></ul>
  9. 9. Why are we using MODAF? <ul><li>By providing a common “language” to describe MoD business it: </li></ul><ul><ul><li>Gives a means of managing across all lines of development / through life </li></ul></ul><ul><ul><li>Allows the identification of overlap, duplication, gaps </li></ul></ul><ul><ul><li>Enables unambiguous requirements that enhance interoperability </li></ul></ul><ul><ul><li>Provides commonality and rigour to MoD processes </li></ul></ul><ul><ul><li>Provides improved contextual information on the systems to the approving authorities </li></ul></ul><ul><li>All of which allow more efficient use of the budget and delivery of enhanced capability </li></ul>Essential enabler for NEC
  10. 10. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  11. 11. Foundations of MoD Architecture MODAF Object Taxonomy MODAF Meta Model Enterprise Architecture Style guide for building architectures Language for describing EA and its elements Meta-data for categorising EA elements
  12. 12. Harmonising multiple perspectives
  13. 13. 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:
  14. 14. MODAF Views <ul><li>MODAF is based upon DoDAF but with tailoring to MoD lifecycle / processes and as a result of US and UK lessons learned </li></ul><ul><li>Most DoDAF views will be incorporated largely as-is with tailoring to MoD terminology, ERM, etc </li></ul><ul><li>Some DoDAF views may be modified to incorporate lessons learned </li></ul><ul><li>Two new viewpoints included: </li></ul><ul><ul><li>Strategic Views – mainly support capability management </li></ul></ul><ul><ul><li>Acquisition Views – support the acquisition lifecycle </li></ul></ul>
  15. 15. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  16. 16. Outline MODAF Concept of Use CRD StV SCV-2 SCV-3 SCV-4 … Capability Management (Acquisition Processes) Assurance CIP Fielding TV TV-1 TV-2 Gap NEC Use Cases SAG Scenarios IERs … OV Use Cases OV-1 OV-2 OV-3 … URD User Requirements ARP TDPs Research & Technology SRD SV AcV SV-1 SV-2 SV-3 … SV-8 SV-9 AcV-2 Acquisition JSP DEF STAN STANAG ISO … Standards Architecture Repository Architecture Coordination
  17. 17. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  18. 18. Development of MODAF Initial views & consensus work on meta-model Initial MARS paper & selection of XMI View Development Meta-model update XMI & MARS update MODAF validation Full piloting MODAF
  19. 19. MODAF Development <ul><li>Will utilise existing DoDAF products where possible </li></ul><ul><li>Similar documentation approach to DoDAF –executive summary, handbook, desk book </li></ul><ul><li>Will develop progressively with multi-stage stakeholder reviews to minimise surprises and volume of new material at each stage </li></ul><ul><li>Using white papers as discussion documents prior to integrating the full MODAF product set </li></ul>
  20. 20. <ul><li>Central equipment customer is overall project manager </li></ul><ul><li>Core funding for framework, enablers and aspects of governance </li></ul><ul><li>Training & population activity costs outside scope </li></ul><ul><li>Federated approach to change </li></ul><ul><li>Approved target is validated MODAF by Jun 05 </li></ul>MODAF Change Programme
  21. 21. <ul><li>Validation of framework and enabling elements </li></ul><ul><li>Testing the ease of implementing MODAF views </li></ul><ul><li>Understanding the relationship between MODAF and project processes </li></ul><ul><li>Develop populated MODAF example views for use in COI Deskbooks </li></ul><ul><li>Proving tool interchange </li></ul><ul><li>Assess benefits realisation </li></ul>Piloting Objectives
  22. 22. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  23. 23. Enterprise Architecture Enterprise Architecture is a architectural, model-based approach to understanding, analysing and resolving enterprise issues Architectural, model-based approach MODAF Meta Model <ul><li>Consistent models </li></ul><ul><li>Rich diagrams and views </li></ul><ul><li>Integrated Repository </li></ul>EA queries & views understanding, analysing and resolving Good, focused modelling Better descriptions
  24. 24. <ul><li>Underlying architecture and consistency are key factors </li></ul><ul><li>20 of 33 views will have UML representation </li></ul><ul><li>Significant UML ‘back catalogue’ & user community </li></ul><ul><li>Choice of XMI for tool interchange </li></ul><ul><li>Majority of tool support will be UML based </li></ul><ul><li>International & industrial dimensions </li></ul>MODAF & UML/SysML
  25. 25. MODAF Meta Model <ul><li>SysML </li></ul><ul><ul><li>Modelling language for systems engineering </li></ul></ul><ul><ul><li>Key Concepts: </li></ul></ul><ul><ul><ul><li>Activity: concept for modelling behaviour </li></ul></ul></ul><ul><ul><ul><li>Assembly: concept for modelling structures which have behaviour </li></ul></ul></ul><ul><li>MODAF Meta Model </li></ul><ul><ul><li>Consistently models a complex system of systems </li></ul></ul><ul><ul><li>Extends SysML with concepts applicable to modelling an enterprise </li></ul></ul><ul><ul><li>Focused modelling of operational, system, implementation and programme viewpoints </li></ul></ul>
  26. 26. MODAF Meta Model (M 3 ) & UML Meta Object Facility (MOF) UML 2 Meta-Model SysML Profile M 3 Profile
  27. 27. Example
  28. 28. <ul><li>The business requirement for MODAF </li></ul><ul><li>MODAF explained </li></ul><ul><ul><li>What is it? </li></ul></ul><ul><ul><li>How will it work? </li></ul></ul><ul><ul><li>How is it being delivered? </li></ul></ul><ul><li>Architectural Modelling Language </li></ul><ul><li>Technical enablers for MODAF </li></ul>MODAF
  29. 29. <ul><li>Architectural Repository </li></ul><ul><li>M 3 & Toolset Interchange Mechanism </li></ul><ul><li>Taxonomy </li></ul><ul><li>Tool interchange & vendor support </li></ul>MODAF Dependencies
  30. 30. <ul><li>Business need & high level commitment strong </li></ul><ul><li>Intense development to date </li></ul><ul><li>Potent mix of AFs and UML </li></ul><ul><li>Plan for validated framework by Jun 05 with many more deliverables by April </li></ul><ul><li>More information from MODAF.com website. </li></ul>Conclusions
  31. 31. Ministry of Defence Architectural Framework (MODAF) Institute of Electrical Engineers Commander Bill Biggs Royal Navy 17th February 2005

×