SRS Document 1.

Page 1 of 23

Session: 2014 - 2016 | Department of computer science & it

10/21/16

Chapter 1
1. Introduction
The SRS of banquet hall contains the whole material related to the project. This SRS is
divided into different section. In which 1st section define the product functionalities. 2nd
section define the over all description of product and 3 rd section define its specific
requirements. Banquet hall is an important place for the ceremonies and provides the
place and services to their customers. By the time it is important to maintain the system
of this type by a computer system. The record maintenance, services, booking and record
keeping is the major aspects of this project.

1.1 Purpose
The purpose of this SRS is to define the entire system requirements efficiently that easily
understandable for coder. .

1.2

Scope

Manage the function services.

Keeping record of function.

Manage new and old reservation.

Cancelling and submitting the reservation.

Change the function date in reason.

Managing the catering(with meal and without meal), waiters and chef.

Manage the VIP(Special) and common function.

Applicable for only Windows.

1.3
SRS Document 1.0

Definitions, Acronyms, and Abbreviations.

Page 2 of 23

10/21/16

1.3.1 Catering
A caterer provides food to the different parties. The caterer can be hired
independently or can be part of a package designed by the venue.

1.3.2 Catering with Meal

Provide food services to the participants. In which have per head system.

1.3.3 Catering without Meal

Food services provide by users.

1.3.4 VIP
VIP Stand For very important person.

1.4 References
[1] National Electrical Contractors Association (1922). "Electrical Construction and
Maintenance". Electrical Construction and Maintenance (McGraw-Hill Publishing
Company) 22: 58. Retrieved28 January 2015 Jump up^ "Ngram View "Lesson 2 Windows NT System Overview". Microsoft TechNet. Microsoft. Retrieved November 25,
2014.er". Retrieved 28 January 2015.

[2] "Lesson 2 - Windows NT System Overview". Microsoft TechNet. Microsoft.

Retrieved November 25, 2014.

1.5 Overview
In this SRS descriiption:
(1) Documentation defines the detail of the project material.
(2) Detail of the SRS working.
In the description of SRS it is defined everything clearly that the system will work
according to the directions given to it. The chances of failure has been reduced to its
minimum level. The SRS defined the every step of the working accordingly. The SRS
presentation elaborates the function of new version and removes the old one that is
manual.
Chapter 2 defines the general product functions, iintended application, constraints to be
respected and the assumption made in order to define requirements.

SRS Document 1.0

Page 3 of 23

10/21/16

Chapter 3 specifies functional (Section 3.1) and non-functional requirements (all other
sections), usability, reliability, security, performance and maintainability considerations
and requirements to a level of detail sufficent to enable designers to design a system to
satisfy these requirements and testers to test that the system satisfies these requirement

Chapter 2
2. The Overall Description
The banquet hall mannagement system provides the best
facilities to user. In this system the administrative part will have the all records of the
system. The overall description summarize the all aspects of the system. Banquet hall
management system contains some facilities like reservation system of the function,
manage staff of the hall, services like decoration and food management etc.
There are three different halls booked together or separately. The main hall, shop line hall
and dining hall. Main hall has a stage for various uses. It is Air-conditioned hall with
well-Furnished glazed flooring. The people managing the hall are qualified professionals
dedicated to their works. In decoration have different categorised for decorating the hall
like flowering, carpets and caters. When a customer will book the banquet hall for a
specific date it is confirm to take the time of the reservation. The customer is allowed to
change the date in any cause. If hall is not reserved of that date then no charges deduct
and if he wants to return his payment then deduct the 30% charges.
The customer is bound to pay the 40% amount on the reservation time as advance.
Amount is based on the services and the strength of the function attendant. If strength is
increase then charges increase as per head. The function will be provided the best
services to the customer. If the customer will not attend the function on the booked date it
is clearly mention that the banquet hall management system is not responsible of any loss
and customer pay 80% charges. The customer is supposed to be responsible to all
condition.
The staff services and food services will be provided by the management system anyhow
a customer can make changes their own, like they can change the menu before the time or
they can prepare their food by their own expenses. In such condition customer has facility
to given the amount back after deduction. All functions will be opened at 10:00 am and
closed at the time of 10:00 pm. Reservation Timing is 10:00am to 9:00pm. The system is
properly handled by the managing side. All records are the assets of the management
system.

SRS Document 1.0

Page 4 of 23

10/21/16

2.1 Product Perspective

Currently the organisation is keeping records in paper and registers. The
limitations of such a system can be easily lost or wearied and may result in misuse or
permanent loss of important data.
Record regarding payments and availability also needs authentication from
unauthorized users. Staff details and other details like maintenance, cleaning, caterers
also need to be maintained in order. Maximum work of billing and receipts is hand
written and also a bit time consuming.
Therefore, to manage the all record and without loss data we make the system
computerized. All the data about system like reservation , billing, decoration and staff are
stored. The following statements show the prospective of the system.
Maintain the records of all the customers and long term clients.
Maintain the records of all the caterers, cleaning, decoration and maintenance staff.
Maintaining and printing bills, keeping record of advance and balance payments.
Maintaining the availability of dates of halls.
Easy addition (insertion), retrieval and updating of client details and requirements.
Client/Customer feedbacks and suggestions can be entered and taken in to consideration
for further development.
Manager and staff logins are different and have specific rights to access, retrieve or
update data.
Generate reports on progress of the banquet hall on monthly basis.
Data and Report can be generated as a when required by the user.

2.1.1 Operations

Every Organisation needs to manage all the different activities in organisation. It is

managed by a Manager or the owner.

Owner manages booking of halls, Checks availability of halls, advance and balance
Payment by the customers.

SRS Document 1.0

Page 5 of 23

10/21/16

Categorising pricelist according to customers requirement and for time, space and
services utilized by clients for the function.

Manager maintains each and every record for ease of its work.

Manager keeps track of all the upcoming functions and arrangements to be made.

2.1.2 Site Adaptation Requirements

Only requiired the driver software of printer devices.

2.2 Product Functions

The system maintain the records of all the customers and long term clients.
The system maintain the records of all the caterers, cleaning, decoration and maintenance
staff.
The system maintaining and printing bills, keeping record of advance and balance
payments.
The system maintaining the availability of dates of halls.
The system easy addition (insertion), retrieval and updating of client details and
requirements.
Manager and staff logins are different and have specific rights to access, retrieve or
update data.
The system generate reports on progress of the banquet hall on monthly basis.
Data and report can be generated as a when required by the user.

2.3 User Characteristics

User must have ability to read and write English.

User must have good skills in computer technology.

Awareness with the operation of the basic Graphical User Interface (GUI)
components of the Windows operating system.

SRS Document 1.0

Page 6 of 23

10/21/16

2.4 General Constraints

1. The project should to be finished inside indicated time period including Planning,
Designing, Development, Testing and Deployment.
2. The admin and manager should login system.
3. No compromise on quality.
4. Reiliable.
5. User friendly.

2.5 Assumptions and Dependencies

The system is not required to save generated report.
Credit card payments not included.

SRS Document 1.0

Page 7 of 23

10/21/16

Chapter 3
3. Specific Requirements
The specification requirements is functional and non-functional requirements. The
functional requirement according to the use case.
Requirement ID
Functional and non-functional requirements are unique identified by ID.
Description
In this section specify all functional and non-functional requirements. All the
requirements are correct and according to the project.
Priority
Its tell the difference b/w functional and non-functional requirements. High priority
show the functional requirements and low priority requirements show the non-functional
requirements.

3.1 External Interface Requirements

This section contain all the software requirement at the level of detail. It is
combine with the, use cases is sufficient to enable inventers to design a
system to satisfy those requirements and esters to rest that the system fulfils
those requirements.

3.1.1 User Interfaces

The User Interface Screens are described in table 1.
Table 1: Hotel Management User Interface Screens
Screen Name

Description

Login

Log into the system as Admin or Manager

Reservation

Retrieve button, update/save reservation, cancel reservation,

modify reservation, change reservation, adjust room rate, accept

SRS Document 1.0

Page 8 of 23

10/21/16

Screen Name

Description

payment type/credit card

Check-in

Either hall is reserved or not.

Checkout

Checkout customer, generate bill.

Customer Record

Add or update customer records

Reports

Select, view, save, and delete reports

3.1.3 Hardware Interfaces

Specify the use of other required hardware products.

Hardware Specifications
Processor Type
System RAM
Hard Disk

Intel Core i3 3.00 MHz or higher.

2GB minimum
160 GB Recommended

3.1.3 Software Interfaces

Specify the use of other required software products and interfaces with other application
systems. For each required software product, include:

Software Requirements
Operating System
Front End
Back End

Microsoft Windows 7 professional

or later
Visual Studio 2012 or higher
SQL server 7 or higher

3.1.3.1 Microsoft SQL Server

The system must use SQL Server as its database component. Communication with the
DB is through ODBC connections. The system must provide SQL data table definitions
to be provided to the company DBA for setup.

SRS Document 1.0

Page 9 of 23

10/21/16

A key point to remember is that you do NOT want to specify software here that you think
would be good to use. This is only for customer-specified systems that you have to
interact with. Choosing SQL Server as a DB without a customer requirement is a Design
choice, not a requirement. This is a subtle but important point to writing good
requirements and not over-constraining the design.

3.1.4 Communications Interfaces

The system will be standalone product that does not require any communication
interfaces.

3.2 Functional Requirements

Function 1
Input
Output
Processing

Make Reservation
Code, hall id, number of male and female , date, time, function
type.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 3
Input
Output
Processing

Add kitchen record

Code, dish name ,.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 2
Input

Add customer record

member code, phone number, company ,name , e-mail, gender,
address, CNIC
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Output
Processing

Function 3
Input
Output
Processing

Add Catering record

Code, name , total.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 4

Add Staff members

SRS Document 1.0

Page 10 of 23

10/21/16

Input
Output
Processing

Code , employee name , employee address, CINC salary, age ,

occupation e-mail.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 5
Input
Output
Processing

Search Halls
Check availability , no of functions , date.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 6
Input
Output
Processing

Add Payments
Total , pay time, credit card details.
Database record , Database successfully updated message.
Validate the given details and record the information in to the
database.

Function 7
Input
Output
Processing

Issue bill
Billing no, strength, price , taxes , date , services.
Printed version of the bill.
Validate the given details and record the information in to the
database.

Function 8
Input
Output
Processing

Taking Backups
Location to save the backup file.
Display a message backup successfully created.
Validate the given details and record the information in to the
database.

SRS Document 1.0

Page 11 of 23

10/21/16

3.3 Use Cases

A use case is a set of scenarios that describing an interaction between a user and a system. The
two main components of a use case diagram are use cases and actors. In many design processes,
the use case diagram is the first that designers will work with when starting a project. The main
purpose of a use case diagram is to show what system functions are performed.

3.3.1 Use Case #1

SRS Document 1.0

Page 12 of 23

10/21/16

3.3.2 Use Case #2

3.4 Classes/Objects
A class is a system entity that models a real-world object. A class is made up of
attributes which define the information that each class knows about itself and
operations which are the processes that a class can carry out. Often you will see
operations referred to as methods.

SRS Document 1.0

Page 13 of 23

10/21/16

3.4.1 <Class Diagram>

SRS Document 1.0

Page 14 of 23

10/21/16

3.4.2 <Object Diagram>

SRS Document 1.0

Page 15 of 23

10/21/16

3.5 Non Functional Requirements

ID

Requirements

priority

Req 14

Only admin and manager can login to the system.

Low

Req 15

On phone call , booking not grunted until credit is confirm.

Low

Req 16

Provide simple and VIP format to user.

Low

Req 17

Every function decoration show the type of function.

Low

Req 18

In simple category common material is used.

Low

Req 19

In VIP category , stylish material is used like vine glass, carpets etc.

Low

Req 20

According to weather cooling fans and hitters are used.

Low

Req 21

Provide sound system thats extra charges.

Low

Req 22

User pay holding tax and GST tax.

Low

Req 23

Print the booking form.

Low

SRS Document 1.0

Page 16 of 23

10/21/16

Req 24

Provide annual and monthly report of all function.

Low

Req 25

In per head system the price is should less as increase of members.

Low

Req 26

Different category for stage that according to the function type also in Low
common and VIP format like using flower and carpets etc.

Req 27

If hundred then waiter should 3 and if 2 hundred members then 6 waiter Low
required and so on.

3.6 Logical Database Requirements

An entity-relationship diagram is a data modeling technique that creates a graphical
representation of the entities, and the relationships between entities, within an information
system.

SRS Document 1.0

Page 17 of 23

10/21/16

SRS Document 1.0

Page 18 of 23

10/21/16

3.7 Design Constraints

Our system should be standalone that run on window environment. We are developing by using
c#.

3.7.1 Standards Compliance

The graphical user interface looking consistence and feel easy to use.

SRS Document 1.0

Page 19 of 23

10/21/16