|
Step
|
Description
|
|
20
|
To plan the contents of the release, the release manager creates release packages in the application release and adds the Development Change Requests to the release packages.
|
|
21
|
To assign the work correctly to developers, the development manager uses Serena Development Manager to break the requests into development tasks. As they are created, the tasks are synchronized with Dimensions CM task requests. When the tasks are ready to be worked on, the team lead moves them into development and assigns them to individual developers.
|
|
22
|
The developers create and update source code using their preferred development environments. Development changes are delivered to Dimensions CM against the tasks. After the tasks are delivered they are built and unit tested using a continuous build integration system, such as Hudson.
|
|
23
|
When all of the development tasks for a change request are completed, the development team performs testing.
|
|
24
|
Change requests are transitioned back to the development team after they have been successfully tested.
|
|
25
|
The development manager and project manager use Serena Development Manager to continually review the list of requests in progress and move work out of the project as needed based on remaining time and business priorities.
|
|
26
|
To build the completed Development Change Requests, the build manager uses Serena Development Manager to create a development package of completed requests. The development package is used to take the changes through the formal build process. The stream where the development work is taking place is automatically related to the package. A baseline of that stream is created and is automatically related to the development package. The baseline assembles all of the source code changes associated with completed Development Change Requests.
|
|
27
|
The build manager delegates the development package to a build engineer and transitions it to its next state, Ready for Build.
|
