The Enterprise Architecture Workspace Your Architecture Blueprint Martin

The Enterprise Architecture Workspace: Your Architecture Blueprint Martin Owen Senior Product Manager, IBM Rational martin. [email protected] ibm. com Select View/Master/Slide Master to add Session Number Here © 2009 IBM Corporation

IBM Rational Software Conference 2009 Agenda § Overview of Enterprise Architecture lifecycle 4 Enterprise Architecture as a Blueprint 4 The difference between EA and S/W development lifecycles § The Enterprise Architecture Workspace 4 Basic Concepts 4 Usage Patterns § “As Is” – “To Be” ; Baselines & Variants § Change Management Interface § Peripheral Tools § What a workspace is not § Demonstration § Q&A Germany Nov 2009 – Enterprise Architecture Workspaces 2

IBM Rational Software Conference 2009 Overview of EA lifecycle Germany Nov 2009 – Enterprise Architecture Workspaces 3

IBM Rational Software Conference 2009 Architecture enables organisations to “do the right things right” Strategic Intent Smart Strategy "These are the projects we should do” “Do the right things” SOA principles & platform The Enterprise’s Architecture Smart Planning Smart Design, Development, Delivery “Do things right” Project Scoping Project Prioritisation & planning "These are the projects we will do” Project Scoping External Design Internal Design Build Cycle Deployment Germany Nov 2009 – Enterprise Architecture Workspaces Deployment & Delivery “Here you are!” 4

IBM Rational Software Conference 2009 Architecture… more detail… UPSTREAM EA: Identifying viable projects (including those that will use BPM) to help realise the enterprise architecture requires a DOWNSTREAM EA: Ensuring projects can exploit the architecture’s “standard components” or building blocks, including those that are doing things the BPM way Strategic Intent requires each part to be described and published in an easy-to-use, easyto-find “catalogue like” format good set of “models”, capable of portraying the overall “as is” and “to be” architectural landscape Enterprise Transition Initiatives “These are our roadmaps” “Are we still moving the right direction? ” "These are the projects we should do” Enterprise Business Architecture “Are our target architectures still right? ” Architecture Governance Enterprise IT Architecture Functional Operational "Are we designing these systems the way we said we want them done? ” "This is the way these systems should be designed” Business & IT solution design Project Scoping Project prioritisation & planning External Design Internal Design Build Cycle Deployment Business & IT solution design "These are the projects we will do” Project Scoping External Design Internal Design Build Cycle Deployment Business & IT solution design Project Scoping External Design Internal Design Build Cycle Deployment Germany Nov 2009 – Enterprise Architecture Workspaces Strategic Delivery “Here you are!” 5

IBM Rational Software Conference 2009 The EA Lifecycle § Techniques involved 4 Enterprise Architecture Modeling (Strategy, Business Process, High Level Architecture, Services and Capabilities, Roadmaps, Organizations, Plans) 4 Documentation & Reporting § Change is… 4 Continuous, slower (than change in s/w development), medium-high approval cycle (governance) § Change i/f, Audit IDs, Refined ACL 4 Multiple plans and programs are proposed § The main output is an architecture blueprint 4 Recommendations 4 Constraints § How to transition and decide between blueprints 4 Timelines/Roadmaps 4 Costs TOGAF 9 ADM Germany Nov 2009 – Enterprise Architecture Workspaces 6

IBM Rational Software Conference 2009 The Implementation & Deployment Lifecycle § We can contrast EA with the implementation & deployment lifecycle § Change is … 4 Frequent, rapid, reviewed quickly, light-medium approval cycle 4 Multiple simultaneous changes made to the same artifacts as common practice § The main output is “something that runs or executes” 4 Multiple branches could exist 4 …. as multiple releases exist § Construction Tools are involved 4 Debuggers, Compilers, Editors 4 Test Suites, Modeling, Deployment § Change Management tools 4 Bug trackers, Task management 4 Source Control and Configuration Germany Nov 2009 – Enterprise Architecture Workspaces 7

IBM Rational Software Conference 2009 Architecture… with frequency of change… Model to Plan Low Frequency Changes Merge (from various sources) Reviewed manually, often with extended team Model to Build High Frequency Changes Automated Merge Germany Nov 2009 – Enterprise Architecture Workspaces 8

IBM Rational Software Conference 2009 The Enterprise Architecture Workspace Germany Nov 2009 – Enterprise Architecture Workspaces 9

IBM Rational Software Conference 2009 What is an Enterprise Architecture Workspace ? § A container of EA modeling artifacts 4 Spans across Definitions, Diagrams, Symbols etc (SA terminology) 4 Spans across domains (Business Modeling, Strategy Mapping, Network Diagrams, Organization charts etc) § The workspace is isolated for the purpose of a dedicated project, program etc 4 Changes done in this workspace will not affect the master blueprint 4 Once approved, changes can be rolled up into the master blueprint § A workspace can be “baselined” 4 A frozen snapshot in time of the entire architecture § New workspaces can be created from a “baselined” workspace 4 Spawn a new project with pre populated content § Changes in Workspaces can be associated with tasks or change request in a change tracking system Germany Nov 2009 – Enterprise Architecture Workspaces 10

IBM Rational Software Conference 2009 EA Workspace Patterns E. Opportunities & Solutions Compliance Program osal Prop ation u Eval / As Is e To B G. F. EA ce / plian ce Com rnan Gove E. Opportunities & Solutions Implementation Governance Migration Planning EA 1. 2 V 1. 3 Acquisition Outsourcing Initiative EA EA EA 2. 0 V 1. 3 EA 1. 3 V 1. 3 G. H. Implementation Governance Architecture Change Management Set Constrains & Define Guidelines print Blue sh Refre Collect and Incorporate Feedback § Development, Deployment § Program Timelines § Business Process Germany Nov 2009 – Enterprise Architecture Workspaces 11

IBM Rational Software Conference 2009 “AS IS” vs. “TO BE” Scenario: Zoom in Workspace Alternative To Be – X Outsourcing Initiative X EA EA EA 1. 3 V 1. 3 EA 1. 4 V 1. 3 As Is Workspace Y To Be – Alternative Y Germany Nov 2009 – Enterprise Architecture Workspaces 12

IBM Rational Software Conference 2009 What a workspace is not… § It is not a User Interface (UI) filter 4 Use the “views” feature introduced in SA 11. 0 to organise browser tree 4 Static & Dynamic views should be used as UI filters § It is not a folder 4 Using workspace as a folder may bring about undesired results § Users cannot report across workspaces § Users cannot link/relate items across workspaces 4 Examples: § DO: Create a Workspace to modify the existing EA Repository in order to develop a proposal § DON’T: Create a workspace describing the HR department and another for the Finance department – You will not be able to relate the HR manager to the Finance data base Germany Nov 2009 – Enterprise Architecture Workspaces 13

IBM Rational Software Conference 2009 Germany Nov 2009 – Enterprise Architecture Workspaces 14

IBM Rational Software Conference 2009 Germany Nov 2009 – Enterprise Architecture Workspaces 15

IBM Rational Software Conference 2009 © Copyright IBM Corporation 2009. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. Germany Nov 2009 – Enterprise Architecture Workspaces 16