Effectiveness of SRS in Testing

I am a tester and recently, I was asked to prepare SRS of a new feature which was getting introduced in the product. While working on the preparation of the SRS document, I realized that it’s very difficult for me. But slowly I understood that I should communicate frequently with the client and ensure that everything regarding the project was clearly understood by me.
An SRS is a very important document for the implementation the testing of project. A good SRS can usually be prepared by an experienced person. While creating an SRS document the communication with the Business team and the developers is extremely important as they are the only people who can tell you exactly about the project and what the requirements are.
In case of testing, if tester has a good SRS with him then he can do testing effectively. A Tester should know what, is the exact functionality of the application and what the major points he has to keep in mind while testing so that project doesn’t get any issue after launch in market. All flows are also clearly mentioned in the SRS. If tester has SRS with him while testing, he don’t get any problem or issue and there is less need to communicate with the development or business team while testing.
We may also face some problem while creation of SRS. It may be possible that 1st time all the requirements are not clear to you. It may be possible that in every meeting some requirements may change and you have to make changes in SRS corresponding to that change, change may be minor or major. The documents which are provided by either development team or the business team also help in creating a more comprehensive SRS.
After the 1st phase completion of SRS you should send it to the business team which is working on that project. Business team reviews the SRS and if they want any change in it, they list it out and the changes should be incorporated by the author. If they find complete requirements and other information regarding project in SRS they approve the SRS. After approval it’s not easy to make change in SRS and not advisable also. If in future you want to make some changes in the requirements of flow of the project, 1stly you have to take approval from senior manager of that project and after the approval from him the changes can make to the SRS, if he rejects those changes then SRS cannot be updated.
While working on SRS, we have to keep some points in mind for making it effective.
These points are as follows:
• You should know purpose and scope of project.
• You should have all the requirements for project.
• You should know the flow of application.
• You should know all the people teams involved in the project.
• Talk, talk and talk it all out. Don’t assume things on your own.
• Proof read the SRS before mailing it for approval.
• Delicately maintain the various iterations which a SRS goes through, so that you don’t miss out any changes.
• Remember, it’s not the creativity which people look for in a SRS, it’s how logically you have summarized all the technical flows in the application.
CresTech noida - Leading outsourced testingCompany provide software performance testing in Delhi, software performance testing in NCR, software testing companies in NCR. To know more visit any of the links above.