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.
Dig Deeper on Topics Archive
Related Q&A from Mike Kelly
There are multiple ways performance testing can be handled on an Agile team. An expert describes the benefits of various approaches. Continue Reading
Every software tool is individually designed to meet various needs and requirements of projects, teams and project managers. Learn what tools experts... Continue Reading
Creating user acceptance tests out of basic software requirements documents can be a daunting task. Expert Mike Kelly points out logical approaches ... Continue Reading