<PROJECT NAME>

System Requirement Specification

Version <version No>

<Company Logo>
<Post appropriate organization logo from given below. In case of internal project
use both the logos>
System Requirements Specification<client >
Project Name <Name of the Project>
Document Name System Requirements
Specification

Author Reviewer Approver

_______________________ _____________________ _________________

_

Document Version History

Version number Effective Date Nature of Modification

Document Distribution
<Specific the names of individual from customer side as well as from our IT
Company’s side who will be receiving this document. Also specify their role as
PM, VH, TL etc>

This document will be directly distributed to the following individuals.

Sr.No Name of the Role

individual
<Client Name>
1
2
IT Company
1
2

Master file are stored electronically and are available to all associates
Printed copies of the master files are for reference only
 System Requirement Specification<Client Logo>

Table of Contents

1. Introduction..............................................................3
1.1 Purpose......................................................4

1.2 Scope.........................................................4

1.3 Definitions, acronyms and abbreviations..4

1.4 References...................................................4

1.5 Document Structure....................................4

2. System requirements..................................................4
2.1 System overview..........................................4

2.2 Assumptions and dependencies .................4

3. Functional Requirements............................................5
3.1 Requirements...1..........................................5

3.2 Requirements ...N.........................................6

4. External Requirements...............................................6
4.1 User Interfaces.............................................6

4.2 Hardware Interfaces....................................6

4.3 Software Interfaces......................................6

4.4 Communications Interfaces.........................6

5. Non-Functional Requirements.........................................7
 5.1 Performance requirements.................................7

5.2 Safety and security requirements.......................7

5.3 Usability requirements.........................................7

5.4 Scalability & Maintainability requirements ........7

5.5 Packaging requirements.......................................7

5.6 Compatibility Requirements.................................8

6 Acceptance Criteria............................................................8

7 Post Implementation..........................................................8

8 Annexure(s)........................................................................8
1. INTRODUCTION

1.1 Purpose
<in this subsection, specify the purpose of the document and the intended
audience>

1.2 SCOPE
<In this subsection, describe the domain to be covered and brief description of
the domain. Also specify exclusions, if any>

1.3 DEFINITIONS, ACRONYMS AND ABBRECIATIONS

<in this subsection, provide all the terms used in this document. Also list in the same subsection
acronyms and abbreviations required to properly interpreting the document>

Abbreviation Description

1.4 REFERENCES

Sr.no Document Document Version Author Released

title No date
1
2
3
4

1.5 DOCUMENT STRUCTURE

<in this subsection, describe the contents of the rest of the document and explain
how the document is organized.>

2. System Requirements

2.1 System overview

<In this subsection describe the overview of the system. Following points many be
considered-

. Product perspective

. System goals & Objectives

. User Classes and characteristic

. Design and Implementation Constraints

. Operating Environment

. Others, if any>

2.2 Assumptions and Dependencies

<Specify Assumptions and / or dependencies, if any, related to the system under
development. Assumptions could include third-party or commercial components
that you plan to use, issues around the development, design, testing, 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.3 EXCLUSIONS
<Write system functions which is not considered for current system/software
development>

3. FUNCTIONAL REQUIREMENTS
<In this section, describe all the functional requirements of the system. High-level
functional requirements will be further broken up into lower level requirements.
This vertical traceability of requirements should be clearly visible in this section.
For each lowest level requirement, detailed description is to be given. For each
lowest level requirement the dependences between the requirements need to be
recorded. Following is the suggestive list of points to be considered for
description. Alternatively, one can write functional requirements in descriptive
and easy to understand way which should be covering most of the points form the
following given guideline>

3.1 Requirements....1

. Requirements ID :<>

. Reference: Provide reference of customer requirements :<>

. Requirements description: short description of the requirement

. Uses-Case id (as applicable) :<>

. Prerequisites:

. Reason/Justification for the requirement :<>

. Feasibility of requirements:

. Requirements validation: In this subsection, explain how the

requirement has been validated with client. If there are any supportive Document,
give the hyperlink of the document.

. Business rule(s) and Exception:

 . Data required:

.Output / reports: Items generated because of the execution of this

function

. Interface requirements: Requirements with respect to

. User

. Hardware

.Software

. Communications (inter functional)

. Design/Operational constraints: like speed, response time etc

. Risk: Identify risk associated with implementation of this functionality

. Dependencies: Dependency on system, user for executing this

functionality

. Non-Functional Requirement: Reference of associated Non-functional

requirements.

.Others >

3.2 REQUIREMENTS...N
<Repeat the heading in section 3.1 for each individual requirement>

4. EXTERNAL INTERFACE REQUIREMENTS

<this paragraph shall identify the requirements external interface (that is,
relationships with other entities that involve sharing, providing or exchanging
date). The identification shall state which entities have fixed interface
characteristics (and which are being developed or modified (thus having interface
requirements imposed on them). One or more interface diagrams shall be
provided to depict the interfaces >

4.1 USER INTERFACES

<Describe the logical characteristics of each interface between the software
product and the users. This may include sample screen images, any GUI standards
or product family style guide that are to be followed, screen layout constraints,
standard buttons and function (e.g., help) that will appear on every screen,
keyboard shortcuts, error message display standards, and so on. Define the
software components for which a user interface is needed. Details of the user
interface design should be documented in a separated user interface specification.
>

4.2 HARDWARE INTERFACES

<Describe the logical and physical characteristics of each interface between the
software product and the hardware component of the system. This many include
the support device type, the nature of the data and control interactions between
the software and the hardware, and the communication protocols to be used. >

4.3 SOFTWARE INTERFACES

< Describe the connections between this product and other specific software
components. (Name and version), including databases, operating system, tools,
libraries and integrated commercial components. Identify the data items or
messages coming into the system and going out and describe the purpose of each.
Describe the services needed and the nature of communications. Refer to
documents that describe detailed application programming interface protocols.
Identify data that will be shared across software components. If the data sharing
mechanism must be implemented in a specific way (for example. use of a global
data area in multitasking operating system), specify this as an implementation
constraint. >
4.4 COMMUNICATIONS INTERFACES
< describe the requirement associated with any communications functions
required by this product, including e-mail, web browser, network server
communications protocols, electronic forms, and so on. Define any pertinent
message formatting identify any communication standard that will be used. Sucsh
as FTP OR HTTP. Specify any communication security or encryption issues, data
transfer rates, and synchronization mechanisms. >

5 NON- FUNCTIONAL REQUIREMENTS

5.1 Performance Requirements

<Requirements to address the response time of the system. Following can
be considered in detail:

. Size of Memory

. Throughput

. Transaction rate

. Load capacity

. Number of terminals

. Number of concurrent users

. Size of database

. Memory per user >

5.2 SAFETY AND SECURITY REQUIREMENTS

< This paragraph shall specify the requirements, if any concerned with
preventing or minimizing unintended hazards to personnel, property, and the
physical environmental. This shall also specify the requirements, if any concerned
with maintaining security and privacy. These requirements shall include, as
applicable. The security/privacy environment and degree of security or privacy in
which the system must operate. >

5.3 USABILITY REQUIREMENTS

<Requirements that address the ability of the system to be easily learned
and used >

5.4 SCALABILITY & MAINTAINABILITY REQUIREMENTS

<Specify the requirements that will address ability of system to easily
correct the problem in cost effective way with less impaction on other part of the
system. Scalability identifies the requirements related to expanding system in
terms of volume, users etc. >

5.5 PACKAGING REQUREMENTS

<This section shall specify the requirements, if any, for packaging, labeling,
and handling the system for delivery. This would also include requirements related
to deployment on server>

5.6 COMPATIBILITY REQUIREMETS

< Backward or forward compatibility requirements>

6. ACCEPTANCE CRITERIA
<Write down the agreed upon acceptance criteria for the project/ deliverables.
Provide references and details of the pertinent documents (Proposal/ contract/
minutes of meeting/ Tele-con/etc)>

7. POST IMPLEMENTATION
.Scope of warranty/support/maintenance

.Type (Resolution of Defects /Issues/Enhancements.etc)

 . Level

.Period of warranty/Support/Maintenance

8 ANNEXURE(S)

<If any>