The EA 3 Cube Approach. Dr. John Gøtze

Transcription

1 The EA 3 Cube Approach Dr. John Gøtze John.goetze@qualiware.com 1

2 The EABOK provides a living, evolving reference of ready-to-use knowledge about EA. Enterprise Architects analyze areas of common activity within or between enterprises or organizations, where information and other resources are exchanged to guide future states from an integrated viewpoint of strategy, business and technology. 2

3 Strategy IT Business 3 3

4 The EA3 Cube Approach EA = Strategy + Business + Technology Dr Scott Bernard US Federal Chief Architect EA3 is owned by ieai: 4

5 EA = The analysis and documentation of an enterprise in its current and future states from a strategy, business, technology perspective. Security / Standards / Workforce Technology Business Strategy Framework Dimension 3: Artifacts The documentation of components at each level of the architecture, including all threads Lines of Business Goals & Initiatives Products & Services Data & Information Systems & Applications s & C O M P O N E N T S Framework Dimension 1: Levels Sub-architectures; distinct functional areas and their relationships Framework Dimension 2: Segments Vertical sub-areas of the enterprise with distinct business activities and resources 5

6 TRANSFORMATION DESIGN Security / Standards / Workforce Technology Business Strategy Lines of Business Goals & Initiatives Products & Services Data & Information Systems & Applications s & C O M P O N E N T S Architecture Management & Transition Plan Lines of Business Updated Strategic Goals & Initiatives Improved Business Products and Services Enhanced Data and Information Flows Integrated Systems and Applications Optimized s and C O M P O N E N T S CURRENT ARCHITECTURE FUTURE ARCHITECTURE 6

7 A complete EA approach must have all of these elements, which are specifically designed to work together in the context of the governance process. 7

8 EA Core Element #1 - Governance The first basic element is Governance which identifies the planning, decisionmaking, and oversight processes and groups that will determine how the enterprise architecture is developed and maintained, as part of an organization s overall governance. MIT: + Project models + Linking mechanisms EA 3 : Embedded architecture Task forces ISO38500 principles 8

9 EA Core Element #2 - Methodology The second basic element is Methodology which are specific steps to establish and maintain an EA program, via the selected approach. Phase I: EA Program Establishment Step 1: Establish the EA Management Program and identify a Chief Architect. Step 2: Establish an EA implementation methodology. Step 3: Establish EA governance and links to other management processes. Step 4: Develop an EA Communication Plan to gain stakeholder buy-in. Phase III: Documentation of the EA Step 11: Evaluate existing business and technology documentation for use in the EA. Step 12: Document current views of existing EA components in all framework areas. Step 13: Develop several future business/technology operating scenarios. Step 14: Identify future planning assumptions for each future scenario. Step 15: Document future views of planned EA components in all framework areas. Step 16: Develop an EA Management Plan to sequence planned changes in the EA. Phase II: EA Framework and Tool Selection Step 5: Select an EA documentation framework. Step 6: Identify EA Lines of Business/Crosscuts and the order of their documentation. Step 7: Identify the EA components to be documented framework-wide. Step 8: Select documentation methods appropriate for the framework. Step 9: Select software applications/tools to support automated EA documentation. Step 10: Select and establish an on-line EA repository for documentation and analysis. Phase IV: Use and Maintain the EA Step 17: Use EA documentation for resource planning and decision-making. Step 18: Regularly update current and future views of EA components. Step 19: Maintain an EA Repository and related modeling and analysis capabilities. Step 20: Release annual updates to the EA Management Plan. Section 3.1 Obtain Executive Section 3.2 Buy-In and Establish Section 7 Maintain the Support Management Enterprise Structure Architecture and Control Use Control EA Define an the and Control Architecture Section 4 Section 6 Enterprise and Oversight Process Architecture and Approach Develop Develop the Baseline Sequencing Plan Develop Enterprise Target Architecture Section 5 Enterprise Section 5 Architecture Section 5 DODAF 9

10 SCOPE (CONTEXTUAL) Planner Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Builder DETAILED REPRESEN- CONTEXT) TATIONS (OUT-OF- Sub- Contractor FUNCTIONING ENTERPRISE DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why List of Things Important to the Business ENTITY = Class of Business Thing e.g. Semantic Model Ent = Business Entity Reln = Business Relationship e.g. Logical Data Model Ent = Data Entity Reln = Data Relationship e.g. Physical Data Model Ent = Segment/Table/etc. Reln = Pointer/Key/etc. e.g. Data Definition Ent = Field Reln = Address e.g. DATA List of Processes the Business Performs Function = Class of Business Process e.g. Business Process Model Proc. = Business Process I/O = Business Resources e.g. Application Architecture I/O = User Views Proc.= Application Function e.g. System Design I/O = Data Elements/Sets Proc.= Computer Function e.g. Program I/O = Control Block Proc.= Language Stmt e.g. FUNCTION List of Locations in which the Business Operates Node = Major Business Location e.g. Business Logistics System Node = Business Location Link = Business Linkage e.g. Distributed System Architecture Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics e.g. Technology Architecture Node = Hardware/System Software Link = Line Specifications e.g. Architecture Node = Addresses Link = Protocols e.g. NETWORK List of Organizations Important to the Business People = Major Organizations e.g. Work Flow Model People = Organization Unit Work = Work Product e.g. Human Interface Architecture People = Role Work = Deliverable e.g. Presentation Architecture People = User Work = Screen Format e.g. Security Architecture People = Identity Work = Job e.g. ORGANIZATION TIME List of Events Significant to the Business Time = Major Business Event e.g. Master Schedule Time = Business Event Cycle = Business Cycle e.g. Processing Structure Time = System Event Cycle = Processing Cycle e.g. Control Structure Cycle = Component Cycle Time = Execute e.g. Timing Definition Time = Interrupt Cycle = Machine Cycle e.g. SCHEDULE TM List of Business Goals/Strat Ends/Means=Major Bus. Goal/ Critical Success Factor e.g. Business Plan End = Business Objective Means = Business Strategy e.g., Business Rule Model End = Structural Assertion Means =Action Assertion e.g. Rule Design End = Condition Means = Action e.g. Rule Specification End = Sub-condition Means = Step e.g. STRATEGY SCOPE (CONTEXTUAL) Planner ENTERPRISE MODEL (CONCEPTUAL) Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Builder DETAILED REPRESEN- TATIONS (OUT-OF CONTEXT) Sub- Contractor FUNCTIONING ENTERPRISE EA Core Element #3 - Framework The third basic element is Framework which identifies the scope of the overall architecture and the type and relationship of the various sub-architecture levels and threads. Not all frameworks allow for segments or integrate strategy, business, technology. ENTERPRISE MODEL (CONCEPTUAL) ENTERPRISE ARCHITECTURE - A FRAMEWORK John A. Zachman, Zachman International (810) Systems Technical Operational DODAF TOGAF Integrating the Federal EA Framework and Reference Models Security Profile Zachman Strategy PRM Business BRM Information & Data DRM Applications & Services SRM Technology Security Architecture Departmental Crosscuts LOB & OA Mission Verticals TRM Common Operating Environment FEAF Common Threads Segments Security, Standards, Workforce Technology Business Strategy Functional Areas Lines of Business Goals & Initiatives Vertical Processes & Services Data & Information Systems & Applications s & Components Crosscutting Components Hierarchical Levels 10

11 EA Core Element #4 - Artifacts The fourth basic element is Artifacts which identifies the types and methods of documentation to be used in each sub-architecture area, including strategic analyses, business plans, internal controls, security controls, and models of workflows, data, systems, and networks. 11

12 EA Core Element #5 - Standards The fifth basic element is Standards which identify business and technology standards for the enterprise in each domain, segment, and component of the EA. This includes recognized international, national, local, and industry standards as well as enterprise-specific standards. 12

13 EA Core Element #6 Best Practices The sixth basic element is Associated Best Practices which are proven ways to implement parts of the overall architecture or subarchitectures, in context of meta EA. Strategic Level Strategic Planning, Scenario Planning Balanced Scorecard, SWOT Analysis Business Level Business Plans / Process Reengineering Business Process Improvement Technology Level Service-Oriented Architecture (SOA) Object-Oriented Data Modeling/Design System Development Lifecycles IT Library (ITIL) Security / Standards / Workforce Technology Business Strategy Lines of Business Goals & Initiatives Products & Services Data & Information Systems & Applications s & Meta Context C O M P O N E N T S 13

14 The front: Viewpoints Security / Standards / Workforce Technology Business Strategy Goals & Initiatives Products & Services Data & Information Systems & Applications s & Framework Levels / Sub-architectures CURRENT Perspectives Cross-cutting Planning Threads 14

15 15 etwork structure etwork structure etwork structure twork tructure ork ucture ork ucture ork ucture ork ucture ks e s d s es k ture re c s etwork structure etwork structure etwork structure twork tructure ork ucture ork ucture ork ucture ork ucture ks e s d s es k ture re c s ess C O M P O N E N T S Enterprise Components Segments etwork structure etwork structure etwork structure twork tructure ork ucture ork ucture ork ucture ork ucture ks e s d s es k ture re c s etwork structure etwork structure etwork structure twork tructure ork ucture ork ucture ork ucture ork ucture ks e s d s es k ture re c s ess C O M P O N E N T S Enterprise Components Segments Lines of Business Vertical and horisontal The overall system-of-concern The depth: Architectural scopes System-of-concern

16 EA Components Goals & Initiatives Products & Services Data & Information Systems & Applications Technology & Mission Statement Strategic Goals Strategic Initiatives Manufacturing Financial Services Marketing & Sales Data Interchange Web Sites Knowledge Warehouse Databases & Data Marts Information Systems Desktop Applications Intranets & Extranets Telecommunications Buildings & Equipment Vertical Components Examples of EA Components Crosscutting Components 16

17 EA as the Meta Model for Enterprises Business Level Strategic Level SOA SWOT CPIC Balanced Scorecard Business Cases Six Sigma Alternatives Analysis BPI / BPR EA is the meta model and context for all other bestpractices and approaches SDLC 17

18 What is Enterprise? Oxford Dictionary: 1. A project or undertaking, especially a bold or complex one 2. A business or company 18

19 What is Architecture? FEAF-II and EA 3 A systematic approach that organizes and guides design, analysis, planning, and documentation activities. ISO 42010: Fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution. 19

20 ISO EA 3 designed to be conformant with ISO/IEC/IEEE 42010:

21 By the way: ISO 420x0 Ongoing ISO/IEC JTC1/SC7/WG42 work: Architecture processes and work products Architecture evaluation EA 3 contributes and will align. 21

22 EA3 Artifacts EA supports planning and decisionmaking through documentation and information that provides an abstracted view of an enterprise at various levels of scope and detail. 22

23 Strategic models 23

24 Business 24

25 Information 25

26 Applications 26

27 EA 3 Certification Carnegie Mellon University s Certified Enterprise Architect program is based on EA 3 Three courses: EA Fundmentals EA Applied EA Advanced More about the courses: 27

28 Danish Government s OIO EA 28

29 The Federal Enterprise Architecture Framework v2 describes a suite of tools to help government planners implement the Common Approach. The Consolidated Reference Model (CRM) equips OMB and Federal agencies with a common language and framework to describe and analyze investments. It consists of a set of interrelated reference models that describe the six sub-architecture domains in the framework: Strategy Business Data Applications Security 29

30 Common Approach to Federal EA "The role of an enterprise architect is to help facilitate and support a common understanding of needs, help formulate recommendations to meet those needs, and facilitate the development of a plan of action that is grounded in an integrated view of not just technology planning, but the full spectrum of planning disciplines to include mission/business planning, capital planning, security planning, infrastructure planning, human capital planning, performance planning, and records planning." Released May 2, 2012 Memo from Federal CIO VanRoekel: 30

31 The Common Approach to Federal EA 31

32 Collaborative Planning Methodology (FEAF-II) 06/05/15 32

33 33

34 A few points about TOGAF Incomplete Style mashup Designed by committee ADM <> Continuum Weak metamodel Weak on governance IT centric 34 34

35 EA Identity? 35

36 Gartner: Bimodality Vanguard Foundation Vanguard enterprise architects, driving innovation with disruptive technologies Foundational enterprise architects, delivering systems of record and maintaining the (primarily technology) estate 36

37 Vanguard? ENTERPRISE ARCHITECT Supporting cast: Technical Debt Collectors The Pace-Layerer The Mad Data Scientist The Ruthless Digitalizer And other superheroes 37

38 Thank You! Join us at 38