|
Step
|
Description
|
|
1
|
The business analyst uses Serena Service Manager to raise a new Business Change Request to modify an application.
|
|
2
|
The business case for the new version of the application is reviewed and approved by all the relevant stakeholders, for example, the Executive team.
|
|
3
|
The project manager uses Serena Requirements Manager to create a new Application Lifecycle Management (ALM) project and transitions it to the Inception state.
|
|
4
|
To address the Business Change Request in a specific project, the project manager uses Requirements Manager to associate the Business Change Request with the ALM project.
|
|
5
|
The project management team reviews the Business Change Request and approves the project.
|
|
6
|
The project manager uses Requirements Manager to transition the project to its next state, Elaboration.
|
|
7
|
To deliver the changes in a specific quarter, the release manager uses Serena Release Manager to create an application release in the appropriate quarterly release train, and associates the Business Change Request with the application release.
|
|
8
|
The business analyst creates a new collection of requirements for the release using the Dimensions RM.
|
|
9
|
The business analyst the breaks down the Business Change Requests into various classes of functional requirements.
|
|
10
|
The business analyst raises a requirements approval request, which in turn creates a snapshot of the requirements collection.
|
|
11
|
The reviewers of the functional requirements receive notification from Requirements Manager and open a web link to a snapshot in Requirements Manager. They make review comments against the snapshot and the requirements, and approve or reject the Requirements Approval ticket.
|
