A software requirements specification (SRS) is a description of the intended purpose and environment for a software which is under development.

This totally describes what the software will do and how it will function. An SRS minimizes the time and effort required by developers to achieve desired goals and also minimizes the development cost. A good SRS defines how an application will interact with system hardware, other programs and human users in a wide variety of real-world situations. Parameters such as operating speed, response time,availability, portability, maintainability, footprint, security and speed of recovery from adverse events are evaluated. Methods of defining an SRS are described by the IEEE (Institute of Electrical and Electronics Engineers) specification 830-1998.[1] http://searchsoftwarequality.techtarget.com/definition/software-requirements-specification Types of diagrams that are used in Software Requirements Specification (SRS) are: Dataflow diagram Use case diagram Sequence diagram Class diagram Activity diagram

Dataflow Diagram It is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design).[2] http://en.wikipedia.org/wiki/Dataflow_diagram

Use case Diagram It is the simplest representation of users interaction with system and specifications of a particular use case, it can be drawn in various types by the user which can interact with the system.

Sequence Diagram It is an interaction diagram that represents how processes will be operated with one another in an order. This are related with the use case diagrams logically of a system which is under development.

Class Diagram In Unified Modelling Language(UML), class diagram is a type of structure diagram that represents systems structure by showing the classes of a system, their operations and relationships among objects.

Activity Diagram Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams are intended to model both computational and organisational processes (i.e. workflows). Activity diagrams show the overall flow of control.

Entity Relation Diagram An entityrelationship model (ER model) is a data model for describing the data or information aspects of a business domain or its process requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database. The main components of ER models are entities (things) and the relationships that can exist among them

Advantages of SRS
SRS provides information regarding features that are required in the final system. Price of the project can be accurately judged. All the requirements from customer can be managed.

An example of a real-life scenario