Ministry of Defence Architectural Framework (MODAF) - PowerPoint PPT Presentation

1 / 31
About This Presentation
Title:

Ministry of Defence Architectural Framework (MODAF)

Description:

Ministry of Defence Architectural Framework (MODAF) Institute of Electrical Engineers Commander Bill Biggs Royal Navy 17th February 2005 Why Enterprise Architecture? – PowerPoint PPT presentation

Number of Views:171
Avg rating:3.0/5.0
Slides: 32
Provided by: ia1dand
Category:

less

Transcript and Presenter's Notes

Title: Ministry of Defence Architectural Framework (MODAF)


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

2
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 FBIs
    Trilogy Information Technology Modernization
    Program, Computer Science and Telecommunications
    Board, National Academies Press, Washington,
    D.C., 2004

3
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

4
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

5
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

6
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
    BISAs.
  • 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.

7
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 200203 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 MoDs failure to invest enough money and
    time to sufficiently de-risk projects in the
    Assessment Phase.

8
Architectures and Architectural Frameworks
  • 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

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

11
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
12
Harmonising multiple perspectives
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
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

15
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

16
Outline MODAF Concept of Use
(AcquisitionProcesses)
Capability Management
StV
SCV-2 SCV-3 SCV-4
CRD
17
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

18
Development of MODAF
Initial views consensus work on meta-model
Initial MARS paper selection of XMI
MODAF
View Development
Full piloting
MODAF validation
Meta-model update XMI MARS update
19
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

20
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

21
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

22
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

23
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
24
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

25
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

26
MODAF Meta Model (M3) UML
Meta Object Facility (MOF)
UML 2 Meta-Model
SysML Profile
M3 Profile
27
Example
28
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

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

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

31
Ministry of DefenceArchitectural
Framework(MODAF)
  • Institute of Electrical Engineers
  • Commander Bill Biggs Royal Navy
  • 17th February 2005
Write a Comment
User Comments (0)
About PowerShow.com