University of Sahiwal

<Project Title>
Software Requirements Specification
Version <1.0>
By
Student Name and Roll No

[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in
square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the
author and should be deleted before publishing the document. A paragraph entered following this style
will automatically be set to normal (style=Body Text).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select
File>Properties and replace the Title, Subject and Company fields with the appropriate information for
this document. After closing the dialog, automatic fields may be updated throughout the document by
selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must
be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and
the field contents. See Word help for more information on working with fields.]
<Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>

Confidential <Company Name>, 12/8/2024 Page 2

 <Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

Table of Contents
Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms, and Abbreviations 3
1.4 References 3
1.5 Overview 4

2. Overall Description 4
2.1 Product Perspective 4
2.2 Product Functions 4
2.3 User Characteristics 4
2.4 Assumptions and Dependencies 4

3. Specific Requirements 4
3.1 Functional Requirements 4
3.2 Non-Functional Requirements 4
3.3 Design Constraints 4
3.4 Interfaces 4
3.4.1 User Interfaces 5
3.4.2 Hardware Interfaces 5
3.4.3 Software Interfaces 5
3.4.4 Communications Interfaces 5
3.5 Legal, Copyright, and Other Notices 5
3.6 Applicable Standards 5

4. Supporting Information 5

5. References 5

Confidential <Company Name>, 12/8/2024 Page 3

 <Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

Software Requirements Specification

1. Introduction

Introduction about Project

1.1 Purpose
The purpose this documents

1.2 Scope
The scope of Project

1.3 Definitions, Acronyms, and Abbreviations

SRS – Software Requirements Specification
End users – The people who will be actually using the systems.
SERVER: Refers to the Host machine
CLIENT: Refers to the user of Solution

1.4 References
An Integrated Approach to Software Engineering Approach - Pankaj Jalote Software
Engineering a Practitioner’s Approach - Roger S Pressman

Software Requirement Specifications from Internet.

IEEE (Institute of Electrical and Electronics Engineers) Guide to Software Requirements

Specifications.

1.5 Overview
The SRS is organized into two main sections. The first is The Overall Description and the second

Confidential <Company Name>, 12/8/2024 Page 4

 <Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

is the Specific Requirements.

2. Overall Description
This section will give an overview of the whole system.

2.1 Product Perspective

Overall Perspective of Product

2.2 Product Functions

Overall Product Functions

2.3 User Characteristics

User Constrain

2.4 Assumptions and Dependencies

All Assumptions and dependencies

3. Specific Requirements
Requirement specification

3.1 Functional Requirements

Functional requirement of System
3.2 Non-Functional Requirements
All nonfunctional requirements

3.3 Design Constraints

Design constraints
3.4 Interfaces
[This section defines the interfaces that must be supported by the application. It should contain adequate
specificity, protocols, ports and logical addresses, and the like, so that the software can be developed and
verified against the interface requirements.]

3.4.1 User Interfaces

[Describe the user interfaces that are to be implemented by the software.]
3.4.2 Hardware Interfaces
[This section defines any hardware interfaces that are to be supported by the software, including logical
structure, physical addresses, expected behavior, and so on.]
3.4.3 Software Interfaces

Confidential <Company Name>, 12/8/2024 Page 5

 <Project Name> Version: <1.0>
Software Requirements Specification Date: <dd/mmm/yy>
<document identifier>

[This section describes software interfaces to other components of the software system. These may be
purchased components, components reused from another application or components being developed for
subsystems outside of the scope of this SRS but with which this software application must interact.]
3.4.4 Communications Interfaces
interface with a Local Area Network (LAN) to maintain communication with all its devices. It
Licensing Requirements

[Defines any licensing enforcement requirements or other usage restriction requirements that are to be
exhibited by the software.]
3.5 Legal, Copyright, and Other Notices
[This section describes any necessary legal disclaimers, warranties, copyright notices, patent notices,
wordmark, trademark, or logo compliance issues for the software.]
3.6 Applicable Standards
[This section describes by reference any applicable standard and the specific sections of any such
standards which apply to the system being described. For example, this could include legal, quality and
regulatory standards, industry standards for usability, interoperability, internationalization, operating
system compliance, and so forth.]
4. Supporting Information
[The supporting information makes the SRS easier to use. It includes:
 Table of contents
 Index
 Appendices
These may include use-case storyboards or user-interface prototypes. When appendices are included, the
SRS should explicitly state whether or not the appendices are to be considered part of the requirements.]
5. References

Confidential <Company Name>, 12/8/2024 Page 6