ClearQuest Application Lifecycle Management Training - PowerPoint PPT Presentation

clearquest application lifecycle management training n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
ClearQuest Application Lifecycle Management Training PowerPoint Presentation
Download Presentation
ClearQuest Application Lifecycle Management Training

play fullscreen
1 / 71
ClearQuest Application Lifecycle Management Training
196 Views
Download Presentation
gina
Download Presentation

ClearQuest Application Lifecycle Management Training

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. ClearQuest Application Lifecycle Management Training Agile Demo

  2. Default Activity-> Project->SetDefault Project • Developer • Checks out code in CC Explorer and Creates New Activity Category Activity (Dev) Release Request Task

  3. Developer • Checks out code in CC Explorer and Creates New Activity • Developer • Deliver change • Test • Complete Delivery & Activity Activity (Dev)

  4. Developer • Checks out code in CC Explorer and Creates New Activity • Developer • Deliver change • Test • Complete Delivery & Activity Activity (Dev) Build Baseline • Builder • Create Baseline • Run Build • Validate Build and Promote

  5. Request Submitter • In Windows Eclipse client or CQWJ • Login as ‘Dev_ToDo’ (Password is BLANK) • In Eclipse, you can also pre-log in as Test_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 • Choose Type • Choose Severity • Give (brief) tour of Request • Owner should be set to Requestor_ToDo • Click OK

  6. 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 = ‘Release_ToDo’ Click on Request in Result Set grid Resize Display so Request->Tasks field shows Highlight the Request and Click UtilityCreateTask Note new Request->Task Owner should be set to Role->Primary for Project= ‘Project_ToDo’, RoleLabel = ‘DevLead’ Project Triage

  7. Lead Developer • Login as ‘DevLead_ToDo’ (Password is BLANK) • Execute query \Public queries\Practices\ToDo\REST\Dev Lead • Category = ‘Category_ToDo’ • Release = ‘Release_ToDo’ • Click on Task in Result Set grid • Change_State ActivateTask then click Apply • Set Task Owner to ‘TestLead_ToDo’ for Project= ‘Project_ToDo’, RoleLabel = ‘TestLead’ • Resize Display so Task->Activities field shows • Click UtilityCreateActivity • 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’ • You can also test with a Task->Type = 'Enhancement' and another ='New Functionality' Different sets of Activities should appear

  8. Project Test Lead Test Lead Assigning work • Login as ‘TestLead_ToDo’ (Password is BLANK) • Execute query \Public queries\Practices\ToDo\REST\Test Lead • Category = ‘Category_ToDo’ • Release = ‘Release_ToDo’ • Dbl-Click the ‘Test’ Type Activity on the Task • Choose ActivityOpen Action • Owner Choice_List should be automatically set to Role->Members values for Project= ‘Project_ToDo’, RoleLabel = ‘Test’ • Click OK

  9. 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 = ‘Release_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 ActivityOpen Action • Owner should be set from the Role->Members for Project= ‘Project_ToDo’, RoleLabel = ‘Doc Assess’ or ‘Developer’ depending on the Activity->Type • Click OK

  10. 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 = ‘Release_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 • Click Apply

  11. UCM Developer (skip if non-UCM developer) • Login to test machine as 'almtest' • 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 • Attempt to ReOpen the Activity. You should not be permitted to do this.

  12. Project Release Engineer Create Baseline of Code • Switch hats to become RE <Simulate Scripting> • Login as ‘ReleaseEngineer_ToDo’ (Password is BLANK) • Choose Menu Actions->New Baseline • Baseline = ‘<TOD> Baseline’ • PVOB = <TOD> PVOB’ • Project • ADD->Search <Highlight Project where Category = ‘Category_ToDo’ and Release = ‘Release_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

  13. 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->NewBuild • Build= ‘<TOD>Build’ • On ALM Tab • Choose Project • ADD->Search • Highlight record for Project and click OK • Baseline click ADD • enter ‘<TOD>’ used to create Baseline • click->Search • Highlight Baseline created earlier and click OK • Build Status = ‘Passed’ • Owner should be automatically set to Role->Primary for Project= ‘Project_ToDo’, RoleLabel = ‘ReleaseEngineer’ • Click OK on Build record

  14. Project Release Engineer (Build) UCM • Login as ‘ReleaseEngineer_ToDo’ (Password is BLANK) • Execute Baseline and Build UCM scripts

  15. 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 = ‘Release_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 Validated In Build • Enter ResolutionSummary and Resolution

  16. 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 = ‘Release_ToDo’ • Choose ‘Doc Assess’ Type Activity • <assume Doc assessment is done at this point> • If Documentation work is needed, the DocAssessor will: • Enter ResolutionSummary and Resolution • note the Activity->Task (in M3 this will be provided for you) • Complete the Type = ‘DocAssess’ Activity • click the ActivitiesRelatedNew button • Fill in the Task , the Type = ‘Dev’, 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.

  17. 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 = ‘Release_ToDo’ • Assess Activity States • Note Build containing ‘Dev’ fix (if Build was created) • Click Task Actions button and clickComplete • Click Task Apply

  18. Request Submitter • 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 = ‘Release_ToDo’ • Request State = ‘Opened’ • Task State = ‘Completed’ • Note States of Task and Task.Activities • Accept the work done on the Request