Tomorrow never dies. making sure EA survives the man with the golden gun...

Transcription

1 Tomorrow never dies making sure EA survives the man with the golden gun...

2 Two companies combine

3 Metropolitan s EA Structure Enterprise Architect Enterprise Architecture Group Architecture Business Unit Architecture Group Line of Business Supporting Functions Domain Architecture Solution Architecture Retail Employee Benefits Group Technology & Services Group risk Management Business & Information Architect Data Architect Solution Architect Solution Architect Business Architect Business Unit Architect International Business Unit Asset Architect Management Corporate Actuarial Group People Services Application Architect Solution Architect Health Group Collective Investment Group Finance Group Empowerment & Corporate Affairs Technology Architect

4 EA Strategy 2008 EA Practice/Discipline EA CORE EA Methodology EA Repository

5 Ensuring Alignment WHO (Practice) WHAT (Methodology) WHERE/HOW (Repository) Business Architect & Business Analyst PERFORMED BY Manage Business Operating Model REALISED BY Business Models (process, product, channel, etc.) Information Architect PERFORMED BY Manage Information Classes REALISED BY Information Models Data Architect & Data Analyst PERFORMED BY Manage Business Data REALISED BY Data Models Application Architect & Systems Analyst PERFORMED BY Manage Application Portfolio REALISED BY Application Models SOA Architect & Systems Analyst PERFORMED BY Manage Application Services Portfolio REALISED BY Application Service Models Technology Architect PERFORMED BY Manage Infrastructure Portfolio REALISED BY Infrastructure Models Solution Architect PERFORMED BY Manage Solution Delivery REALISED BY Solution & IT Landscape Models

6 Agenda Moving towards an alternative paradigm (For your eyes only) The struggle to get knowledge documented in the enterprise (Die another day) Current EA methodologies lack what the business needs (License to kill) A plan to make sure that everybody contributes to EA (Live and let die) How to show the value that EA can deliver (Diamonds are forever) Get EA into the boardroom (The world is not enough)

7 MOVING TOWARDS AN ALTERNATIVE PARADIGM For your eyes only

8 Good or Bad Architecture: You Decide

9 Good or Bad Architecture: You Decide

10 What makes for Good Architecture? The Roman architect Vitruvius in his treatise on architecture, De Architectura, wrote that there were three principles of good architecture: 1. Firmatis (Durability) It should stand up robustly and remain in good condition. 2. Utilitas (Utility) It should be useful and function well for the people using it. 3. Venustatis (Beauty) It should delight people and raise their spirits.

11 The Architect Paradigm SOLUTION ARCHITECT PROJECT MANAGER LEAD DEVELOPER or SYSTEMS ANALYST NETWORK OR SYSTEMS ENGINEER LEAD DATABASE ADMINISTRATOR DOMAIN ARCHITECT

12 What is Espionage/Spying? Espionage or spying involves an individual obtaining information that is considered secret or confidential without the permission of the holder of the information.

13 Why use the Spying paradigm? Businesses do not want to share information, as they see it as their competitive advantage Strategies and tactics are not always clearly articulated Strategies and tactics are often implicit to what the business does Architects have to spy on businesses to extract their information and visualize it

14 Types of Spies Agent of influence Agent provocateur Atomic spies Covert agent Dangle (espionage) Defection Double agent Field agent Informant Intelligence officer Labor spies Mole (espionage) Non-official cover Official cover Resident spy Sleeper agent Spymaster Stay-behind Undercover Walk-in agent

15 How does a spy operate? 1. Observe/Learn 2. Infiltrate/Engage 3. Access/Extract 4. Exit/Disengage 5. Debrief/Report

16 THE STRUGGLE TO GET KNOWLEDGE DOCUMENTED IN THE ENTERPRISE Die another day

17 Data, Information, Knowledge, Intelligence 1. Data: Representation of facts, concepts, or instructions in a formalized manner suitable for communication, interpretation, or processing by humans or by automatic means. 2. Information: The meaning that a human assigns to data by means of the known conventions used in their representation. 1: 2:

18 Data, Information, Knowledge, Intelligence 3. Knowledge: expertise, and skills acquired by a person through experience or education; facts and information; 4. Intelligence: a term describing a property of the mind including related abilities, such as the capacities for abstract thought, understanding, communication, reasoning, learning, learning from past experiences, planning, and problem solving. 1: 2:

19 From Data to Wisdom Connectedness Wisdom Understanding principles Knowledge Understanding patterns Information Understanding relationships Data Understanding

20 Capturing Knowledge Internalized: Absorbed & understood by the human mind Knowledge Processed & Analyzed: A reconstructed picture of historical events &/or projections of possible future events Information Captured & Stored Externalized: Verbalized &/or illustrated Data

21 WHAT DOES A SPY DO?

22 HE SCARES THE LIVING DAYLIGHTS OUT OF EVERYBODY to encourage them to capture the NECESSARY INFORMATION

23 WHAT DO WE DO?

24 Modeled Information (MI5)

25 Copyright Real IRM Solutions (Pty) Ltd Metropolitan Enterprise Architecture Conceptual Framework Version April 2009 Product Models Lines of Business Product Group Product Type Channel Models Channel Group Channel Type Channel Customer Models Customer Type Location Models Location Type Location Business Risk Models Business Risk Category Business Risk Process Models (L0) Enterprise Process (L1) Macro Process (L2) Process Project Detail Models Project (L2) Process Business Architecture Project Models Programme (L3) Sub-process Business Services Models Business Service Group Business Cycles Models Business Cycle Group Business Cycle Business Service Type Detail Models Business Service Type Customer Type Channel Type Location Type Business Controls (L3) Sub-process (L4) Activity (L5) Task Product Type Information Element Application Systems Project Portfolio Project Business Service Type Business Cycle Events Product Type Detail Models Product Type Business Cycle Business Service Type Customer Type (L3) Sub-process (L3) Sub-process Models Type Business Service Type Logical Data Model Physical Data Model Role Type Role Job Job/Role Allocation Sub-process Detail Models (L3) Sub-process Business Rule Information Classification Location Type Location Job Document Product Type Business Service Type Business Risk Application Classification Application Services Activity Detail Models (L4) Activity Business Rule Application Systems Application Components Job Document KPI Business Role Location Type Business Cycle Events Business Controls Channel Information Element Business Rule Models Business Rule Category Business Rule Type Business Rule Terminology Models Terms Abbreviations Business Metric Models Scorecard KPA KPI Document Detail Models Document Document Scorecard Ownership Model Scorecard Governance Document Models Document Category Document Type Document Information Delivery Model Information Element KPI Information Architecture Logical Data Model Document Application Services Business Role Message Channel Information Classification Models Information Classification Information Element Information Ownership Model Information Classification Information Element Information Sourcing Model Information Element Logical Data Model Document Application Services Business Role Message Structure Data Architecture Data Models Message Models Logical Data Model Message Physical Data Model Message Structure Logical Data Access Model Application Services Logical Data Model Message Physical Data Access Model Application Component Physical Data Model Message Structure Application Classification Application Services Logical Application Models IT Role Access Model Application Systems Application Components Physical Application Architecture System Process Model Application Component Application Systems Physical Solution Design Model Infrastructure Device Application System Application Component Physical Data Model (L4) Activity (L5) Task Logical Solution Design Model Infrastructure Types Application Classification Message Structure Infrastructure Location Model Devices Infrastructure Ownership Model Devices Infrastructure Models Infrastructure Classification Infrastructure Types Devices Technology Architecture Location Application Components Role Legend Application Services Risk Terminology Logical Application Ownership Model Application Classification Application Services Application Component Physical Application Ownership Model Application System Logical Data Model Message Business Cycle Business Service Process Customer Location Channel Product Primitive Models Document Metric Information Message Data Application Technology Project Composite Models

26 Copyright Real IRM Solutions (Pty) Ltd Metropolitan Enterprise Architecture High Level Conceptual Framework Business Version May 2009 Product Models Channel Models Location Models Customer Models Project Models Business Rule Models Business Services Models Business Cycles Models Process Models Models Business Risk Models Information Terminology Models Business Metric Models Governance Document Models Information Classification Models Data Application Technology Data Models Message Models Application Models Infrastructure Models

27 CURRENT EA METHODOLOGIES LACK WHAT THE BUSINESS NEEDS License to kill

28 EA is the Bridge between Business & IT EA Business IT

29 EA is a Bridge Really? Business EA IT

30 EA is a Bridge on different Levels Business EA IT

31 EA is a Bridge of different Types Business EA IT

32 EA is a Bridge Combined Business EA IT

33 The languages are different CRM Workflow Business Intelligence SOA Platforms Operating Systems Financial Return CRV Principles Standards Governance Domains Solutions Repository Financial Return Innovation Agility Talent Management Compliance Growth Information Management

34

35 The Gartner EA Process Model

36 Corporate Executive Board

37 The levels of detail are different Those Architects are so theoretical! They produce nothing I can use See, business and IT can be aligned Those Architects are so technical! They do not understand my business at all Business EA IT

38 WHAT DOES A SPY DO?

39 HE TAKES A CHANCE AT CASINO ROYAL and constantly ADAPTS HIS GAME to ensure that he wins

40 WHAT DO WE DO?

41 We defined our EA process but we recognize that process definitions are an illusion.

42 We defined our artifacts Conceptual Architecture Domain Architectures (AS-IS and TO-BE) Business Information Data Applications Technology Security Reference Architectures SOA ECM Collaboration Position Papers Brief documents describing position on technology e.g. Open Source Roadmaps but we recognize that it is more important to learn from creating these than having the artifacts perfectly done.

43 Business Value We ensure Architectural Fit Projects Architectural Fit? Business & IT Strategy Target EA Does it support this? 3 Does it also fit here? 2 Current EA Does it fit here? 1 New business demands Time Are these aligned to the business strategies? 5 Does it deliver on this? What is the experience with the vendor and/or product? 6 4

44 Business Capabilities

45 A PLAN TO MAKE SURE THAT EVERYBODY CONTRIBUTES TO EA Live and let die

46 WHAT DOES A SPY DO?

47 FINDS A QUANTUM OF SOLACE..to ensure that the RIGHT PEOPLE are involved at the RIGHT TIME

48 WHAT DO WE DO?

49 We integrated EA with the SDLC process Initiation, Feasibility & Investigative Analysis Business Plan Business Case Business Strategy, Drivers & Objectives Business Model Planning & Detailed Analysis Analyse & Plan Business Architecture: As-Is to the To-Be. Value Chain, Processes, as required Views Business Requirements Specification (BRS) Test Pack & Plan Risk Analysis & Management Plan Design Project Plan & Time Box Update Acquisition Strategy & Plan Test Pack & Plan Update Update Solution Architecture Build/Buy: Install/ Configure Code/ Develop Solution Build Specifications (Configuration Management): Environment Build Install & Configuration Base Infrastructure Install & Configuration Business Application(s) & Component(s) Install & Configuration Integration & Interface Configuration Collective/ Integration Install & Configuration Test Performance Requirements Criteria Update Test Pack & Plan Test Results & Sign-offs QA Business Requirements Specification Update Systems Requirements Specification Update Test Pack & Plan Update Common Requirements Vision Project Charter Update Solution Map Solution Architecture Solution Design: Update Systems Requirements Specification Unit Test Code/ Develop Solution Functional Test Solution Integration Test UAT Test Performance & Break/Load/ Multi-User Test Regression Test Security Test Acquisition Strategy (specifically RFP requests & selection criteria) Solution Designs Solution Map Cost Analysis (High Level) Application Portfolio / (Potential Solutions) Technology Portfolio / (Potential Solutions) Project Team Presentations Business & Solution Concept Establish Roadmap & Project Approach for next phase Systems Requirements Specification (SRS) Cost Analysis (Detailed) Update Solution Plans: Environment Build Strategy & Plan BCP & DRP Planning strategy Integration & Interface Control Requirements & Plan Conversion/Migration/Transition Strategies & Plans Collective / Integration Configuration Specifications Plan Acquisition Strategy (based on Cost Analysis) Project Team Presentations Finalize BRS Checkpoint: SRS in context of overall Business requirements and Solution Architecture. Check Point: Solution Architecture Checkpoint: Acquisition Strategy Plan (RFI /RFP / RFQ / Std Procurement Process etc) Environment Design Base Infrastructure Design Business Application(s) & Component(s) Design Integration & Interface Design Collective/ Integration Configuration Design Acquisition Strategy (based on Cost Analysis) BCP & DRP Specification Solution Map Update Operations & Maintenance Guide / Schedule Project Team Presentations Finalize financials, processes, risks, functional & non functional deliverables to business. Checkpoint: End to end view of overall solution design ALL contributors to present design Configure Build/Buy Solution Map Update Update Operations & Maintenance Guide / Schedule Checkpoint: Solution Build end to end Project Team view Presentations Checkpoint: Operations & Maintenance BCP & DRP Strategy Change Request & Notification Release Plan Update Operations & Maintenance Guide / Schedule Project Team Presentations Overall Test Results Performance Results Finalize: Operations & Maintenance Solution Build Specifications (Configuration Management): Code Test Results (Report) Solution Map Update

50 Copyright Real IRM Solutions (Pty) Ltd Metropolitan Enterprise Architecture Conceptual Framework Version April 2009 Product Models Lines of Business Product Group Product Type Channel Models Channel Group Channel Type Channel Customer Models Customer Type Location Models Location Type Location Business Risk Models Business Risk Category Business Risk Process Models (L0) Enterprise Process (L1) Macro Process (L2) Process Project Detail Models Project (L2) Process Business Architecture Project Models Programme (L3) Sub-process Business Services Models Business Service Group Business Cycles Models Business Cycle Group Business Cycle Business Service Type Detail Models Business Service Type Customer Type Channel Type Location Type Business Controls (L3) Sub-process (L4) Activity (L5) Task Product Type Information Element Application Systems Project Portfolio Project Business Service Type Business Cycle Events Product Type Detail Models Product Type Business Cycle Business Service Type Customer Type (L3) Sub-process (L3) Sub-process Models Type Business Service Type Logical Data Model Physical Data Model Sub-process Detail Models (L3) Sub-process Document Business Analysts & Architects Product Type Business Rule Role Type Business Service Type Role Job Job/Role Allocation Information Classification Location Type Location Job Business Risk Application Classification Application Services Activity Detail Models (L4) Activity Business Rule Application Systems Application Components Job Document KPI Business Role Location Type Business Cycle Events Business Controls Channel Information Element Business Rule Models Business Rule Category Business Rule Type Business Rule Terminology Models Terms Abbreviations Business Metric Models Scorecard KPA KPI Document Detail Models Document Document Scorecard Ownership Model Scorecard Governance Document Models Document Category Document Type Document Information Delivery Model Information Element KPI Information Architecture Logical Data Model Document Application Services Business Role Message Channel Information Classification Models Information Classification Information Element Information Ownership Model Information Classification Information Element Information Sourcing Model Information Element Logical Data Model Document Application Services Business Role Message Structure Data Architecture Data Models Message Models Logical Data Model Message Physical Data Model Message Structure Logical Data Access Model Application Services Logical Data Model Message Physical Data Access Model Application Component Physical Data Model Message Structure Application Classification Application Services Logical Application Models IT Role Access Model Application Systems Application Components Physical Application Architecture System Process Model Application Component Application Systems Physical Solution Design Model Infrastructure Device Application System Application Component Physical Data Model (L4) Activity (L5) Task Logical Solution Design Model Infrastructure Types Application Classification Message Structure Infrastructure Location Model Devices Infrastructure Ownership Model Devices Infrastructure Models Infrastructure Classification Infrastructure Types 51 Devices Technology Architecture Location Application Components Role Legend Application Services Risk Terminology Logical Application Ownership Model Application Classification Application Services Application Component Physical Application Ownership Model Application System Logical Data Model Message Business Cycle Business Service Process Customer Location Channel Product Primitive Models Document Metric Information Message Data Application Technology Project Composite Models

51 Copyright Real IRM Solutions (Pty) Ltd Metropolitan Enterprise Architecture Conceptual Framework Version April 2009 Product Models Lines of Business Product Group Product Type Channel Models Channel Group Channel Type Channel Customer Models Customer Type Location Models Location Type Location Business Risk Models Business Risk Category Business Risk Process Models (L0) Enterprise Process (L1) Macro Process (L2) Process Project Detail Models Project (L2) Process Business Architecture Project Models Programme (L3) Sub-process Business Services Models Business Service Group Business Cycles Models Business Cycle Group Business Cycle Business Service Type Detail Models Business Service Type Customer Type Channel Type Location Type Business Controls (L3) Sub-process (L4) Activity (L5) Task Product Type Information Element Application Systems Project Portfolio Project Business Service Type Business Cycle Events Product Type Detail Models Product Type Business Cycle Business Service Type Customer Type (L3) Sub-process (L3) Sub-process Models Type Business Service Type Logical Data Model Physical Data Model Role Type Role Job Job/Role Allocation Sub-process Detail Models (L3) Sub-process Business Rule Information Classification Location Type Location Job Document Product Type Business Service Type Business Risk Application Classification Application Services Activity Detail Models (L4) Activity Business Rule Application Systems Application Components Job Document KPI Business Role Location Type Business Cycle Events Business Controls Channel Information Element Business Rule Models Business Rule Category Business Rule Type Business Rule Terminology Models Terms Abbreviations Business Metric Models Scorecard KPA KPI Document Detail Models Document Document Scorecard Ownership Model Scorecard Governance Document Models Document Category Document Type Information Delivery Model Information Element Systems Analysts & Architects KPI Channel Document Information Architecture Logical Data Model Document Application Services Business Role Message Information Classification Models Information Classification Information Element Information Ownership Model Information Classification Information Element Information Sourcing Model Information Element Logical Data Model Document Application Services Business Role Message Structure Data Architecture Data Models Message Models Logical Data Model Message Physical Data Model Message Structure Logical Data Access Model Application Services Logical Data Model Message Physical Data Access Model Application Component Physical Data Model Message Structure Application Classification Application Services Logical Application Models IT Role Access Model Application Systems Application Components Physical Application Architecture System Process Model Application Component Application Systems Physical Solution Design Model Infrastructure Device Application System Application Component Physical Data Model (L4) Activity (L5) Task Logical Solution Design Model Infrastructure Types Application Classification Message Structure Infrastructure Location Model Devices Infrastructure Ownership Model Devices Infrastructure Models Infrastructure Classification Infrastructure Types 52 Devices Technology Architecture Location Application Components Role Legend Application Services Risk Terminology Logical Application Ownership Model Application Classification Application Services Application Component Physical Application Ownership Model Application System Logical Data Model Message Business Cycle Business Service Process Customer Location Channel Product Primitive Models Document Metric Information Message Data Application Technology Project Composite Models

52 A Framework per Business

53 Repository Folder Structure Reflects the Business Structure

54 HOW TO SHOW THE VALUE THAT EA CAN DELIVER Diamonds are forever

55 Showing the value of EA is difficult! What does value mean? How can EA value be quantified? How can one prove that EA is the reason why there is value, when it is part of a bigger process?

56 WHAT DOES A SPY DO?

57 HE DEVELOPS A GOLDEN EYE to IDENTIFY OPPORTUNITIES that deliver value and SEIZE THEM

58 WHAT DO WE DO?

59 Improving Impact & Value of EA FINANCIAL Business Case Analysis Strategic Planning Process Optimization Performance Management COMPLIANCE Security/Privacy Compliance PROJECTS Transition Planning Project Impact Analysis Skills Planning Resource Allocation Sourcing EA Process and EA Knowledge Repository Business Resumption Planning Application Portfolio Risk License Compliance Standards Compliance Asset Redundancies ASSETS

60 Maslow + EA Level: Output: Driven by: STRATEGIC EA = BA+IA+TA Business Direction + Strategy TACTICAL Solution Architectures Projects + Business Initiatives OPERATIONAL Standards + Guideline Business + Technology Change

61 EA Framework Business Drivers, Alignment to Bus. Strategy Strategic Domain Principles Solution Principles Service Delivery, Capacity Planning Why, What Objectives, Goals Tactical Domain Models Architectural Design Service Support How, Who Budget, Performance measures Operational Roadmap Methodology, Standards, Guidelines Execution Architecture When, Where Business Plan Build Run (Domain Arch) (Solution Arch) (Execution Arch)

62 EA and Portfolio Management EA has a unique, enterprise-wide view. IT inventory is first step toward establishing a portfolio Use traditional portfolio management to identify areas for investment, service enabling, and migration Portfolios to manage include: Application portfolio Data portfolio Infrastructure portfolio Project portfolio

63 Technical Condition Application Portfolio View Portfolio Assessment A1 A8 P7 P5 A4 A3 A6 P4 P1 8 A7 6 P8 4 P2 P9 P10 2 P11 A9 A10 P12 P6 P3 A5 A Business Value

64 GET EA INTO THE BOARDROOM The world is not enough

65 Getting into the boardroom is difficult! Architects are seen as technologists that does not know or understand business Architecture is not understood and therefore it is difficult to get invited

66 WHAT DOES A SPY DO?

67 HE SENDS IN DR. NO in his place to important meetings and makes sure Dr. NO LOOKS GOOD

68 WHAT DO WE DO?

69 Architects in the boardroom?! WE DECIDED THAT ARCHITECTS SHOULDN T BE IN THE BOARDROOM Architects must enable business to express EA in the boardroom

70 Architecture is Central to Planning Mission Vision Objectives Model Processes Indicators (KPI s) Business Strategy Drive Business Operations Information Technology Enterprise Architecture Apply Projects Determine Application Infrastructure Data Strategic Tactical Operational Solutions Overlap Solutions

71 Enterprise Governance Ecosystem Tactical Transformation Enterprise Strategy and Planning Project Portfolio Management Enterprise Architecture Strategic Transformation

72 Process Drilldown FINANCIAL Business Visioning COMPLIANCE Environment Analysis Strategy Formulation Enterprise Strategy and Planning Prioritization and Risk Analysis Investment The Managed Portfolio Business Strategic Alignment Future State Creation Tracking Project Portfolio Management Transformation Enterprise Architecture Current State Identification Project Management Lifecycles PROJECTS Resources Gap Analysis ASSETS

73 Proposed Metropolitan EA Structure Architecture Management Committee Enterprise Architecture Board Program Management Office Architecture Advisory Board EA Core Team Solution Architecture Team Architecture Workgroups Domain Architecture Teams EA Modeling Teams SME SME SME Business IT Dept.

74 THANK YOU! QUESTIONS?

75