|
Step
|
Description
|
|
28
|
After the build has completed successfully, outputs are automatically collected back into Dimensions CM against a build request, and a revised baseline is produced. The development package is automatically updated with the revised baseline of built objects. This is an iterative cycle until all development and build work is successfully completed.
|
|
29
|
The build manager uses Serena Development Manager to transition the development package to its next state, Ready for Test.
|
|
30
|
The development team performs testing. When the testing is complete, the development manager transitions the development package to its next state, Complete.
|
|
31
|
When the testing is complete, the development manager transitions the development package to its next state, Ready for Release.
|
|
32
|
The project management team uses Serena Dashboard to review metrics, such as build successes, and approves the finished work.
|
|
33
|
The development manager uses Serena Development Manager to transition the project to its next state, Transition.
|
|
34
|
To ensure that the IT operations team upgrades the hardware for this release, the release manager adds the Requests For Change to the release train.
|
