INTRODUCTION EA
INTRODUCTION TO INSTRUCTOR Instructor: Pongpan Manupeerapan EA Technical Consultant Certified IBM Certified Solution Designer Rational System Architect: BPMN Emphasis IBM Certified Deployment professional MAXIMO Asset Management NECTEC Network System Administration Techniques for IT Professional
AGENDA What is Architecture? What is EA? EA Artifact EA Values Who should involve? What is Framework? Zachman TOGAF EA Implementation Key to Success EA Tools
COURSE OVERVIEW After completing this module, you will be able to: Explain what is Enterprise Architecture (EA) Explain some of the benefits of EA Explain why analysis is key and why reactive solutions lead to problems Explain how frameworks are important for good Enterprise Architecture
MAJOR TREND
WHAT IS ARCHITECTURE Architecture (Latin architectura, after the Greek ἀρχιτέκτων arkhitekton from ἀρχι- "chief" andτέκτων "builder, carpenter, mason") is both the process and the product of planning, designing, andconstructing buildings and other physical structures. Architectural works, in the material form ofbuildings, are often perceived as cultural symbols and as works of art. Historical civilizations are often identified with their surviving architectural achievements.
ARCHITECTURE LEVEL
WHAT IS ENTERPRISE ARCHITECTURE IBM: The Enterprise Architecture discipline defines and maintains the architecture models, governance, and transition initiatives needed to effectively co-ordinate semi-autonomous groups towards common business and/or IT goals 1 Enterprise architecture is the process of translating business vision and strategy into effective enterprise change by creating, communicating and improving the key principles and models that describe the enterprise's future state and enable its evolution. 2 Similar definitions, consistent intent 1. Enterprise Architecture in the era of On-Demand, IBM Academy of Technology Study, October 2004 2. Short form, Gartner Defines the term Enterprise Architecture, Anne Lapkin, Gartner, July 12, 2006
ENTERPRISE ARCHITECTURE ARTIFACT Métier Business Applications & Systems Business Processes: support the strategy, Operational organization The Applications support the Business, implement the business functions in the IT systems Information & Data The Information is key for the organization: It is the fuel that drives the architecture Network & Infrastructure Infrastructure that supports the IS: -Technical components: servers, networks, etc. -Technology: platforms, etc.
EA : PLANNING FUNCTION BETWEEN STRATEGY FORMULATION AND DELIVERY Component Scheduling Shipping Yarn Buying Order Entry Cash Management Accounting Component Design Yarn Dyeing Inventory Assortment Planning Component Knitting Tagging & Packing Raleigh Plant Knits Division Seneca Plant Yankee Group AEI Corporate Yarn Division Saturn Group Business Opportunity Enterprise Strategy Bus Strategy IT Strategy Technology Availability Strategy = the city s purpose & goals Strategy Program focus Enterprise wide focus Enterprise Architecture Transition Planning Enterprise Architecture = the city plan Planning Bus Arch ture Business Structure Business Locations Fire and hope! IT Architecture Architecture Governance Design and Delivery Business Operating Environment and IT Infrastructure System Design = the buildings Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Change Programs
Define Architecture Process & Approach Current State Business Strategy Future State Business Architecture Obtain & Maintain Buy In & Support Governance Project Management Business Architecture Data/Information Architecture Change Management Risk Management Understanding of Organizations Data/Information Architecture Application Architecture Enterprise Analysis Communicatio ns Strategy Enterprise Modeling Value Measurement & Management Enterprise Information Technology Acumen Leadership & Decision Making Application Architecture Technical / Infrastructure Architecture Enterprise Integration Portfolio Management Migration / Implementation Planning Technical / Infrastructure Architecture Where we are How we re going to get there Where we want to be
ENTERPRISE ARCHITECTURE VALUE Provides a clear view of how the business and technology resources will support and achieve an organization s business goals and initiatives. Understand the strategy, the business, the systems and the infrastructure and how they interrelate. Moving "need to know" information to those that "know they need" upstream and down stream and in both directions. Helps us prioritize and decide which things to do and in what order. Doing the Right Things Governs the change and building of things. Doing the Things Right
WHO SHOULD INVOLVE EA is not System, Information, Services or Solution It s not IT Function, It s Everyone 15
WHAT IS FRAMEWORK An enterprise architecture framework (EA framework) defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers or views, and offers models - typically matrices and diagrams - for documenting each view.
ALL EAS HAVE A FRAMEWORK Prelim: Framework and Principles TOGAF H Architecture Change Management A Architecture Vision B Business Architecture G Implementation Governance Requirements C Information System Architectures F Migration Planning E Opportunities and Solutions D Technology Architecture FEAF Strategy Business Opportunity Business Strategy Information Technology Strategy Technology Availability Enterprise wide focus Planning Enterprise Architecture Business Architecture IT Architecture - Processes - Applications - Information - Information - People - Locations - Technology Transition Plan EA3 Project focus Design and Delivery Business Operating Environment and IT Infrastructure IT Solutions IBM DoDAF
The Zachman Framework for Enterprise Architecture
ZACHMAN FRAMEWORK Developed in 1982 at IBM by John Zachman, first published in 1987 Applies physics and basic engineering principals to the enterprise as a whole Tool for engineering and manufacturing enterprises Has a defined set of rules to follow for successful implementations
ZACHMAN S ARCHITECTURAL PRINCIPLES 1. Make sure you have alignment through the entire framework. 2. Make sure all models are developed based on the same standards managed from an enterprise-wide perspective. 3. Make sure all hardware and software is compatible based on standards for effective communication.
ZACHMAN S ARCHITECTURAL PRINCIPLES 4. Make sure business rules are enforced consistently across the enterprise. 5. Make sure systems are defined logically (row 3 and 4 models), independent of technology (row 5) so technology can be easily changed. 6. Make sure change is incorporated as a management criteria so any aspect of the enterprise can be maintained in a dynamic environment.
THE FRAMEWORK OF TOGAF 9 The TOGAF framework provides the core phases of the Architecture Development Method (ADM), presented as circles surrounding requirements. Bidirectional lines are drawn from each of the outer ADM circles to the center Requirements circle. This represents how requirements drive the creation of the architecture, and how the architecture is created to satisfy requirements.
DEFINITION OF TOGAF The Open Group Architecture Framework (TOGAF) is a framework and detailed method for building, maintaining, and gaining value from an enterprise architecture for an organization. TOGAF 9 is the latest evolution of the framework, and its accompanying Architecture Development Method (ADM) The TOGAF specification is an open standard that has been created and is maintained by The Open Group (www.opengroup.org).
TYPES OF ARCHITECTURES IN TOGAF Business Architecture -- addresses the needs of users, planners, and business management, Data/Information Architecture -- addresses the needs of database designers, database administrators, and system engineers, Application (Systems) Architecture -- addresses the needs of system and software engineers, and Information Technology (IT) Architecture -- addresses the needs of acquirers, operators, administrators, and managers.
EA IMPLEMENTATION
KEY TO SUCCESS Strong lead Architect Stakeholder understanding and support Engaging the business Do Every Level of Architect Don t take too mush on current State Respect to What it is More Communication Keep E Repositories Update
EA TOOLS
EA PRACTICE
CAPTURE AND MODEL ALL DOMAINS OF THE ORGANIZATION
BUSINESS ARCHITECTURE
BUSINESS PROCESS
DATA ARCHITECTURE
MASTER DATA
APPLICATION ARCHITECTURE
TECHNOLOGY ARCHITECTURE