The SRS is used to identify risks, estimate cost and schedule, drive the design and implementation of the system, and to act as a contractual agreement to support eventual customer acceptance of the product. The SRS is created as a hierarchical document including an introduction, overall description of the product describing constraints, assumptions, and dependencies etc, and a section in which specific requirements are described. Typically requirements are organized by type such as external interfaces, functional requirements, performance requirements, design constraints, and other quality requirements [9]. Many organizations adopt standard templates for organizing the SRS and structuring requirements attributes. These templates are useful because they clearly define the sections of the SRS and the structure of each individual requirement.