I always took part in Functional Spec Reviews , finding defects init , tracing between rs and fs.is there any other thing i need to do as QA.do we have any system where QA participate in FS desiging.?or we just do reviews and informes if there are some issue.
This particular testing is called Testing the Design. Where we as QA find the design flaws and documentation issues that might come up while testing and then extra time will be spent or the testers will be in ambiguity, and might make their own decisions, which can be wrong or right.
In some companies, new applications are designed through use of JAD sessions - Joint Application Design sessions. These sessions bring in users, BAs, developers, QA, and representatives from any other area that might be impacted by the application, and the group jointly designs the application. This gives QA the opportunity to bring up issues or testing considerations before the specifications are even written.
Unlike Sumit, we do not refer to functional spec reviews as "Testing the Design". It's a form of static testing, similar to the desk checking developers do of code, and we do inform the author of the spec and the PM of any potential issues we find. We only follow such a rigorous process for large projects. We do similar work for smaller projects, but the process is less formal and may take place during a just-in-time analysis review.