Software Requirements SRS Documents – Goals and Characteristics

The Software Requirements SRS Documents 

The Software Requirements SRS Documents are the documents or set of documentation that describe the features and behavior of a system or software application.

  • It is a description of a software system to be developed.
  • Traces out functional and non-functional requirements.
  • Includes a set of use cases that describe user interactions that the software must provide.
  • Establishes the basis for an agreement between customers and suppliers.
  • Permits a rigorous assessment of requirements before design can begin and reduces later redesign.
  • Provides a realistic basis for estimating product costs, risks, and schedules.
  • Used appropriately, software requirements specifications can help prevent software project failure.
  • Enlists enough and necessary requirements that are required for the project development.


Goals of SRS Document:

A well designed, well written SRS document accomplishes the following four major goals:

  • Feedback to customers
  • Problem decomposition
  • Input to design specification
  • Production validation check


Characteristics of SRS Document:

The main characteristics or features of SRS documents are written as:

  1. Accuracy: This is the first and foremost requirement. The development team will get nowhere if the SRS which will be the basis of the process of software development, is not accurate.
  2. Clarity: SRS should be clearly stating what the user wants in the software.
  3. Completeness: The software requirement specification should not be missing any of the requirements stated in the business requirements documentation that the user specified.
  4. Consistency: The document should be consistent from beginning till the end. It helps the readers understand the requirements well.
  5. Prioritization of Requirements:Software Requirement Specification should not simply be a wish list. The requirements should follow the order of priority and preference.
  6. Verifiability: At the end of the project, the user should be able to verify that all that all the agreed deliverables have in fact been produced and meet the project management requirements specified.
  7. Modifiability: The SRS should be written in such a way that it can be modified when the development team and user feel the need.
  8. Traceability: Each requirement stated in the SRS should be uniquely associated to a source such as a use case or interaction document.


503 total views, 2 views today

A Soon-to-be Computer Engineer by profession, he has profound devotion to add Data Scientist as a prefix to his name. He’s been to the nooks of the web (at least of the surface web) and planning to add some real figures in his pocket!

Leave a Reply