Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

WA1537 Introduction to Enterprise Architecture Training and ...


Published on

  • Be the first to comment

  • Be the first to like this

WA1537 Introduction to Enterprise Architecture Training and ...

  1. 1. WA1537 Introduction to Enterprise Architecture Training and Courseware This two day course provides a comprehensive introduction to the discipline and methodology of Enterprise Architecture (EA). The course is designed for architects and team leads who are new to EA. It will provide the high level concepts behind EA, its value proposition within enterprises, and an understanding of how to apply EA in practice. It will also discuss the various roles and responsibilities involved in effective EA adoption. In addition to high-level concepts and methodologies, this course will provide a practical understanding of how EA is developed in a step-by-step process. Topics • Why Architecture matters? • Standard architecture practices and processes • Developing business alignment • Technology lifecycle / technology change management • Architectural Governance models • Developing reusable and flexible architectures • Metrics for architecture • Developing buy-in across the organization • Documenting architectures • Architecture design philosophies Audience This course is aimed at architects and senior technical leads with no existing background in EA. Prerequisites Previous full life-cycle experience as an architect or technical lead is required. Duration Two days
  2. 2. WA1537 Introduction to Enterprise Architecture Training and Courseware Course Outline 1. Introduction • You and Your Expectations • Objectives and goals • Our approach to understanding EA • Our approach to understanding EA: guidance, team, and projects • 2-day Agenda • Key Reference Material • Session Guidelines 2. Why Architecture Matters • City Planners • Architects • Why Do We Need EA? • The Journey That Lies Ahead • Architecture Definitions (Wikipedia) • Architecture Definitions (Gartner) • Enterprise, Solution, and Software Architectures • Solution Architecture • Strategic Needs for Architecture • EA from Strategy to Technology • Strategic Needs for Architecture • Tactical EA: IT Yearly Planning • Tactical EA: IT as an Investment Portfolio • Operational Needs for Architecture • Solution Architecture Example: SAP at MIT • Architecture Is Not Only Design 3. Standard Architecture Practices and Processes • EA Domains and Views • EA Domains and Views: Business, Data, Application, Technology • EA Domains and Views: Separation of Concerns • EA Domains • Business-Dependent and Business-Independent • Context Domain Example: MIT Context and Goals • Business Domain Examples: Financial Industry • Data Domain Example: MIT Data Model • EA Domains Are All Equally Important • Abstraction Levels: Conceptual, Logical, and Physical • Each Abstraction Level Has a Unique Goal and Audience • Conceptual Level Answers the WHAT Question • Delta Airlines’ Conceptual Architecture • Metlife Conceptual Architecture
  3. 3. • ING Core Architecture • Logical Level Answers the HOW Question • Logical Architecture Vision • Physical Level Answers the WITH WHAT Question • Physical Architecture Example: Microsoft System Architecture • EA Frameworks • EA Frameworks Family Tree • Zachman: Concise Definition • Zachman Framework • What is the Zachman Framework? • Zachman Framework Strengths and Weaknesses • TOGAF Origins • TOGAF 2008 Revision Objectives • TOGAF 8 Goals • TOGAF and Other Frameworks/ Bodies of Knowledge • TOGAF 8 Components • Architecture Development Method and Overview • ADM: Basic Principles • TOGAF: Demand for Information • TOGAF 8 Summary • EA Frameworks • Choosing the Right EA Framework • Which Industry Standard Framework Is Adopted by Your Organization? • EA Frameworks Adoption Stats • Why Does EA Framework Adoption Often Fail? • Why Is There No Universal EA Framework? • EA Framework: Conflicting Requirements • EA Frameworks: Comparison • EA Frameworks: Recommendations 4. Developing Business Alignment • Business Context and Objectives • Business Modeling Explores a Wide Range of Issues • Drivers and Principles • EA Principles: Definition • Categories of Principles • EA Principles: They are Essential • EA Principles in the Wild • Components of EA Principles • Qualities of Principles • EA Principles: Creation Process • Applying Architecture Principles • Business Principle: TOGAF Example • Data Principle: NIH Example • Enterprise Principle: MIT Example • Business Architecture, Capabilities, and Services • Business Modeling Discipline Key Takeaways • Good Enterprise Business Models Are Stable • Define Enterprise Strategy: Business Context • Mission, Vision, Strategy • Model the Organization
  4. 4. • Business Process Modeling • Value Chain • Value Stream Maps • Organization Model and Value Chain • Use Case Models • BPMN Diagrams • BPMN Example with Swimlanes • Retail High Level Capability Map with Applications Overlay • A Business Function Is a Specialized Service Centre • Business Service: Connect Business Functions • Identify Business Services in 3 Ways • The Essentials of Business Services • Business Modeling Techniques and Approaches • Identify Process Automation Opportunities • Conceptual Business Model or Model of the Business Domain • Conceptual Business Model Example (EUP) • Business Domain Examples: Financial Industry • Five Principles of Composite Process Design • Capability Interaction Model • NIH Business Processes • Cross-Reference Matrices: EA’s Best Friend • Business Modeling Approach: Go in, Go Up, Go Out, Go Down • EA Reference Models • IBM Industry Frameworks • APQC Process Classification Framework (PCF) • SCOR: Supply-Chain Operations Reference Model • Value Chain Reference Model 5. Technology Lifecycle and Change Management • Technology Architectures • TOGAF 8.1 Technical Reference Model (TRM) • TOGAF8.1 TRM: Application Software • TOGAF8.1 TRM: Application Platform Services • TOGAF8.1 TRM: Data Management Services Details • TOGAF8.1 TRM: Communications Infrastructure • Taxonomy of Service Qualities • TOGAF8.1 Standards Information Base (SIB) • NIH Application Principles • Transition Plans • EA Transformation Plan • How To Create the Migration Plan • Identify Gaps • Implement EA Measurements • How To Prioritize • Rational Unified Process • Two Dimensions of the RUP Process • Static Dimension of RUP: Disciplines • The RUP Iteration • Enterprise Unified Process: EUP • EUP Process • 7 New Disciplines in EUP
  5. 5. • 2 New Phases in EUP • EUP Modifies RUP 6. Architectural Governance • EA Governance • What Is Governance? • What Is IT governance? • IT governance archetypes • Governance Arrangement Matrix • IT governance at UPS • How Enterprises Govern- Most Typical • The Rationale for EA Governance • Too Many EAs Do Not Collect Metrics • Expect Stale Enterprise Architecture Data in Organizations • IT Governance Design Framework • Implementing IT Governance • COBIT • Governance Framework COBIT • Factors Leading to the Need for IT Governance • Use of COBIT 7. Reusable and Flexible Architectures • SOA • SOA Value Proposition • The SOA Value Proposition • Reducing Integration Expense • Integration Costs Illustration • Ripple Effect of Changes • The Value of SOA Layering • SOA Reduces Integration Costs • Increasing Asset Reuse • SOA Economics/ROI • Increasing Business Agility • SOA Agility • Reducing Business Risk • Other Advantages • Business Advantages • Hasn’t This Been Said Before? • Layers of Services • What Is Layering? • SOA Layers • Common Layers • BPM • What Is A Business Process? • Business Process Management • Business Process Modeling • SOA and Business Process • Process Modeling and SOA • The Process-Centric Organization
  6. 6. • From Ad-Hoc to Formalization • Process-Centric Organizations • The Value of Process-Centricity 8. Develop EA Buy-In Across the Organization • EA Lifecycle • Enterprise Architecture Lifecycle • EA Maturity • GAO Enterprise Architecture Management Maturity Framework (EAMMF) • Initiate an EA Program • EA as an Enterprise Asset • Obtain Executive Buy-In • Issue Executive EA Policy • Obtain Senior Executives and Business Units Support • EA in your Organization • Establish Management Structure and Control • Chief Enterprise Architect • Establish EA Steering Committee • Establish EA Office • EA Core Team • EA team composition • Enterprise Architects Have an Impact Beyond IT • EA Program Activities and Results • EA Body of Knowledge (EABoK) 9. Documenting Architectures • Modeling Languages • Model Visually • Unified Modeling Language • Documenting Use Cases • Action Sequence • Use Case Relationships • Class Association Relationship • Sequence Diagram • BPMN Introduction • Key Tasks in Process Modeling • Roles and Responsibilities • Process Modeling Standards • BPMN and BPEL • Basic Structure of a Process • Modeling Roles & Responsibilities • Using Swim Lanes • Black Box White Box Modeling • UML and BPMN comparison • EA Tools • Need for EA Tools • EA Tools Minimum Requirements • EA Tools: Market Review • EA Tools: Current Market Analysis
  7. 7. • Ties Between EA, SOA, BPM Tools • Tools for Conceptual/Domain Modeling • Application Portfolio Management – APM • BPMS Tools Overview • BPMN Tool: Lombardi Blueprint • Casewise: Framework • Popkins Architecture • Troux EA software 10. Architecture Design Philosophies • Patterns and Bricks • Patterns • “Brick” • Using Bricks to Guide Technology Evolution • Model-Driven Architecture (MDA) • What Is MDA? Model Driven Architecture • Linking MDA to EA via Business Architecture • MDA: Benefits and Drawbacks • Enterprise Service Bus (ESB) • Service Oriented Architecture (SOA) • Business Process Management (BPM) • SOA + BPM + ESB - IBM SOA solution stack • IBM SOA Reference Model • ESB – IBM reference model • Enterprise Service Bus (ESB) 11. EA Lessons Learned and Anti-Patterns • Key EA Lessons Learned • 3 Critical Changes EA Must Make To Survive Hard Times • As Bluntly As I Know How • Scott Ambler’s EA Anti-Patterns • 30,000 Feet and Climbing • Detailed Enterprise Modeling • Goldplating • Technology Above All 12. Breakouts • B1.1- Introduce all participants • B2.1- Describe an architect • B6.1- Are you living under a monarchy? (How is EA governed in your organization?) • B9.1- Which EA deliverables can you use?
  8. 8. 13. EA class workshop – Applying EA to your organization Description As part of our 3, 4 or 5 day EA classes, breakouts and hands-on sessions are dedicated to applying specific concepts, tools and approaches to real-life problems in your organization. 1. half day and full day sessions are worked into the class agenda with participants working in teams, sometimes competing and sometimes collaborating to reach final results; 2. session must be very dynamic to adapt to the reality & issues faced by class participants in their organization; 3. preparation is required to identify the most appropriate topics to address from the sample list provided Workshop Objectives This session overall goal is to confront participants with “typical” issues they face with an Enterprise Architecture practice or Programme. 1. put in practice enterprise architecture deliverables 2. experiment with different approaches to select the most appropriate 3. explore more in depth certain aspects of EA as it pertains to participant’s current context The workshop session is not designed to deliver an initial or draft EA material for the organization but rather it aims to leave behind an initial list of topics that participants feel must be addressed once EA class is over. Sample workshop topics This list provides a sample of possible topics that can be covered during the session to reach the objectives defined with EA class leader. • EA governance in your organization: feudal or federated? • EA principles: gathering appropriate information • EA tooling: why MS Excel sometimes is not the right tool for the job • EA framework selection: picking the right framework and customizing it to your need