ibm managing and governing change for enterprise architecture

®

IBM Software Group

© 2008 IBM Corporation

Managing and governing change for enterprise architecture

Bill DuncanFederal, Aerospace & DefenseTelelogic Brand Software

Bill DuncanFederal, Aerospace & DefenseTelelogic Brand Software

IBM Software Group | Rational software

2

Enterprises are global and rapidly changing

Every organization must accommodate change, whether that change is due to: Shifting marketplace demands

Dynamic competitive environments

Internal restructuring

Customer requirements

Competitive pressures

State of the economy

Mergers/acquisitions


3

Enterprise architecture—help turn change into a competitive advantage Enterprise architecture (EA) and

enterprise planning can help organizations intelligently prepare for change and pursue successful transitions in manageable, progressive phases Identify our comprehensive current state

Create plans to support optimization and continued improvement

Help identify the impact that our changes will make to the organization

Exploit assets of the enterprise that should effectively guide solution development and project delivery

Communicate information, analyses and decisions in rapid, continuous cycles, helping to create a smarter, more efficient organization


4

EA change management and governance—the foundation for migrating to the future state Enterprise architecture should never be considered “complete”

As the business grows and evolves, so should the architecture governing its systems and processes

Architecture must remain dynamic and able to change with the demands of the business environment

The objective of the EA discipline is to deliver knowledge, facilitate the voyage and help ensure that the proper path is followed

This “living” project brings forth challenges in maintaining data and modeling consistency that: Follow standards that were previously approved

Incorporate new technical patterns and services, information, solutions and business processes

Evolve the future-state roadmaps to reflect changes in business strategy


5

Enterprise architecture governance touches a large team of decision makers

Architectural Vision, Transition

& Vitality

Architecture Blueprint

Technology Scans, Assessments, Labs, Metrics,

Issues, on demand

Architecture Implementation

Architecture LeadershipSponsored issues & opportunities

Executive Committees

Special Task Forces

Business Direction

& OpportunitiesIT Direction

& Opportunities

Technology BriefingsBusiness Units

Service Levels, Issues &

Escalations

Architects

Operations

Architect Design Develop Test Implement

Projects/Solutions Lifecycle

Approvals & Resources

Guidance, Standards &

Direction


6

Building an enterprise architecture—the formal approval structure

Architecture board Decides on which IT

is best suited for the needs of the enterprise

Decides when a change in the architecture is needed

Prioritizes initiativesOffice of the chief architect Ensures that solution

designs comply with the architecture

Maintains the architecture

Project design authorities Use the architecture to best

satisfy the project’s needs

Architecture board

Office of the chief architect

Project design authorities


7

Architecture governance—what is appropriate for your organization? Striking the right balance is important

The manner in which enterprise architects engage with business, solution and IT architects must fit the enterprise’s management style Too loose can lead to inaccurate contributions

and circumventing of important standards and policies

Too structured can equal “analysis paralysis”

Which fits your wider cultural context? Which applies to your organization now? Which will be needed in the future? Command and control

“Do what I say, and I will ensure you do” Guide and govern

“Use the architecture, and we’ll discuss those areas where it does not make sense”

Publish and trust“I know you will do your best—go do it” And whichever style you choose, a balance will be needed


8

The IBM solution—Telelogic System Architect and Telelogic Change integration

Offers organizations a formal method to help manage the complexity associated with deploying EA and business process analysis (BPA) that span business and IT

Helps manage changes of models and tasks through the ability to integrate Telelogic® System Architect® with Telelogic Change™ solutions

In this release, the integration can deliver the following benefits: Help establish governance and compliance in the EA process

Better manage lifecycle customization

Support project security

Track project progress through Change reporting

Help manage the following questions in EA deployment: Who is responsible for this change?

Why was this changed?

What is the impact of this change?


9

System Architect and Change: how it works—the integrated workflow


10

Be up and running more quickly by leveraging proven integrated lifecycle management

Assign

Complete Task (IR)

CreatedCreated

AssignedAssigned

ResolvedResolved

ConcludedConcluded

Task(Work on IR)

Task(Work on IR)

Resolve ConcludeIR

Set "Default" IR

AssignedAssigned

ValidatedValidated

ConcludedConcluded

Validate Conclude

CreatedCreated

AssignedAssigned

ReviewedReviewed

ApprovedApproved

AppliedApplied

AssignRCR Send to Review Approved Apply (In DOORS)

Work on RCR

Work on RCR

Complete RCRSet "Default" RCR

10


11

How does it apply to enterprise architecture—a sample scenario

System Architect approved reference architecture model

Change repository

“AS IS”

System Architect work space for proposed changes

“TO BE”

(3) A new workspace is created (or existing identified) for the proposed work …

(2) Change request (CR) is assigned by CCM to an analyst

(1) A change request is createdEnterprise Architect


12

How does it apply to enterprise architecture—a sample scenario (continued)

System Architect approved reference architecture model

Change repository

“AS IS”

System Architect work space for proposed changes

“TO BE”

(4) Analyst links work area to change request, performs work, assigns work for reviewerBusiness Analyst, Architect

(5) Identified changes are approved and assigned to analyst to “deliver” to approved area …

Enterprise Architect

(6) Analyst delivers work to approved area and closes the change request Business

Analyst, Architect


13

A tightly integrated solution—the System Architect user’s perspective A new toolbar is introduced in

System Architect Without leaving, view a list of

change requests that can be filtered per the needs of the team member

A new change review form is introduced in System Architect

Track change history

View how changes have been modified, approved or rejected over time


14

A tightly integrated solution—change management for the architecture board When you click on the

change request in System Architect:

The change request launches in the Telelogic Change intuitive Web Interface

Change request details are displayed


15

Industry-proven change management capabilities—Telelogic Change Robust repository for managing and communicating

process and change

Designed for easy deployment (Web) and customization

Built-in lifecycle editor (XML)

Comprehensive reporting and metrics

Better manage who is working on what, and where

Electronic signatures

Track changes within a release From requirements to models, source code and

test cases

Hand off change requests to distributed teams

Application programming interface (API) Web services BSF triggers

15


16

Appendix: How it works—more details


17

How it works

1. In SAEM, enable change management for particular encyclopedia


18

How it works (continued)

2. In SAEM, specify settings of change database


19


3. In System Architect .ini file settings, specify your role and user


20


4. In System Architect, view ERs by type and select specific ERs in the Change toolbar

5. As you work, you will be working against selected ER


21

New Change toolbar

Show list of CRs depending onfilter settings such as: State

Change request #

Title

Allow selection of one of the CRs, making it the “active CR” It is okay to have no active CR

A “Refresh” button can update the CR and state lists

An “Open CR” button opens the active CR in Telelogic Change

A “Show Change History” button can open a form showing changes associated with the active CR


22

How it works

6. In a System Architect definition, click on History to view history of changes to a definition’s property


23

History is associated with active CR

The active CR is associated with history records as they are created


24

How it works

7. In System Architect, select Change History to get history of your changes


25

Supporting change-related information retrieval

A new form in System Architect shows System Architect history records related to a given CR:

From an entry in this form, the user can: Open the definition or diagram and then view property history

Print or save to file


26

How it works—navigation

8. In System Architect, click on the “Open CR” button in the Change toolbar


27

How it works—navigation (continued)

Telelogic Change launches with the CR brought up


28

Telelogic Change 5.0—central change server

Changing Requirements

MarketAnalysis

DesignChanges

R&D

CompetitiveAnalysis

RegulatoryCompliance

Customer Needs

ProductFeedback

Integrated Lifecycle Change Management with Telelogic Change

SoftwareConfiguration

and Build/Release Management

Telelogic Synergy™

IBM Rational® ClearCase®

Subversion

Product andPortfolio

Management

Model-drivenArchitecture

andDevelopment

ChangeManagement

ToolsJIRA

IBM RationalClearQuest®

BugzillaChange

EnterpriseArchitecture

RequirementsManagement

BusinessProcessModeling

Metrics andMeasurement

TestAutomation

Governanceand

Compliance

ProjectManagement

ServiceManagement

28


29

How it works—navigation

Case B: The user is in Change and wants to know more about the objects changed in the System Architect encyclopedia for a particular CR

9. Click the “Show Change History” button in Change to see a list of the System Architect encyclopedia changes associated with the desired CR


30

For more information

To learn more, please visit:

www.telelogic.com

Learn more about IBM Rational software at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management

Rational trial downloads Leading Innovation Web site developerWorks® Rational IBM Rational TV IBM Business Partners IBM Rational case studies


31

Copyright information

© Copyright IBM Corporation 2008

IBM CorporationSoftware GroupRoute 100Somers, NY 10589U.S.A.

Produced in the United States of AmericaOctober 2008All Rights Reserved

IBM, the IBM logo, ibm.com, Rational, and Telelogic are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at ibm.com/legal/copytrade.shtml

Other company, product, or service names may be trademarks or service marks of others.

References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates.

The information contained in this document is provided for informational purposes only and provided “as is” without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. Without limiting the foregoing, all statements regarding IBM future direction or intent are subject to change or withdrawal without notice and represent goals and objectives only. Nothing contained in this documentation 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.

IBM customers are responsible for ensuring their own compliance with legal requirements. It is the customer’s sole responsibility to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer's business and any actions the customer may need to take to comply with such laws.

RAP14036-USEN-00

ibm managing and governing change for enterprise architecture

Business

processes architecture

architecture governancewhat

ea change management

telelogic change solutions

telelogic change integration

enterprise architects

enterprise architecturehelp

business processes