Software Requirements Specifications
<Project Title>
Project Code:
Internal Advisor:
External Advisor:
Project Manager:
Project Team:
Submission Date:
_____________________
Project Manager’s Signature
<Project code> Software Requirements Specifications <Version x>
Document Information
Category Information
Customer FAST-NU
Project <Project Title>
Document Requirement Specifications
Document Version 1.0
Identifier PGBH01-2003-RS
Status Draft
Author(s) <Names of all the authors of this document>
Approver(s) PM
Issue Date Sept. 15, 2003
Document Location
1. Advisor
Distribution 2. PM
3. Project Office
Definition of Terms, Acronyms and Abbreviations
This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret
the terms used in the document properly.
Term Description
ASP Active Server Pages
RS Requirements Specifications
Sept. 15, 2003 Page 2 of 7
<Project code> Software Requirements Specifications <Version x>
Sept. 15, 2003 Page 3 of 7
<Project code> Software Requirements Specifications
Table of Contents
1. INTRODUCTION........................................................................................................................4
1.1 Purpose of Document..............................................................................................4
1.2 Project Overview.......................................................................................................4
1.3 Scope..........................................................................................................................4
2. OVERALL SYSTEM DESCRIPTION............................................................................................4
2.1 User characteristics..................................................................................................4
2.2 Operating environment............................................................................................4
2.3 System constraints...................................................................................................4
3. EXTERNAL INTERFACE REQUIREMENTS..................................................................................5
3.1 Hardware Interfaces.................................................................................................5
3.2 Software Interfaces..................................................................................................5
4. FUNCTIONAL REQUIREMENTS.................................................................................................5
5. NON-FUNCTIONAL REQUIREMENTS.........................................................................................5
5.1 Performance Requirements....................................................................................5
5.2 Safety Requirements................................................................................................5
5.3 Security Requirements............................................................................................5
5.4 User Documentation................................................................................................6
6. References...............................................................................................................................6
<Project code> Software Requirements Specifications
1. Introduction
1.1 Purpose of Document
Describe the purpose of this document and provide a description of the intended audience i.e., the personnel
who will be reading this document.
1.2 Project Overview
State a brief description of the project under study. Describe how the software will be used and identify the
relevant goals and benefits.
1.3 Scope
List down the scope of the project. Describe what the system will and will not do.
2. Overall System Description
Describe the environment, in which the system will be developed and used, the anticipated users of the system
and the known constraints, assumptions and dependencies.
2.1 User characteristics
Provide the various user classes that you anticipate will use this system. Distinguish the most important user
classes for this system from the less critical ones.
2.2 Operating environment
Describe the environment in which the software will operate, including the hardware platform, operating
system and other software components or applications with which it must coexist.
2.3 System constraints
Identify any constraints or limitations on the system. Constraints may include the following:
Software constraints
Hardware constraints
Cultural constraints (includes language etc.)
Legal constraints
Environmental constraints (e.g., the environment where the software will be installed, It could be a
noisy environment, which may require that there is no sound event in the project).
User constraints (e.g., the project is developed for children, so it may be required that the project has
more graphic controls rather than textual controls).
Off the shelf components that might be used in the project may have their constraints that are
consequently transferred to the project.
<Project code> Software Requirements Specifications
3. External Interface Requirements
This section is intended to specify any requirements that ensure that the new system will connect properly to
external components. Place a context diagram showing the external interfaces at a high level of abstraction.
3.1 Hardware Interfaces
Describe the characteristics of each interface between the software and hardware components of the system.
This description might include the supported device types, the nature of the data and control interactions
between the software and the hardware.
3.2 Software Interfaces
Describe the connections between this system and other external software components (identified by name and
version), including databases, operating systems, tools, libraries, and integrated commercial components.
Identify and describe the purpose of the data items or messages exchanged among the software components.
Describe the services needed and the nature of the inter-component communications. Identify data that will be
shared across software components.
4. Functional Requirements
This section should contain a textual description of the requirements related to the customer’s business. This
should contain a list of all the business events related to the business process.
5. Non-functional Requirements
5.1 Performance Requirements
The performance characteristics of the system that are required by the business should be outlined in this
section. Performance characteristics include the speed, precision, capacity, safety, and reliability of the
software. These characteristics define the performance of the project.
5.2 Safety Requirements
Specify the requirements that are concerned with possible loss, damage, or harm that could result from the use
of the system. Define any safeguards or actions that must be taken, as well as potentially dangerous actions
that must be prevented. Identify any safety certifications, policies, or regulations to which the system must
conform.
5.3 Security Requirements
Specify any requirements regarding security, integrity, or privacy issues that affect the use of the system and
protection of the data used or created by the system. Define all user authentication or authorization
requirements, if any. Identify any security or privacy policies or certifications the system must satisfy.
<Project code> Software Requirements Specifications
5.4 User Documentation
List the user documentation components that will be delivered along with the software, such as user manuals,
online help, and tutorials.
6. References
This section should provide a complete list of all documents referenced at specific point in time. Each document
should be identified by title, report number (if applicable), date, and publishing organization. Specify the
sources from which the references can be obtained. (This section is like the bibliography in a published book).
Ref. No. Document Title Date of Release/ Publication Document Source
