Enterprise architecture planning

Slides:



Advertisements
Similar presentations
Light Enterprise Architecture
Advertisements

An enterprise architecture (EA) Theory
Enterprise Architecture Planning Methodology - Implementation Steps - Tony Baker, MBA, CMC
Information Technology Project Management – Third Edition
Evolution of Parametric Analysis within Rolls-Royce Purchasing
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
Brief History of Architecture Frameworks
The Institute for Learning and Research Technology is a centre of excellence in the development and use of Information and Communication Technology to.
All Rights Reserved: JusticeExperts.com Enterprise? What Enterprise? Enterprise Development.
IT Planning.
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
The Use of Zachman Framework Primitives for Enterprise Modeling
© 2005 by Prentice Hall 1 Chapter 2: The Database Development Process Modern Database Management 7 th Edition George Lamperti.
1 Objective of today’s lesson S oftware engineering occurs as a consequence of a process called system engineering. Instead of concentrating solely on.
Enterprise Architecture
Certified Business Process Professional (CBPP®)
Introduction to Systems Analysis and Design
Certified Business Process Professional (CBPP®) Exam Overview
Software Engineer Report What should contains the report?!
Maine Course Pathways Maine School Superintendents’ Conference June 24 – 25, 2010.
3106 Use of UML 2.0 Diagrams for Systems Architecture Modeling Gundars Osvalds Systems of Systems Architect The Boeing Company.
Enterprise Architecture
Project Human Resource Management
IMA CIM Overview. IMA Mission “Provide a knowledge-sharing platform for business professionals where proven Internet.
SKILLS AUDITS The Skills Framework
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © 2013 Curt Hill Frameworks, Methodologies, Ontologies and Taxonomies Wasn’t that a mouthful?
Marketing Strategy and the Marketing Plan
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Acquiring Information Systems and Applications
Research & Technology Implementation TxDOT RTI OFFICE.
Enterprise Architecture Enterprise Architecture = a framework or ‘blueprint’ for how the organization achieves the business objectives at hand and in future.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Standards Certification Education & Training Publishing Conferences & Exhibits 1Copyright © 2006 ISA ISA-SP99: Security for Industrial Automation and Control.
Enterprise Architecture The EA 3 view Copyright © 2013 Curt Hill.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Systems Analysis and Design in a Changing World, Fourth Edition
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
EPA Enterprise Data Architecture Metadata Framework Assessment Kevin J. Kirby, Enterprise Data Architect EPA Enterprise Architecture Team
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Enterprise Architecture HOW COMPANIES ARE EXPLOITING INFORMATION TO THROUGH IT.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
1 Sobah Abbas Petersen Adjunct Associate Professor TDT4252 Modelling of Information Systems Advanced Course TDT4252, Spring 2011 Lecture.
Information Architecture The Open Group UDEF Project
Aligning Business Process Architecture and Enterprise Architecture: A Model Driven - Service Oriented Approach Chris Capadouca Business Solutions Architect.
How the CDC Enterprise Architecture Development Methodology Can Help You Albert Decker, Northrop Grumman John Fitzpatrick, CDC.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
Managing Enterprise Architecture
Managing Enterprise Architecture
Zachman Framework Lecture 2.
Project Planning: Scope and the Work Breakdown Structure
MANAGEMENT of INFORMATION SECURITY, Fifth Edition
CGS 2545: Database Concepts Fall 2010
Enterprise Architecture Planning
Identify the Risk of Not Doing BA
EIN 6133 Enterprise Engineering
ETOM Aryatama Wisnu Wardhana Vania Puspa Andari Febrianto Nugroho
The Open Group Architecture Framework (TOGAF)
Enterprise Architecture Methods
Regional Architecture Development for Intelligent Transportation
By Jeff Burklo, Director
CAF Quarterly Meeting Measuring the Value of an EA Practice
System architecture, Def.
IEEE Architecture Council Overview
Bridging the ITSM Information Gap
Presentation transcript:

Enterprise architecture planning SOFTWARE-rt

Enterprise Architecture Planning (EAP) in Enterprise Architecture is the planning process of defining architectures for the use of information in support of the business and the plan for implementing those architectures Overview One of the earlier professional practitioners in the field of system architecture Steven H. Spewak in 1998 defined Enterprise Architecture Planning (EAP) as "the process of defining architectures for the use of information in support of the business and the plan for implementing those architectures." Spewak’s approach to EAP is similar to that taken by DOE in that the business mission is the primary driver. That is followed by the data required to satisfy the mission, followed by the applications that are built using that data, and finally by the technology to implement the applications.[1] SOFTWARE-rt

This hierarchy of activity is represented in the figure above, in which the layers are implemented in order, from top to bottom. Based on the Business Systems Planning (BSP) approach developed by John Zachman, EAP takes a data-centric approach to architecture planning to provide data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. This view counters the more traditional view that applications should be defined before data needs are determined or provided for. SOFTWARE-rt

[edit] Zachman framework EAP topics [edit] Zachman framework EAP defines the blueprint for subsequent design and implementation and it places the planning/defining stages into a framework. It does not explain how to define the top two rows of the Zachman Framework in detail but for the sake of the planning exercise, abbreviates the analysis. The Zachman Framework provides the broad context for the description of the architecture layers, while EAP focuses on planning and managing the process of establishing the business alignment of the architectures.[2] SOFTWARE-rt

EAP is planning that focuses on the development of matrixes for comparing and analyzing data, applications, and technology. Most important, EAP produces an implementation plan. Within the Federal Enterprise Architecture, EAP will be completed segment enterprise by segment enterprise. The results of these efforts may be of Governmentwide value; therefore, as each segment completes EAP, the results will be published on the ArchitecturePlus web site. SOFTWARE-rt

Enterprise Architecture Planning model consists of four levels: EAP components Enterprise Architecture Planning model consists of four levels: Layer 1 - getting started : This layer leads to producing an EAP workplan and stresses the necessity of high-level management commitment to support and resource the subsequent six components (or steps) of the process. It consists of Planning Initiation, which covers in general, decisions on which methodology to use, who should be involved, what other support is required, and what toolset will be used.[2] SOFTWARE-rt

business processes, and Layer 2 - where we are today : This layer provides a baseline for defining the eventual architecture and the long-range migration plan. It consists of: Business process modeling, the compilation of a knowledge base about the business functions and the information used in conducting and supporting the various business processes, and Current Systems and Technology, the definition of current application systems and supporting technology platforms. SOFTWARE-rt

Layer 3 - the vision of where we want to be : The arrows delineate the basic definition process flow: data architecture, applications architecture, and technology architecture. It consists of: Data Architecture - Definition of the major kinds of data needed to support the business. Applications Architecture - Definition of the major kinds of applications needed to manage that data and support the business functions. Technology Architecture - Definition of the technology platforms needed to support the applications that manage the data and support the business functions. SOFTWARE-rt

Layer 4 - how we plan to get there : This consists of the Implementation / Migration Plans - Definition of the sequence for implementing applications, a schedule for implementation, a cost/benefit analysis, and a clear path for migration. SOFTWARE-rt

EAP methodology The Enterprise Architecture Planning (EAP) methodology is beneficial to understanding the further definition of the Federal Enterprise Architecture Framework at level IV. EAP is a how to approach for creating the top two rows of the Zachman Framework, Planner and Owner. The design of systems begins in the third row, outside the scope of EAP.[2] EAP focuses on defining what data, applications, and technology architectures are appropriate for and support the overall enterprise. Exhibit 6 shows the seven components (or steps) of EAP for defining these architectures and the related migration plan. The seven components are in the shape of a wedding cake, with each layer representing a different focus of each major task (or step). SOFTWARE-rt

Applications Spewak approach to Federal Enterprise Architecture has helped organizations with modeling, business strategy planning, process improvement, data warehousing, and various support systems designs, data administration standards, object-oriented and information engineering methodologies, and project management. SOFTWARE-rt