-
Notifications
You must be signed in to change notification settings - Fork 8
5 REQ analyze
The collected trace, review, test, 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.
not yet implemented in mantra's context refers to requirements that are neither traced nor manually verified.
It must be ensured that the collected data is valid, because reliable data is required for any useful analysis.
If a trace, test, coverage, or review contains invalid data, the data must be stored in mantra separately to valid content, but the data should still be available for inspection. The data must be stored separately, because it must not be considered for analysis of the state of the project.
A trace is valid if it points to an existing requirement.
A coverage entry is valid if it points to either an existing test run or test case.
Deprecated requirements must not be used in a project. This means that deprecated requirements must not be referenced by any trace or review.
-
Parents: [
analyze.validate,review.verify_req]
A manually verified requirement is valid if it points to an existing requirement.
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.