Software Requirements

Specification
For

Hotel Management ERP

System

Version 1.0 approved

Prepared by Muhammad Hassan Yamin

Preston University

9th Nov 2018

Copyright © 1999 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.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions..................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics....................................................................................................2
2.4 Operating Environment..................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies.....................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose

Enterprise resource planning (ERP) is business process management

software that allows an organization to use a system of integrated
applications to manage the business and automate many back office
functions related to technology, services and human resources.
ERP software typically integrates all facets of an operation — including
product planning, development, manufacturing, sales and marketing — in
a single database, application and user interface.
A 2016 study by Panorama Consulting Solutions, LLC, indicates that
Organizations implement ERP for the following reasons:
 To replace out-of-date ERP software (49%)
 To replace homegrown systems (16%)
 To replace accounting software (15%)
 To replace other non-ERP systems / had no system (20%)

1.2 Document Conventions

<Describe any standards or typographical conventions that were followed
when writing this SRS, such as fonts or highlighting that have special
significance. For example, state whether priorities for higher-level
requirements are assumed to be inherited by detailed requirements, or
whether every requirement statement is to have its own priority.>
1.3 Intended Audience and Reading Suggestions
The audience for the system use are Managers, Receptionists, and
Accountants.
Software Requirements Specification for <Project> Page 2

1.4 Product Scope

The project scope is to Automate and optimize the entire Hotel

Management System so that minimum workforce is required and
data is accurate, retrieval is fast. The entire System is user friendly so
that a person with minimum expertise can operate the system.
Finally increase the work flow of Business.

2. Overall Description

2.1 Product Perspective

Accounting system, its inventory and the booking that is going to be
done against that Event so the owner has to manage each part
separately using multiple team members each with their own
domain of expertise and the entire data in not at one place but
dispersed in to different sections.
So the entire system has to be optimized in a way that all data can be
at one place and storing or retrieving of that data would be one click
away.
2.2 Product Functions
<Summarize the major functions the product must perform or must let the
user perform. Details will be provided in Section 3, so only a high level
summary (such as a bullet list) is needed here. Organize the functions to
make them understandable to any reader of the SRS. A picture of the
major groups of related requirements and how they relate, such as a top
level data flow diagram or object class diagram, is often effective.>
2.3 Operating Environment
The System is compatible with all the latest web browsers.
2.4 Assumptions and Dependencies
To increase the performance of the software we will need to update our
Project according to the ongoing technologies. For which jQuery,
Jason/web services and Ajax etc. will be used. The only issue would be on
the implementation phase, regarding the trial and error plus it may also
consume more time.
Software Requirements Specification for <Project> Page 3

3. External Interface Requirements

3.1 User Interfaces

These are the interface of our ERP System:
 Dashboard.
 Inventory.
 Facilities.
 Customer.
 Order.
 Bookings.
3.2 Hardware Interfaces
Our System is compatible with all the devices that support a web browser.

3.3 Software Interfaces

The front and back end of our system is on Visual Studio. Data base is
maintained in SQL Server.
3.4 Communications Interfaces
The communication between the visual studio and the database is
maintained through ADO.net.

4. System Features
The objective of this product is to save time, maximize output and save
resources.
4.1 Booking

4.1.1 Description and Priority

The feature is considered to be of high priority because a client
might be interested in booking an event. On the other hand, all
the accounts and ledgers will linked to booking.
4.1.2 Stimulus/Response Sequences
All the accounts/ledgers will be made on the basis of booking of
the client and can be updated on it as well.
Software Requirements Specification for <Project> Page 4

4.1.3 Functional Requirements

The ERP System offers
REQ-1: Custom Package
REQ-2: Pre-defined Package

5. Other Nonfunctional Requirements

5.1 Performance Requirements

<If there are performance requirements for the product under various
circumstances, state them here and explain their rationale, to help the
developers understand the intent and make suitable design choices.
Specify the timing relationships for real time systems. Make such
requirements as specific as possible. You may need to state performance
requirements for individual functional requirements or features.>
5.2 Safety Requirements
<Specify those requirements that are concerned with possible loss,
damage, or harm that could result from the use of the product. Define any
safeguards or actions that must be taken, as well as actions that must be
prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use. Define any safety
certifications that must be satisfied.>
5.3 Security Requirements
All queries of Data base is stored in stored procedures and this avoids SQL
injection.
5.4 Software Quality Attributes
The system is based on Object Orientated Programming. The Data base
layer is on another class that can be reused.
5.5 Business Rules
Data base access is given to no one except the developer.
Admin, cashier, inventory system have their own access according to their
roles.
Software Requirements Specification for <Project> Page 5

6. Other Requirements
<Define any other requirements not covered elsewhere in the SRS. This might include database
requirements, internationalization requirements, legal requirements, reuse objectives for the
project, and so on. Add any new sections that are pertinent to the project.>

Appendix A: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each SRS.>