...
A known challenge in modeling with requirement references (see section Measuring Model Complexity) the granularity of requirements. In particular when coming from different source they scope and clarity of requirements may vastly differ. Some authors write six requirements in one. Some requirements are not testable. Some are not clearly defined. Finally, testers generally do not have the right to modify requirements in ALM systems.
...
Requirements can also be understood and used “way points” or “[pure] testing requirements” in model coverage. They can be useful to track specific data coverage or to even troubleshoot coverage issues. For example, adding an ad-hoc requirement with a skip action pre-condition “Username is Stephan and password is 123” after a fill form action, makes it easy to pinpoint via the Test Targets view in the Conformiq Test Design perspective all test(s) where this user and password is used at this point of the control flow.
Recommendation: Use ad-hoc requirement actions to specify and track pure testing requirements, or to trouble shoot test coverage. Use requirement categories to separate them from other requirements. |