A SRS allows developers to be clear on the goals of the software and on what they should focus on. Furthermore, it allows them to:
– Save time on communication
– Minimize development efforts
– Gives the customer feedback
– Eliminate task duplication
– Facilitate the transfer to new users or to new machines
– Breaks problems down into parts
– Serves as the main document to verify the validation and testing processes
– Referring to past SRS documents helps identify deficiencies and process flaws.