Architectural Framework. The business requirement for MODAF MODAF explained –What is it? –How...

Post on 12-Jan-2016

220 views 0 download

Tags:

Transcript of Architectural Framework. The business requirement for MODAF MODAF explained –What is it? –How...

Architectural Framework

Architectural Framework

• 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

MODAFMODAF

Why MoDAF

To Support Complex decision making process, may affect whole business.

What is MoDAF• Modaf is a specific set of views of an enterprise.

• MODAF provides a coherent set of rules and templates, known as Views, that, when populated, provide a graphical and textual visualisation of the business area being processing

• Architectural modellers who need guidance on the creation and interchange of MODAF views (including for example: architecting principles, view coherence rules and tool selection criteria)

• Each View offers a different perspective on the business to support different stakeholder interests.

The Views are divided into 7 categories:

• Strategic Views (StVs) define the desired business outcome, and what capabilities are required to achieve it

• Operational Views (OVs) define (in abstract rather than physical terms) the processes, information and entities needed to fulfil the capability requirements

• Service Oriented Views (SOVs) describe the services, (i.e. units of work supplied by providers to consumers), required to support the processes described in the operational Views

• Systems Views (SVs) describe the physical implementation of the Operational and Service Orientated Views and, thereby, define the solution

• Acquisition Views (AcVs) describe the dependencies and timelines of the projects that will deliver the solution

• Technical Views (TVs) define the standards that are to be applied to the solution

• All Views (AVs) provide a description and glossary of the contents of the architecture

...Enterprise Architecture

1. Business Process View2. Strategic View3.Program Management/Control View4.Solution View

• 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

MODAFMODAF

MODAF v. 1.1 (6 Viewpoints, 38 Views)

• “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.”

• NEC is about joining up the business and battlespace

• Enables us to federate systems, sensors, effectors and hence improve military effectiveness

Network Enabled CapabilityNetwork Enabled Capability

Architecture characteristics

• Separation of component concerns• Generic: Conceptual Data Model / Meta Model• Instantiation: Logical and Physical Data Model • View: window/snapshot onto model• Architectural products• Viewpoints• Levels of abstraction

– Complexity– Requirements-solutions

MODAF SV-1

MODAF Meta-Model: New

Capability Deployment

CapabilityConfigurationCapability

Configuration

PhysicalAsset

PhysicalAsset

OrganisationalResource

OrganisationalResource

configured with

StandardStandard

subject todoctrine

hosted on

SystemSystem

owns

configured with

deployed to

NodeNode

realised by

OperationalActivity

OperationalActivity

FunctionFunctionhas

supports

RoleRole

is assigned

operates

conducts

HV-B: Quality Objectives and Metrics (example)

Problems incurrent situation?Problems incurrent situation?• 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.

• Without change, we run the risk:– Advantage of inefficiency - project activities

wrongly phased, reproduced or repeated.– Dis-Advantage of major performance gaps

overlooked, or emerging late in acquisition, requiring expensive remedial action.

Architectures and Architectural Frameworks

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

Why are we using MODAF?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

• 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

MODAFMODAF

Foundations of MoD Architecture

Foundations of MoD Architecture

MODAF

Object Taxonom

y

MODAF Meta Model

Enterprise Architectur

e

Style guide for building

architectures

Language for describing EA and

its elements

Meta-data for categorising EA

elements

Architectural FrameworkArchitectural Framework

“the structure of components, their relationships, and the principles andguidelines governing their design and evolution over time”

MODAF ViewsMODAF 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

• 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

MODAFMODAF

• 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

MODAFMODAF

Initial views& consensus work on meta-model

Initial MARS paper& selection of XMI

View Development

Meta-model updateXMI & MARS update

MODAF validation

Full piloting

MODAF

Development Cycle ....Development Cycle ....

MODAF DevelopmentMODAF 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

• 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

MODAF Change ProgrammeMODAF Change Programme

• 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

MODAFMODAF

Enterprise Architecture

Enterprise Architecture is a architectural, model-based

approach to understanding, analysing and resolving

enterprise issues

Architectural, model-based approachArchitectural, model-based approach

MODAF Meta Model

• Consistent models• Rich diagrams and views• Integrated Repository

EA queries & views

understanding, analysing and resolvingunderstanding, analysing and resolving

Good, focused modelling

Better descriptions

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

MODAF Meta Model (M3) & UML

Meta Object Facility (MOF)

UML 2 Meta-Model

SysML Profile

M3 Profile

• 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

MODAFMODAF

• Architectural Repository• M3 & Toolset Interchange

Mechanism• Taxonomy• Tool interchange & vendor support

MODAF DependenciesMODAF Dependencies