Test cases from requirements specifications and use cases |
| > |
QUESTION:
Assuming both requirements specifications and use cases are available, which one would be more appropriate to use for creating test cases and, further, to be traced to from the test cases?
|
|
|
To continue reading for free, register below or login
To read more you must become a member of SearchSoftwareQuality.com
');
// -->

ANSWERED May 2008:
If I were on a project where both requirements specifications and use cases were created, I would expect that I would use both for creating test cases. Each provides a different view of what the application should be doing, how it's used, and what the intended product should look like. Both are critically important to my testing, and both would probably have equal weight in my testing process.
As for traceability, if that's a requirement, the best person to ask is the auditor who will be ensuring compliance. If you're working in an environment where traceability is important, then I would assume you would want to trace your test cases back to both sets of artifacts, but the best way to be sure is to ask.
|
|
|

|
|
 |

 |
 |
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
 |
 |
 |
|
 |
 |
 |
|
 |
|
 |