Software Requirements Specification for Project

HOLMES
INSTITUTE
FACULTY OF
HIGHER
EDUCATION
UNDERGRADUA
TE PROGRAM
Software Requirements
Specification
for
<Project>
Version 1.0 approved
Prepared by <author>
<organization>
<date created>
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for <Project> Page ii
Table of Contents
Table of Contents...........................................................................................................................ii
Revision History............................................................................................................................iii
1. Introduction..............................................................................................................................1
1.1 Purpose.......................................................................................................................................1
1.2 Document Conventions..............................................................................................................1
1.3 Intended Audience and Reading Suggestions.............................................................................1
1.3.1 Overall Description:...............................................................................................................1
1.3.2 System Features:....................................................................................................................1
1.3.3 External Interface requirements:.............................................................................................1
1.4 Project Scope..............................................................................................................................2
1.5 References..................................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective....................................................................................................................2
2.2 Product Features.........................................................................................................................2
2.3 User Classes and Characteristics................................................................................................3
2.3.1 Customer................................................................................................................................3
2.3.2 Co-CEO.................................................................................................................................3
2.3.3 Products.................................................................................................................................3
2.3.4 Employees..............................................................................................................................3
2.4 Operating Environment..............................................................................................................3
2.5 Design and Implementation Constraints.....................................................................................3
2.6 User Documentation...................................................................................................................3
2.7 Assumptions and Dependencies.................................................................................................3
3. System Features.......................................................................................................................4
3.1 Product information....................................................................................................................4
3.1.1 Objective:...............................................................................................................................4
The purpose is to determine the functioning that is provided with each bikes globally. This will help
the employees to check the details regarding each bike and the components associated with the
system.....................................................................................................................................................4
3.1.2 Priority:..................................................................................................................................4
3.1.3 Source:...................................................................................................................................4
3.1.4 Actor:.....................................................................................................................................4
3.2 Customer details.........................................................................................................................4
3.2.1 Objective:...............................................................................................................................4
3.2.2 Priority:..................................................................................................................................4
3.2.3 Source:...................................................................................................................................4
3.2.4 Actor:.....................................................................................................................................4
3.3 Order details...............................................................................................................................5
3.3.1 Objective:...............................................................................................................................5
3.3.2 Priority...................................................................................................................................5
3.3.3 Source:...................................................................................................................................5
3.3.4 Actor:.....................................................................................................................................5
3.4 Report generation by employee..................................................................................................5
3.4.1 Objective:...............................................................................................................................5
3.4.2 Priority:..................................................................................................................................5
3.4.3 Source:...................................................................................................................................5
3.4.4 Actors:....................................................................................................................................5
3.5 Stock determination....................................................................................................................5
3.5.1 Objective:...............................................................................................................................5
3.5.2 Priority:..................................................................................................................................6

Software Requirements Specification for <Project> Page iii
3.5.3 Source:...................................................................................................................................6
3.5.4 Actor......................................................................................................................................6
3.6 Employee monitoring.................................................................................................................6
3.6.1 Objective:...............................................................................................................................6
3.6.2 Priority:..................................................................................................................................6
3.6.3 Source:...................................................................................................................................6
3.6.4 Actor:.....................................................................................................................................6
4. External Interface Requirements...........................................................................................6
4.1 User Interfaces............................................................................................................................6
4.2 Hardware Interfaces....................................................................................................................6
4.3 Software Interfaces.....................................................................................................................7
4.4 Communications Interfaces........................................................................................................7
5. Other Nonfunctional Requirements.......................................................................................7
5.1 Performance Requirements.........................................................................................................7
5.2 Safety Requirements...................................................................................................................7
5.3 Security Requirements................................................................................................................7
5.4 Software Quality Attributes........................................................................................................7
6. Other Requirements................................................................................................................8
Appendix A: Glossary...................................................................................................................8
Appendix B: Analysis Models.......................................................................................................8
Appendix C: Issues List...................................................................................................................9
Revision History
Name Date Reason For Changes Version

Software Requirements Specification for <Project> Page 1
1. Introduction
1.1 Purpose
The purpose of the system is to provide an information system that would be containing all the
procedure to make the business efficient for the organizations. This document is used for the
Collection and analysis of the data required for the system. The system requirements of the
system are to identified in this system. A detailed overview of the software development for the
GBI organization has been described in this document.
1.2 Document Conventions
The Harvard conventions have been followed in this document. The Bold-faced text has been
used as an indication of the Headings and the sub headings in the document. Italicized texts have
been used for the normal fonts in the document
1.3 Intended Audience and Reading Suggestions
The Document has been intended for the project team to read. In addition to this the marketing
group in the organization would also be reading this document. The main stakeholders of the GBI
organization would be reading this document to understand the system which has been
developed for them. The management committee would be reviewing this document to check if all
the functionalities in the system has been developed as per expectation or not. The specificity of
the project that has been conducted by the project is to be provided from the SRS. Other features
needed to be review by this document is:
1.3.1 Overall Description:
The Staffs in the GBI organization are required to get accustomed to the processes that are being
followed currently in the organization and for the system.
1.3.2 System Features:
The scope of the system which is being designed for the organization are being provided from
this SRS document.
1.3.3 External Interface requirements:
The hardware developers would be able to get knowledge about the software that is being
developed. This would help them in making efforts to acquire the hardware interface required to
support the software interface for the organization.