It is said that for better Quality qa's / software testers must be involved in the complete life cycle of the product . but how can this be acheived practically . How exactly can a qa contribute towards requirements .
Do you have a formal Requirement Management process ? If you have, QA shloud check if this process is followed:
-Are all the requirements gathered and systemized: type, attributes,... ?
-Wich is the status of each requirement ?
- All the changes to any requirements are documented ?
Basicalyy, QA should assure that the process is followed correctly.
If you don't have a formal process in place I can tell you what our QA does ... trying to define and put in place such a process (but not alone)
If you need a reason to be happy - FIND IT, don't wait it !
One important phase where Software Testers can be included is the finalization of specifications (e.g. external specifications). It is because during testing there are many points which are discovered which fall at specification. When this kind of situation arises, developers generally says "It is not a bug, it is specification". But if QA people also go through the specification during their finalization, chances of these kind of bugs is very less. Due to this lots of time, effort and money is saved and it improves quality of the product too.
Second is messages displayed in the software. Many a times, messages which are grammetically wrong or which are not according to context are displayed, which is very bad for the software. QA people should also review these messages. Similar areas are manual and online help.
Let me tell you all,
Thats testers should be included from the very begining of the phase like Reviewing of SRS , Bugs like GUI Issues and messages and even functionality will be caught and SRS can go in detail, which will help testers also to know the better product and test effectively.