SOFTWARE REQUIREMENT SPECIFICATION (SRS) VERIFICATION
1) SRS should have the descriptive details on all the requirements – existing and new for the release.
- Should include details on functional, non functional, performance and design requirements
- Details of interfaces and GUI specifications should be present.
- For each functional requirement it should clearly specify:
- What all has to happen on doing a particular action on the system?
- Where all it should happen?
- When it has to happen?
- What all should not happen?
- If any of these is not specified , identify it and note for discussion.
2) Proper version history for the various features should be mentioned.
3) All the new features should be elaborately explained in the SRS.
4) It should mention the operating environment (Software and Hardware) recommended for proper functioning of the application.
- Should include OS, additional (3rd party) software or packages (with version) required for the application.
- Recommended values of system memory, RAM, processor speed, server/Desktop usability etc should be mentioned.
5) Any constraints on the design, H/w or S/W requirements, Standard compliance, etc should be mentioned in SRS
6) Any testability limitations should be clearly specified
7) All assumptions based on which the application is developed should be listed
8) Interface diagrams, Call flows or flow charts depicted should be cross checked with the understanding obtained.
9) SRS should have reference for all records like CDR parameter details, Configuration file parameters details and other operation steps.
10) Ensure that all the requirements are properly reviewed and signed off by respective stake holders/stake holder representatives.