Ibm Managing And Governing Change For Enterprise Architecture


Published on

Published in: Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Standard template for internal and external Rational presentations. If internal presentations are confidential, please add: “IBM Confidential” to the slide masters. Select: View / Master / Slide Master and add “IBM Confidential”
  • Ibm Managing And Governing Change For Enterprise Architecture

    1. 1. Managing and governing change for enterprise architecture Bill Duncan Federal, Aerospace & Defense Telelogic Brand Software
    2. 2. Enterprises are global and rapidly changing <ul><li>Every organization must accommodate change, whether that change is due to: </li></ul><ul><ul><li>Shifting marketplace demands </li></ul></ul><ul><ul><li>Dynamic competitive environments </li></ul></ul><ul><ul><li>Internal restructuring </li></ul></ul><ul><ul><li>Customer requirements </li></ul></ul><ul><ul><li>Competitive pressures </li></ul></ul><ul><ul><li>State of the economy </li></ul></ul><ul><ul><li>Mergers/acquisitions </li></ul></ul>
    3. 3. Enterprise architecture—help turn change into a competitive advantage <ul><li>Enterprise architecture (EA) and enterprise planning can help organizations intelligently prepare for change and pursue successful transitions in manageable, progressive phases </li></ul><ul><ul><li>Identify our comprehensive current state </li></ul></ul><ul><ul><li>Create plans to support optimization and continued improvement </li></ul></ul><ul><ul><li>Help identify the impact that our changes will make to the organization </li></ul></ul><ul><ul><li>Exploit assets of the enterprise that should effectively guide solution development and project delivery </li></ul></ul><ul><ul><li>Communicate information , analyses and decisions in rapid, continuous cycles, helping to create a smarter, more efficient organization </li></ul></ul>
    4. 4. EA change management and governance— the foundation for migrating to the future state <ul><li>Enterprise architecture should never be considered “complete” </li></ul><ul><ul><li>As the business grows and evolves, so should the architecture governing its systems and processes </li></ul></ul><ul><ul><li>Architecture must remain dynamic and able to change with the demands of the business environment </li></ul></ul><ul><li>The objective of the EA discipline is to deliver knowledge, facilitate the voyage and help ensure that the proper path is followed </li></ul><ul><li>This “living” project brings forth challenges in maintaining data and modeling consistency that: </li></ul><ul><ul><li>Follow standards that were previously approved </li></ul></ul><ul><ul><li>Incorporate new technical patterns and services, information, solutions and business processes </li></ul></ul><ul><ul><li>Evolve the future-state roadmaps to reflect changes in business strategy </li></ul></ul>
    5. 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 Leadership Sponsored issues & opportunities Executive Committees Special Task Forces Business Direction & Opportunities IT Direction & Opportunities Technology Briefings Business Units Service Levels, Issues & Escalations Architects Operations Architect Design Develop Test Implement Projects/Solutions Lifecycle Approvals & Resources Guidance, Standards & Direction
    6. 6. Building an enterprise architecture—the formal approval structure <ul><li>Architecture board </li></ul><ul><li>Decides on which IT is best suited for the needs of the enterprise </li></ul><ul><li>Decides when a change in the architecture is needed </li></ul><ul><li>Prioritizes initiatives </li></ul><ul><li>Office of the </li></ul><ul><li>chief architect </li></ul><ul><li>Ensures that solution designs comply with the architecture </li></ul><ul><li>Maintains the architecture </li></ul><ul><li>Project design authorities </li></ul><ul><li>Use the architecture to best satisfy the project’s needs </li></ul>Architecture board Office of the chief architect Project design authorities
    7. 7. Architecture governance—what is appropriate for your organization? <ul><li>Striking the right balance is important </li></ul><ul><li>The manner in which enterprise architects engage with business, solution and IT architects must fit the enterprise’s management style </li></ul><ul><ul><li>Too loose can lead to inaccurate contributions and circumventing of important standards and policies </li></ul></ul><ul><ul><li>Too structured can equal “ analysis paralysis ” </li></ul></ul><ul><li>Which fits your wider cultural context? Which applies to your organization now? Which will be needed in the future? </li></ul><ul><ul><li>Command and control “Do what I say, and I will ensure you do” </li></ul></ul><ul><ul><li>Guide and govern “Use the architecture, and we’ll discuss those areas where it does not make sense” </li></ul></ul><ul><ul><li>Publish and trust “I know you will do your best—go do it” </li></ul></ul>And whichever style you choose, a balance will be needed
    8. 8. The IBM solution—Telelogic System Architect and Telelogic Change integration <ul><li>Offers organizations a formal method to help manage the complexity associated with deploying EA and business process analysis (BPA) that span business and IT </li></ul><ul><li>Helps manage changes of models and tasks through the ability to integrate Telelogic ® System Architect ® with Telelogic Change ™ solutions </li></ul><ul><li>In this release, the integration can deliver the following benefits: </li></ul><ul><ul><li>Help establish governance and compliance in the EA process </li></ul></ul><ul><ul><li>Better manage lifecycle customization </li></ul></ul><ul><ul><li>Support project security </li></ul></ul><ul><ul><li>Track project progress through Change reporting </li></ul></ul><ul><li>Help manage the following questions in EA deployment: </li></ul><ul><ul><li>Who is responsible for this change? </li></ul></ul><ul><ul><li>Why was this changed? </li></ul></ul><ul><ul><li>What is the impact of this change? </li></ul></ul>
    9. 9. System Architect and Change: how it works— the integrated workflow
    10. 10. Be up and running more quickly by leveraging proven integrated lifecycle management Assign Complete Task (IR) Created Assigned Resolved Concluded Task (Work on IR) Resolve Conclude IR Set &quot;Default&quot; IR Assigned Validated Concluded Validate Conclude Created Assigned Reviewed Approved Applied Assign RCR Send to Review Approved Apply (In DOORS) Work on RCR Complete RCR Set &quot;Default&quot; RCR
    11. 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 created Enterprise Architect
    12. 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 reviewer Business 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. 13. A tightly integrated solution—the System Architect user’s perspective <ul><li>A new toolbar is introduced in System Architect </li></ul><ul><ul><li>Without leaving, view a list of change requests that can be filtered per the needs of the team member </li></ul></ul><ul><li>A new change review form is introduced in System Architect </li></ul><ul><ul><li>Track change history </li></ul></ul><ul><ul><li>View how changes have been modified, approved or rejected over time </li></ul></ul>
    14. 14. <ul><li>When you click on the change request in System Architect: </li></ul><ul><ul><li>The change request launches in the Telelogic Change intuitive Web Interface </li></ul></ul><ul><ul><li>Change request details are displayed </li></ul></ul>A tightly integrated solution—change management for the architecture board
    15. 15. Industry-proven change management capabilities—Telelogic Change <ul><li>Robust repository for managing and communicating process and change </li></ul><ul><li>Designed for easy deployment (Web) and customization </li></ul><ul><li>Built-in lifecycle editor (XML) </li></ul><ul><li>Comprehensive reporting and metrics </li></ul><ul><li>Better manage who is working on what, and where </li></ul><ul><li>Electronic signatures </li></ul><ul><li>Track changes within a release </li></ul><ul><ul><li>From requirements to models, source code and test cases </li></ul></ul><ul><li>Hand off change requests to distributed teams </li></ul><ul><li>Application programming interface (API) </li></ul><ul><ul><li>Web services </li></ul></ul><ul><ul><li>BSF triggers </li></ul></ul>
    16. 16. Appendix: How it works—more details
    17. 17. How it works <ul><li>In SAEM, enable change management for particular encyclopedia </li></ul>
    18. 18. How it works (continued) <ul><li>In SAEM, specify settings of change database </li></ul>
    19. 19. How it works (continued) <ul><li>In System Architect .ini file settings, specify your role and user </li></ul>
    20. 20. How it works (continued) <ul><li>In System Architect, view ERs by type and select specific ERs in the Change toolbar </li></ul><ul><li>As you work, you will be working against selected ER </li></ul>
    21. 21. New Change toolbar <ul><li>Show list of CRs depending on filter settings such as: </li></ul><ul><ul><li>State </li></ul></ul><ul><ul><li>Change request # </li></ul></ul><ul><ul><li>Title </li></ul></ul><ul><li>Allow selection of one of the CRs, making it the “active CR” </li></ul><ul><ul><li>It is okay to have no active CR </li></ul></ul><ul><li>A “Refresh” button can update the CR and state lists </li></ul><ul><li>An “Open CR” button opens the active CR in Telelogic Change </li></ul><ul><li>A “Show Change History” button can open a form showing changes associated with the active CR </li></ul>
    22. 22. How it works <ul><li>In a System Architect definition, click on History to view history of changes to a definition’s property </li></ul>
    23. 23. History is associated with active CR <ul><li>The active CR is associated with history records as they are created </li></ul>
    24. 24. How it works <ul><li>In System Architect, select Change History to get history of your changes </li></ul>
    25. 25. Supporting change-related information retrieval <ul><li>A new form in System Architect shows System Architect history records related to a given CR: </li></ul><ul><li>From an entry in this form, the user can: </li></ul><ul><ul><li>Open the definition or diagram and then view property history </li></ul></ul><ul><ul><li>Print or save to file </li></ul></ul>
    26. 26. How it works—navigation <ul><li>In System Architect, click on the “Open CR” button in the Change toolbar </li></ul>
    27. 27. How it works—navigation (continued) <ul><li>Telelogic Change launches with the CR brought up </li></ul>
    28. 28. Telelogic Change 5.0—central change server Changing Requirements Market Analysis Design Changes R&D Competitive Analysis Regulatory Compliance Customer Needs Product Feedback Integrated Lifecycle Change Management with Telelogic Change Software Configuration and Build/Release Management Telelogic Synergy ™ IBM Rational ® ClearCase ® Subversion Product and Portfolio Management Model-driven Architecture and Development Change Management Tools JIRA IBM Rational ClearQuest ® Bugzilla Change Enterprise Architecture Requirements Management Business Process Modeling Metrics and Measurement Test Automation Governance and Compliance Project Management Service Management
    29. 29. How it works—navigation <ul><li>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 </li></ul><ul><li>Click the “Show Change History” button in Change to see a list of the System Architect encyclopedia changes associated with the desired CR </li></ul>
    30. 30. For more information To learn more, please visit: <ul><li>Learn more about IBM Rational software at: </li></ul><ul><li>IBM Rational software </li></ul><ul><li>IBM Rational Software Delivery Platform </li></ul><ul><li>Process and portfolio management </li></ul><ul><li>Change and release management </li></ul><ul><li>Quality management </li></ul><ul><li>Architecture management </li></ul><ul><li>Rational trial downloads </li></ul><ul><li>Leading Innovation Web site </li></ul><ul><li>developerWorks ® Rational </li></ul><ul><li>IBM Rational TV </li></ul><ul><li>IBM Business Partners </li></ul><ul><li>IBM Rational case studies </li></ul>
    31. 31. Copyright information <ul><li>© Copyright IBM Corporation 2008 </li></ul><ul><li>IBM Corporation Software Group Route 100 Somers, NY 10589 U.S.A. </li></ul><ul><li>Produced in the United States of America October 2008 All Rights Reserved </li></ul><ul><li>IBM, the IBM logo,, 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 &quot;Copyright and trademark information&quot; at </li></ul><ul><li>Other company, product, or service names may be trademarks or service marks of others. </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul><ul><li>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. </li></ul>RAP14036-USEN-00