Topic: Requirement phase testing

Message

What should testers do in the requirement phase?  

In
my current SV&V team, testers and team leads are responsible for
reviewing the requirement document. However, I found it rather
ineffective. First of all, there’s no deliverables from SV&V team
for requirement review. Therefore, there isn’t any time allocated for
the task. Most of the time, testers are so busy with other tasks
assigned, they only start to read the doc when they attend the
requirement review meeting. 

Also, since there’s no
deliverables required, there’s no guarantee that testers had actually
read and think about every requirement even if they are given time.
They could get away with few comments and don’t really have to read
through the whole document.

I’ve found following methods from two books:

1.
William E. Parry mentioned "Requirements’ testing is primarily
performed through the creation of test conditions and functional
checklists" in his CBOK. However, I’m not quite sure if any of those
can be done in the requirement phase. Does any one have examples of
creation of test conditions and functional checklists during
requirement phase? Are they effective? 
2. Elfriede Dustin
mentioned in "Effective Software Testing" the creation of a checklist
to verify following characteristics: Correctness, Completeness,
Consistency, Testability, Feasibility, Necessity, Prioritization,
Unambiguousness, and Traceability. This seems to be doable. However,
does this checklist method helpful in reality? Anyone has experience or
example of this? Could this be defined as a SV&V deliverable? 

Author	Message
Deep009 Newbie Joined: 30Apr2007 Online Status: Offline Posts: 1	Topic: Requirement phase testing Posted: 30Apr2007 at 3:28am
	What should testers do in the requirement phase? In my current SV&V team, testers and team leads are responsible for reviewing the requirement document. However, I found it rather ineffective. First of all, there’s no deliverables from SV&V team for requirement review. Therefore, there isn’t any time allocated for the task. Most of the time, testers are so busy with other tasks assigned, they only start to read the doc when they attend the requirement review meeting. Also, since there’s no deliverables required, there’s no guarantee that testers had actually read and think about every requirement even if they are given time. They could get away with few comments and don’t really have to read through the whole document. I’ve found following methods from two books: 1. William E. Parry mentioned "Requirements’ testing is primarily performed through the creation of test conditions and functional checklists" in his CBOK. However, I’m not quite sure if any of those can be done in the requirement phase. Does any one have examples of creation of test conditions and functional checklists during requirement phase? Are they effective? 2. Elfriede Dustin mentioned in "Effective Software Testing" the creation of a checklist to verify following characteristics: Correctness, Completeness, Consistency, Testability, Feasibility, Necessity, Prioritization, Unambiguousness, and Traceability. This seems to be doable. However, does this checklist method helpful in reality? Anyone has experience or example of this? Could this be defined as a SV&V deliverable? Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Quality Assurance @ OneStopTesting : Quality Methodologies / Streams @ OneStopTesting