Section 4 of IEEE 830 (how to produce a good SRS)
Nature (goals) of SRS
Functionality, interfaces, performance, qualities, design constraints
Environment of the SRS
Where does it fit in the overall project hierarchy
Characteristics of a good SRS
Generalization of the characteristics of good requirements to the document
Evolution of the SRS
Implies a change management process
Prototyping
Helps elicit software requirements and reach closure on the SRS
Including design and project requirements in the SRS
Focus on external behavior and the product, not the design and the production process (describe in a separate document)