-
Notifications
You must be signed in to change notification settings - Fork 0
5 REQ analyze
The collected traces and coverage data may be used to analyze various aspects of a project.
As a project manager, I want to be able to see a list of requirements that are not yet implemented, because this provides an overview of the project state.
It must be ensured that the collected trace and coverage data is valid, because reliable data is required for any useful analysis.
If a trace, coverage, or review contains invalid information, it must be stored in mantra separately to valid content, because the data must not be considered to detect the state of a requirement, but the data should still be available for inspection.
Required checks are added as sub-requirements to this requirement.
All traces point to existing requirements.
All coverage entries point to existing traces with matching requirement IDs.
Deprecated requirements must not be used in a project. This means that deprecated requirements must not be referenced by any traces, coverage, or reviews.
-
Parents:
analyze.validate,review.verify_req
All manually verified requirements point to existing requirements.
It should be possible to run custom queries against the collected trace and coverage data, because this allows to define what to analyze per project, without requiring to adapt mantra.
Please create an issue if you found any spelling mistakes.
You may also create an issue if you think the content of this wiki should be improved.
Note: This wiki is managed in its own repository. Any commits made using the edit button will be overwritten.
Note: Issues for the wiki are handled in the mantra repository, but pull requests for the wiki are handled in the mantra-wiki repository.
This wiki is MIT licensed, and works together with mantra.