1. © 2007 IBM Corporation ® ClearQuest Application Lifecycle Management Training ToDo Demo

2. ALM Training CRM29 Submitter Submit request Project Category Release Request

3. ALM Training CRM29 Task Triage admin Triage requests Add and plan Task Project Category Release Request Submitter Submit request

4. ALM Training CRM29 Project Category Release Task DevLead Test Lead Activate Task Assign Activities Activity (Test) Activity (Test) Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Request Tester Developer Triage admin Triage requests Add and plan Task Submitter Submit request

5. ALM Training CRM29 Developer Deliver change Complete Activity Project Category Release Task DevLead QE Lead Activate Task Assign Activities Activity (Dev) Activity (Dev) Request Triage admin Triage requests Add and plan Task Submitter Submit request

6. ALM Training CRM29 Developer Deliver change Complete Activity Builder Create Baseline Run Build Validate Build and Promote Project Category Release Task Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Baseline Build Request DevLead QE Lead Activate Task Assign Activities Triage admin Triage requests Add and plan Task Submitter Submit request

7. ALM Training CRM29 Tester Perform tests Complete Activity Builder Create Baseline Run Build Validate Build and Promote Project Category Release Task Activity (Test) Activity (Test) Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Baseline Build Request Developer Deliver change Complete Activity DevLead QE Lead Activate Task Assign Activities Triage admin Triage requests Add and plan Task Submitter Submit request

8. ALM Training CRM29 Tester Perform tests Complete Activity Test Lead Review status Complete Task Project Category Release Task Activity (Test) Activity (Test) Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Baseline Build Request Builder Create Baseline Run Build Validate Build and Promote Developer Deliver change Complete Activity DevLead QE Lead Activate Task Assign Activities Triage admin Triage requests Add and plan Task Submitter Submit request

9. ALM Training CRM29 Tester Perform tests Complete Activity QE Lead Review status Complete Task Project Category Release Task Activity (Test) Activity (Test) Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Baseline Build Request Builder Create Baseline Run Build Validate Build and Promote Developer Deliver change Complete Activity DevLead QE Lead Activate Task Assign Activities Triage admin Triage requests Add and plan Task Submitter Accept Task

10. ALM Training CRM29 Tester Perform tests Complete Activity Developer Deliver change Complete Activity Builder Create Baseline Run Build Validate Build and Promote Submitter Submit request QE Lead Review status Complete Task Project Category Release Task DevLead QE Lead Activate Task Assign Activities Activity (Test) Activity (Test) Activity (Doc Assess) Activity (Doc Assess) Activity (Dev) Activity (Dev) Baseline Build Request Triage admin Triage requests Add and plan Task

11. ALM Training CRM29 Request Submitter  (Note: CQ 7.0.1.03-06 do not show Request->Tasks or Task->Activities when CreateTask/Activity are executed and CQ 7.1.0.2 does not support the execution of RSA Actions like these at all. CQ 7.0.1.07 and 7.1.0.1 do not exhibit these problems)  In Windows Eclipse client or CQWJ  Login as ‘Requestor_ToDo’ (Password is BLANK)  In Eclipse, you can also pre-log in as Triage_ToDo, DevLead_ToDo, Dev_ToDo, TestLead_ToDo, Test_ToDo, ReleaseEngineer_ToDo  Click New Request icon  Enter Headline  Choose Category  Choose ‘Category_ToDo’  ( Point out Project (If you set one on chosen Category) –Point out Phase (If you set one on chosen Project) –Point out Iteration (If you set one on chosen Phase) Note: If using CQ Web 7.0.1 you will need to select the Project using the Add button before you will see any choices in the Request->Type form Control  Enter Headline  Set Type = ‘Defect’ and choose Severity  Give (brief) tour of Request  Owner should be set to Requestor_ToDo  Click OK

12. ALM Training CRM29

13. ALM Training CRM29

14. ALM Training CRM29

15. ALM Training CRM29

16. ALM Training CRM29 Project Triage  Creating Tasks and setting Dev Lead Ownership  Login as ‘Triage_ToDo’ (Password is BLANK)  Execute \Public queries\Practices\ToDo\REST\Triage query  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Click on Request in Result Set grid  Resize Display so Request->Tasks field shows  Highlight the Request and Click Utility CreateTask  Note new Request->Task  Owner should be set to Role->Primary for Project= ‘Project_ToDo’, RoleLabel = ‘DevLead_ToDo’

17. ALM Training CRM29

18. ALM Training CRM29 Lead Developer  Login as ‘DevLead_ToDo’ (Password is BLANK)  Execute query \Public queries\Practices\ToDo\REST\ Dev Lead  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Click on Task in Result Set grid  Change_State Activate Task  Set Task Owner to ‘TestLead_ToDo’ for Project= ‘Project_ToDo’, RoleLabel = ‘DevLead_ToDo’  Resize Display so Task->Activities field shows  Click Utility CreateActivity  Note new Task->Activities (Dev/Doc Assess/Test) in the Submitted State  Ratl_mastership for ‘Dev’ Activity should be WorkConfiguration->Role->Primary->ratl_mastership for a WorkConfiguration where Project= ‘Project_ToDo’, Record_Type =‘Activity’, Type = ‘Dev’  ratl_mastership for ‘Doc Assess’ Activity should be WorkConfiguration->Role->Primary->ratl_mastership for a WorkConfiguration where Project= ‘Project_ToDo’, Record_Type =‘Activity’, Type = ‘Doc Assess’  ratl_mastership for ‘Test’ Activity should be WorkConfiguration->Role->Primary->ratl_mastership for a WorkConfiguration where Project= ‘Project_ToDo’, Record_Type =‘Activity’, Type = ‘Test’  Open the ‘Dev’ Type Activity and set the Owner to ‘Dev_ToDo’ (Use right mouse Open Record then Change State->Open) (Web does not refresh changed State, but it will be Opened)  You can also test with a Task->Type = 'Enhancement' and another ='New Functionality' Different sets of Activities should appear for the latter

19. ALM Training CRM29

20. ALM Training CRM29

21. ALM Training CRM29

22. ALM Training CRM29

23. ALM Training CRM29

24. ALM Training CRM29

25. ALM Training CRM29

26. ALM Training CRM29

27. ALM Training CRM29 Project Test Lead Test Lead Assigning work  Login as ‘TestLead_ToDo’ (Password is BLANK)  Execute query \Public queries\Practices\ToDo\REST\ Test Lead  Dbl-Click the ‘Test’ Type Activity on the Task  Choose Activity Open Action  Owner Choice_List should be automatically set to Role->Members values for Project= ‘Project_ToDo’, RoleLabel = ‘Test_ToDo’  Set Owner =‘Test_ToDo’ then Click OK

28. ALM Training CRM29 Project Doc Lead Doc Lead Assigning Doc Assessment work  Login as ‘DocLead_ToDo’ (Password is BLANK)  Execute query \Public queries\Practices\ToDo\REST\Doc Lead  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Two Types of Activity may cause Task records to be displayed:  ‘DocAssess’ –These track the Assessment of the need for Documentation  ‘Dev’ with DocRelated = ‘Yes’ (see Doc Assessor slide later) –These track the actual Development of Documentation  Dbl-Click the ‘Doc Assess’ Type Activity on the Task  Choose Activity Open Action  Owner should be set from the Role->Members for Project= ‘Project_ToDo’, RoleLabel = ‘Doc Assessor_ToDo’ or ‘Developer’ depending on the Activity->Type  Set Owner = ‘DocAssessor_ToDo’ then Click OK

29. ALM Training CRM29 Non-UCM Developer (skip if UCM developer)  Login as ‘Dev_ToDo’ (Password is BLANK)  Execute query \Public queries\Practices\ToDo\REST\ Developer  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Click on Task in Result Set grid  Resize Display so Task->Activities field shows  Highlight ‘Dev’ Activity  Simulate Fixing code  Dbl-Click then Choose Complete Action  highlight ID and Ctrl-C (To be used by ReleaseEngineer later in Demo)  Enter ResolutionSummary  Set ResolutionCode = ‘Fixed’  Click Apply

30. ALM Training CRM29 UCM Developer (skip if non-UCM developer)  Open the My Activities folder in CC Explorer  You should see the Activity created in the preceding ToDo 05_Create Activities Test Case.  Make it the Default activity  Add a Notepad file to the Dev stream using Add to Source Control.  You should be able to look at the Activity in ALM and see that State = ‘Activated’  Deliver then Complete the Delivery in CC explorer or CCRC  You should be presented with the Activity form.  Set ResolutionCode=’Fixed’ and enter a ResolutionSummary  The State should be Completed  Click OK

31. ALM Training CRM29

32. ALM Training CRM29

33. ALM Training CRM29

34. ALM Training CRM29

35. ALM Training CRM29

36. ALM Training CRM29 Project Release Engineer: Simulate Create Baseline of Code  Switch hats to become RE  Login as ‘ReleaseEngineer_ToDo’ (Password is BLANK)  Choose Menu Actions->New ALMBaseline  Baseline = ‘ Baseline’  PVOB = PVOB’  Owner = ‘ReleaseEngineer_ToDo  Project –ADD->Search <Highlight Project where Category = ‘Category_ToDo’ and Release = ‘ReleaseLabel01_ToDo’ –Click Activities Tab, Activities field Add –Paste Copied Activity ID into Search Key Box and click Search –Highlight only record and click OK  Click OK on new Baseline

37. ALM Training CRM29

38. ALM Training CRM29

39. ALM Training CRM29

40. ALM Training CRM29 Project Release Engineer (Build): Simulate Build script (non-UCM)  Login as ‘ReleaseEngineer_ToDo’ (if not already logged in as that UserID) (Password is BLANK)  Menu Actions->New Build  Build= ‘ Build’  On ALM Tab  Choose Project  ADD->Search  Highlight record for Project and click OK  Baseline click ADD  enter ‘ ’ used to create Baseline  click ->Search  Highlight Baseline created earlier and click OK  BuildType= ‘Platform’  Build Status = ‘Passed’  Owner should be automatically set to Role->Primary for Project= ‘Project_ToDo’, RoleLabel = ‘ReleaseEngineer’  Click OK on Build record

41. ALM Training CRM29

42. ALM Training CRM29

43. ALM Training CRM29

44. ALM Training CRM29 Project Tester  Completing Test Type Activities  Login as ‘Test_ToDo’ (Password is BLANK)  Execute \Public queries\Practices\ToDo\REST\Tester (for Projects NOT using Build/Activity) or ‘Tester W Build’ (for Projects using Build/Activity)  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Look at ‘Dev’ Activity and (if present) Build info.  Install Build, Test successfully  Choose ‘Test’ Type Activity  Dbl-Click and Choose Complete Action  Choose a Build in Validated In Build  Enter ResolutionSummary and Resolution

45. ALM Training CRM29

46. ALM Training CRM29

47. ALM Training CRM29

48. ALM Training CRM29

49. ALM Training CRM29 Project Doc Assessor  Completing ‘Doc Assess’ Type Activities  Login as ‘DocAssessor_ToDo’ (Password is BLANK)  Execute \Public queries\Practices\ToDo\REST\Doc Assessor query  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Choose ‘Doc Assess’ Type Activity   If Documentation work is needed, the DocAssessor will:  Complete the Type = ‘DocAssess’ Activity  Enter ResolutionSummary and Resolution  Note the Activity->Task  Click the ActivitiesRelated New button  Checkmark the DocRelated checkbox then any other fields on the new Activity  Apply the changes to it  then Apply the changes to the ‘DocAssess’ Activity.

50. ALM Training CRM29 Test Lead Completing Task  Test Lead Completing Task  Login as ‘TestLead_ToDo’ (Password is BLANK)  Execute \Public queries\Practices\ToDo\REST\ Completing Tasks  Category = ‘Category_ToDo’  Release = ‘ReleaseLabel01_ToDo’  Assess Activity States  Note Build containing ‘Dev’ fix (if Build was created)  Click Task Actions button and click Complete  Set ResolutionSummary  Set ResolutionCode = ‘Approved’  Click Task Apply

51. ALM Training CRM29

52. ALM Training CRM29

53. ALM Training CRM29 Request Acceptance  Throughout the development cycle, I may be checking on the status of my Requests  Login as ‘Requestor_ToDo’ (Password is BLANK)  Execute \Public queries\Practices\ToDo\REST\Requestor query  Project.Category= ‘Category_ToDo’  Project.Release = ‘ReleaseLabel01_ToDo’  Request State IN ‘Opened,Rejected’  Task State = ‘Completed’  Note States of Task and Task.Activities  Accept the work done on the Request

54. ALM Training CRM29

55. ALM Training CRM29

56. ALM Training CRM29

57. ALM Training CRM29 Comments, Questions and Responses  Owner of a record is expected to be the only person directly modifying or state transitioning the record  This is not hard coded into the system, merely a suggested approach  If you wish to modify a record you are not the Owner of, do a QuestionOrComment Action  May indicate that you are just commenting or that you are Requesting a Response  You may Respond to a Question or Comment  You may also indicate that a Request is a Duplicate  MarkAsDuplicate  DuplicateComplete  Query Unanswered Questions

58. ALM Training CRM29

59. ALM Training CRM29

60. ALM Training CRM29

61. ALM Training CRM29

62. ALM Training CRM29

63. ALM Training CRM29

64. ALM Training CRM29

65. ALM Training CRM29

66. ALM Training CRM29

67. ALM Training CRM29

68. ALM Training CRM29

69. ALM Training CRM29 Duplicates  In order to indicate that a Request is a Duplicate of another Request, we do the following:  1) Request2 is seen as a duplicate of Request1.  2) Select Request2.  3) Choose the MarkAsDuplicate Action. (This creates a Comment on the Request->Comment Tab with ResponseRequested on Request2 and a Comment = " >".)  4) DBl-Click the Comment and Modify it to update the Comment indicating that this is seen as a Duplicate. The DuplicateOf field will be Mandatory. Enter the ID of Request1 in the Comment->DuplicateOf field and Save the Comment  5) The Owner of Request2 runs a query (ToDo_Duplicates Needing Completion) or is notified of the DuplicateOf Comment with ResponseRequested by email.  6)The Owner of Request2 decides if they agree that their Request is a Duplicate of Request1.  7) If they agree that their Request2 is a Duplicate of Request1 they execute the Request->DuplicateComplete Action on Request2. This State transitions Request2 to Completed State.  8) The Owner of Request2 dbl-Clicks the Request->Comment and choose the Respond Action.  9) They dbl-click the Comment->Response and Modify it to add their response and save it.  10) If they do not think that Request2 is a Duplicate of Request1, The Owner of Request2 dbl-Clicks the Request- >Comment and chooses the Respond Action.  11) They dbl-click the Comment->Response and Modify it to add their response saying that they do not agree for the following reasons and save their Response. They do not Complete the Request2 by Accepting it.

70. ALM Training CRM29 Rejected, Unreproducible and WorksAsDesigned Requests  Perform steps on ‘Request Submitter’ Slide (11)  Note the Request->ID for later use  Login as ‘Triage_ToDo’  Execute \Public queries\Practices\ToDo\REST\Triage query  Click Utilities icon on any Request  Choose Reject_Request (or Unreproducible or WorksAsDesigned)  A Task for the ‘ALL’ Project will appear in the Request->Task Form Control  Note: One tester reported thatthey did not see the new Task appear immediately. If this occurs, reaccess the Request  It will be in the Completed State  No further Tasks will be permitted to be created  Any pre-existing Tasks will be Commented  Reverse this  Login as ‘TestLead_ToDo’  Access Request by Request->ID then ReOpen the Task  Change the Project to ‘Project_ToDo’  Set Mandatory field values with Type = ‘Defect’, Owner = ‘DevLead_ToDo’, etc.  Remove ResolutionSummary  Click ‘OK’ button

71. ALM Training CRM29 Rejected, Unreproducible and WorksAsDesigned ‘Dev’ Tasks  Login as ‘DevLead_ToDo’  Execute \Public queries\Practices\ToDo\REST\Dev Lead query  Note the Task->ID for later use  Click Change State icon and choose Complete Action on the Task just ReOpened  Set ResolutionCode = ‘Reject_Task’  Add ResolutionSummary  The Task will be state transitioned to the Completed State  Any pre-existing Activities will be Commented (CQ ALM 1.1 only)  Reverse this  Login as ‘TestLead_ToDo’  Use Edit->Find Record by Task->ID then ReOpen the Task  Set Owner = ‘DevLead_ToDo’  Remove ResolutionSummary  Click ‘OK’ button

72. ALM Training CRM29 Rejected, Unreproducible and WorksAsDesigned ‘Dev’ Activities  Login as DevLead_ToDo  Execute \Public queries\Practices\ToDo\REST\Dev Lead query  Activate the Task just ReOpened  Set Owner = ‘TestLead_ToDo’  Click Apply/OK  Do Utilities-> CreateActivity  Open the additional, new ‘Dev’ Activity and set ‘Dev_ToDo’ as the Owner  Login as ‘Dev_ToDo’  Execute \Public queries\Practices\ToDo\REST\Developer query  Click ChangeState icon and choose Complete Action on ‘Dev’ Activity  Set ResolutionCode = ‘Reject_Activity’  Add ResolutionSummary  The Activity will be state transitioned to the Completed State  To reverse this, ReOpen the Activity and remove the ResolutionSummary and click OK

73. ALM Training CRM29 Setting up for ‘ When Tests have Failed ’ scenario  Execute steps on ‘Lead Developer’ slide (18)  Execute steps on ‘Project Test Lead‘ slide (27)  Execute steps on ‘Project Release Engineer: Simulate Create Baseline of Code’ Slide referencing ‘Dev’ Activity from previous slide (36)  Execute steps on ‘Project Release Engineer (Build): Simulate Build script (non-UCM)’ Slide referencing Baseline just created (40)

74. ALM Training CRM29 When Tests have Failed (slide 1 of 2)  Login as ‘Test_ToDo’  Execute \Public queries\Practices\ToDo\REST\Tester w Build query  Dbl-Click the Task->Activities record with Type =‘Test’ and click the Modify icon  ADD a FailedInBuild entry on Baseline and Build Tab  Optionally: Add a Comment to the ’Dev’ Activity (Certain versions of CQ 7.0.1 exhibit errors, reconnect to work around this)  Login as ‘Dev_ToDo’ Execute \Public queries\Practices\ToDo\REST\Tasks with My FailedInBuild Activities  Modify the Activity that Failed the Test  choose New RelatedActivity on the Related Records Tab  fill in Activity Mandatory fields (Type = ‘Dev’ Task and Project auto set by New button)  Click OK  Dbl Click (Or select and choose ‘Show Record Details’) and choose Change State- >Open/Activate  Set Owner = ‘Dev_ToDo’ and click OK  Simulate performing New work  Select Activity->ID and ctrl-C  Complete New ‘Dev’ Activity (ResolutionCode = ‘Fixed’)

75. ALM Training CRM29 When Tests have Failed (slide 2 of 2)  Login as ReleaseEngineer  Execute steps on ‘Project Release Engineer Create Baseline of Code’ Slide referencing ‘Dev’ Activity from previous slide.  Execute steps on ‘Project Release Engineer (Build) Simulate Build script (non- UCM)’ Slide referencing Baseline just created  Login as ‘Test_ToDo’  Execute \Public queries\Practices\ToDo\REST\Tester w Build query  The tester would perform a test that validates the fix  Dbl-Click the Task->Activities record with Type =‘Test’ and click the Change State- >Complete Action  ADD a ValidatedInBuild or NoPlanToTestInBuild entry on Baseline and Build Tab  Set ResolutionCode to ‘Validated’ or ‘No Plan To Test’  Optionally: Add a Comment to the ’Dev’ Activity

76. ALM Training CRM29 Tasks with unacceptable ‘Dev’ Activity (Slide 1 of 2)  Login as ‘TestLead_ToDo’  Execute \Public queries\Practices\ToDo\REST\Completing Tasks query  Click Modify icon and choose Modify Action on Task  Set ResolutionCode = ‘Reject_Development’  Optionally: Activity->QuestionOrComment Activities not accepted  Login as ‘Dev_ToDo’  Execute \Public queries\Practices\ToDo\REST\Developer query  Modify the Activity that caused the Test Lead to set Task->ResolutionCode = ‘Reject_Development’  choose New RelatedActivity on the Related Records Tab  fill in Activity Mandatory fields (Task and Project auto set by New button)  Click OK  Dbl Click (Or select and choose ‘Show Record Details’) and choose Change State- >Open/Activiate  Set Owner = ‘Dev_ToDo’ and click OK  Select Activity->ID and ctrl-C  Perform New work and Complete New ‘Dev’ Activity

77. ALM Training CRM29 Tasks with unacceptable ‘Dev’ Activity (Slide 2 of 2)  Login as ReleaseEngineer  Execute steps on ‘Project Release Engineer Create Baseline of Code’ Slide referencing ‘Dev’ Activity from previous slide.  Execute steps on ‘Project Release Engineer (Build) Simulate Build script (non-UCM)’ Slide referencing Baseline just created  Login as ‘Test_ToDo’  Execute \Public queries\Practices\ToDo\REST\Tester w Build query  The tester would perform a test that validates the fix  Dbl-Click the Task->Activities record with Type =‘Test’ and click the Change State->Complete Action  If a ValidatedInBuild (or NoPlanToTestInBuild depending on previous choice) already exists  Select it and click Remove button  ADD new ValidatedInBuild (or NoPlanToTestInBuild) entry on Baseline and Build Tab  Set ResolutionCode to ‘Validated’ or ‘No Plan To Test’ respectively  Optionally: Add a Comment to the ’Dev’ Activity  Note: The Task will continue to be displayed by the ‘Tester w Build’ Query until the Task- >ResolutionCode is changed to something other than ‘Rejected_Development’ or ‘Rejected_Test’  Login as ‘TestLead_ToDo’  Execute \Public queries\Practices\ToDo\REST\Completing Tasks query  Click Change State icon and choose Complete Action on Task  Set ResolutionCode = ‘Approved’  Optionally: Set BTBuild to mark when work was Approved.

78. ALM Training CRM29 Requests with unacceptable Task(s) and/or Activities  Login as ‘Requestor_ToDo’  Execute \Public queries\Practices\ToDo\REST\Requestor query  Choose Request Change State Reject_Solution Action  It will be in the Rejected State  Optionally: Task or Activity->QuestionOrComment explaining why not accepted  Login as ‘ProjectAdmin_ToDo’ Query: Project Admin  Follow-up with Requestors and Task Owners to determine whether to ReOpen Task  Once the solution has been reworked successfully  Login as ‘Requestor_ToDo’  If an acceptable solution has been provided, Accept the Request  Request will be in the Completed State

79. ALM Training CRM29 ClearQuest Application Lifecycle Management Demo End of ALM Training