Maintaining up-to-date state
Requirements constantly change, therefore your team needs to maintain test documentation in up-to-date state to remove false errors caused by product verification using the obsolete test documentation.
Devprom ALM significantly reduces workloads for documentation maintenance due to automation of change control process. Now it’s not a problem to maintain technical documentation for projects whose requirements change constantly. System stores relationships between project artifacts automatically, e.g., between requirements and technical documentation.
In processes with preliminary design
When business requirement or system requirement is changed, system marks its covering test scenarios as obsolete (not up-to-date). You have only to filter them in the list and proceed to editing.
System will display requirement modifications, and you have only to correct the corresponding sections of technical documentation.
In lightweight development processes
If a team works with the source requirements, they maintain test documentation in up-to-date state using a function tree (impact mapping, story mapping, or epics). User stories and test documentation are bound to functions or epics.
After the story is implemented, Devprom ALM automatically marks all test scenarios linked with function (or epic) of this story as obsolete. All you have to do is to open the registry of obsolete scenarios, make the required changes, and restore coverage.