<SHAMAS MURTAZA>

BANQUET HALL MANAGEMENT

SYSTEM
SESSION: 2014-2016
<CS&IT/IUB>

SOFTWARE DESIGN DESCRIPTION DOCUMENT

VERSION: 1.0

SDD Document 1.0

Page 2 of 3

10/21/16

1. INTRODUCTION
The second phase SDD is complete description of the SRS in visual form. In
which it SDD of Banquet Hall Management System is divided in sub section like system
architecture , data design , component design human interface design and requirement
matrix In which diagrams, charts, graphs, and photos may be used to define the different
stages of working.
SDD also a form of documentation in which a reader can get the idea of the project, so in
this SDD the BANQUET HALL MANAGEMENT SYSTEM is trying to reflect in
graphical form.
1.1 Purpose
The purpose of SDD is to describe the design details, architectures and entityrelationships involved in the development of the Banquet Hall Management System.

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.

Keep record of employees.

Print bill.

1.3 Overview
. The second phase SDD is complete description of the SRS in visual form. The overview of
software design document (SDD) is to describe the design details, architectures and entityrelationships involved in the development of the banquet hall management system.
The banquet hall management 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.
SDD Document 1.0

Page 3 of 3

10/21/16

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

1.4 Reference Material

IEEE Std 1058-1998, IEEE Standards for Softwear Project Management.

Pressmans, Roger S., Software Engineerings, 4th editions, McGraw-Hill, 1997

Fairleys, R. E., Works breakdown Structure, Softwares Engineerings Project Managements, IEEE
CS Press, 1997.

1.5 Definitions and Acronyms

Term

Definition

Administrator

The person who manages and can make

required changes.

BHMS

Banquet hall Management System

Database

Collection of all information.

SDD

Software Design Document

.

2. SYSTEM OVERVIEW

SDD Document 1.0

Every Organization needs to manage all the different activities in organization. It is

managed by a Manager or the owner.

Page 4 of 3

10/21/16

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

Categorizing 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.

3. SYSTEM ARCHITECTURE
3.1 Architectural Design
The architecture design is as follows:-

Architectural
Design

Hardware

Database

Software

Design

design

design

3.1 Hardware Architecture

Hardware provides the efficiency to the system. Best hardware modules can upgrade the
performance of the system so that the hardware design for this system is:1. System using greater than the Pentium class.
2. Ram more than 2 GB
3. Rom more than 350 GB.
4. Operating system using Microsoft version windows 7 or more.
5. Printer

SDD Document 1.0

Page 5 of 3

10/21/16

3.2 Database design

Name: Event
Description: The table stores the details of the Event.
Field
Event_id
Event_name
Event_date
Event_Time
No of Guest

Type
Int
Varchar
Varchar
Varchar
Int

Size
Default
30
30
30
Default

Name: Hall
Description: The table stores the details of the Hall.
Field
Hall_id
Hall_Name
Hall_Location
Hall_Capacity
Hall_Cost

Type
Int
Varchar
Varchar
Int
Numeric

Size
Default
30
90
Default
9,2

Name: Package
Description: The table stores the details of the packages.
Field
Package _id
Package _Name
Package_Cost
Package_Items

Type
Int
Varchar
Numeric
Varchar

Size
Default
30
9,2
30

Name: Customer
Description: The table stores the details of the Customers.
Field
Customer_id
Customer_Name
Customer_Address
SDD
Document 1.0
Customer_Contact
Customer_Email

Type
Int
Varchar
Numeric
Varchar
Varchar

Size
Default
30
90
Page30
6 of 3
30

10/21/16

Name: Employees
Description: The table stores the details of the Customers.
Field
Empid
Fname
Mname
Lname
Dob
Gender
Cont
Email
Addr
Dept.
Post
Joindate
Sal
empQual
empExpr

Type
Int
Varchar
Varchar
Varchar
Varchar
Varchar
bigint
Varchar
Varchar
Varchar
Varchar
Varchar
Numeric
Varchar
Varchar

Size
Default
30
30
30
20
12
Default
30
30
20
20
20
9,2
200
200

Name: SweetDish
Description: The table stores the details of the SweetDishes.
Field
Sdid
Sdname
Sdprice

SDD Document 1.0

Type
Int
Varchar
Varchar

Size
Default
30
30

Page 7 of 3

10/21/16

3.3 Software design

User interface flows diagrams.

.
3.2 Decomposition Description

Use Case Diagram

SDD Document 1.0

Page 8 of 3

10/21/16

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.

Activity Diagram
Activity diagrams describe the workflow behavior of a system. The diagrams
describe the state of activities by showing the sequence of activities performed.
Activity diagrams show the flow of activities through the system. Diagrams are
SDD Document 1.0

Page 9 of 3

10/21/16

read from top to bottom and have branches and forks to describe conditions and

parallel

SDD Document 1.0

Page 10 of 3

10/21/16

Sequence Diagram
Sequence diagrams go to a groups of UML diagrams called Communication
Diagrams. Sequence diagrams define how substances interact over the sequence of
time through an conversation of messages. Only sequence diagram frequently
represent the flows of events for a single use cases.

SDD Document 1.0

Page 11 of 3

10/21/16

3.3 Design Rationale

History-based rationale:Consists of the design history the sequence of events that occurred while performing the
design the information given in the whole SDD is based on the historical irony, The past
time was old fashioned and designed the documentation with old methods. The
confliction arise and the system making with the new time development.
The methods using in this SDD is totally based with new settings. The system
development is concern with the new titles, graphs, charts, design documentation, activity
diagrams, sequence diagrams and flow charts which will completely explains the working
in understandable manners. If it would not use then system would be considered as old
one.
.

4. DATA DESIGN
4.1 Data Description

Structure Chart(System Level)

SDD Document 1.0

Page 12 of 3

10/21/16

4.2 Data Dictionary

Users:
Contain detail about the users who is interacting with system in order to provide system
Access according to user rights. User could be of following three types.
Administrator who manage complete system.
Owner who is the stakeholder of the system.
Customer who take the facilities from the system.

Administrator
The administrator will manage the whole system, i.e. hes responsible to insertion ,deletion and
updation are perform by Administrator. According to system he will add new hall ,employ
,package and other related information.
.

5. COMPONENT DESIGN
The system is capable to do work according to the direction. Every simplest or complex
component is responsible to do work which is assigned to it. The system considers every
component as best efficient way component for the mutual cooperation of the whole
process. Component design follows as:-

Hardware

Software

Database

The short detail of the component design working describes as the user after log in to the
system will choose an option for the reservation of hall or other action. Consider an
example if a user choose the option to save new event, he or she will press the tab of
Insert new event. The given data in the text box will be stored in the database and a user
can also retrieve the data on demand and a user can print it as well.

6. HUMAN INTERFACE DESIGN

6.1 Overview of User Interface

Event Table

SDD Document 1.0

Page 13 of 3

10/21/16

The event table is a table of data that is classically written to the log file for
each state and also looks in the Study window. The event table covers timing
information about exact events that occur during the setup. Only incentive
events with event codes will look in the event table.
Sr.no

Event

1.

New Event

2.

New
Employee

3.

New
Customer

4.

New
Requirement

Enter New
Requirements

Staff /
Admin

5.

New Hall
Booking

Enter
Booking
Details

Admin

6.

Bill

Enter Bill
Details

Admin

7.

Maintenance

Enter
Maintenance
Records

Staff /
Admin

SDD Document 1.0

Trigger
Enter Event
Details
Enter
Customer
Details
Enter
Employee
Details

Source
Admin
Admin

Admin

Activity

Response

Destination

Insert Event
Details
Insert
Customer
Details
Insert
Employee
Details
Insert
Requirement
Details
Insert
Booking
Details

Added New
Event

Database

Added New
Customer

Database

Added New
Employee

Database

Added New
Requirement

Database

Added New
Booking

Customer /
Database

Retrieve Bill
Details

Bill Details
Retrieved

Customer /
Database

Enter
Maintenance
Records

Reports
Entered

Database /
Admin

Page 14 of 3

10/21/16

6.2 Screen Images

Login Page

New Event Date and time, Customer Details, No

field Blanks

SDD Document 1.0

Page 15 of 3

10/21/16

Add Package

SDD Document 1.0

Page 16 of 3

10/21/16

SDD Document 1.0

Page 17 of 3

10/21/16

New Employee

6.3 Screen Objects and Actions

A discussion of screen objects and actions associated with those objects.

7. REQUIREMENTS MATRIX
Components:
Requirements
from SRS
(Use case):
UC1
UC2

Login
logout
Component

Enquiry
train Booking seats or Cancelling seats or
Component
berths Component
berths Component

X
X

SDD Document 1.0

X
X

Page 18 of 3

X
X

10/21/16