The business analyst tallies the reviewers’ votes and comments. If changes are required to the snapshot, she rejects the Requirements Approval ticket and makes the changes. She creates a new snapshot of the document, which creates a new Requirements Approval ticket in Requirements Manager. The review process starts again. The approval process is repeated until final approval of the snapshot is received from all of the reviewers.


The business analyst uses Requirements Manager to transition the Requirements Approval ticket to the next state, Approved, which starts the testing phase.


To provide the QA team with test requirements, the business analyst then publishes the requirements which automatically creates test requirements in HP Quality Center.


Quality management assets are managed by HP Quality Center or other testing tools. The QA Manager updates test requirements and adds further details. The test requirement definitions are based on the detailed functional requirements. The QA team turns test requirements into test cases and groups them into test suites.


To enable the development team to understand the work that will be required, the development manager uses Serena Development Manager to review the detailed functional requirements and creates Development Change Requests.


The IT infrastructure needs to be upgraded to support the anticipated increased traffic to the online application. Therefore, the IT Manager uses Serena Service Manager to raise Requests For Change to install new switches and servers.


The Executive management team uses Serena Dashboard to review the project. For example, are there sufficient resources, documentation, and test plans? Are the requirements met? The project is approved for development.


The project manager uses Serena Development Manager to transition the project to the next state, Construction.