Hello Babynus,

During the life cycle of a project, a product or a business process, the associated requirements may evolve. And when a requirement evolves, there is often important impact on others items.

It is really crucial to be able to identify impacts as quickly as possible. Especially on related items, such as tests and associated functions. It is also very important to be able to propagate this impact.

Therefore, in order to optimize the management of changing requirements and their impacts, it is then important to add simples functionalities of synthesis of changes and tracking. Le goal is to trigger immediately a process of tracking "impacts" on items related to requirements.

I. To propagate the changes:
1) a dropdown list with check box that displays the list of responsible of requirements and the other persons involved in the validation of the requirement which changed (or deleted)
Objective: to inform at least one responsible. This information would be optional or mandatory depending on the choice of the project manager.

2) a dropdown list with check box that displays the list of tests related to the modified requirements
objective:
- To be able to select or Deselect the impacted tests. (==> traceability)

3) a dropdown list with check box that displays the list of responsible of tests affected.
objective:
- to be able to inform the responsible whom tests are impacted. At least one responsible should be informed or by default the test manager.

II. To follow the changes:
1) A report of the latest changes of requirements with a filter possibility depending on the project, product, version, business process, function, etc.

This report can be exported (PDF, XLS or Word / OpenOffice).
This point joined the Ticket # 1578 November 10, 2014 9:05.

(This is very useful for steering committee meetings)

Cordially