Please login or join to subscribe to this thread
List above are not techniques to validate requirements. There is a lot of sources about the topic outside there. The important thing to understand is: 1-Verification and Validation are components of Project Quality knowledge area. 2-Validation is done over deliverables. In this case, the requirements especification or any other similar thing.
I'm with Sergio on this one. Are you interested in QA techniques used for requirements?
There was no option to edit/delete the question. I realized after posting.
Let me rephrase my question –
During requirements gathering what other techniques one should follow to validate requirements are understood and captured.
Typically, it includes -
2. Making requirements traceable
3. Generating requirements package
4. Communicate the requirements
Please share thoughts / add to the list.
Please login or join to reply