Scenario 4: Deploy refactoring changes

This scenario demonstrates how to deploy refactoring changes to the corporate website of Qlarius Health Insurance.

Note: To run this scenario, first set up the environment, as described in Prerequisites.

Scenario overview

  • The release manager raises enhancement requests.

  • The development team lead primes a child task from each request.

  • A web developer makes the refactoring changes, delivers the modifications, and relates them to the tasks.

  • The team lead promotes and deploys the requests and tasks to the SIT stage and deployment area, and then promotes them to the QA stage.

  • The QA manager deploys the requests and tasks to the QA deployment area and then promotes them to the PRE-PROD stage.

  • The release manager deploys the requests and tasks to the PRE-PROD deployment area and then promotes and deploys them to the LIVE stage and production environments.

Back to top

Scenario information

  • The following scenario is used: QLARIUS:JAVA_BRANCHA_STR

  • No builds are required as only a text file is modified.

  • There is a division of responsibilities between the employees at the following stage transitions:

    • SIT to QA

    • QA to PRE-PROD

  • This scenario uses the following web application deployment areas:

    Stage Deployment area Deploy by Default enabled on area?
    DEV LCL_DEV_JBRNCHA_AREA03 Yes
    SIT LCL_SIT_JBRNCHA_AREA03 Yes
    QA LCL_QA_JBRNCHA_AREA03 No
    PRE‑PROD LCL_PP_JBRNCHA_AREA03 No
    LIVE LCL_LIVE_JBRNCHA_AREA03 No

For a list of the promotion and deployment privileges required by the users, see Scenario privileges.

Back to top

Scenario prerequisites

  1. Create a work area on your local machine for the user Wendy, for example:

    C:\streams\JAVA_BRANCHA_STR\wendy

  2. Log in to the web client as a user that has the privileges to promote and deploy baselines to any stage and area, for example, the tool administrator, typically dmsys.

  3. Take a tip baseline of the stream JAVA_BRANCHA_STR.

  4. To deploy the files in the stream to all deployment areas, promote and deploy the baseline:

    1. Select the baseline, and click Promote in the toolbar.

    2. In the Promote dialog box, check that SIT is selected for the Next Stage, and click Next.

    3. To deploy immediately, check that the Perform Deployments option is set to As Soon As Possible.

    4. In the Areas for Deployment field, check that the LCL_SIT_JBRNCHA_AREA03 deployment area is selected. Click Next.

    5. Review the summary of the promotion and deployment activity and command, and click Finish.

  5. Repeat the earlier step for the other stages and deployment areas:

    QA LCL_QA_JBRNCHA_AREA03
    PRE-PROD LCL_PRE-PROD_JBRNCHA_AREA03
    LIVE LCL_LIVE_JBRNCHA_AREA03
  6. Log out of the web client.

Back to top

Run this scenario

The following table describes the tasks performed in this scenario.


Action Procedure

The release manager raises enhancement requests.

Refactoring changes are required to the corporate website of Qlarius Health Insurance. Rita, the release manage, raises two enhancement requests to manage the change:

  • The first request is a refactoring change to create a resources directory and move the file main.css from the website directory to the new directory.

  • The second request is an enhancement to main.css.

  1. Log in to the Dimensions CM web client as Rita.

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

  3. In the Requests tab, in the toolbar, click New and select CR. The New Request dialog box opens.

  4. In the Title field, enter Create resources directory and move CSS file.

  5. In the Detailed Description field, enter a description.

  6. In the Attributes tab, from the Severity/Priority list, select a value.

  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.

  8. Repeat steps 3 to 7 to create the second request and use the title Modify CSS file.

The release manager delegates the request to the team lead.

Rita delegates the requests to the development team lead, Ted, whose team is responsible for maintaining the website.

  1. Select both requests, and in the toolbar click Delegate. The Delegate wizard opens.

  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 requests have been added to his Request inbox.

The release manager actions the requests to their next state.

Rita actions the requests to their next state, UNDER WORK.

  1. Select the requests, and in the toolbar select Action. The Action Multiple Requests dialog box opens.

  2. Click Finish. The requests are removed from Rita’s request inbox.

  3. Log out of the web client.

The development team lead primes a child task from each request.

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

  1. Log in to the web client as Ted.

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

  3. In the Requests tab, select the Request inbox.

  4. Select the first request that was raised by Rita, Create resources directory and move CSS file.

  5. In the toolbar, click Prime, and select Task. The Prime Request dialog box opens.

  6. Click Submit and then 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.

  7. To prime a child task from the second request, Modify CSS file, repeat steps 4 to 6.

The development team lead delegates the tasks to a web developer.

Ted delegates both tasks to a web developer, Wendy.

  1. Select both tasks, and in the toolbar click Delegate. The Delegate wizard opens.

  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 Wendy, and click Add.

The wizard closes automatically. Dimensions CM sends an email to Wendy notifying her that requests have been added to her Request inbox.

The development team lead actions the tasks to their next state.

Ted actions the tasks to their next state, UNDER WORK.

  1. Select both child tasks, and in the toolbar select Action. The Action Multiple Requests dialog box opens.

  2. Click Finish. The tasks are removed from Ted’s request inbox.

  3. Log out of the web client.

The web developer updates her local work area.

Wendy, the web developer, reads the emails and checks her Request inbox. She updates her local work area from the website folder.

  1. Log in to the web client as Wendy.

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

  3. Change Wendy’s work area to the one that you created earlier in Scenario prerequisites.

  4. In the Items tab, in the Dirs tab, expand the Qlarius Underwriter folder, and select website.

  5. In the toolbar, click Update. The Update from Stream dialog box opens.

  6. Click Next and then Finish.

  7. Click Close.

The web developer makes some refactoring changes.

In Wendy’s local work area do the following:

  1. In the website folder, create a new subfolder called resources.

  2. Move main.css from the website folder to the resources folder.

The web developer delivers the refactoring changes.

Wendy delivers the refactoring changes to Dimensions CM and relates them to the first task.

  1. In the web client, in the navigation pane, select the website folder (in the Items tab > Dirs tab).

  2. In the toolbar, click Deliver. The Deliver to Stream dialog box opens.

  3. Check that the Moves/Renames option is selected.

  4. Click Next.

    Ensure that the following changes types are selected:

    • Qlarius Underwriter\website\main.css (Deletion)

    • Qlarius Underwriter\website\resources (Addition)

    • Qlarius Underwriter\website\resources\main.css (Addition)

  5. Click Next.

  6. In the Relate to Request(s) field, click Select. The Select Request wizard opens.

  7. From the Product Name list, select QLARIUS.

  8. From the Type Name list, select TASK.

  9. Click Next.

  10. Select the task Create resources directory and move CSS file and click Finish.

  11. In the Deliver to Stream dialog box, click Finish.

  12. Click Close.

The refactoring changes are delivered to Dimensions CM.

The web developer verifies that the refactoring changes were deployed.

The Deploy by Default option is enabled for the DEV web application deployment area, so when Wendy delivered the refactoring changes, they were automatically deployed. She checks that deployment was successful.

  1. Select the Deployment view.

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

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

    2. Select Show Current Stream.

  3. Select the History tab.

  4. In the navigation pane, expand the DEV stage node and select the LCL_DEV_JBRNCHA_AREA03 web application deployment area.

  5. In the content pane, verify that the main.css was successfully deployed. The Event Result column should display Succeeded.

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

    In the navigation pane, verify that there is a folder called resources.

  7. Select the resources folder, and in the content pane verify that main.css was deployed.

The web developer modifies the file.

In Wendy’s local work area modify main.css in the resources directory. For the purpose of this scenario make a minor edit, for example, add a comment to the top of the file.

The web developer delivers the modification to Dimensions CM.

Wendy delivers the modified file to Dimensions CM relates it to the second task.

  1. In the Items tab, in the Dirs tab, expand Qlarius Underwriter, and select the resources folder.

  2. In the toolbar, click Deliver. The Deliver to Stream dialog box opens.

  3. Click Next.

  4. Check that main.css is selected and click Next.

  5. In the Relate to Request(s) field, click Select. The Select Request wizard opens.

  6. From the Product Name list, select QLARIUS.

  7. From the Type Name list, select TASK.

  8. Click Next.

  9. Select the task Modify CSS file and click Finish.

  10. In the Deliver to Stream dialog box, click Finish.

  11. Click Close.

  12. Make a note of the latest revision of main.css.

The web developer verifies that the modification was deployed.

Wendy checks that deployment was successful.

  1. Select the Deployment view.

  2. Select the History tab.

  3. In the navigation pane, expand the DEV stage node and select the LCL_DEV_JBRNCHA_AREA03 web application deployment area.

  4. In the content pane, verify that the main.css was successfully deployed a second time.

    The Event Result column should display Succeeded.

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

  6. Select the resources directory, and in the content pane verify that the latest revision of main.css is deployed.

The web developer delegates the tasks to the team lead for peer review.

Wendy delegates the tasks to Ted for peer review.

  1. In the Requests tab, select the Request inbox.

  2. Select both tasks, and in the toolbar click Delegate. The Delegate wizard opens.

  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 tasks have been added to his Request inbox.

The web developer actions the tasks to their next state.

Wendy actions the tasks to their next state, PEER REVIEW.

  1. Select the first child task, and in the toolbar select Action. The Action wizard opens.

  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 Wendy’s Request inbox.

  7. Repeat steps 1 to 6 for the second child task.

  8. Log out of the web client.

The team lead does a peer review and actions the tasks to their final state.

Ted has read his emails, seen the tasks in his Request inbox, and done a peer review of the refactoring changes. He actions both tasks to their final state, CLOSED.

  1. Log in to the web client as Ted.

  2. In the Requests tab, select the Request inbox, select both tasks, and in the toolbar click Action. The Action wizard opens.

  3. Click Finish. The child tasks are removed from Ted’s Request inbox.

The team lead promotes and deploys the requests and tasks to the SIT stage.

To perform system integration testing, Ted promotes and deploys the requests and tasks to the SIT stage and web application deployment area. Ted promotes both requests in the same operation and lets Dimensions CM automatically deploy the refactoring changes in the correct sequence. Dimensions CM does the following:

  • Creates the resources directory and moves main.css from the website directory to the resources directory.

  • Deploys the latest revision of main.css to the resources directory.

Note: If you select multiple requests, or a request with child requests, Dimensions CM automatically resolves the refactoring changes. This applies to both manual and automatic (Deploy by Default) deployments.

  1. In the Requests tab, select both parent requests.

  2. In the toolbar, click Promote. The Promote wizard opens.

  3. Check that the Promote Child Requests option is selected. This promotes and deploys the child tasks with their parent requests.

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

  5. To deploy now, check that the Perform Deployments option is set to As Soon As Possible.

  6. In the Areas for Deployment field, select the SIT LCL_SIT_JBRNCHA_AREA03 deployment area. Click Next.

    Note: If both areas are selected, clear SIT LCL_SIT_JBRNCHA_AREA01.

  7. Review the summary of the deployment and promotion activities and command, and 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 refactoring changes were 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 both requests were 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 all the requests and child tasks were deployed successfully.

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

    In the navigation pane verify that there is a folder called resources.

  7. Select the resources folder, and in the content pane verify that the latest revision of main.css is deployed.

Ted performs system integration testing.

The team lead promotes the requests and tasks to the QA stage.

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

  1. In the Requests tab, select the requests.

  2. In the toolbar, click Promote. The Promote wizard opens.

  3. Check that the option Promote Child Requests is selected.

  4. In the Next stage field, check that QA is selected. Click Next.

  5. Because Deploy by Default is not enabled, no deploy options are available. Click Next.

  6. Review the summary of the promotion activity and command, and 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 both requests were promoted successfully from SIT to QA.

The team lead actions the requests to their next state.

Ted actions the requests to their next lifecycle state, IN TEST, so that QA can test the website.

  1. In the History tab, select the first request, and in the toolbar select Action. The Action wizard opens.

  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 description.

  5. Click Finish. The request is removed from Ted’s Request inbox.

  6. Repeat steps 1 to 5 for the second request.

  7. Log out of the web client.

The QA manager deploys the requests and tasks to the QA deployment area.

Tao reads the email and checks her Request inbox. She deploys both requests in the same operation and lets Dimensions CM automatically deploy the refactoring changes in the correct sequence.

  1. Log in to the web client as Tao.

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

  3. Select the Deployment view, and check that the current stream is displayed.

  4. Select the Pending tab.

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

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

  7. Select both requests, and in the toolbar click Deploy. The Deploy wizard opens.

  8. Check that the Deploy Child Requests option is selected.

  9. Check that the Deploy Stage is set to QA. Click Next.

  10. To deploy the requests now, check that the Perform Deployments option is set to As Soon As Possible.

  11. In the Areas for Deployment field, check that the following QA deployment area is selected: LCL_QA_JBRNCHA_AREA03. Click Next.

  12. Review the summary of the deployment activity and command, and click Finish.

  13. Select the History tab.

  14. In the content pane, verify that the requests and child tasks were successfully deployed to the QA area LCL_QA_JBRNCHA_AREA03.

The QA manger verifies that the refactoring changes were deployed.

Tao verifies that the refactoring changes were deployed to the QA web application deployment area.

  1. In the My Current Project view, expand Deployment Areas > QA Stage > LCL_QA_JBRNCHA_AREA03 > Qlarius Underwriter > website.

    In the navigation pane, verify that there is a folder called resources.

  2. Select the resources folder, and in the content pane verify that the latest revision of main.css is deployed.

The QA team performs their tests.

The QA manager actions the requests to their final lifecycle state.

QA testing has been completed successfully, so Tao closes the enhancement requests.

  1. In the History tab, select both requests, and in the toolbar click Action. The Action wizard opens.

  2. Click Finish. The request are removed from Tao’s request inbox.

The QA manager promotes the requests and tasks to the PRE-PROD stage.

QA testing has been completed successfully so Tao promotes the requests and tasks to the PRE-PROD stage. Deploy by Default is not enabled so the requests and tasks cannot be automatically deployed to the PRE-PROD deployment area.

  1. In the History tab, select the requests.

  2. In the toolbar, click Promote. The Promote wizard opens.

  3. Check that the option Promote Child Requests is selected.

  4. In the Next stage field, check that PRE-PROD is selected. Click Next.

  5. Because Deploy by Default is not enabled, no deploy options are available. Click Next.

  6. Review the summary of the promotion activity and command, and click Finish. .

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

  7. In the navigation pane, select the PRE-PROD stage node.

  8. In the content pane, verify that both requests were promoted from QA to PRE-PROD.

  9. Log out of the web client.

The release manager deploys the requests and tasks to the PRE- PROD deployment area.

Rita reads the email and checks her Request inbox. She deploys both requests in the same operation and lets Dimensions CM automatically deploy the refactoring changes in the correct sequence.

  1. Log in to the web client as Rita.

  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 PRE-PROD stage node and select the LCL_PP_JBRNCHA_AREA03 deployment area.

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

  6. Select both requests, and in the toolbar click Deploy. The Deploy wizard opens.

  7. Check that the Deploy Child Requests option is selected.

  8. Check that the Deploy Stage is set to PRE-PROD. Click Next.

  9. To deploy the requests now, check that the Perform Deployments option is set to As Soon As Possible.

  10. In the Areas for Deployment field, check that the following PRE-PROD deployment area is selected: LCL_PP_JBRNCHA_AREA03. Click Next.

  11. Review the summary of the deployment activity and command, and click Finish.

  12. Select the History tab.

  13. In the content pane, verify that the requests and child tasks were successfully deployed to the QA area LCL_PP_JBRNCHA_AREA03.

The release manger verifies that the refactoring changes were deployed.

Rita verifies that the refactoring changes were deployed to the PRE-PROD web application deployment area.

  1. In the My Current Project view, expand Deployment Areas > PRE-PROD Stage > LCL_PP_JBRNCHA_AREA03 > Qlarius Underwriter > website.

    In the navigation pane, verify that there is a folder called resources.

  2. Select the resources folder, and in the content pane verify that the latest revision of main.css is deployed.

The release team performs their tests.

The release manager promotes the requests and tasks to the LIVE stage.

Testing has been completed successfully, so Rita promotes the requests and tasks to the LIVE stage. Because Deploy by Default is not enabled, the requests and tasks cannot be automatically deployed to the PRE-PROD deployment area.

  1. In the Deployment view, in the navigation pane, select the LCL_PP_JBRNCHA_AREA03 deployment area.

  2. Select the History tab and select the requests.

  3. In the toolbar, click Promote. The Promote wizard opens.

  4. Check that the Promote Child Requests option is selected.

  5. In the Next stage field, check that LIVE is selected. Click Next.

  6. Rita has the privilege to deploy at the same time as the promotion but chooses not. Do not select any deployment areas. Click Next.

  7. Review the summary of the promotion activity and command, and click Finish.

  8. In the Deployment view, select the History tab, and in the navigation pane select the LIVE stage node.

  9. In the content pane verify that both requests were promoted successfully from PRE-PROD to LIVE.

The release manager deploys the requests and tasks to the LIVE deployment area.

Let’s assume that it is now the regular maintenance period when the LIVE web application deployment area is offline. Rita checks what requests are ready to be deployed to the LIVE stage. Rita deploys both requests in the same operation and lets Dimensions CM automatically deploy the refactoring changes in the correct sequence.

  1. Select the Pending tab.

  2. In the navigation pane, select the LCL_LIVE_JBRNCHA_AREA03 deployment area.

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

  4. Select both requests, and in the toolbar click Deploy. The Deploy wizard opens.

  5. Check that the Deploy Child Requests option is selected.

  6. Check that the Deploy Stage is set to LIVE. Click Next.

  7. To deploy the requests now, check that the Perform Deployments option is set to As Soon As Possible.

  8. In the Areas for Deployment field, check that the following LIVE deployment area is selected: LCL_LIVE_JBRNCHA_AREA03. Click Next.

  9. Review the summary of the deployment activity and command, and click Finish.

  10. Select the History tab.

  11. In the content pane, verify that the requests and child tasks were successfully deployed to the QA area LCL_LIVE_JBRNCHA_AREA03.

The release manger verifies that the refactoring changes were deployed.

Rita verifies that the refactoring changes were deployed to the LIVE web application deployment area.

  1. In the My Current Project view, expand Deployment Areas > LIVE Stage > LCL_LIVE_JBRNCHA_AREA03 > Qlarius Underwriter > website.

    In the navigation pane, verify that there is a folder called resources.

  2. Select the resources folder, and in the content pane verify that the latest revision of main.css is deployed.

End of scenario

Back to top

Scenario privileges

The following tables list the promotion and deployment privileges required by each user in the scenario.

Promotion privilege Privilege owner Required at these stages

REQUEST_PROMOTE_NEXTSTAGE
ITEM_PROMOTE_NEXTSTAGE

Team lead DEV
SIT
QA Manager QA
Release Manager PRE-PROD
Deployment privilege Privilege owner Required for these areas
The SIT and LIVE areas are Deploy by Default areas, and no deployment privileges are required.
REQUEST_DEPLOY
ITEM_DEPLOY
QA Manager LCL_QA_JBRNCHA_AREA03
Release Manager LCL_PP_JBRNCHA_AREA03

Back to top