Project Report

On
Online Banquet Booking
System
ACKNOWLEDGEMENT

We have taken efforts in this project. However, it would not have been possible without the
kind support and help of many Faculties. We would like to extend my sincere thanks to all
of them.

We highly indebted to XYZ Group Of Institutions, Ghaziabad for their guidance and
constant supervision as well as for providing necessary information regarding the project &
also for their support in completing the project.

We would like to express my gratitude towards my parents & member of XYZ for their
kind co-operation and encouragement which help us in completion of this project. Last but
not least, many thanks go to the head of the project, Mr. XYZ whose have invested his full
effort in guiding the team in achieving the goal. We have to appreciate the guidance given
by other supervisor as well as the panels especially in our project presentation that has
improved our presentation skills thanks to their comment and advices.

We would like to express our special gratitude and thanks to all above mentioned people for
giving us such attention and time. Our thanks and appreciations also go to our colleague in
developing the project and people who have willingly helped us out with their abilities.
1. INTRODUCTION

1.1. Scope of the Project

The objective of this application is to develop a system that effectively manages all the data
related to the various banquet booking events that take place at the venue. The purpose is to
maintain a centralized database of all banquet event related information. The goal is to
support various functions and processes necessary to manage the data efficiently.

1.2. Existing System

This existing system is not providing secure registration and profile management of all the
users properly. This system is not providing on-line Help. This system doesn’t provide
tracking of users activities and their progress. This manual system gives us very less security
for saving data and some data may be lost due to mismanagement. This system is not
providing event management through internet. This system is not providing proper events
information. The system is giving manual information through the event management
executer.

1.3. Proposed System

The development of this new system contains the following activities, which try to automate
the entire process keeping in the view of database integration approach. This system
maintains user’s personal, and contact details. This system will provide on line help and
search capabilities. User friendliness is provided in the application with various controls
provided by system rich user interface. Authentication is provided for this application only
registered users can access. Banquet event information files can be stored in centralized
database which can be maintained by the system. This system provides the users to manage
the banquet events systematically.
2. SYSTEM ANALYSIS

2.1 FEASIBILITY STUDY

A feasibility study is a high-level capsule version of the entire System analysis and Design
Process. The study begins by classifying the problem definition. Feasibility is to determine
if it’s worth doing. Once an acceptance problem definition has been generated, the analyst
develops a logical model of the system. A search for alternatives is analyzed carefully.
There are 3 parts in feasibility study.

2.1.1 Operational Feasibility

Question that going to be asked are Will the system be used if it developed and implemented.
If there was sufficient support for the project from the management and from the users.
Have the users been involved in planning and development of the Project.

2.1.2 Technical feasibility

Does the necessary technology exist to do what is been suggested Does the proposed equipment
have the technical capacity for using the new system? Are there technical guarantees of
accuracy, reliability and data security? The project is developed on Pentium III with 128 MB
RAM.
The environment required in the development of system is any windows platform.
The observer pattern along with factory pattern will update the results eventually.
The language used in the development is PHP, Apache Server and database as MySQL.

2.1.2 Economical Feasibility

To decide whether a project is economically feasible, to consider various factors as cost

benefit analysis, long-term returns and maintenance costs.
2.2 FUNCTIONAL REQUIREMENTS
Functional requirement defines a function of a software system or its component. A
function is described as a set of inputs, the behaviour, and outputs. Functional requirements
may be calculations, technical details, data manipulation and processing and other specific
functionality that define what a system is supposed to accomplish. Behavioural
requirements describing all the cases where the system uses the functional requirements are
captured in use cases.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the following
modules:

Online Banquet Booking System Module

In OBBS project we use PHP and MySQL database. It has two modules.
1. Admin Module
2. User Module

Admin Module

1. Dashboard: In this section, admin can see all detail in brief like the total services, Total
unread queries, Total read queries, Total new booking, Total Approved booking, Total
Cancelled Booking and Total Event Type
2. Services: In this section, admin can manage services (add/delete).
3. Type of Event: In this section, admin can manage event type (add/delete).
4. Pages: In this section, the admin can manage about us and contact us pages.
5. Booking: In this section, admin can view new, approved, cancelled bookings and also
give a remark.
6. Contact us Queries: In this section, admin can view and maintain the Queries.
7. Reports: In this section, admin can view booking in a particular period.
Search: In this section, admin can search booking details and user queries with the help of
name, mobile number and booking id

Admin can also update his profile, change password and recover password.

User (Unregistered Users): user can view the website and check out the information about
“Online Banquet Booking System” and they can also sent message to administration.

Registered Users: Only registered users can book the banquet and view status of his/her
booking.
Registered users can also update his profile, change password and recover password.

2.3 NON-FUNCTIONAL REQUIREMENTS

Performance Requirements:
Performance is measured in terms of the output provided by the application. Requirement
specification plays an important part in the analysis of a system. Only when the requirement
specifications are properly given, it is possible to design a system, which will fit into
required environment. It rests largely with the users of the existing system to give the
requirement specifications because they are the people who finally use the system. This is
because the requirements have to be known during the initial stages so that the system can
be designed according to those requirements. It is very difficult to change the system once it
has been designed and on the other hand designing a system, which does not cater to the
requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system the system
should be accurate.
The system should be better than the existing system
Reliability:

In this system reliability means the mail which is send by the source must reach the target
user with any modification and accurate.

Security:

The web server and database server should be protected from hacking, virus etc

Portability:

The application will be developed using standard open source software like PHP, Apcahe
web server, MySQL database, Internet Explorer Browser etc these software will work
both on Windows and Linux o/s. Hence portability problems will not arise.

Availability:
This software will be available always.

Maintainability:
In this system the presentation layer is clearly separated from the service layer. So any
modification in future will be done with less effort. The database will be running at the
server. Users access these forms by using the user-ids and the passwords.
2.4 HARDWARE REQUIREMENTS:

Intel P-IV based

Processor : system

Processor Speed : 2.0. GHz

RAM : 1GB

Hard Disk : 40GB to 80GB

2.5 SOFTWARE REQUIREMENTS:

Database : MySQL

Server : Apache

Frontend : HTML

Scripting language : Java Script

IDE : Sublime

Technology : PHP
3. SYSTEM DESIGN
3.1 UML DIAGRAMS

The unified modelling language allows the software engineer to express an analysis model
using the modelling notation that is governed by a set of syntactic semantic and pragmatic
rules.

3.1.1 Class Diagram:

The class diagram shows a set of classes, interfaces, collaborations and their relationships.

Fig: 3.1.1.1 Class diagram for on OBBS

3.1.2 Use case diagrams:

Use case diagram consists of actors, use cases and their relationships. These diagrams are
especially important in organizing and modelling the behaviours of a system.

Visit Website

Signup

Login

View Service

Enquiries

Book Banquet

USER
View Booking
Status

Update Profile

Change Password

Use case diagram for user

Sign in

Dashboard

My Profile

Change Password

Manage Services
(Add / Delete)

Manage Event Type

Admin
(Add / Delete)

Manage Bookings
(Approved / Cancelled)

Manage Queries

Search
Booking/Queries

Generate Report

Website Settings

Use case diagram for Administrator

3.1.2 Data Flow Diagram:

Zero Level DFD:

Enquiry
Management

Event Type User

Management
OBBS

Service Booking
Management Management
Login
Management
First Level DFD:

Manage Enquiries Generate Report

Login Management Search Booking

System User Manage Services

OBBS
Management

Manage Pages

Registration
Management
Manage Booking
Second Level DFD

Manage
Services

Login to Check
Admin System Roles of Manage Event
Access type

Manage Pages

Manage
Booking

Forgot Manage
Password Check Manage Enquiries
Credential Modules

Manage Report

Search Booking

Login to Check Change

User System Roles of Password
Access

Change Profile

Send Booking
Request

Forgot Check
Password Credential Create Enquiries

Manage
Modules View Services

View Pages
3.2 ER-DIAGRAM

ER diagram for Online Banquet Booking System

3.3 Tables

The data in the system has to be stored and retrieved from database. Designing the database is

part of system design. Data elements and data structures to be stored have been identified at

analysis stage. They are structured and put together to design the data storage and retrieval

system.

A database is a collection of interrelated data stored with minimum redundancy to serve many

users quickly and efficiently. The general objective is to make database access easy, quick,

inexpensive and flexible for the user. Relationships are established between the data items and
unnecessary data items are removed. Normalization is done to get an internal consistency of data

and to have minimum redundancy and maximum stability. This ensures minimizing data storage

required, minimizing chances of data inconsistencies and optimizing for updates. The MySQL

database has been chosen for developing the relevant databases.

Online Banquet Booking System (OBBS) contains 7 MySQL tables:

tbladmin : This table store the admin login details

tblbooking: This table store the booking details.

tbleventtype: This table store the type of event details.

states: This table store the sates name.

cities: This table store the cities name on the basis of states.

tblpage: This table about us and contact us detail.

tblservice: This table store the details of banquet services.

tbluser: This table store the details of registered user

tblcontact: This table store the details of enquires.

4. IMPLEMENTATION

INTRODUCTION:

Implementation is the stage of the project when the theoretical design is turned out into a
working system. Thus, it can be considered to be the most critical stage in achieving a
successful new system and in giving the user, confidence that the new system will work and
be effective. The implementation stage involves careful planning, investigation of the
existing system and its constraints on implementation, designing of methods to achieve
changeover and evaluation of changeover methods.

4.1 TECHNOLOGIES USED

Programming Language

PHP

 PHP stands for PHP: Hypertext Pre-processor

 PHP is a server-side scripting language, like ASP
 PHP scripts are executed on the server
 PHP supports many databases (MYSQL, Informix, Oracle, Sybase, Solid, Generic
ODBC, etc.)
 PHP is an open source software

 PHP is free to download and use

MYSQL

 MYSQL is a database server

 MYSQL is ideal for both small and large applications
 MYSQL supports standard SQL
 MYSQL compiles on a number of platforms

 MYSQL is free to download and use

CSS

 Cascading Style Sheets (CSS)

 Simple mechanism
 Easy for adding style (e.g., fonts, colors, spacing) to Web documents.
5. TESTING

Introduction

The purpose of testing is to discover errors. Testing is the process of trying to

discover every conceivable fault or weakness in a work product. It provides a
way to check the functionalities of components, sub assemblies, and/or a finished
product it is the process of exercising software with the intent of ensuring that the
software system meets its requirements and user expectations and does not fail in
an unacceptable manner. There are various types of tests. Each test type addresses
a specific testing requirement.

5.1 Types of Testing

5.1.1 Unit Testing
Unit testing focuses verification effort on the smallest unit of software design, the
module. The unit testing, we have is white box oriented and some modules the
steps are conducted in parallel.

5.1.2. Integration Testing

Testing is done for each module. After testing all the modules, the modules are
integrated and testing of the final system is done with the test data, specially
designed to show that the system will operate successfully in all its aspects
conditions. Thus the system testing is a confirmation that all is correct and an
opportunity to show the user that the system works. The purpose of integration
testing is to verify functional, performance and reliability requirements placed on
major design items. These "design items", i.e. assemblages (or groups of units), are
exercised through their interfaces using black box testing, success and error cases
being simulated via appropriate parameter and data inputs. Simulated usage of
shared data areas and inter-process communication is tested and individual
subsystems are exercised through their input interface.

Test cases are constructed to test that all components within assemblages interact
correctly, for example across procedure calls or process activations, and this is done
after testing individual modules, i.e. unit testing.
5.1.5 System Testing

System testing ensures that the entire integrated software system meets requirements. It tests
a configuration to ensure known and predictable results. An example of system testing is the
configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

White Box Testing

This type of testing ensures that

All independent paths have been exercised at least once
All logical decisions have been exercised on their true and false sides
All loops are executed at their boundaries and within their operational bounds All

internal data structures have been exercised to assure their validity.

To follow the concept of white box testing we have tested each form .we have created
independently to verify that Data flow is correct, All conditions are exercised to check their
validity, All loops are executed on their boundaries.

Basic Path Testing

Established technique of flow graph with Cyclometer complexity was used to derive test
cases for all the functions. The main steps in deriving test cases were:

Use the design of the code and draw correspondent flow graph.

Conditional Testing

In this part of the testing each of the conditions were tested to both true and false aspects.
And all the resulting paths were tested. So that each path that may be generate on particular
condition is traced to uncover any possible errors.

Data Flow Testing

This type of testing selects the path of the program according to the location of
Definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of
testing. These were particularly useful in nested statements.

Loop Testing

In this type of testing all the loops are tested to all the limits possible. The following
exercise was adopted for all loops: All the loops were tested at their limits, just
above them and just below them. All the loops were skipped at least once. For
nested loops test the inner most loop first and then work outwards. For concatenated
loops the values of dependent loops were set with the help of connected loop.
Unstructured loops were resolved into nested loops or concatenated loops and tested
as above. Each unit has been separately tested by the development team itself and all
the input have been validated.
6. Output Screen of Project

Home Page
About Us

Services
Contact Us

User Registration
Login Panel

Forgot Password
User Profile

Change Password
Book Services

Booking History
View Booking History Details

Admin Panel

Login Panel
Profile

Change Password
Add Services

Manage Services
Add Event Type

Manage Event Type

About Us Page

Contact Us
New Booking

View New Booking Details

Approved Booking

View Approved Booking Details

Cancelled Booking

View Cancelled Booking Details

Unread Enquiries

View Enquiries
Between Dates Report

Between Dates Report Details

Search Booking
7. CONCLUSION

While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and resources – that
would generate a proper System While making the system, an eye has been kept on making
it as user-friendly, as cost-effective and as flexible as possible. As such one may hope that
the system will be acceptable to any user and will adequately meet his/her needs. As in case
of any system development processes where there are a number of shortcomings, there have
been some shortcomings in the development of this system also. The project is still under
modification.
8. FUTURE SCOPE

The scope of the project includes that what all future enhancements can be
Done in this system to make it more feasible to us:-

• Databases for different products range and storage can be provided.

• Multilingual support can be provided so that it can be understandable by the
person of any language.
• More graphics can be added to make it more user-friendly and
understandable.
• Manage & backup versions of documents online.
9. REFERENCES

 www.w3schools.com
 php.net
 en.wikipedia.org/wiki/PHP
 www.hotscripts.com/category/php/
 www.apache.org
 www.mysql.com/click.php?e=35050