IBM Rational Software Development Conference 2008 Introducing Application

® IBM Rational Software Development Conference 2008 Introducing Application Lifecycle Management on IBM® Rational® Clear. Quest® Carolyn Pampino Solution Architect, IBM Rational cpampino@us. ibm. com CRM 18 © 2007 IBM Corporation

IBM Rational Software Development Conference 2008 Disclaimer and Non-Disclosure ! h c u O § This solution is available from Devworks for CQ 7. 0. 1 users; 4 http: //www. ibm. com/developerworks/rational/downloads/08/cq_almpackage/index. html § included in Clear. Quest 7. 1 § IBM Rational Plans are subject to change § Nothing in this document is intended to create any representations or warranties § IBM Rational warranties are contained in the applicable license agreements CRM 18 2

IBM Rational Software Development Conference 2008 Agenda Pow! The What and Why of this Solution Core Concepts 4 Projects 4 Work 4 System-wide Settings Customization options and examples Integrations 4 Themes 4 UCM 4 Build Forge 4 Requisite. Pro CRM 18 3

IBM Rational Software Development Conference 2008 What is Application Lifecycle Management on CQ? § Out-of-box ALM Solution for Clear. Quest (schema and packages) § Process model focused on work completed in the context of a Project § Requests are planned as Tasks and performed as Activities § Workload can be balanced across Phases and Iterations of a Project § Each project team can customize the configuration Submitter • Submits request for change • (Validate release) Test Lead • Ensure quality Tester • Test changes in baselines Change Control Mgr • Triage requests • Assigns tasks to projects Change performed in the context of Project Request Category Task Release Activity Project and Plan definition Work and Delivery definition Team Lead • Assigns activities to complete tasks Developer • Work on activities • Develop and deliver changes Release Engineer • Integrate and build delivered changes • Create baselines CRM 18 4

IBM Rational Software Development Conference 2008 CQALM Out-Of-The-Box Schema - Objectives § Useful to 100% of new and existing Clear. Quest customers 4 Provide at least 70% of functionality out-of-the box 4 Scalable ALM model from Small teams to Enterprise Programs and Projects 4 Multisite and UCM enabled, but not required 4 Available as a download for CQ 7. 0. 1 users 4 Delivered with Clear. Quest v 7. 1 as a set of packages and a schema s! ook Gadz § Reduce customer cost-of-ownership & improve ROI 4 Reduce time to deployment by at least 50% 4 Remove the need for ‘one-size does not fit-all’ records with complex state transitions 4 Empower project managers & team leads to configure projects without impacting the schema 4 Reduce the amount of administrative changes needed to support enterprise users § Provide fundamental “building blocks” to get started 4 Provide a secure Project Context with Role-based ‘allowed actions’ 4 Govern projects using project and work tracking capabilities 4 Simplify the ability to support regulatory compliance initiatives 4 Out-of-box ALM Sample Database demonstrating Open. UP support CRM 18 5

IBM Rational Software Development Conference 2008 Agenda w! o l p Ka The What and Why of this Solution Core Concepts 4 Projects 4 Work 4 System-wide Settings Customization options and examples Integrations 4 Themes 4 UCM 4 Build Forge 4 Requisite. Pro CRM 18 6 6

IBM Rational Software Development Conference 2008 Core Concepts 1 Projects provide security, roles, and a context 2 Work is completed in the context of a project 3 There are system-wide settings that you can modify without having to change the schema CRM 18 7 7

IBM Rational Software Development Conference 2008 Introducing Projects Project Role User Group super / sub prev / next Existing Clear. Quest Security Context Category Release Security-policy Work Configuration Phase And others we’ll discuss later Iteration Project definition ALM System-wide settings Projects provide the context for doing work & are uniquely identified Security determines visibility, Roles determine allowed actions for users Phases and Iterations divide projects into time-boxed deliverables Project definitions can change without modifying the schema CRM 18 8

IBM Rational Software Development Conference 2008 Projects, Roles and Security 1 Create Users and Groups User Role 5 Group Create ALM Role Existing Clear. Quest Project 3 Choose Security Policy Security Context super / sub prev / next Security-policy Role Label Project definition ALM System-wide settings Security Policy determines who can see which projects 2 Create ALM Security Policy Role determines who can do what (Allowed Actions) 4 Create ALM Role Label CRM 18 9 9

IBM Rational Software Development Conference 2008 Creating a Security Policy 1 Provide a name and description 2 Add one or more CQ Groups Note: Everyone group opens access to all users CRM 18 10 10

IBM Rational Software Development Conference 2008 Creating a Role 1 Set the Project 3 2 Add users Choose a Role Label or Create a New one 4 CRM 18 Refine the Approved Actions 11 11

IBM Rational Software Development Conference 2008 Projects Uniqueness Project super / sub 3 Category Type Label Choose Category super / prev / next Category 4 sub Choose Release Label Project definition ALM System-wide settings Category provides a classification 1 Create ALM Categories Release defines the version 2 Create ALM Release Label(s) CRM 18 12 12

IBM Rational Software Development Conference 2008 Categories Classify Projects Category Type Label Product A Category Type Label Service A Category Feature B Category Feature Category Product B CRM 18 Service B Category Feature A Category Feature B Category 13 13

IBM Rational Software Development Conference 2008 Projects Planning & Work Configuration Project super / sub prev / next 3 Create Phase(s) 4 Create Iteration(s) 5 Phase Label Iteration Label Work Type Label Create Work Configuration(s) Work Configuration Work Type Role Project definition ALM System-wide settings Phases & Iterations create time-boxed deliverables 1 Work Types define the ‘nature’ of the work 2 Create Phase & Iteration Label(s) Create ALM Type(s) Work Configuration defines a recommended process CRM 18 14 14

IBM Rational Software Development Conference 2008 Managing “Work” User Request § Assess § Plan related § Design Task related Activity § Defect § Enhancement § Implement § Test § Deploy §… Activity Work Type § New Feature §… Work and Delivery definition ALM System-wide settings Requests define the ‘need’ & where it was ‘found’ Tasks define the work needed to complete the request for a project Activities are assigned to individuals & collectively complete the Task Work Type identifies the ‘nature’ of the work CRM 18 15 15

IBM Rational Software Development Conference 2008 Simple State Transitions Request Task Activity Open Submit Opened Re-Open Ready. To. Waiting Re. Open Reject Re-Open Withdrawn Accept Completed Activate Complete Activate Opened Activated Activate Re. Open CRM 18 Open Withdraw Rejected Submitted Opened Completed Completed 16

IBM Rational Software Development Conference 2008 Understanding the Context Switch Current Approach Submit Validate Close CQ ALM Approach Request (Defect) Project Team A Task (Defect) Develop Activity (Develop) Activity (Validate) Project Team B Task (Defect) Activity (Develop) Activity (Review) Activity (Validate) Replace one-size fits-all state transitions with Project defined activity sets CRM 18 17 17

IBM Rational Software Development Conference 2008 The Flow Problem information Close or Withdraw Request Accept or Reject Request Initiate Request Submit Request Process Request Accept or Reject Task Create Task Process Task Complete Activities Create Activities Process Activities Requests are triaged, Tasks are created for projects Activities complete the task A completed task is reviewed and the request is closed. CRM 18 18 18

IBM Rational Software Development Conference 2008 About Types & Work Configurations Request § Defect § Enhancement § New Feature §… Work Configuration § Request = Defect § Task = Defect Task § Defect Activity § Develop Activity § Review Activity § Validate § Plan Project § Design Architecture § Refine Requirements §… Work Configuration § Task= Defect § Activites=Develop, Review, Test A type of request may need a special type of task A type of task may have its own set of activities Work configurations define these ‘process policies’ for a project CRM 18 19 19

IBM Rational Software Development Conference 2008 Builds and Baselines Activity Baseline Project Build Baselines capture the set of completed activities Builds track the status of the build Testers use these to determine what to test CRM 18 20 20

IBM Rational Software Development Conference 2008 Baseline 1 Choose Project 2 Identify UCM stream 3 Identify PVOB or Location 4 List completed activities (Diff Baselines) Automate the creation of the Baseline and Build records as part of your build process CRM 18 21 21

IBM Rational Software Development Conference 2008 Build 1 Choose Project 2 Set Build Type and Build Status 3 Choose Baseline Automate the creation of the Baseline and Build records as part of your build process CRM 18 22 22

IBM Rational Software Development Conference 2008 System-wide settings Category Type Label Security Policy Iteration Label Admin Phase Label Category Release Label Work Type Resolution Code Label Role Label Status Label System-wide records Type Label System-wide labels Labels let you use your vocabulary across the enterprise System-wide records facilitate re-use & consistency across projects CRM 18 23 23

IBM Rational Software Development Conference 2008 Agenda BAM! The What and Why of this Solution Core Concepts 4 Projects 4 Work 4 System-wide Settings Customization options and examples Integrations 4 Themes 4 UCM 4 Build Forge 4 Requisite. Pro CRM 18 24 24

IBM Rational Software Development Conference 2008 An Agile Iteration Example My Project Assign “Activities” Phase (Iteration) Request (General) Task (General) Iteration (1) Activity (Implement) related Activity (Implement) Activity (Test) Activity (Document) Activity (Test) Activity (Document) Manage by “Iterations” Set a default Request for the project Set a default Task for the Request Activities automatically associated to Task Agile Work and Delivery definition CRM 18 25 25

IBM Rational Software Development Conference 2008 Adaptive Workflow – Open. UP example § Open. UP (Open Unified Process) § An exemplary process in the Eclipse Process Framework project. § Open. UP is very similar the Rational Unified process and is scaled for Agile teams. § Open. UP downloads are available from the following URL: http: //www. eclipse. org/epf/downloads/openup_downloads. php nts CRM 18 26

IBM Rational Software Development Conference 2008 Adaptive Workflow – Open. UP example § Open. UP (Open Unified Process) § An exemplary process in the Eclipse Process Framework project. § Open. UP downloads are available from the following URL: http: //www. eclipse. org/epf/downloads/openup_downloads. php nts Role Label(s) Phase Label(s) 1 Create Role Labels 2 CRM 18 Create Phase Labels. Alternatively add Iteration labels 27 27

IBM Rational Software Development Conference 2008 Adaptive Workflow – Open. UP example Task Types Map to the Lifecycle 3 Task Type= Initiate Project Activity Type Maps to lifecycle step 4 Activity Type= Define Vision, Role = Analyst Activity Type= Plan Project, Role= Project Manager 5 Work Configuration binds them Work Configuration for Task= Initiate Project, include the above Activities & Roles CRM 18 28 28

IBM Rational Software Development Conference 2008 Open. UP Example – Inception Phase Request (Run Project) Task (Initiate Project) Act. (Define Vision) Act. (Plan Project) Task (Manage Iteration) Act. (Plan Iteration) Act. (Manage Iteration) Task (Identify Reqs) Activity (Outline Reqs) Activity (Detail Reqs) Task (Technical Approach) Activity (Outline Architecture) CRM 18 Act. (Assess Results) 29

IBM Rational Software Development Conference 2008 Defect handling Options Defect = Request (Defect) Task (Fix) Trace Defects to Feature on Request record Defect = Task Request (Feature) Task (Implement) Defect = Activity Request (Feature) Task (Implement) Act. (Develop) Act. (Test) Task (Defect) Multi-projects Reports where request=defect CRM 18 Act. (Develop) Act. (Test) Act. (Defect) Trace Defects to Feature on Task record 30

IBM Rational Software Development Conference 2008 Agenda a! g n u b Kowa The What and Why of this Solution Core Concepts 4 Projects 4 Work 4 System-wide Settings Customization options and examples Integrations 4 Themes 4 UCM 4 Build Forge 4 Requisite. Pro CRM 18 31 31

IBM Rational Software Development Conference 2008 GDALM Integration Themes § Alignment of Work 4 Ability to turn release requirements into project and component iteration plans and provide visibility into those plans for health tracking through the lifecycle. § Requirements Driven Development and Testing 4 Ability for test cases to align with requirements for validation. § Defect Management 4 The flow of a defect and how it impacts development, test, and iteration plans. The visibility and ability to report defects back from testing, allowing leads and developers can act upon them § Build Clarity & Quality 4 Ability to determine when Requirements are implemented in the build and what Defects are fixed. Ability to trace from builds to coverage, result and quality metrics. CRM 18 32

IBM Rational Software Development Conference 2008 Integration Use Cases IBM Rational Requisite. Pro Composer IBM Rational Clear. Quest Manage Requirements Create Sketch IBM Rational Team Concert Triage Requests Plan Iterations w/ Task & Activities IBM Rational Build Forge Plan Iteration w/ Work. Item Reuse*, Develop, Test, Build and Deliver changes Integrate and Build Alternate UCM workflow Rational Analyzer, Clear. Quest and Clear. Case integrated IBM Rational Quality Manager Plan Tests w/ Work. Item QM Test integration build Watch. Fire App. Scan integrated Submit defect CRM 18 33

IBM Rational Software Development Conference 2008 Putting it all together Group Security-context User Role prev / next super / sub prev / next Project Phase Iteration § Assess § Plan § Design Release Category § Implement § Test Project definition § Deploy super / sub Work Configuration Request related § Defect Delivered as a schema and as two packages (ALMProject, ALMWork) CRM 18 § Enhancement § New Feature Work and Delivery definition Task related Activity Failed_in related Validated_in Fixed_in Build Baseline 34 34

IBM Rational Software Development Conference 2008 Improving ROI – early indicators § Cost savings on a “real” engagement 4 5 months duration, 30 -42 days of billable time § Details: 4 Schema Requirements § 1 month duration: customer meetings, documentation and review. § 5 -7 days of billable time 4 Schema Design § 1 month duration: customer meetings, documentation, and review. § 5 -7 days of billable time 4 Schema Implementation § 3 Iterations over the course of 3 months § 15 -20 days billable time 4 Develop Custom Training for end users § 5 -8 days billable time § Activities performed during the schema implementation iterations CRM 18 CH! N U CR ALM schema Reduced to 2 months Duration 10 -15 days billable time Requirements Time Reduced by 25%. Design Time Reduced by 50%. Implementation Time Reduced by 66%. Training Time Reduced by 50%. 35

IBM Rational Software Development Conference 2008 Early Adopters & Other Opportunities § Clear. Quest early adopters 4 Several Rational field-driven early adopters 4 Providing design discussion & feedback § Internal IBM early adopters 4 Information Management, Tivoli, RATLC, Collaboration with URMS team § ALM Redbook public draft 4 Includes major sections CQALM and Team Concert, including interop scenarios 4 Available at the IBM Redbooks website CRM 18 36 36

IBM Rational Software Development Conference 2008 CQALM Provides an ALM Hub Benefits: § Integrated with Rational Products Providing Full Development Lifecycle Team Concert Quality & Test Lab Manager § Simplify Compliance Reporting Clear. Case / UCM ü Provides Visibility to: ü Requisite. Pro for Requirements Management and Trace Relationships ü Asset Manager (RAM) to Cooperatively Develop & Reuse Assets ü Clear. Case/UCM for Version Control of Development Activities ü Team Concert for Small, Agile Teams RAM CQALM Practitioner Tools Requisite. Pro Portfolio Manager ü Partner Extensibility for Inclusion of Complementary Solutions CRM 18 37 37

IBM Rational Software Development Conference 2008 Summary § Projects provide security, roles, and a context § Work is completed in the context of a project by using Requests, Tasks and Activities § There are system-wide settings that you can modify without having to change the schema § Reduce CQ Administration time § Empower Project teams to configure the project for their own needs CRM 18 Submitter • Submits request for change • (Validate release) Test Lead • Ensure quality Tester • Test changes in baselines Change Control Mgr • Triage requests • Assigns tasks to projects Change performed in the context of Project Request Category Task Release Activity Project and Plan definition Work and Delivery definition Release Engineer • Integrate and build delivered changes • Create baselines 38

IBM Rational Software Development Conference 2008 Additional Information § Developer. Works 4 article 1: http: //www. ibm. com/developerworks/rational/library/edge/08/mar 08/pampinopierce/index. html 4 article 2: http: //www. ibm. com/developerworks/rational/library/edge/08/apr 08/pampinopierce/index. html § ALM Redbook Public Draft CRM 18 39

IBM Rational Software Development Conference 2008 QUESTIONS CRM 18 40

IBM Rational Software Development Conference 2008 WANT MORE? CRM 18 41

IBM Rational Software Development Conference 2008 a! g n u b Kowa Pow! CRM 18 Ka-plo w! ! ooks z d a G Come Talk to us! C H! C N RU BAM! 42

IBM Rational Software Development Conference 2008 ! K N I ZO THANK YOU Learn more 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 developer. Works Rational IBM Rational TV IBM Rational Business Partners © Copyright IBM Corporation 2008. 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, the ondemand business logo, Rational, the Rational 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. CRM 18 43