Performance specification documents for a software project

User context:Who is the software for? How many copies are needed? How much will each copy cost?

Functionality. What is the software supposed to do?

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

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

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

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.?

Feature list. List of the features that the software has starting with the bare minimum set working through a v1.0 list onward to a it would be great list and onward to an all sing and dancing list.

Much borrowed from: