Suppose after testing is over, dev team came to know that SRS is captured wrong or somthing missed out..We come to a conclusion that this product is non conformed as per clients req. so we have to go back and update and capture SRS and Design and do coding again.. For this process of work.. we need process..
Any one if u have such process - can u please give me some inputs.
I go for the best bcoz. i am the best.
A number of issues come to mind after reading your post. The main thing is that the development process your company uses is broke.
It seems that your company is using the classic waterfall model of software development which puts testing at the end of the process. If you wait til the end to determine that the initial requirements were either wrong, misunderstood, or missed, you have just wasted ALL the money that was invested in the product. One possible solution is to use a V-Model which adds Software Quality Assurance and Software Testing at all phases of the development cycle.
A number of things can be done to fix this. Bear in mind that this list is not all inclusive and will depend on the environment.
1) Users need to be involved throughout the entire lifecycle of the project. This will help ensure that the final baselined requirements are correct, understood, implemented, and tested.
2. Software Quality Assurance, Software Configuration Management, and Software Test personnel need to be involved throughout the entire lifecycle of the project, not just at the end.
3. Develop a methodology for requirements traceability. If you track the requirements through all phases of the project, you will ensure that they are included in the design, code, and test cases.
Hope this helps, or at least gives you a starting point,
Carl E. Cornett, CSTE
"Knowledge is not power, it just means you have to do all the work if you don't share it."