CRM 18 IBM Rational Software Development Conference 2008 © 2007 IBM Corporation ® Introducing Application Lifecycle Management on IBM ® Rational ® ClearQuest ® Carolyn Pampino Solution Architect, IBM Rational

IBM Rational Software Development Conference 2008 CRM 18 2 Disclaimer and Non-Disclosure  This solution is available from Devworks for CQ users;   included in ClearQuest 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 Ouch!

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

IBM Rational Software Development Conference 2008 CRM 18 4 What is Application Lifecycle Management on CQ? Tester Test changes in baselines Developer Work on activities Develop and deliver changes Release Engineer Integrate and build delivered changes Create baselines Test Lead Ensure quality Project Category Release Team Lead Assigns activities to complete tasks Change Control Mgr Triage requests Assigns tasks to projects Change performed in the context of  Out-of-box ALM Solution for ClearQuest (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 Request Task Activity Project and Plan definition Work and Delivery definition Submitter Submits request for change (Validate release)

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

IBM Rational Software Development Conference 2008 CRM 18 6 Agenda The What and Why of this Solution Core Concepts  Projects  Work  System-wide Settings Customization options and examples Integrations  Themes  UCM  Build Forge  RequisitePro 6 Ka-plow!

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

IBM Rational Software Development Conference 2008 CRM 18 8 Introducing Projects Project Category Role User super / sub prev / next Release Project definition Security-policy Group Existing ClearQuest ALM System-wide settings Work Configuration Security Context Phase Iteration And others we’ll discuss later 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 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

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

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

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

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

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

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

IBM Rational Software Development Conference 2008 CRM Managing “Work” 15 Request Task Activity User related  Defect  Enhancement  New Feature  …  Defect  Enhancement  New Feature  … Work and Delivery definition  Assess  Plan  Design  Implement  Test  Deploy  …  Assess  Plan  Design  Implement  Test  Deploy  … Work Type 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 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 related Activity

IBM Rational Software Development Conference 2008 CRM Simple State Transitions Request Activity Opened Withdrawn Completed Rejected Open Withdraw Re-Open Accept Re-Open ReOpen Reject Opened Completed Activated Open Complete Activate Complete Re-Open Activate ReOpen Task Submitted Opened Completed Activated Submit Open Complete ReadyToWaiting Activate CompleteReOpen

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

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

IBM Rational Software Development Conference 2008 CRM About Types & Work Configurations 19 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 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 Request  Defect  Enhancement  New Feature  …  Defect  Enhancement  New Feature  … Task  Defect  Plan Project  Design Architecture  Refine Requirements  …  Defect  Plan Project  Design Architecture  Refine Requirements  …  Develop Activity  Review  Validate Work Configuration  Request = Defect  Task = Defect  Request = Defect  Task = Defect Work Configuration  Task= Defect  Activites=Develop, Review, Test  Task= Defect  Activites=Develop, Review, Test

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

IBM Rational Software Development Conference 2008 CRM Baseline 21 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

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

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

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

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

IBM Rational Software Development Conference 2008 CRM Adaptive Workflow – OpenUP example  OpenUP (Open Unified Process)  An exemplary process in the Eclipse Process Framework project.  OpenUP is very similar the Rational Unified process and is scaled for Agile teams.  OpenUP downloads are available from the following URL: nts

IBM Rational Software Development Conference 2008 CRM Adaptive Workflow – OpenUP example 27 Role Label(s) 1 Create Role Labels Phase Label(s) 2 Create Phase Labels. Alternatively add Iteration labels  OpenUP (Open Unified Process)  An exemplary process in the Eclipse Process Framework project.  OpenUP downloads are available from the following URL: nts

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

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

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

IBM Rational Software Development Conference 2008 CRM Agenda The What and Why of this Solution Core Concepts  Projects  Work  System-wide Settings Customization options and examples Integrations  Themes  UCM  Build Forge  RequisitePro 31 Kowabunga!

IBM Rational Software Development Conference 2008 CRM GDALM Integration Themes  Alignment of Work  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  Ability for test cases to align with requirements for validation.  Defect Management  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  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.

IBM Rational Software Development Conference 2008 CRM Integration Use Cases Create SketchManage Requirements Plan Iteration w/ WorkItem Reuse*, Develop, Test, Build and Deliver changes Integrate and Build QM Plan Tests w/ WorkItem Alternate UCM workflow Test integration build WatchFire AppScan integrated Submit defect Rational Analyzer, ClearQuest and ClearCase integrated IBM Rational Build Forge IBM Rational Team Concert IBM Rational RequisitePro IBM Rational RequisitePro Composer IBM Rational ClearQuest IBM Rational Quality Manager Triage Requests Plan Iterations w/ Task & Activities

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

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

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

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

IBM Rational Software Development Conference 2008 CRM 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 Tester Test changes in baselines Release Engineer Integrate and build delivered changes Create baselines Test Lead Ensure quality Project Category Release Change Control Mgr Triage requests Assigns tasks to projects Change performed in the context of Request Task Activity Project and Plan definition Work and Delivery definition Submitter Submits request for change (Validate release)

IBM Rational Software Development Conference 2008 CRM Additional Information  DeveloperWorks  article 1: pierce/index.html  article 2: pierce/index.html  ALM Redbook Public Draft

IBM Rational Software Development Conference 2008 CRM QUESTIONS

IBM Rational Software Development Conference 2008 CRM WANT MORE?

IBM Rational Software Development Conference 2008 CRM Come Talk to us! CRUNCH! Kowabunga! K o w a b u n g a ! BAM! Ka-plow! Gadzooks! Pow!

IBM Rational Software Development Conference 2008 CRM © Copyright IBM Corporation 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 on- demand 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. Learn more at:  IBM Rational software IBM Rational software  IBM Rational Software Delivery Platform IBM Rational Software Delivery Platform  Process and portfolio management Process and portfolio management  Change and release management Change and release management  Quality management Quality management  Architecture management Architecture management  Rational trial downloads Rational trial downloads  Leading Innovation Web site Leading Innovation Web site  developerWorks Rational developerWorks Rational  IBM Rational TV IBM Rational TV  IBM Rational Business Partners IBM Rational Business Partners THANK YOU ZOINK!