Software Requirements Specification of XXX software

Doc # Version: 2013 Page 1 / 6

Faculty of Computer and Mathematical Sciences

Universiti Teknologi MARA
Kelantan

SOFTWARE REQUIREMENTS SPECIFICATION

for

[name of your software/application]

Name Signature

[name of your company]

 Software Requirements Specification of XXX software

Doc # Version: 2013 Page 2 / 6

TABLE OF CONTENTS
1 INTRODUCTION 3
1.1 Document overview 3
1.2 Abbreviations and Glossary 3
1.2.1 Abbreviations 3
1.3 References 3
1.4 Project References 3
1.5 Standard and regulatory References 3
2 REQUIREMENTS 4
2.1 Functionalities and Performance 4
2.2 Requirements Desription 5
2.3 Safety, security, and privacy protection 5
2.4 Help 5
3 Resources 6
3.1 Hardware resources 6
3.2 Software resources 6

[name of your company]

 Software Requirements Specification of XXX software

Doc # Version: 2013 Page 3 / 6

1 INTRODUCTION

1.1 Document overview

This document presents the software requirements specifications of XXX software development
project.
It describes:
 Requirements of functionalities, performances, interfaces, environment …
 Tests principles and definitions of validation methods of requirements,
 The compliance of requirements to customer needs,
 The relative importance and precedence of requirements

1.2 Abbreviations and Glossary

1.2.1 Abbreviations
Add here abbreviations

1.3 References

1.4 Project References

# Document Identifier Document Title

[R1] ID Add your documents references.
One line per document
For example a statement of work, a user interface mock-up …

1.5 Standard and regulatory References

# Document Identifier Document Title

[STD1] Add your documents references.
One line per document
For example: ISO 13485, ISO 14971, IEC 62304, and so on

[name of your company]

 Software Requirements Specification of XXX software

Doc # Version: 2013 Page 4 / 6

2 REQUIREMENTS
Note : have a look at http://en.wikipedia.org/wiki/Requirement, article in wikipedia. It’s well
written and the links at the bottom are useful.

2.1 Functionalities and Performance

This is the core of your SRS. It contains the purpose of your software expressed in technical
requirements

You may organize this part in sub-sections like:

 Module 1 : Student Information
o 1.1 The system shall add new student record.
o 1.2 The system shall edit students’ record.
o 1.3 The system shall delete students’ record.
o …
 Module 2 : Report Generation
o 2.1 The system shall generate students’ enrolment list.
o 2.2 The system shall generate list of female student.
o 2.3 The system shall generate list of male student.
o 2.4 The system shall generate list of semester 1 student.
 Module 3 : Authorization
o 3.1 The system shall check user id and password.
o 3.2 The system shall give notification to unauthorized user.
 Module 4 : Staff Information
o 4.1 The system shall add new staff record.
o 4.2 The system shall delete staff record.
o 4.3 The system shall search staff record.
Or sub-sections like:
 Function 1
o Sub-Function 1.1
o Sub-Function 1.2
o …
 Function 2
o …
 Function 3
o …
 (and so on)
Choose your own structure which best fits your needs.

Requirements shall not be vague. They shall be understandable and testable.

Ask yourself “How am I going to test this?” when you write a requirement

[name of your company]

 Software Requirements Specification of XXX software

Doc # Version: 2013 Page 5 / 6

2.2 Requirements Desription

Examples of requirement:

Requirement ID SRS-XXX-010 SAMPLE

Title Student Information

The system shall add new student record. For example, student ID,
Description
student’s name, student’s address, etc.
Version V1.0

Requirement ID SRS-XXX-020 SAMPLE

Title Student Information

The system shall edit students’ record. For example, student ID, student’s
Description
name, student’s address, etc.
Version V1.0

Note for ITS332 supervisors: In Section 2.1, the requirement ID must be consistent with module list.

2.3 Safety, security, and privacy protection

This section is about software features like confidentiality, integrity control, reliability, and
availability. See CyberSecurity requirements of FDA and HIPAA requirements if necessary
Requirement ID SRS-XXX-030 SAMPLE

Title Student data

Student data must be keyed in using correct format. The patient’s data are:
Description  Contact No: 019-9996666,
 IC No:999999-99-9999
Version V1.0

2.4 Help
The user guide is always very important for medical devices. It may be online, in this case add
requirements here about the online help ….
Requirement ID SRS-XXX-060 SAMPLE

Title Online user guide

Description XXX contains an online user guide
Version V1.0

[name of your company]

 Software Requirements Specification of XXX software

Doc # Version: 2013 Page 6 / 6

3 Resources

3.1 Hardware resources

Requirement ID SRS-XXX-080 SAMPLE

Title Hardware configuration

XXX shall run with the expected response times on a PC with the following
minimal configuration:
Description  2 Gb RAM
 ...

Version V1.0

3.2 Software resources

Requirement ID SRS-XXX-090 SAMPLE

Title Software configuration

XXX runs in the following software environment:
Description  (describe OS version),

Version V1.0

[name of your company]