Banquet Hall Management System: Project Entitled

BanQuet Management System Page
2011-2012
Project Entitled
BanQuet Hall Management System
Submitted by
Mr. XXXXXX
Guided by
Prof. XXXXXXXXXX
Bachelor of Science
Department of Computer Science
XXXXX of Arts, Science and College, Mumbai-31

XXXXXXXXX COLLEGE OF COMMERCE & ECONOMIC

AND
XXXXXXXX COLLEGE OF SCIENCE
DEPARMENT OF COMPUTER SCIENCE
Certificate
This is to certify that Mr. XXXXXXXXXXXX (Seat No: ) has
successfully completed the project entitled BanQuet Hall Management
System undertaken at the XXXXXXX College under the guidance of Prof.
XXXXXXX towards partial fulfillment of Bachelor of Science in the subject
of Computer Science of University of Mumbai during the academic year 2011-
2012.
Internal Guide Head of Department
College seal External Examiner

(With Date)
ACKNOWLEDGMENT
I express gratitude and thanks to Almighty God, my Parents and friends

without whose unsustained support, I could not have made my career in Computer
Science. I would also like to express my sincere gratitude towards the Owner of
XXXXXX Hall, Mr. XXXXXXXX for giving me his precious time and support for
completing this project.
I wish to place on my record my deep sense of gratitude to my project guide,

Mrs. CCCCCCCCCC, Head of the Department of Computer Science for her
constant motivation and valuable help through the project work. She has taken pain
to go through the project and make necessary correction as and when needed.
I also extend my thanks to other Faculty members, lab attendants,

engineering dept. and staff members for their Cooperation for without whom this
project would have been distant reality.
CCCCCCCCCCCC
T.Y.BSc Computer Science
Table of Contents:
Sr. No. Contents Page No.

I. Preliminary Investigation 5
i Organizational Overview. 6
ii Description of System 6
iii Limitations of present system 7
iv Proposed system and its adv 7
v Feasibility Study 8
vi Stakeholders 10
vii Gantt chart 11
II System Analysis
i Fact Finding Technique(Questionnaire)
ii Event Table
iii Use Case Diagram
iv Entity Relationship Diagram
v Activity Diagram
vi Class Diagram
vii Object Diagram
viii Sequence Diagram
ix State Diagram
III System Design
i Converting ERD to Tables
ii Design Class Diagrams
iii Component Diagrams
iv Package Diagram
v Deployment Diagram
vi Structure Chart(System Level)
IV System Coding
i Menu Tree
ii List of Tables
iii Program Description and Naming Convention
iv Validations
v Test Cases
vi Screen Layouts & Report Layouts
Program Listing
V System Implementation
VI Future Enhancements
VII References and Bibliography
I.
Preliminary Investigation
Organizational Overview
XXXXX PARTY HALL is a managed hall that is being used for

various functions and purposes like Marriages, Engagements, Birthday parties,
Thread ceremonies (Janoi), Child naming (Namkaran) Ceremonies,
Anniversary parties, Baby Shower (Godh bharai), Meetings/Conferences/
Workshops, Prayer meetings, Surveys etc. And also for long term activities
like Dance classes, Yoga classes, Tuition classes, Karate classes etc. It is
Located at CCCC (E).
Their 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.
Description of System
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.
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.
Limitations of Present System

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.
Proposed system and Its Advantages:

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.
Feasibility Study:
An analysis has been done before BanQuet Hall Management System

was taken into consideration for development. A detailed discussion on the
process and uses was done with the owner and thus we agreed on proceeding
with this project.
Technology and system feasibility
XXXXXXX Party Hall is a hall business. It includes registering new

incoming events, checking of the available dates and maintaining the condition
of the current premises.
The currently developed system takes care of the major business part
that is, maintaining records of events and customers. It also helps the owner to
keep records of the employees. This software has keyboard and mouse inputs.
The output can be operated on screen or in few cases a hard copy can also be
retrieved by the user
The system can be operated by manager and the owner. The system can
also be used by multiple users in case of future enhancement and expansion of
the business. All the details of the operation and functioning of the software
will be made available to the user.
As much as possible the project will tried to make error free, but there is
some probability of errors in the system as hardware or operating system
problems. In case of corruption of the software, there will be no harm to
database and software can be reinstalled and all the data can be retrieved and
worked upon again.
Economic feasibility
This Software helps the user economically in the following way:
Cost-based study: The development cost is very less than all the other
available softwares in market; since it the first version of the software. It will
also prove to be very profitable keeping in mind the other high valued
softwares. Operation of the software will be the only cost of electricity used
by the computer used and may rise in case if a person is hired to operate the
software.
Time-based study: The time required to achieve returns on investment

on this software is minimal as the software itself is of minimum cost with one
years support and free up-gradation of the software is included. The future
version of the softwares may be available on higher prices and
Operational feasibility
Total working capacity of the organization will be improved. Also the

maintaining of records without loss and detoriation will be taken care of which
will also save space occupied by registers and ease of searching and updating
the details.
Schedule feasibility
The project is estimated to be completed within a year. The basic
software is installed in to the users system on testing basis. The dates of the
deadlines are desirable and in case of delay of more than three months, the
entire amount will be paid back within next one months time.
System Requirements:
Hardware Specifications
Processor Type Intel Pentium III 733 MHz or
higher.
System RAM 256 MB minimum
Hard Disk 10 GB Recommended
Software Requirements
Operating System Microsoft XP professional SP2 or
later
Front End Visual Studio 2008 or higher
Back End SQL server 2005 or higher
BanQuet Management System Page |
Stake Holders
A stakeholder is any individual or organization that is affected by the activities

of a business. They may have a direct or indirect interest in the business, and
may be in contact with the business on a daily basis, or may just occasionally.
Stakeholders are defined as "those groups without whose support the

organization would cease to exist."
The main stakeholders are:
Admin:-
The Admin is the Owner of the Hall
Manager:
Manager has got all the Rights to Add, Update and Delete records
about the Customers, Functions and Staff.
Gantt chart
II.
System Analysis
Fact Finding Techniques (Questionnaire)
Following Questions were asked to the development officer during the initial
phase of project development.
What is your working process?

Is it manual or computerised?
How do you store data?
How do you maintain your data?
What are the Softwares you use to manage your data?
What are the System Requirement?
How are the advantages of the current system?
What are the Disadvantages of the Current System?
Event Table
The event table is a table of data that is typically written to the log file for each
scenario and also appears in the Analysis window. The event table contains
timing information about specific events that occur during the scenario. Only
stimulus events with event codes will appear in the event table.
Sr.no Event Trigger Source Activity Response Destination
Enter Event Insert Event Added New
1. New Event Admin Database
Details Details Event
Enter Insert
New Added New
2. Customer Admin Customer Database
Employee Customer
Details Details
Enter Insert
New Added New
3. Employee Admin Employee Database
Customer Employee
Details Details
Insert
New Enter New Staff / Added New
4. Requirement Database
Requirement Requirements Admin Requirement
Details
Enter Insert
New Hall Added New Customer /
5. Booking Admin Booking
Booking Booking Database
Details Details
Enter Bill Retrieve Bill Bill Details Customer /

6. Bill Admin
Details Details Retrieved Database
Enter Enter
Staff / Reports Database /
7. Maintenance Maintenance Maintenance
Admin Entered Admin
Records Records
Use Case Diagram
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.
ERD
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.
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 read from top to bottom and have branches and forks to describe conditions
and parallel activities.
Class Diagram
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.
Object Diagram
An Object diagram focuses on some particular set of object instances and

attributes, and the links between the instances. A correlated set of object
diagrams provides insight into how an arbitrary view of a system is expected
to evolve over time. Object diagrams are more concrete than class diagrams,
and are often used to provide examples, or act as test cases for the class
diagrams. Only those aspects of a model that are of current interest need be
shown on an object diagram.
Sequence Diagram
Sequence diagrams belong to a group of UML diagrams called Interaction

Diagrams. Sequence diagrams describe how objects interact over the course of
time through an exchange of messages. A single sequence diagram often
represents the flow of events for a single use case.
State Diagram
State diagrams describe all of the possible states of an object as events occur.
Each diagram usually represents objects of a single class and tracks the
different states of its objects through the system.
III.
System Design
Converting ERD to Tables
Name: Event
Description: The table stores the details of the Event.
Field Type Size
Event_id Int Default
Event_name Varchar 30
Event_date Varchar 30
Event_Time Varchar 30
No of Guest Int Default
Name: Hall
Description: The table stores the details of the Hall.
Field Type Size
Hall_id Int Default
Hall_Name Varchar 30
Hall_Location Varchar 90
Hall_Capacity Int Default
Hall_Cost Numeric 9,2
Name: Package
Description: The table stores the details of the packages.
Field Type Size
Package _id Int Default
Package _Name Varchar 30
Package_Cost Numeric 9,2
Package_Items Varchar 30
Name: Customer
Description: The table stores the details of the Customers.
Field Type Size
Customer_id Int Default
Customer_Name
Field Varchar
Type 30 Size
Customer_Address
Empid Numeric
Int 90
Default
Customer_Contact
Fname Varchar
Varchar 30
30
Customer_Email
Mname Varchar
Varchar 30
30
Lname Varchar 30
Name: Employees
Dob Varchar 20
Gender Varchar 12 Description: The
Cont bigint Default table stores the details of
Email Varchar 30 the Customers.
Addr Varchar 30
Panno Varchar 10
Dept. Varchar 20
Post Varchar 20
Joindate Varchar 20
Sal Numeric 9,2
empQual Varchar 200
empExpr Varchar 200
Name: SweetDish
Description: The table stores the details of the SweetDishes.
Field Type Size
Sdid Int Default
Sdname Varchar 30
Sdprice Varchar 30
Design Class Diagram
a. User Interface Classes
User interface-flow diagrams are typically used for one of

two purposes. First, they are used to model the
interactions that users have with your software, as

defined in a single use case. Because user interface-flow
diagrams offer a high-level view of the interface of a
system. user interface-flow diagrams can be used to
determine if the user interface will be usable. If there are
many boxes and many connections, it may be a signal to
you that your system is too large for people to learn and
understand.
b. Persistent Classes
Persistent Classes are user defined classes whose instances can be stored
in a database. Instances of these classes that represent objects in the
database are called persistent objects or persistent instances. Objects

that do not represent anything in the database are called transient
objects or transient instances.
Component Diagram
The component diagram's main purpose is to show the structural relationships

between the components of a system. Components are wired together by using
an assembly connector to connect the required interface of one component

with the provided interface of another component.
Package Diagram
Package diagrams can use packages that represent the

different layers of a software system to illustrate the layered
architecture of a software system. The dependencies between
these packages can be adorned with labels / stereotypes to

indicate the communication mechanism between the layers.
Deployment Diagram
The nodes appear as boxes, and the artifacts allocated to each

node appear as rectangles within the boxes. Nodes may have
subnodes, which appear as nested boxes. A single node in a

deployment diagram may conceptually represent multiple
physical nodes, such as a cluster of database servers.
Structure Chart(System Level)

IV.
System Coding
Menu Tree
Main
Manage Add New Event Change Password Logout
List of Tables with Attributes and Constrains
Name: Bill
Description: The table stores the details of Bills.
Field Type Size Key Null Description
billid Int defaul Primary Not null Id of the bill
t
bookdate Varchar 20 Null Date of Booking
hallcost Numeric (9,2) Null Cost of hall
packagecos Numeric (9,2) Null Cost of package
t
swtdshcost Numeric (9,2) Null Cost of SweetDish
totalbill Numeric (9,2) Null Total Cost
paymode Varchar 20 Null Mode of Payment
chqno Varchar 20 Null Cheque no.
chqdate Varchar 20 Null Date on cheque
Name: Customer
Description: The table stores the details of Customer.
custid Int default Primary Not null Id of the customer
custfname Varchar 30 Null First name of the customer
custlname Varchar 30 Null Last name of the customer
custcontact1 Varchar 11 Null Contact no. of customer
custcontact2 Varchar 11 Null Contact no. of customer
custemail Varchar 70 Null Email of customer
custadd Varchar 300 Null Customers address
Name: Employee
Description: The table stores the details of Employee.
Empid Int Default Primary Not null Id of the employee
Fname Varchar 20 Null First Name of employee
Mname Varchar 20 Null Middle Name of employee
Lname Varchar 20 Null Last Name of employee
Dob Varchar 20 Null Date of birth of employee
Gender Varchar 12 Null Gender of the employee
Cont Bigint Default Null Contact no. of the employee
Email Varchar 50 Null Email id of the employee
Addr Varchar 200 Null Address of the employee
Panno Varchar 10 Null Pancard no of the employee
Dept Varchar 20 Null Department in which the
employee is working
Post Varchar 20 Null Post on which the employee
is working
Joindate Varchar 10 Null Date of joining of
employee
Sal Numeric (9,2) Null Salary of the employee
empquali Varchar 200 Null Qualification of the
fication employee
Empexpr Varchar 200 Null Experience of the employee
Name: Hall
Description: The table stores the details of Hall.
Hallid Int Defaul Primary Not null Id of the hall
t
Hallname Varchar 30 Null Name of the Hall
Hallloc Varchar 90 Null Location of the Hall
Hallcapacit Int Defaul Null Capacity of the hall
y t
Hallprice Numeric 9,2 Null Price of the hall
Name: Sweet Dish
Description: The table stores the details of Spare Parts.
Sdid Int Default Primary Not null Id of the dish
Sdnam Varchar 30 Null Name of the dish
e
Sdprice Numeric (9,2) Null Price of the dish
Name: Package
Description: The table stores the details of Employee.
Pckid Int Defaul Primar Not Id of the package
t y null
Pckname Varchar 30 Null Name of the Package
Pckprice Numeri 9,2 Null Price of the package
c
Pckit1 Varchar 30 Null Item in the package
Name: Event
Description: The table stores the details of Events.
Eventid Int Default Primary Not null Id of the event
Eventname Varchar 30 Null Name of the Event
Eventsdate Varchar 30 Null Start date of the Event
Eventedate Varchar 30 Null End Date of the event
Eventstime Varchar 30 Null Start time of the Event
Eventetime Varchar 30 Null End time of the event
Eventegues Varchar 30 Null Estimated guest at the
t event
Custid Int default Foreign Null Customer related to the
Event
Hallid Int default Foreign Null Hall booked for the event
Pckid Int default Foreign Null Package booked for the
event
Sdid Int default Foreign Null Sweet dish booked for the
event
Billid Int default Foreign Null Bill no generated for the
event
Program Description and Naming Convention
Sr.No Class Name Page Name Description

1. Splash Splash.vb Splash form
2. Login LoginForm.vb Login form
3. Main MainPage.vb Main form
4. Manage Manage.vb To add, search, delete
& update in All the
Modules of the System
5. Package Details PackageDet.vb To add and update
records in Packages
6. Sweet Dish SweetDishDet.vb To add and update
Details records in Packages
7. Hall Details HallDet.vb To add and update
records in Sweet Dish
8. Employee EmployeeDet.vb To add and update
Details records in Employee
9. Check Hall CheckAvail.vb To Check Availability
Availability of Hall
10. Add Package to AddPackage.vb To Add Package to
Event Event
11. Add Package to AddCustomer.vb To Add Customer to
Event Event
12. System Users Authenticate.vb To add, search, delete
& update System Users
Validations
Login Page Maximum three attempts
Private Sub Login_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Login.Click
con.Close()
Dim cmd As New SqlCommand("select * from login where loginname='"
& TextBox1.Text & "'", con)
Dim sdr As SqlDataReader
Dim b As Boolean
con.Open()
cmd.Connection = con
sdr = cmd.ExecuteReader
b = sdr.Read
If b = True Then
If TextBox1.Text = sdr(0) And TextBox2.Text = sdr(1) Then
If TextBox1.Text = "admin" Or TextBox1.Text = "a" Then
MainPage.Label7.Text = TextBox1.Text
MainPage.LinkLabel1.Enabled = True
MainPage.LinkLabel6.Enabled = False
MainPage.Show()
Me.Hide()
Else
MainPage.Label7.Text = TextBox1.Text
MainPage.LinkLabel1.Enabled = False
MainPage.LinkLabel6.Enabled = True
MainPage.Show()
Me.Hide()
End If
Else
If i > 2 Then
MessageBox.Show("Login Attempts Exceeded", "Login Error",
MessageBoxButtons.OK, MessageBoxIcon.Hand)
End
Else
MessageBox.Show("Wrong Password. Attempts Made " & i,
"Login Error", MessageBoxButtons.OK, MessageBoxIcon.Error)
i=i+1
End If
End If
Else
MessageBox.Show("InValid User. Login Attempts Made " & i, "Data
Read Error")
i=i+1
If i > 3 Then
MessageBox.Show("Login Attempts Exceeded", "Login Error",
MessageBoxButtons.OK, MessageBoxIcon.Hand)
End
End If
End If
sdr.Close()
con.Close()
End Sub
Authenticate Page password
Private Sub TextBox3_TextChanged(ByVal sender As System.Object, ByVal e

As System.EventArgs) Handles TextBox3.TextChanged
len = TextBox3.Text.Length
If len > 16 Then
MessageBox.Show("Password Cannot Be More Than 16 Characters",
"Password Error", MessageBoxButtons.OK, MessageBoxIcon.Information)
End If
End Sub
Private Sub TextBox3_LostFocus(ByVal sender As System.Object, ByVal e
As System.EventArgs) Handles TextBox3.LostFocus
len = TextBox3.Text.Length
If len < 7 Then
MessageBox.Show("Password Cannot Be Less Than 7 Characters",
"Password Error", MessageBoxButtons.OK, MessageBoxIcon.Information)
TextBox3.Text = ""
TextBox3.Focus()
End If
End Sub

If Not (TextBox3.Text = TextBox4.Text) Then
MessageBox.Show("New Passwords Doest Not Match", "MisMatch",
MessageBoxButtons.OK, MessageBoxIcon.Information)
TextBox3.Text = ""
TextBox4.Text = ""
TextBox3.Focus()
End If
End Sub
New Event Date and time, Customer Details, No

field Blanks
Private Sub Button6_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button6.Click
If Label26.Text = "New" Then
If ComboBox1.SelectedItem = "" Then

MessageBox.Show("Event Should be Selected from the Dropdown List",
"Event Not Selected", MessageBoxButtons.OK,
MessageBoxIcon.Information)
Else
If TextBox9.Text = 0 Then
MessageBox.Show("Hall Booking Failed", "Book Hall",
Else
If TextBox21.Text = 0 Then
MessageBox.Show("Total Cost Field Invalid. Please Click on the
Calculate or Select Appropriate Values.", "Invalid Bill",
Else
If DateTimePicker1.Value < Today Then

DateTimePicker1.Value = Today
MessageBox.Show("Date Already Past. Please Select an
Appropriate Date", "Date is InValid", MessageBoxButtons.OK,
Else
If DateTimePicker2.Value < DateTimePicker1.Value Then

DateTimePicker2.Value = DateTimePicker1.Value
MessageBox.Show("Start Date and End Date Conflict.
Please Select an Appropriate Date", "Date is InValid",
Else
If TextBox1.Text = "" Or TextBox2.Text = "" Or TextBox3.Text =

"" Or TextBox4.Text = "" Or TextBox5.Text = "" Or TextBox6.Text = "" Then
MessageBox.Show("Invalid Customer or Empty Customer
Deatils", "Invalid/Blank Customer Detail", MessageBoxButtons.OK,
MessageBoxIcon.Error)
Else
If ComboBox2.SelectedItem = "" Then
MessageBox.Show("Select Payment Mode", "Payment
Mode Not Selected", MessageBoxButtons.OK, MessageBoxIcon.Information)
Else
If ComboBox2.SelectedItem = "Cheque" Then
If TextBox7.Text = "" Or TextBox8.Text = "" Then

MessageBox.Show("Cheque Details Are Blank
or Inapproriate", "Check Cheque Detail", MessageBoxButtons.OK,
Else
If RadioButton1.Checked = True Then
CODINGS..
End If
End If
End If
End If
End If
End If
End If
End If
End If
End If
End If
Email Address , Contact No. Validations have been

done on New Event and New Employee Forms
Example below New Event Form
Private Sub TextBox3_KeyPress(ByVal sender As System.Object, ByVal e As

System.Windows.Forms.KeyPressEventArgs) Handles TextBox3.KeyPress
len1 = TextBox3.Text.Length
If Char.IsDigit(e.KeyChar) = False And Char.IsControl(e.KeyChar) =
False Then
e.Handled = True
MessageBox.Show("Please Enter Numeric Values Only(0 - 9)")
End If
End Sub

If TextBox5.Text <> "" Then
Dim r As Match = Regex.Match(Trim(TextBox5.Text), "^([0-9a-zA-Z]
([-.\w]*[0-9a-zA-Z])*@([0-9a-zA-Z][-\w]*[0-9a-zA-Z]\.)+[a-zA-Z]{2,3})$",
RegexOptions.IgnoreCase)
If r.Success = False Then
MessageBox.Show("Please Enter a Valid Email Address",
"Information", MessageBoxButtons.OK, MessageBoxIcon.Information)
TextBox5.Text = ""
TextBox5.Focus()
Exit Sub
End If
End If
End Sub
Test Cases
Sr. Component Form Test Procedure Expected Actual Result

No Name Name Condition Output
1 Login LoginF To check Enter with It should It display pass
orm.vb login form blank display message
with valid Username, message InValid User.
input Password InValid Login
OR either User. Login Attempts
anyone as Attempts OR
blank OR OR Wrong Wrong
Wrong User Password. Password.
Name or Attempts Attempts
Password & Made Made
click on
login button
2. Event EventD To Check All the It should It display Pass
Record et.vb if All the Required display message
Data Is Fields messages According to
Entered According According to the Error
Correctly to selected the Errors
According Event.
to the
Select
Event
3. Hall Record Hall To Check Enter It should It display Pass
Det.vb if the Characters display messages
Details are in Price or messages Please Enter
Entered capacity Please Enter Numeric
Correctly Column Numeric Values Only(0
OR Blank Values - 9)
Fields Only(0 - 9) OR All
OR All Fields anre
Fields anre Required
Required
4. Package Packag To Check Enter It should It display Pass
Record eDet.vb if the Characters display messages
Details are in Price or messages Please Enter
Entered capacity Please Enter Numeric
Correctly Column Numeric Values Only(0
OR Blank Values - 9)
Fields Only(0 - 9) OR All
OR All Fields anre
Fields anre Required
Required
Sr. Component Form Test Procedure Expected Actual Result

No Name Name Condition Output
5. Employee Employ To Check Enter It should It should Pass
Record eeDet.v if the Characters display display
b Details are in Price or messages messages
Entered capacity Please Enter Please Enter
Correctly Column OR Numeric Numeric
Invalid Values Only(0 Values
Email - 9) Only(0 - 9)
OR Blank OR Please OR Please
Fields Enter a Valid Enter a
Email Valid
Address Email
ORAll Fields Address
anre Required ORAll
Fields anre
Required
Screen Layout
1. Splash Screen
2. Login Form
3. MainPage
4. Manage Form
5. New Event
6. Check Hall Availability

7. Add Package
8. Add Customer
9. Bill
DELETED
10. New Hall
11. New Package

12. New Sweet Dish
13. New Employee

V.
System Implementation
Implementation Procedure
After completion of each module of BanQuet Hall Management System, a

small working model and the required database was created and installed on
the system of the organization.
The Owner and Users were trained to use the system and their responses and
suggestions for updating were noted. The suggestions were considered and
changes were implemented wherever possible. The copy of the updated Model
was once again installed and the same above procedure was repeated with the
full system till the end user was satisfied sufficiently with the system.
An exe file was created by adding the current project to a setup project and
then was built by using build project using build menu.
Once the project has completed with the coding the application, and tested on
multiple machines, it is ready to be deployed. In order to deploy any
application, the user can use the Publish wizard provided by Microsoft.
To Publish your application you have to perform the following steps:-
1) Start the Publish Wizard.

2) Specify the location to publish the application.
3) Select how the user will install the application
4) Where will the application check for the updates.
5) Select finish to Publish your application.
Future Enhancements
No matter how much testing is done before deploying the project, there is
probability of errors in the system. I have tried my best, so that there are no
errors in the system. I will give support to the system and provide some
maintenance work to it as and when required.
System Enhancements
For the system that is developed, there is a chance for more
development.
Some ideas in my mind, of Enhancements of this system are as follow
To design such a system that can be used by many users at same time.
System supporting credit card swapping and banking.
References and Bibliography
Reference:-
1. Beginning Microsoft Visual Basic 2008
Publication - Wiley Publishing, Inc.
By - Thearon Willis and Bryan Newsome.
2. Mastering Microsoft Visual Basic 2008

Publication - Wiley Publishing, Inc.
By Evangelos Petroutsos and Mark Ridgeway.
Softwares:-
1. Microsoft SQL Server 2005 Enterprise Edition
http://www.microsoft.com/download/en/details.aspx?id=21844.
2. Microsoft Visual Studio 2008 Professional Edition.

https://www.dreamspark.com/Product/Product.aspx?productid=1
Websites
1. http://www.samplequestionnaire.com/
2. http://www.dotnetperls.com/datetime-format-vbnet
3. http://www.dotnetperls.com/timespan-vbnet
4. http://www.techrepublic.com/article/working-with-dates-and-times-in-
vbnet/6089546
5. http://www.techrepublic.com/article/calculate-period-of-time-with-
net/5760752
6. http://www.youtube.com/watch?v=acTj3T1PjXQ
7. http://www.exforsys.com/tutorials/vb.net-2005/vb.net-validation.html
8. http://www.daniweb.com/software-development/vbnet/threads/136032
9. http://books.google.co.in/bkshp?hl=en&tab=wp
10.http://www.dreamincode.net/forums/topic/122719-how-to-get-data-
from-datagridview-row-in-the-text-boxes/
11.http://vb.net-informations.com/dataset/vb.net-ado.net-dataset-
tutorial.htm
12.http://msdn.microsoft.com/en-us/library/ms123401.aspx
13.http://msdn.microsoft.com/en-in/ms348103

Banquet Hall Management System: Project Entitled

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Banquet Hall Management System: Project Entitled

Caricato da

Copyright:

Formati disponibili

BanQuet Management System Page

BanQuet Hall Management System

Department of Computer Science

XXXXX of Arts, Science and College, Mumbai-31

XXXXXXXXX COLLEGE OF COMMERCE & ECONOMIC

DEPARMENT OF COMPUTER SCIENCE

Internal Guide Head of Department

College seal External Examiner

I express gratitude and thanks to Almighty God, my Parents and friends

I wish to place on my record my deep sense of gratitude to my project guide,

I also extend my thanks to other Faculty members, lab attendants,

Sr. No. Contents Page No.

XXXXX PARTY HALL is a managed hall that is being used for

Every Organisation needs to manage all the different activities in

Owner manages booking of halls, Checks availability of halls, advance

Categorising pricelist according to customers requirement and for time,

Manager keeps track of all the upcoming functions and arrangements to

Limitations of Present System

Currently the organisation is keeping records in paper and registers. The

Record regarding payments and availability also needs authentication

Proposed system and Its Advantages:

Maintain the records of all the caterers, cleaning, decoration and

Maintaining and printing bills, keeping record of advance and balance

Maintaining the availability of dates of halls.

Easy addition (insertion), retrieval and updating of client details and

Client/Customer feedbacks and suggestions can be entered and taken in

Generate reports on progress of the banquet hall on monthly basis.

Data and Report can be generated as a when required by the user.

An analysis has been done before BanQuet Hall Management System

Technology and system feasibility

XXXXXXX Party Hall is a hall business. It includes registering new

This Software helps the user economically in the following way:

Time-based study: The time required to achieve returns on investment

Total working capacity of the organization will be improved. Also the

A stakeholder is any individual or organization that is affected by the activities

Stakeholders are defined as "those groups without whose support the

The main stakeholders are:

Fact Finding Techniques (Questionnaire)

What is your working process?

Enter Bill Retrieve Bill Bill Details Customer /

Use Case Diagram

A use case is a set of scenarios that describing an interaction between a user

An entity-relationship diagram is a data modeling technique that creates a

A class is a system entity that models a real-world object. A class is made up of

An Object diagram focuses on some particular set of object instances and

Sequence diagrams belong to a group of UML diagrams called Interaction

Converting ERD to Tables

Design Class Diagram

a. User Interface Classes

User interface-flow diagrams are typically used for one of

interactions that users have with your software, as

database are called persistent objects or persistent instances. Objects

The component diagram's main purpose is to show the structural relationships

an assembly connector to connect the required interface of one component

Package diagrams can use packages that represent the

these packages can be adorned with labels / stereotypes to

The nodes appear as boxes, and the artifacts allocated to each

subnodes, which appear as nested boxes. A single node in a

Structure Chart(System Level)

Manage Add New Event Change Password Logout

List of Tables with Attributes and Constrains

Program Description and Naming Convention

Sr.No Class Name Page Name Description