The Software Requirements Specification (SRS) focuses on the collection and organization of all requirements
surrounding your project. It is useful for collecting your project software requirements in a formal, IEEE830-style document.
Since you might find yourself with several different tools for collecting these requirements, it is important to
realize that the collection of requirements may be found in several different artifacts and tools. For this reason, we
will collect the requirements for our SRS in a package which may be a single document or a collection of various
artifacts that describe the requirements.
(See the More Information section for additional guidelines).
The SRS package controls the evolution of the system throughout the development phase of the project, as new features
are added or modified to the Vision document, they are elaborated within the SRS Package.
The following people use the Software Requirements Specification:
Designers use the SRS Package as a reference when defining responsibilities, operations, and attributes on classes,
and when adjusting classes to the implementation environment.
Implementers refer to the SRS Package for input when implementing classes.
The Project Manager refers to the SRS Package for input when planning iterations.
Testers use the SRS Package as an input to considering what tests will be required.