This is the step 3 of the software development life cycle as shown in the picture below. At this level the documentation is design along with some prototypes and code samples.What should the SRS (Software Requirements Specification) address?

From the IEEE standard:

The basic issues that the SRS writer(s) shall address are the following:

a) Functionality. What is the software supposed to do?

b) External interfaces. How does the software interact with people, the system’s hardware, other hardware, and other software?

c) Performance. What is the speed, availability, response time, recovery time of various software functions, etc.?

d) Attributes. What are the portability, correctness, maintainability, security, etc. considerations?

e) Design constraints imposed on an implementation. Are there any required standards in effect, implementation language, policies for database integrity, resource limits, operating environment(s) etc.?


What are the characteristics of a great SRS?

Again from the IEEE standard:

An SRS should be

a) Correct

b) Unambiguous

c) Complete

d) Consistent

e) Ranked for importance and/or stability

f) Verifiable

g) Modifiable


software life cycle picture