Tao, the QA manager, does some research and finds that the problem is in a single file, AutoQuote.jar, in the LCL_QA_JBRNCHA_AREA03 web application deployment area. Tao decides that the quickest solution is to prepare a fix and deploy it forward over the file that is causing the problem.

The QA manager raises a change request to track the defect

Tao raises a change request to fix and track the defect.

1. Log into the web client as Tao.

2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR.

3. In the Request view, on the toolbar click New and select CR.

The New Request dialog box appears.

4. In the Title field enter a title for the request, for example: Fix Autoquote.java.

5. In the Detailed description field enter a description.

6. On the Attributes tab, from the Severity/Priority list select a priority.

7. Click Submit and click Close.

The new request is added to Rita’s request inbox with the following ID:

QLARIUS_CR_n 

By default the request is at the DEV stage when it is raised.

The QA manager delegates the request to the team lead

Tao delegates the request to the development team lead, Ted, whose team is responsible for maintaining Qlarius.

1. Select the request and on the toolbar click Delegate.

The Delegate wizard appears.

2. Check that the Capability option is set to Secondary.

3. From the Role to Delegate list select IMPLEMENTOR and click Next.

4. In the ’Candidate users authorized for role assignment’ list select Ted and click Add.

The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a request has been added to his Request inbox.

The QA manager actions the request to its next state

Tao actions the request to its next state, UNDER WORK.

1. Select the request and on the toolbar select Action.

The Action wizard appears.

2. Check that the To next state field is set to UNDER WORK.

3. Click Finish and click OK.

The request is removed from Tao’s request inbox.

4. Log out of the web client.

The development team lead primes a child task from the request

Ted reads the email, views the request in his Request inbox, and primes a child task from the request.

1. Log into the web client as Ted.

2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR

3. In the Request view select the Request inbox and then the request that was raised by Tao.

4. On the toolbar click Prime and select Task.

The Prime Request dialog box appears.

5. (Optional) Update the detailed description.

6. Click Submit and click Close.

The new child task is added to Ted’s request inbox with the following ID:

QLARIUS_TASK_n

By default the child task is at the DEV stage when it is raised.

The development team lead delegates the task to a developer

Ted delegates the child task to a developer, Dinesh.

1. Select the child task and on the toolbar click Delegate.

The Delegate wizard appears.

2. Check that the Capability option is set to Secondary.

3. From the Role to Delegate list select IMPLEMENTOR and click Next.

4. In the ’Candidate users authorized for role assignment’ list select Dinesh and click Add.

The wizard closes automatically. Dimensions CM sends an email to Dinesh notifying him that a task has been added to his Request inbox.

The development team lead actions the task to its next state

Ted actions the task to its next state, UNDER WORK.

1. Select the child task and on the toolbar select Action.

The Action wizard appears.

2. Check that the To next state field is set to UNDER WORK.

3. Click Finish and click OK.

The child task is removed from Ted’s request inbox.

4. Log out of the web client.

The developer updates their work area from the stream

Dinesh reads the email, checks his Request inbox, and updates his work area.

1. Log into the web client as Dinesh.

2. Switch to the following stream: QLARIUS:JAVA_BRANCHA_STR

3. Change Dinesh’s work area to the one that you created earlier (see the pre-requisites at the start of scenario 3).

4. In the Items view, on the navigation pane select the folder that contains Autoquote.java: Qlarius Underwriter > qlarius > interfaces

5. On the toolbar click Update.

The Update from Stream wizard appears.

6. Click Next,

7. Click Finish and then Close.

Dinesh’s work area is updated.

The developer fixes the defect

In Dinesh’s local work area edit Autoquote.java. For the purpose of this scenario make a minor edit, for example, add a comment to the top of the item.

The developer delivers the item and relates it to the task

Dinesh delivers the fixed item to Dimensions CM and relates it to the task.

1. In the Items view, on the toolbar click Deliver.

The Deliver to Stream wizard appears.

2. Check that the Modifications check box is selected.

3. Click Next.

4. Verify that AutoQuote.java is selected and click Next.

5. In the Relate to request(s) field click Select.

The Select Request dialog box appears.

6. From the Product name list select QLARIUS.

7. From the Type name list select TASK.

8. Click Next.

9. Select the task that is delegated to Dinesh and click Finish.

10. In the Deliver to Stream wizard click Finish and then Close.

The developer verifies that the item was automatically deployed to the DEV area

Deploy by default is enabled for the DEV area so when Dinesh delivered the item it was automatically deployed. He checks that the item was successfully deployed.

1. Select the Deployment view.

2. To only display information for the current stream do the following:

a    In the navigation pane click the filter button in the top right corner.

b    Select Show Current Stream.

3. Select the History tab and in the navigation pane select the DEV stage node.

4. In the content pane verify that the AutoQuote.java was successfully deployed to the LCL_DEV_JBRNCHA_AREA03 deployment area.

The developer builds the task and captures the outputs

Dinesh builds the task in the DEV web application deployment area and captures the build outputs in Dimensions CM against the task.

1. On the Requests view select the Request inbox.

2. Select the task, on the toolbar click Build, and select Build.

The Run Build wizard appears.

3. In the Build Configuration field accept the default configuration.

4. From the Build Stage list select DEV.

5. From the Build Area list select LCL_DEV_JBRNCHA_AREA03.

6. Click Next.

7. Select the option Check in build outputs automatically. This will check the build outputs into Dimensions CM.

8. To specify the request that the build outputs will be related to when they are checked into Dimensions CM, in the Specify the request(s) field click Select.

The Select Request wizard appears.

9. Do the following:

a    From the Product name list select QLARIUS.

b    From the Type name list select TASK.

c     Click Next.

d    Select the task that is delegated to Dinesh.

e    Click Finish.

10. In the Run Build wizard click Next.

11. Accept the default build option selections (none) and click Next.

12. Accept the default target selection options.

13. In the target list select Jar Files.

14. Click Next.

A summary of the build command that will be executed is displayed.

15. Click Finish.

16. (Optional) To monitor the progress of the build click the Job <ID number> link.

17. Click Close.

The developer verifies that the build was successful

Dinesh verifies that the build was successful and that the outputs were deployed to the DEV web application deployment area.

1. To verify that the build was successful, in the Deployment view select the History tab.

2. In the navigation pane expand the DEV stage node and select LCL_DEV_JBRNCHA_AREA03.

3. In the content pane verify that the Event Result column displays Succeeded for the following objects:

• Autoquote.jar (the Event Type is Collect)

• QLARIUS:JAVA_BRANCHA_STR (the Event Type is Build)

4. Open Autoquote.jar, make a note of the item revision, and click Cancel.

5. To browse the DEV web application deployment area, in the My Current Project view expand Deployment Areas > DEV Stage > LCL_DEV_JBRNCHA_AREA03

6. Select the folder Qlarius Underwriter.

7. In the content pane verify that the latest revision of AutoQuote.jar is deployed. This should be later than the revision that you made a note of at the start of this scenario.

The developer delegates the task to the team lead for peer review

Dinesh delegates the task to Ted for peer review.

1. In the Requests view select the Request inbox.

2. Select the task and on the toolbar click Delegate.

The Delegate wizard appears.

3. Check that the Capability option is set to Secondary.

4. From the Role to Delegate list select REVIEWER and click Next.

5. In the ’Candidate users authorized for role assignment’ list select Ted and click Add.

The wizard closes automatically. Dimensions CM sends an email to Ted notifying him that a task has been added to his Request inbox.

The developer actions the task to its next state

Dinesh actions the task to its next state, PEER REVIEW.

1. Select the child task and on the toolbar select Action.

The Action wizard appears.

2. In the New State section check that the To next state field is set to PEER REVIEW.

3. Click Next.

4. In the Actual completed date field enter a date.

5. In the Actual development effort (hours) field enter a number.

6. Click Finish.

The task is removed from Dinesh’s request inbox.

7. Log out of the web client.

The team lead does a peer review and actions the task to its final state

Ted has read his email, seen the task in his Request inbox, done a peer review of the defect that Dinesh fixed, and is satisfied with the changes that he made. He actions the task to its final state, CLOSED.

1. Log into the web client as Ted.

2. In the Requests view select the Request inbox, select the task, and on the toolbar click Action.

The Action wizard appears.

3. Check that the To next state field is set to CLOSED.

4. Click Finish and click OK.

The task is removed from Ted’s Request inbox.

The team lead promotes and deploys the request and the task to the SIT stage and area

To perform system integration testing, Ted promotes and deploys the request and task to the SIT stage and web application deployment area.

1. In the Request view, in the Request inbox, select the request.

2. On the toolbar click Promote.

The Promote wizard appears.

3. Check that the option Promote child requests is selected.

4. In the Next stage field check that SIT is selected.

5. Click Next.

6. To deploy immediately, check that the option Perform deployments is set to ’as soon as possible’.

7. In the Areas(s) for deployment field select the SIT LCL_SIT_JBRNCHA_AREA03 deployment area (you might need to deselect LCL_SIT_JBRNCHA_AREA01).

8. Click Next.

A summary of the deployment activity and command that will be performed is displayed.

9. Click Finish.

The team lead verifies that promotion and deployment operations were successful

Ted verifies that promotion and deployment operations were successful and that the modified file was deployed to the SIT web application deployment area.

1. Select the Deployment view and check that only the current stream is displayed.

2. Select the History tab and in the navigation pane select the SIT stage node.

3. In the content pane verify that the request was promoted successfully from DEV to SIT.

4. In the navigation pane expand the SIT stage node and select the LCL_SIT_JBRNCHA_AREA03 deployment area.

5. In the content pane verify that the request and task were deployed successfully to the SIT web application deployment area.

6. To browse the SIT web application deployment area, in the My Current Project view expand Deployment Areas > SIT Stage > LCL_SIT_JBRNCHA_AREA03.

7. Select the folder Qlarius Underwriter.

8. In the content pane verify that latest revision of AutoQuote.jar is deployed.

Ted performs system integration testing.

The team lead promotes the request and task to the QA stage

System integration testing has been completed successfully so Ted promotes the request and task to the QA stage. Deploy by Default is not enabled so the request and task cannot be automatically deployed to the QA deployment area.

1. In the Requests view, in the Request inbox, select the request and on the toolbar click Promote.

The Promote wizard appears.

2. Check that the option Promote child requests is selected.

3. In the Next stage field check that QA is selected.

4. Click Next.

Deploy by Default is not enabled so no deploy options are available.

5. Click Next.

A summary of the promotion activity and command that will be performed is displayed.

6. Click Finish.

Dimensions CM sends an email to the QA manager, Tao, notifying her that a promotion has been performed.

7. In the Deployment view select the History tab and in the navigation pane select the QA stage node.

8. In the content pane verify that the request was promoted successfully from SIT to QA.

The team lead actions the request to its next state

Ted actions the request to its next lifecycle state, IN TEST, so that QA can test the application.

1. On the History tab select the request and on the toolbar click Action.

The Action wizard appears.

2. In the New State section check that the To next state field is set to IN TEST.

3. Click Next.

4. In the Details of solution given field enter a solution.

5. Click Finish.

Note: The task is removed from Ted’s request inbox.

6. Log out of the web client.

The QA manager deploys the request and task to the QA deployment area

Tao reads the email, checks her Request inbox, and deploys the request and task to the QA web application deployment area.

1. Log into the web client as Tao.

2. Select the Deployment view and check that only the current stream is displayed.

3. Select the Pending tab.

4. In the navigation pane expand the QA stage node and select the LCL_QA_JBRNCHA_AREA03 deployment area.

5. In the content pane, from the Show list select Requests.

6. Select the request and on the toolbar click Deploy.

The Deploy wizard appears.

7. Check that the option Deploy child requests is selected.

8. Check that the Deploy Stage is set to QA.

9. Click Next.

10. To deploy the request and child tasks immediately, check that the option Perform deployments is set to ’as soon as possible’.

11. In the Areas(s) for deployment field check that the LCL_QA_JBRNCHA_AREA03 deployment area is selected.

12. Click Next.

A summary of the deployment activity and command that will be performed is displayed.

13. Click Finish.

The QA manager verifies that promotion and deployment operations were successful

Tao verifies that promotion and deployment operations were successful and that the modified file was deployed to the QA web application deployment area.

1. Select the History tab.

2. In the content pane verify that the request and task were deployed successfully.

3. To browse the QA web application deployment area, in the My Current Project view expand Deployment Areas > QA Stage > LCL_QA_JBRNCHA_AREA03.

4. Select the folder Qlarius Underwriter.

5. In the content pane verify that latest revision of AutoQuote.jar is deployed.

The QA team performs their tests.

The QA manager actions the request to its final lifecycle state.

QA testing has been completed successfully so Tao closes the enhancement request that she raised against the defect.

1. In the Request view select the request and on the toolbar click Action.

The Action wizard appears.

2. Check that the To next state field is set to CLOSED.

3. Click Finish and click OK.

The request is removed from Tao’s request inbox.

End of scenario

REQUEST_PROMOTE_NEXTSTAGE

ITEM_PROMOTE_NEXTSTAGE

Team lead

DEV

SIT

The DEV and SIT areas are deploy by default areas and no deployment privileges are required.

REQUEST_DEPLOY

ITEM_DEPLOY

QA Manager

LCL_QA_JBRNCHA_AREA02