Enterprise IT Architectures Enterprise Architecture Governance

Transcription

1 Dr. Hans-Peter Hoidn Executive Architect IBM Software Group Enterprise IT s Enterprise Governance

2 Agenda I. Enterprise Governance & Transition II. SOA Governance III. Q&A 2

3 Enterprise Governance & Transition 3

4 What is Governance? Establishing chains of responsibility, authority and communication to empower people (decision rights) Establishing measurement, policy and control mechanisms to enable people to carry out their roles and responsibilities Corporate Governance IT Governance EA Governance SOA Governance 4

5 Governance involves balancing the key aspects of relationships and processes on a foundation of communication THE WILL THE WAY Trust Charter Alignment Organization Responsibilities Principles Communication Processes Behavior Roles & Respon. Culture Relationships Processes Metrics Tools Communication 5

6 Key terms and phrases Enterprise IT s Governance Principle Policy Guideline Business Steering Committee Management Group ( Review Board) A structure of relationships and processes to direct and control the enterprise in order to achieve the enterprise s goals by adding value while balancing risk versus return over IT and its processes. The IT Governance Institute The underlying general rules which an organization will use to utilize and deploy all business and IT resources and assets, across the enterprise e.g. "IT systems will be designed to be capable of rapid expansion in line with unpredicted business growth. In EA we distinguish between Guiding Principles and Usage Principles. A high level statement of how things will be managed or organized, including management goals, objectives, beliefs and responsibilities. Policies are normally defined at an overall strategy level and can be related to a specific area, for example, Security Policies, Management Policies. In many instances, policies reflect the law and givens, which must be adhered to - this is especially true in the case of Security and Privacy policies A general statement of direction, a desired future state which is not necessarily mandated. Guideline statements are similar in content to principle statements, but without the associated motivation and benefit statements. This group is responsible for providing business guidance, communicating changes in business direction, and for approving major changes and variances to the architecture. This committee should represent all business units, and participants should be senior managers (people with decisionmaking authority, for example, general managers or executive vice presidents). The group responsible for managing the design, deployment, maintenance, and evolution of the Enterprise. In addition, the AMG will be responsible for championing the EA throughout the enterprise. 6

7 Enterprise and Governance Strategy Business Opportunity Business Strategy Information Technology Strategy Technology Availability Enterprise wide focus Project focus Planning Design and Delivery Enterprise Business Processes Information People Locations Transition Plan IT Applications Data Technology Business Operating Environment and IT Infrastructure IT Solutions Ensures Alignment Ensures Vitality Ensures Compliance 7

8 Governance! Importance by Illustrating Service Control Sales Accounting department Legal x x x App. 1 App. 2 x Order fulfillment x x Purchasing Currency conversion service 1. Provide a currency service that fills a specific line of business (LOB) 2. Other LOBs start using the service 3. LOBs increase use of services / quality suffers 4. Service is fixed at provider s expense 5. Fix works temporarily but problem reappears 6. Maintenance costs soar / provider ends service * Scenario from Introduction to SOA Governance, Bobby Woolf. 8

9 Governance! Context of the wider Enterprise Enterprise IT s An Enterprise is only as good as the decision making framework that is established around it. (TOGAF) 9

10 EA Governance (how EA decisions are made) is a subset of IT Governance (how IT decisions are made) IT Principles High level statements about how IT is used in the business IT IT Infrastructure Strategies Organizing logic for data, applications, and infrastructure captured in a set of policies, relationships, and technical choices to achieve desired business and technical standardization and integration Strategies for the base foundation of budgeted-for IT capability (both technical and human), shared throughout the firm as reliable services, and centrally located IT Governance EA Governance Business Application Needs Specifying the business need for purchased or internally developed IT applications IT Investment and Prioritization Decisions about how much and where to invest in IT including project approvals and justification techniques Source: IT Governance. How Top Performers Manage IT: Decision Rights for Superior Results, P. Well & J. Ross, Harvard Business School Press,

11 The Governance and Roadmap areas are nested in IT and Enterprise level work Enterprise Governance Enterprise Plan / Roadmap IT Governance IT Roadmap Governance Roadmap 11

12 Governance specifies how decisions are made within a targeted Management System in this case Enterprise. Howwe govern is similar for each management system Communications How we Govern Principles Goals Objectives Roles Organization Incentives Policies Process/Procedures Standards Guidelines Governance Strategy Business Unit Management System IT Management System EA Management System What we Govern Measurements What we Govern EA Service Delivery EA Assets EA Processes EA Resources EA Assets include: Principles, Policies, Standards, Guidelines, Models What we govern varies for each management system 12

13 EA Governance Caveat A balanced approach Optimal Target based on Requirements Unstructured Free-for-all Unrepeatable process No metrics No documentation Relies on heroes Governance Balanced Repeatable process Measurable Documented and used Continuously improved Too Structured No room for creativity Bureaucratic and slow Too many metrics Policy & procedure excess Often ignored / undermined 13

14 EA Governance affects many decision-makers Business Units Executive Committees Technology Briefings Operations Business Direction and Opportunities Approvals & Resources IT Direction and Opportunities Blueprint Architectural Vision, Transition & Vitality Guidance, Standards & Direction Architects Leadership Sponsored issues and opportunities Implementation Projects/Solutions Life Cycle Service Levels, Issues & Escalations Special Task Forces Technology Scans, Assessments, Labs, Metrics, Issues, on demand Architect Design Develop Test Implement 14

15 Governance Considerations What is required? Processes, Roles and Organization Business & IT Strategies Business Directions IT Strategies Key Requirements Roles Definition Service Model Organization Architectural Compliance, Relevance & Value External Effects Technology Changes Vitality Communication New Requirements & Options Compliance IT Investments Compliance Assessment & Impacts Stakeholders Business Value Principles Models Standards Plans 15

16 Business Application Data Technology Perspectives Conceptual Logical Physical Enterprise IT s Key processes are for Review, Vitality, and Change Management Business Strategy IT Strategy People EA Assets & Resources Info Framework Repository Tools Domains Repository Vitality Process Change Management Process Review Process External Environment Stakeholders 16

17 Business Application Data Technology Conceptual Perspectives Logical Physical Enterprise IT s Typical EA Governance Aspects Rules for EA Management Who Manages EA How EA is Managed Rules Roles & Responsibilities Process Models Procedures Tooling Ownership Organization Measurements Solution Perspectives Physical Logical Conceptual Business Domains Domains Application Data Technology Enterprise Solution Staffing All governance deliverables are interrelated; iteration is required to ensure a consistent view across the complete governance framework 17

18 EA Architects are primarily involved in strategy and solution design stages Vision/Strategy Solution Design Construction Implementation EA-Architect IT-Architect IT-Specialist Project Manager Primary Working Environment Secondary Working Environment and Required Experience/Knowledge 18

19 Committees for ensuring Enterprise Business Strategy IT Strategy Enterprise wide focus Enterprise Transition Plan ARB Review Board Gap Analysis Business Model Governance s ITA Arch. Principles EAF Solutions focus ACRT Compliance Review Team Business & Technical Solutions (Projects) "Solution Life Cycle" Deployable Unit 19

20 Roles and Responsibilities Enterprise IT s Strategic Executive Level IT Steering Committees Review Board Leadership Role/Responsibility Business/IT Direction (Project Funding/Approval) Policy & Direction Leadership & Sponsorship (Governance/Standards/Processes) Tactical Business Architect Technical Review Board Implementation Application Architect Data Architect Technology Architect Compliance at Project Level Reviews, consults, mentors project teams Project Teams 20

21 EA Governance Overview of the boards/committees Management Executive Review Board IT Steering Committee Review Board Compliance Review Team Stakeholders Executive Decision Making CEO President CFO CIO Identify Business Requirements Ensure Business and IT are strategically aligned Review and Approve IT Initiatives & Projects Review and Approve Funding Sponsor and Champion Approve R&D Plan Sponsor and Champion Own and Support Vision and Guiding Principles Ensure Compliance Review, Approve/Deny Changes/ Exceptions/Appeals Ensure Vitality and Review Emerging Technologies Champion Review Projects for Compliance with Standards Provide Guidance to the Stakeholders Maintain Standards and Processes Recommend Improvements Comply with & Provide Feedback to ARB Locally Sponsor and Champion Support Conformance to Submit Requests for Changes and Exceptions Monitor Progress Communicate to Stakeholders 21

22 Enterprise Governance also has many dimensions Enterprise Elements Strategic Alignment - Explicit linkages to IT and Business Strategies in order to support ort and implement those strategies Strategy Principles Fundamental rules upon which the Enterprise is based Vision Represents the governing ideas and directions for a target Enterprise Measurements - Measuring the EA benefits and return on investment to prove its value Artifacts Governance Roadmap Framework Structure of the EA, set of conventions for ensuring consistent notation, terminology and and semantics to to describe EA EA Models / Patterns - Overall EA context, diagrams and views; Assemblies of Components Overall EA context, diagrams and views; Assemblies of Components for for communications and guidance Components / Standards Basic building blocks, defining reusable functionality ity of or services Management Processes - Processes required to manage, use and update the Enterprise Roles Key roles and responsibilities necessary to effectively manage and nduse use the the Enterprise Organization Position and reporting structure of the EA Roles Current Environment - An understanding of the organization's current operating environment Gap Analysis - An assessment of the gaps between the Current installed IT environment, and and the the Target IT IT environment Transition Plan - Transition initiatives required to effect transformation from tthe Current State state to the Target State state 22

23 Enterprise Governance Components EA Strategic Organization EA Operations Vision & Mission Roles & Responsibilities Governance Bodies & Cadence Processes Metrics Principles Tooling Organize Execute 23 Vision, Mission, Charter Development of change vision and specific mission Roles & Responsibilities Who are the architecture participants? How do the participants interact? Decision rights Governance Bodies & Cadence What forums review and approve architecture decisions? Who leads and participates in the architecture forums, and how often do they meet? Processes What activities are governed? Who reviews and approves decisions, and how do escalations occur? Metrics What types of metrics and measures are managed? Principles What is the high level development guidance? Tooling What tools will be utilized?

24 Information Governance Aspects Enterprise IT s Information Governance is a holistic approach to managing and leveraging information for business benefits and encompasses people, processes, and technology Executive Sponsors and Champions Organizational structure and definitions of roles and responsibilities Information Governance Experts Data Stewards, Data Managers Data Quality Experts Data Standardization Processes Processes and Business Rules for ongoing governance Information Governance Policies and Procedures Common Data Standards and Business Definitions Data Quality Remediation Processes Change Management Processes (IT & Business) Metadata Repositories, populated with the common data standards, business definitions, data structures, and data transformation rules Workflow Technology Data Quality Remediation Technology Integrated Development and Information Management Platform Reporting & Performance Management Technology 24

25 Transition initiatives need to be prioritized and approved as part of the overall IT Operating Plan for the enterprise EA inspired initiatives should be considered alongside all requests for IT resource (development and implementation): Technology Life Cycle Management Business Strategy Business Initiatives Business driven Technology driven Acceptance Initiative Life Cycle Initiatives driven Prioritisation Implementation of projects Approval & Resourcing 25

26 So as well as guiding development, the EA framework must also provide transition roadmaps TA Product/Service Evaluation Summary 100% 80% 60% Fair 40% Poor 20% Unacceptable Evaluation Percentages Definition Excellent Good 0% % Overall Evaluation Totals 80% New Technology ( Product/Service ) Evaluation Overall Overall Overall Score max Weight % % Weight Weight Score Weight Max Weight % Raw Raw Score Business Functionality Requirements 90% % 90% % 89% Must Have Attributes 100% % 100% Required Attributes 93% % 93% Desired Attributes 73% % 73% Annual Five Year Business Cost of Ownership 61% % 61% % 64% $1,642,000 $6,354,000 Purchase/Upgrade Costs 33% % 33% $304,000 $1,920,000 Installation Costs 60% % 60% $1,064,000 $1,064,000 Maintenance/Service/Support 73% % 73% $210,000 $3,050,000 Costs Training/Documentation Costs 90% % 90% $64,000 $320,000 Deaquisition Costs 0% % 0% $0 $0 Technical Conformance 100% % 100% % 100% Presentation Services 100% % 100% Application Services 100% % 100% Data 100% % 100% Hardware 100% % 100% Operating System 100% % 100% Communication 100% % 100% Usability/Manageability 79% % 79% % 80% Presentation Services 84% % 84% Application Services 68% % 68% Data 85% % 85% Hardware 76% % 76% Operating System 85% % 85% Communication 80% % 80% Vendor Viability 71% % 71% % 74% Financial Performance 72% % 72% Delivery Performance 50% % 50% Support Services 72% % 72% Training Services 100% % 100% Version:7/30/99 Category Weighting: Relative Percentage of overall importance to the business of the specific Category. The sum of all relevant categories must total 100%. Preferred Product Analysis: Selection Criteria Raw Max Building Block: Operating System Current Migration Future Current Environment OS/390, USS390, OS/400, AIX, Solaris, Unix, Win 9x, 2000, Novell, OS/2, MacOS Retirement Targets Win9x, Novell Tactical Deployment zos, Solaris, Win2000, WinXP Strategic Direction zos, Solaris, WinXP, 2003 Preferred zos, Solaris, Windows Sunset Targets OS/400, MacOS, Win 2000 non-solaris Unix Emerging Linux, Autonomic, Virtualisation, Integration, Consolidation 26

27 SOA Governance 27

28 Governance within the SOA Lifecycle Discover Construct & Test Compose Integrate people Integrate processes Manage and integrate information Gather requirements Model & Simulate Design Financial transparency Business/IT alignment Process control Manage applications & services Manage identity & compliance Monitor business metrics 28

29 Why Governance Matters Enterprise IT s Realize business benefits Business process flexibility Improved time to market Mitigate business risk and regain control Maintaining quality of service Ensuring consistency of service Improved team effectiveness Measuring the right things Communicating clearly between business and IT 29

30 What is SOA Governance? Enterprise IT s Service Consumer Service Provider Consumers Business Process Composition; choreography; business state machines Services atomic and composite Service Components Operational Systems Channel Packaged Application B2B Custom Application OO Application Integration (Enterprise Service Bus) QoS Layer (Security, Management & Monitoring Infrastructure Services) Data (meta-data) & Business Intelligence Governance 3 2 Governance 1 SOA Governance? Extension of IT Governance focused on the lifecycle of services to ensure the business value of SOA SOA Governance is a catalyst for improving overall IT Governance 30

31 SOA Governance Life Cycle Addresses Key Questions How do we govern and manage the Life Cycle of services? What standards do we need to establish and when? What processes do we need to identify, develop, deploy and manage services? How do we govern and manage our SOA Identification, development and deployment approach? What can I reuse from my existing IT Governance Model? What metrics and key performance indicators will we use? What is our SOA Vision and Strategy? How does the registry and repository get used? What controls are necessary? How do we measure our model and the effectiveness of services? Who manages the Services Repository? Who uses it? 31

32 SOA Governance Lifecycle How to establish? Plan the Governance Need Document and validate business strategy for SOA and IT Assess current IT and SOA capabilities Define/Refine SOA vision and strategy Review current Governance capabilities and arrangements Layout governance plan Define the Governance Approach Define/modify governance processes Design policies and enforcement mechanisms Identify success factors, metrics Identify owners and funding model Charter/refine SOA Center of Excellence Design governance IT infrastructure Monitor and Manage the Governance Processes Monitor compliance with policies Monitor compliance with governance arrangements Monitor IT effectiveness metrics Enable the Governance Model Incrementally Deploy governance mechanisms Deploy governance IT infrastructure Educate and deploy on expected behaviors and practices Deploy policies 32

33 Service Governance within SOA Governance Service Governance the governing of the individual service lifecycle management process to maximize how that particular service delivers business value and enables the goals of the business. SOA Governance solution portfolio level Process Modeling Services Metadata Model Organizational Change Human Collaboration Portfolio Management Risk Management Service Governance project service level Registry & Repository Support Policy Lifecycle Management Change Management Service Lifecycle Model Service Level Agreement Dashboards & Other Presentation Decision Rights Management 33

34 Governs the Service Consumers as well as the Service Provider Service Provider Service Consumer Eligibility Account Creation Eligibility V2.1 Account Creation V1.0 Service Level Definition Service Level Agreement Service Level Definition Service Endpoint Service Endpoint 34

35 Example: Defining the Governance Solution Tailor Methodology Execute the JKE SOA Governance Project Identify SOA Business and IT Principles Determine Existing Governance Structure Define CoE Structure Create Project Proposal Create the SOA Governance Framework Implement Tools and Infrastructure WebSphere Lotus Rational Tivoli Roles Processes Policies 33% 10% Metrics Quality Gates Refine Operational Environment 35

36 Interaction Between the Lifecycles Service Lifecycle Policies quality gates controls metrics standards are defined in the Governance lifecycle (for different aspects of Governance) and they are enforced in the service lifecycle Governance Lifecycle metrics are captured to improve governance process 36

37 The Governance Framework (Extensions to Development Processes) All the elements that we need to add to make a process well-governed Policies Roles Processes 33% 10% Metrics Quality Gates non-governed process well-governed process 37

38 Example Enforcement at Development Time exception procedure Implement Service that failed Litmus test human decision policy Services should be reused instead of created whenever possible registry lookup quality gate new roles new activities Services must be compliant with the existing reference architecture review 38

39 Example Enforcing Service Reuse Policy During the Identify Services activities, the SOA Architect implements the Service Reuse policy searching for existing services Service Planning Define Service Focus Identify Service Owners Service Modeling Identify Services Specify Services 1 Service Implementation Design Services Assemble Services 3 4 Service Management Manage Quality of Service Manage Service Levels 11 At the Validate Service Design quality gate the policy is enforced Define Service Funding Realize Services 2 Test Services Deploy Services Manage Service Change Manage Service Security Policy 1 Quality Gate 4 Services should be reused instead of created whenever possible Validate Service Design, semi-automatic enforcement during development 39

40 Example Enforcing Compliance Policy The SOA Architect implements the Compliance with the Reference policy during all the activities in the Service Modeling phase Service Planning Define Service Focus Identify Service Owners Service Modeling Identify Services Specify Services 1 Service Implementation Design Services Assemble Services 3 4 Service Management Manage Quality of Service Manage Service Levels 11 At the Validate Service Design quality gate the policy is enforced with a manual review of the service model Define Service Funding Realize Services 2 Test Services Deploy Services Manage Service Change Manage Service Security Policy 2 Quality Gate 4 Services must be compliant with the existing reference architecture Validate Service Design, manual enforcement during development 40

41 Governance at Development Time Enforcing Policies of Services Life Cycle Ensure Compliance and Define Policies 1 Service state transitions are defined based on governance solution WebSphere Service Registry and Repository 2 Validate Service Ownership 3 5 Registry Lookup to enforce reuse of existing services Publish Service to repository after Litmus test is successful 6 Add a Policy for Dynamic Binding Publish Find Enrich Manage Govern Service Analysis and Design 4 Validate Service Design for Standards Compliance 41

42 When is a Repository Used? In every phase of the Service Lifecycle locate services and policies to use or reuse dynamic selection of service endpoints Deployer Administrator SOA Foundation Runtime Analyst Architect Component Developer Integrator Developer evaluate the impact of change publish support policy enforcement manage service environment Deployer Administrator SOA Foundation Runtime 42

43 Supporting the Steps of Service Life Cycle Created Model Plan Repair Assemble Authorize Development Certify Revoke Manage Retired Deprecate 43

44 Main Capabilities of Service Registry and Repository Service Registry and Repository Publish Find Enrich Manage Govern Publish Find Encourage Reuse Find and reuse services for building blocks for new composite applications. Enrich Enhance Connectivity Enable dynamic and efficient interactions between services at runtime. Govern Enable Governance Govern services throughout the service lifecycle Manage Help optimize service performance Enable enforcement of policies. Impact analysis 44

45 APPENDIX TOGAF 46

46 TOGAF (The Open Group Framework) 9.1 TOGAF Version 9.1 is a detailed method and set of supporting resources for developing an Enterprise. Developed and endorsed by the membership of The Open Group's Forum, TOGAF 9.1 represents an industry consensus framework and method for Enterprise that is available for use internally by any organization around the world - members and non-members of The Open Group alike - subject to license conditions. First developed in 1995, TOGAF was based on the US Department of Defense Technical Framework for Information Management (TAFIM). From this sound foundation, The Open Group Forum has developed successive versions of TOGAF at regular intervals and published them on The Open Group public web site. 47

47 What is TOGAF? TOGAF, an Open Group Standard: A proven enterprise architecture methodology and framework used by the world's leading organizations to improve business efficiency The most prominent and reliable enterprise architecture standard, ensuring consistent standards, methods, and communication among enterprise architecture professionals Enterprise architecture professionals fluent in TOGAF standards enjoy greater industry credibility, job effectiveness, and career opportunities TOGAF helps practitioners avoid being locked into proprietary methods, utilize resources more efficiently and effectively, and realize a greater return on investment 48

48 TOGAF Capability Framework Informs the capability Ensures Realization of Business Vision Capability Framework (Part VII) Sets targets, KPIs, budgets for architecture roles Drives need for Capability maturity Business needs feed into method Development Method (Part II) Delivers new business solutions Business Vision and Drivers Refines Understanding ADM Guidelines & Techniques (Part III) Content Framework (Part IV) TOGAF ADM & Content Framework Business Capabilities 49 Informs the Business of the current state Enterprise Continuum & Tools (Part V) TOGAF Reference Models (Part VI) Operational changes cause updates TOGAF Enterprise Continuum & Tools

49 TOGAF 9.1 Content Metamodel 50 Copyright The Open Group 2011