SRS Template [2011]

[Project Name]

SOFTWARE REQUIREMENTS SPECIFICATION

Project Name

Author
Ritesh Verma

Date

Version
Initial Version

Approver
Sanjeet Maity Shailendra Singh

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

Revision History
Name
Ritesh Kumar Verma

Date

Description
Initial Version

Version
1.0

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

Table of Contents
Contents
1. 1.1. 1.2. 1.3. 1.4. 1.5. 2. 2.1. 2.1.1. 2.1.2. 2.1.3. 2.1.4. 2.1.5. 2.1.6. 2.1.7. 2.2. 2.3. 2.4. 2.5. 2.6. 2.7. 2.8. 3. 3.1. 3.2. 4. Introduction ............................................................................................................................. 5 Purpose ................................................................................................................................ 5 Scope .................................................................................................................................... 5 Definition, acronyms and abbreviation ............................................................................... 5 References ........................................................................................................................... 5 Document Convention ......................................................................................................... 5 Overall Description .................................................................................................................. 6 Product Perspective ............................................................................................................. 6 System Interfaces ............................................................................................................. 6 User Interface ................................................................................................................... 6 Hardware Interfaces......................................................................................................... 7 Software Interfaces .......................................................................................................... 7 Communication Interfaces ............................................................................................... 7 Memory Constraints......................................................................................................... 7 Operations (Optional) ...................................................................................................... 8 Product feature .................................................................................................................... 8 User Class and Characteristics ............................................................................................. 8 Operating Environment ....................................................................................................... 8 Design and Implementation Constraints ............................................................................. 8 User Documentation ............................................................................................................ 9 Assumption and Dependencies ........................................................................................... 9 Apportioning of the requirements....................................................................................... 9 Specific Requirements ............................................................................................................. 9 System Requirement1 (Mention the requirement name) .................................................. 9 System Requirement 2 ( and so on) ................................................................................... 10 Non-Functional Requirements .............................................................................................. 11 3

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

4.1. 4.2. 4.3. 4.4. 4.5. 5.

Logical Database Requirement .......................................................................................... 11 Performance Requirement ................................................................................................ 11 Safety Requirements.......................................................................................................... 11 Security Requirements ....................................................................................................... 11 Software Quality Attributes ............................................................................................... 12 Other Requirements .............................................................................................................. 12

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

1. Introduction 1.1. Purpose

Identify the product whose software requirements are specified in this document, including the revision or release number. Describe the scope of the product that is covered by this SRS, particularly if this SRS describes only part of the system or a single subsystem This subsection should delineate the purpose of the SRS, Specify the intended audience of the SRS.

1.2.

Scope

Provide a short description of the software being specified and its purpose, including relevant benefits, objectives, and goals. Relate the software to corporate goals or business strategies. If a separate vision and scope document is available, refer to it rather than duplicating its content here. An SRS that specifies the next release of an evolving product should contains its own scope statement as a subset of the long tem strategic product vision.

1.3.

Definition, acronyms and abbreviation

This subsection should provide the definition of all terms, acronyms and abbreviations required to properly interpret the SRS. This information may be provided by reference to one or more appendixes in the SRS of reference to other documents.

1.4.

References

This subsection should provide a complete list of all documents referenced elsewhere in the SRS, Identify each document by title, report number (if applicable), date and publication organization, Specify the source from which the reference cab be obtained.

1.5.

Document Convention

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

Describe any standards or typographical convention that were followed when writing this SRS, such as fonts or highlighting that have special significance. For example state whether priorities for higher level requirements are assumed to be inherited by detailed requirements, or whether every requirement statement is to have its own priority.

2. Overall Description
This section of the SRS should describe the general factors that affect the product and its requirements. This section doesnt state specific requirements. Instead, it provides a background for those requirements, which are detailed in the Section 3.0 of the SRS and makes them easier to understand.

2.1.

Product Perspective

This subsection of the SRS should put the product into perspective with other related products. If the product is independent and totally self contained, it should be so stated here. If the SRS defines a product that is component of the larger system, as frequently occurs, then this subsection should relate the requirement of that larger system to functionality of the software and should identify interfaces between that system and software. A block diagram showing the major components of the larger system, interconnections and external interfaces can be helpful.

2.1.1. System Interfaces

This should list each system interface and identify the functionality of the software to accomplish the system requirement and the interface description to match the system.

2.1.2. User Interface

This should specify the logical characteristics of each interface between the software product and its users. This includes those configuration characteristics (e.g., required screen formats, page or window layouts, content of any reports or menus, or availability of programmable function keys) necessary to accomplish the software requirements. This may also require All the aspects of optimizing the interface with the person who must use the system. This may simply Comprise a list of dos and donts on how the system will appear to the user. One example may be a requirement for the option of long or short error messages. Like all others, these requirements should be verifiable, e.g., a clerk typist grade 4 can do function X in Z min after 1

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

h of training rather than a typist can do function X. (This may also be specified in the Software System Attributes under a section titled Ease of Use.)

2.1.3. Hardware Interfaces

This should specify the logical characteristics of each interface between the software product and the hardware components of the system. This includes configuration characteristics (number of ports, instruction sets, etc.). It also covers such matters as what devices are to be supported, how they are to be supported, and protocols. For example, terminal support may specify full-screen support as opposed to line-by-line support.

2.1.4. Software Interfaces

This should specify the use of other required software products (e.g., a data management system, an operating system, or a mathematical package), and interfaces with other application systems (e.g., the linkage between an accounts receivable system and a general ledger system). For each required software product, the following should be provided:
Name Mnemonic Specification number Version Number Source

For each interface, the following should be provided Discussion of the purpose of the interfacing software as related to this software product. Definition of the interface in terms of message content and format. It is not necessary to detail any well-documented interface, but a reference to the document defining the interface is required.

2.1.5. Communication Interfaces

This should specify the various interfaces to communications such as local network protocols, etc.

2.1.6. Memory Constraints

This should specify any application characteristics and limits on primary and secondary memory.

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

2.1.7. Operations (Optional)

This should specify the normal and special operations by the user such as modes of operation, period of interactive operations, period of unattended operations, data processing and support functions, backup and recovery operations

2.2.

Product feature

Summarize the major feature the product contains or the significant functions that it performs or let the user perform. Details will be provided in the Section 3, so only a high level summary is needed here. Organize the functions to make them understandable to any reader of the SRS. A picture of the major groups of related requirements and how they relate, such as top level data flow diagram or class diagram, if often effective.

2.3.

User Class and Characteristics

Identify the various user classes that you anticipate will use this product. User classes may be differentiated based on frequency of use, subset of product functions used, technical expertise, security or privilege levels, educational level or experience. Describe the pertinent characteristics of each user class. Certain requirements may pertain to certain user class. Distinguish the favored user classes from those who are less important to satisfy.

2.4.

Operating Environment

Describe the environment in which the software will operate, including the hardware platform, operating system and versions, and any other software components or applications with which it must peacefully co-exist.

2.5.

Design and Implementation Constraints

Describe any items or issues that will limit the options available to the developers. These might include corporate or regulatory policies, hardware limitations (timing requirements, memory requirements); interfaces to other applications; specific technologies, tools, and databases to 8

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

be used; parallel operations; language requirements; communications protocols; security considerations; design conventions or programming standards (for example, if the customers organization will be responsible for maintaining the delivered software

2.6.

User Documentation

List the user documentation components (such as user manuals, on-line help, and tutorials) that will be delivered along with the software. Identify any known user documentation delivery formats or standards

2.7.

Assumption and Dependencies

List any assumed factors (as opposed to known facts) that could affect the requirements stated in the SRS. These could include third-party or commercial components that you plan to use, issues around the development or operating environment, or constraints. The project could be affected if these assumptions are incorrect, are not shared, or change. Also identify any dependencies the project has on external factors, such as software components that you intend to reuse from another project, unless they are already documented elsewhere (for example, in the vision and scope document or the project plan).

2.8.

Apportioning of the requirements

This subsection of the SRS should identify the requirements that may be delayed until future versions of the system/product.

3. Specific Requirements
This template illustrates organizing the functional requirements for the product by system features, the major services provided by the product. You may prefer to organize this section by use case, mode of operation, user class, object class, functional hierarchy, or combinations of these, whatever makes the most logical sense for your product

3.1.

System Requirement1 (Mention the requirement name)

Description Describe the requirement name

System Requirement details Name of the requirement

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

Stimulus/Response Sequence

Functional Requirement

Qualification provision Constraints Related Requirement Standardization Priority

List the sequence of the user action and system responses that stimulate the behavior defined for this feature.This will define the use cases for the requirement. Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use TBD as a placeholder to indicate when necessary information is not yet available Comprehensively describe the methods to evaluate the function so that test for the requirement and test cases can be extracted. Describe the operational constraints in the situation where the conditions of functions are not satisfied. Dependency on the other requirement Yes/No depending on the situation whether some standards are followed or not Normal / high/low

3.2.

System Requirement 2 ( and so on)

Description Describe the requirement name List the sequence of the user action and system responses that stimulate the behavior defined for this feature.This will define the use cases for the requirement. Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user to carry out the services provided by the feature, or to execute the use case. Include how the product should respond to anticipated error conditions or invalid inputs. Requirements should be concise, complete, unambiguous, verifiable, and necessary. Use TBD as a placeholder to indicate when necessary information is not yet available Comprehensively describe the methods to evaluate the function so that test for the requirement and test cases can be extracted. Describe the operational constraints in the situation where the conditions of functions are not satisfied. Dependency on the other requirement Yes/No depending on the situation whether some standards are followed or not Normal / high/low

System Requirement details Name of the requirement Stimulus/Response Sequence

Functional Requirement

Qualification provision Constraints Related Requirement Standardization Priority

10

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

4. Non-Functional Requirements 4.1. Logical Database Requirement

This should specify the logical requirement for any information that is to be placed in a database. This may include type of information used by various functions, frequency of use, accessing capabilities, data entities and their relationship, Integrity constraints and data retention requirements.

4.2.

Performance Requirement

If there are performance requirements for the product under various circumstances, state them here and explain their rationale, to help the developers understand the intent and make suitable design choices. Specify the timing relationships for real time systems. Make such requirements as specific as possible. You may need to state performance requirements for individual functional requirements or features

4.3.

Safety Requirements

Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the products design or use. Define any safety certifications that must be satisfied

4.4.

Security Requirements

Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied

11

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

5. Software Quality Attributes

Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning

6. Design Constarints.
This should specify the design constraints that can be imposed by other standards, hardware limitations etc.

7. Other Requirements
Define any other requirements not covered elsewhere in the SRS. This might include internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project

12

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL

SRS Template [2011]

[Project Name]

Appendix A: Analysis Models

Optionally, include any pertinent analysis models, such as data flow diagrams, class diagrams, state-transition diagrams, or entity-relationship diagrams

Appendix B: Issue List

This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like

13

Copyright @ Satyam Software Solutions Pvt Ltd

CONFIDENTIAL