IBM Software Group ALM To Do Agile UCM

IBM Software Group | Rational software Disclaimer and Non-Disclosure § 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

IBM Software Group | Rational software Demo to Present 4 ALM “To. Do” agile project. 4 Baseline and Build tools 4 ALMBaseline and BTBuild (Build) records 4 Describe tie into ALMActivities 4 In-the-box UCM integration as it works with ALM 4 Demo an example of how Build. Forge can be used to drive and populate ALM baseline and build data

IBM Software Group | Rational software Other Demos (TBD) § Setting the default ALMProject AND ALMTask for UCM § Using ALM Baseline and Build in a strict process § Composite Baselines with ALM § Non. UCM usage § Mixed UCM and Non. UCM usage § Using Build Forge with ALM

IBM Software Group | Rational software Audience § Release Engineers § Program Managers § Developers and Managers § Quality Engineers

IBM Software Group | Rational software Prerequisites § View a CQ ALM demo explaining the overall high level ALM work flow and features.

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

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

IBM Software Group | Rational software ALMActivities are UCM enabled Contributors Standard in-the-box CC/CQ integration is enabled on the ALMActivity record 9

IBM Software Group | Rational software 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. 10

IBM Software Group | Rational software ALMActivities tracked in Baselines Contributors § UCM: a modified Clear. Tool diffbl finds and adds activities to the Baseline record. § Optional, Queries in ALM can find Completed activities since the last ALMBaseline 11

IBM Software Group | Rational software BTBuilds are created off Baselines 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 12

IBM Software Group | Rational software Baseline/Build scripts provided with ALM § Designed to interface UCM and Non. UCM 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

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

IBM Software Group | Rational software ALM_Project_To. Do § Demo Agile development using ALM and UCM § Options to create and assign ALMActivities to a developer. 4 Activities can be created and assigned first in ALM § Will show up in Clear. Case UCM drop down choice 4 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 4 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

IBM Software Group | Rational software Demo § Working Actitivities § Automated Builds § Validate Activities in Builds

IBM Software Group | Rational software Project_To. Do DEMO Steps § Checkout in Clear. Case UCM as “Dev_To. Do” ID in ALM § Standard, “in-the-box” UCM integration is used to tie Clear. Case 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

IBM Software Group | Rational software Build Forge Project § O 1_ALM_Project_To. Do 4 Start the Build 4 Setting up Build Forge for ALM covered in another demo 4 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 Clear. Case 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

IBM Software Group | Rational software Build Forge 01_ALM_Project_To. Do Build run

IBM Software Group | Rational software 01_ALM_Project_To. Do

IBM Software Group | Rational software ALMBaseline Record created by Build Forge

IBM Software Group | Rational software Activities placed on ALMBaseline from Diffbl

IBM Software Group | Rational software BTBuild Record Created off ALMBaseline Record

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

IBM Software Group | Rational software ALMActivites marked as Validated or Failed in Builds by Developer or Tester