1 ALM ToDo Agile UCM and Buildforge demo April 15, 2008Stu Poulin

2 Disclaimer and Non-DisclosureIBM 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

3 Demo to Present ALM “ToDo” agile project. Baseline and Build toolsALMBaseline and BTBuild (Build) records Describe tie into ALMActivities In-the-box UCM integration as it works with ALM Demo an example of how BuildForge can be used to drive and populate ALM baseline and build data

4 Setting the default ALMProject AND ALMTask for UCM Other Demos (TBD) Setting the default ALMProject AND ALMTask for UCM Using ALM Baseline and Build in a strict process Composite Baselines with ALM NonUCM usage Mixed UCM and NonUCM usage Using Build Forge with ALM

5 Developers and Managers Quality EngineersAudience Release Engineers Program Managers Developers and Managers Quality Engineers

6 Prerequisites View a CQ ALM demo explaining the overall high level ALM work flow and features.

7 ToDo Agile Project Out-of-box ALM Solution for ClearQuestSubmitter Submits request for change (Validate release) Change Control Mgr Triage requests Assigns tasks to projects Out-of-box ALM Solution for ClearQuest ALMProject assigns a Default ALMRequest and Default ALMTask Developers create ALMActivities against the default ALMTask Baseline and Build records track progress of activities Developers and Testers can Verify ALMActivities in Builds QE Lead Ensure quality of delivered changes to releases Team Lead Assigns activities to complete tasks Change performed in the context of Project Default Request Tester Works on activities Test changes in baselines Category Default Task Activity Release Developer Work on activities Develop and deliver changes Project and Plan definition Work and Delivery definition Baseline Release Engineer Integrate and build delivered changes Create baselines Build

8 Putting it all togetherGroup User Security-context Role prev / next prev / next super / sub prev / next Project Phase Iteration Assess Plan Design Implement Test Deploy Release Category super / sub Project definition This demo will focus on ALM: Activities Baselines BTBuilds (Builds) Request Task Activity related related Failed_in Validated_in Fixed_in related Defect Enhancement New Feature Baseline Work and Delivery definition BTBuild

9 ALMActivities are UCM enabledContributors Standard in-the-box CC/CQ integration is enabled on the ALMActivity record 

10 ALMBaseline 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 ALM Baselines provide instant knowledge of Status, Disposition, and location of Activity artifacts in UCM and non-UCM baselines and builds.

11 ALMActivities tracked in BaselinesContributors UCM: a modified ClearTool diffbl finds and adds activities to the Baseline record. Optional, Queries in ALM can find Completed activities since the last ALMBaseline 

12 BTBuilds are created off Baselines1 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

13 Baseline/Build scripts provided with ALMDesigned to interface UCM and NonUCM Change Management (CM) systems to ALM Written in RATLPerl. Released as source to allow you to extend for your own process if needed Fully in ALM documentation Commandline –help for addition information

14 Baseline/Build scripts provided with ALMCreate_baseline_record.pl Creates an ALMBaseline record from the commandline Create_build_record.pl Given an ALMBaseline record creates a BTBuild record off it Update_baseline_record.pl Updates an existing ALMBaseline record from UCM or supplied commandline Update_build_record.pl Update an existing BTBuild record from the commandline Runbasicquery.pl Runs a CQ stored query given commandline params for filters and saves the output to a file in a format compatible with above scripts

15 Demo Agile development using ALM and UCM ALM_Project_ToDo Demo Agile development using ALM and UCM Options to create and assign ALMActivities to a developer. Activities can be created and assigned first in ALM Will show up in ClearCase UCM drop down choice Activities can be created by the Dev as needed Setting a default project will set the default Task and Request Or, another Task created or selected as needed Project setting of Default task allows for quick and unimpeded checkouts. As needed, Activity can be reassigned to a more appropriate task at a later time Checkouts are unimpeded

16 Validate Activities in BuildsDemo Working Actitivities Automated Builds Validate Activities in Builds

17 Project_ToDo DEMO StepsCheckout in ClearCase UCM as “Dev_ToDo” ID in ALM Standard, “in-the-box” UCM integration is used to tie ClearCase UCM to the ALMActivity Prompting for “Activity” New -> ALMActivity – create an activity as needed. Modify File Checkin – Use same Activity Deliver to Default integration stream “Complete” on delivery will display ALMActivity and Prompt for Resolution Standard UCM policy Imagine scenario is repeated by many developers during the day Checkout/in on Integration Stream Manually complete the activity

18 O1_ALM_Project_ToDo Build Forge Project Start the BuildSetting up Build Forge for ALM covered in another demo Review Build steps UCM mkbl – Standard UCM Baseline is made Create_Baseline_Record Runs a diffbl between this new baseline and the last ALMBaseline record stored in ALM. Minimal extra information need be supplied as script can gather information from both ALM and ClearCase UCM Mock source build – builds a web page example Create_Build_Record Given the above Baseline, one or more builds may be created ALM reuses BTBuild record Review in ALM the new Baseline, Activities in the Baseline, BTBuild

19 Build Forge 01_ALM_Project_ToDo Build run

20 01_ALM_Project_ToDo

21 ALMBaseline Record created by Build Forge

22 Activities placed on ALMBaseline from Diffbl

23 BTBuild Record Created off ALMBaseline Record

24 ALMActivities contain their validation statusQueries report ALMActivities that need to be Validated in BTBuilds Positive confirmation that Activity has been looked at in a build and determined to work. Not all UCM Baselines need an ALMBaseline records Only Baselines you wish to “Validate” or “Fail” the ALMActivity for a build ALMBaseline records for a UCM baseline can be created at a later time For example if you decide yesterday’s build should be tracked

25 ALMActivites marked as Validated or Failed in Builds by Developer or Tester