Scribd
Upload
33 views2 pages

Software Requirements Specification - Standard Format

A software requirements specification document provides a complete description of the required behavior and interactions of a software system. It includes functional requirements that define specific behaviors as well as non-functional requirements that impose constraints on aspects like performance, quality, and design. The SRS is developed by communicating with stakeholders to understand necessary requirements, and generally includes sections that introduce the system, describe its overall functions and interfaces, and specify requirements in detail.

Uploaded by

mueed_19915795
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
33 views2 pages

Software Requirements Specification - Standard Format

A software requirements specification document provides a complete description of the required behavior and interactions of a software system. It includes functional requirements that define specific behaviors as well as non-functional requirements that impose constraints on aspects like performance, quality, and design. The SRS is developed by communicating with stakeholders to understand necessary requirements, and generally includes sections that introduce the system, describe its overall functions and interfaces, and specify requirements in detail.

Uploaded by

mueed_19915795
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Software Requirements Specification A software requirements specification (SRS), a requirements specification for a software system, is a complete description of the

behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). The software requirements specification document enlists all necessary requirements for project development.[1] To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with project team and the customer. A general organization of an SRS is as follows [2][3]

Introduction o Purpose o Definitions o System overview o References Overall description o Product perspective System Interfaces User Interfaces Hardware interfaces Software interfaces Communication Interfaces Memory Constraints Operations Site Adaptation Requirements o Product functions o User characteristics o Constraints, assumptions and dependencies Specific requirements o External interface requirements o Functional requirements o Performance requirements o Design constraints Standards Compliance o Logical database requirement

Software System attributes Reliability Availability Security Maintainability Portability Other requirements

You might also like