Print Page | Close Window

Requirements Traceability Printed From: One Stop Testing Category: Quality Assurance @ OneStopTesting Forum Name: Requirements and Design Documents @ OneStopTesting Forum Discription: All those Artifacts generated in Requirement and Design Phases like Use Cases, SRS, Functional & Non-Functional Specefications, Check Lists, Design Documentations etc. URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1281 Printed Date: 24Nov2024 at 7:40pm Topic: Requirements Traceability Posted By: Nisha321 Subject: Requirements Traceability Date Posted: 07May2007 at 3:54am If you are not getting the requirements in a form you need and assuming you have the time, I recommend taking knowledge of the system that you have and writing your own "test" requirements. These would be things you would initially use internally for traceability. This has worked for me in the past. Best outcome was that as word of these requirements got out to other groups in the company, they began to see the value of them (it made our testing more efficient) and they wanted to see what it could do for them, resulting in requirements adoption.

Print Page | Close Window