Architectural Framework

Slides:



Advertisements
Similar presentations
Connected Health Framework
Advertisements

ARCHITECTURE FRAMEWORKS IN COMPLEX ENVIRONMENTS SIMPLIFYING THE MYSTERY OF I.T. SYSTEMS IN SMALL AND LARGE ENTERPRISES JOHN HODGSON, I.T. ARCHITECT.
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
Human Views for MODAF Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf of the Human Factors Integration Defence Technology Centre.
Human Factors Integration for MODAF: Needs and Solution Approaches Anne Bruseberg Systems Engineering & Assessment Ltd, UK (HFI DTC) Gavan Lintern General.
DoDAF V2.0 Community Update Overview
Session 6 Integrated Emergency Management. Objectives of the Session Students will be able to 6.1 Define the principle of integration. 6.2Discuss the.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Lecture 5 Themes in this session Building and managing the data warehouse Data extraction and transformation Technical issues.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Developing the MOD Architectural Framework IA ECC – Information Superiority Ministry of Defence Architectural Framework (MODAF) Institute of Electrical.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Network Enabled Capability Through Innovative Systems Engineering Service Oriented Integration of Systems for Military Capability Duncan Russell, Nik Looker,
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
The database development process
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
Opportunities & Implications for Turkish Organisations & Projects
Tool support for Enterprise Architecture in System Architect Architecture Practitioners Conference, Brussels David Harrison Senior Consultant, Popkin.
Extended Enterprise Architecture Framework (E2AF)
Enterprise Architecture
OMG UML Profile for the DoD and MoD Architecture Frameworks (UPDM) Dwayne Hardy American Systems Jan 30, 2007.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Developing Enterprise Architecture
An Introduction to the new features in TOGAF® 9
Ontologies Reasoning Components Agents Simulations The Eclipse Process Framework Breno Machado.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
The Challenge of IT-Business Alignment
Architecture Ecosystem Foundation (AEF) RFP aesig/ Draft RFP Presentation June 2010.
Introduction to MDA (Model Driven Architecture) CYT.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Software Engineering - I
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
12-CRS-0106 REVISED 8 FEB 2013 APO (Align, Plan and Organise)
 To explain why the context of a system should be modelled as part of the RE process  To describe behavioural modelling, data modelling and object modelling.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures. Core Concepts Key Learning Points: This chapter will help you to answer the following questions: What are the ADM phase names.
Basic Concepts Key Learning Points : The objectives of this chapter are as follows:  To provide an introduction to the basic Concepts of enterprise architectures,
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
® IBM Software Group © 2009 IBM Corporation Viewpoints and Views in SysML Dr Graham Bleakley
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Training Objectives Obtain knowledge of the ITIL terminology, structure and basic concepts and to comprehend the core principles of ITIL practices To.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Process 4 Hours.
Discussion Topics for Exploring OMG UPDM Way-ahead
What is Enterprise Architecture?
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Introduction to MODEM Building a Semantic Foundation for EA: Reengineering the MODAF™ Meta-Model Based on the IDEAS Foundation Model Lt Col Mikael Hagenbo,
The Systems Engineering Context
Abstract descriptions of systems whose requirements are being analysed
The Open Group Architecture Framework (TOGAF)
Enterprise Data Model Enterprise Architecture approach Insights on application for through-life collaboration 2018 – E. Jesson.
Systems Architecture & Design Lecture 3 Architecture Frameworks
Portfolio, Programme and Project
CORE Name: CORE® Description:
Presentation transcript:

Architectural Framework

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 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 View 2. Strategic View 3.Program Management/Control View 4.Solution View

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

MODAF v. 1.1 (6 Viewpoints, 38 Views)

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.” NEC is about joining up the business and battlespace Enables us to federate systems, sensors, effectors and hence improve military effectiveness

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

Organisational Resource MODAF Meta-Model: New Capability Deployment Capability Configuration Physical Asset Organisational Resource configured with Standard subject to doctrine hosted on System owns deployed to Node realised by Operational Activity Function has supports Role is assigned operates conducts

HV-B: Quality Objectives and Metrics (example)

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 “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? 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

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

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

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

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

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

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

Development Cycle .... 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

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

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 Better descriptions Consistent models Rich diagrams and views Integrated Repository understanding, analysing and resolving EA queries & views

MODAF Meta Model SysML MODAF Meta Model 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

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