It should also provide a realistic basis for estimating product costs, risks, and schedules.
This is achieved through detailed and continuous communications with the project team and customer throughout the software development process.
The SRS may be one of a contract's deliverable data item descriptions[4] or have other forms of organizationally-mandated content.
Typically a SRS is written by a technical writer, a systems architect, or a software programmer.
An example organization of an SRS is as follows:[11] It would be recommended to address also verification approaches planned to qualify the software against the requirements, for example with a specific section with a structure that mirrors the section on specific requirements.
[12] Examples of requirements smells are subjective language, ambiguous adverbs and adjectives, superlatives and negative statements.