Online Venue Reservation and Event Management System

By
Somaia Sultana Bithy
(142-35-706)

The project has been submitted in partial fulfillment of the requirement for the degree of
Bachelor of Science in Software Engineering

Department of Software Engineering

DAFFODIL INTERNATIONAL UNIVERSITY
Fall – 2018
 APPROVAL
This Project titled “Online Venue Reservation and Event Management System”, submitted by Somaia
Sultana Bithy, ID: 142-35-706 to the Department of Software Engineering, Daffodil International
University has been accepted as satisfactory for the partial fulfillment of the requirements for the degree of
B.Sc in Software Engineering and approved as to its style and contents.

BOARD OF EXAMINERS

iii ©Daffodil International University

 DECLARATION

We hereby declare that we have taken this project under the supervision of Afsana Begum, Senior
Lecturer, Department of Software Engineering, Daffodil International University. We also declare
that neither this thesis/project nor any part of this has been submitted elsewhere for award of any degree.

iv ©Daffodil International University

 ACKNOWLEDGEMENT

First of all I would like to express my cordial gratefulness to Almighty ALLAH for
HIS kindness, for which I successfully completed my project within time.

I fell grateful to express my boundless honor and respect to my supervisor

Afsana Begum, Senior Lecturer, Department of Software Engineering,
Daffodil International University for her deep knowledge & keen interest in the
field of Software Development that influenced me to carry out of this project.
Her endless patient help, friendly support, great enthusiasm and extensive
knowledge, which have guided me throughout our work and showed the path of
achievement.

I would like to express my heartiest gratitude to Dr. Touhid Bhuiyan, Head,

Department of Software Engineering, Daffodil International University for his
kind help to finish my project

I am also very grateful to all of our Teachers and friends for their valuable
suggestion help and support during the completion of our project, for his kind help to
finish our project and also to other faculty member and the staff of Software
Engineering Department of Daffodil International University.

I would like to thank my entire course mate in Daffodil International University,

who took part in this discuss while completing the course work.

And at last but not the least I must acknowledge with due respect the constant
support and patience of our family members for completing this project.

v ©Daffodil International University

 ABSTRACT

This project entitled “Online Venue Reservation and Event Management

System” is a web based system that reserve hall booking via online will work for
a user or client rather it will be made for an admin.

Admin can control everything. User can be view venue without login when he
booked venue user must have registered and then login in to the system. He can view
with many filter or search that he like. He can be booking his venue that he wants to
choose. And then everything goanna be manual. He also getting food service if he
wants when booking venue. Admin can have approved and send a date for user
booking information to his mail.

The modern technology is used to implement the software to make it more

secured. The technology is Asp.net and MSSQL. Some client side scripts have
also been used to make it user friendly.

vi ©Daffodil International University

 TABLE OF CONTENTS

APPROVAL .........................................................................................................................................................iii
DECLARATION .......................................................................................................................................................... iv
ACKNOWLEDGEMENT..................................................................................................................................... v
ABSTRACT ......................................................................................................................................................... vi
TABLE OF CONTANT ...................................................................................................................................... vii
LIST OF TABLE ................................................................................................................................................... x
LIST OF FIGURE ................................................................................................................................................ xi
Chapter 1: Introduction ................................................................................................................................. 1
1.1 Purpose.......................................................................................................................................... 1
1.2 Stakeholder ......................................................................................................................................... 1
1.3 Technologies ....................................................................................................................................... 2
1.4 Project Schedule.................................................................................................................................. 3
Chapter 2: Requirement Analysis and Design ........................................................................................ 4
2.1 Requirement Collection ...................................................................................................................... 4
2.2 Requirement Analysis ......................................................................................................................... 4
2.2.2 Functional Requirements ............................................................................................................. 5
2.3 Software Requirement Analysis.......................................................................................................... 5
2.3.1 Objective/Goals............................................................................................................................ 5
2.4 Software Requirement Specification .................................................................................................. 6
CHAPTER-3: SYSTEM DESIGN AND DEVELOPMENT ................................................................................. 7
3.1 Entity Relationship Diagram (ERD) ................................................................................................... 7
3.2 Use Case Diagram (UCD)................................................................................................................... 8
3.3 Data Flow Diagram (DFD) ................................................................................................................. 9
3.4 Sequence Diagram ............................................................................................................................ 11
3.5 Activity Diagram .............................................................................................................................. 12
3.6 Database Schema Diagram ............................................................................................................... 13
CHAPTER-4 TESTING ............................................................................................................................. 14
4.1 Importance of Testing ....................................................................................................................... 14
4.2 Testing Parts...................................................................................................................................... 14
4.3 Testing Environment ......................................................................................................................... 14
4.4 Test Plan Strategy ............................................................................................................................. 14
4.5 Test Cases ......................................................................................................................................... 15
4.5.1 Test Case Module-1: - Sign Up .................................................................................................. 15

vii ©Daffodil International University

 4.5.2. Test Case Module-2: - Sign In .................................................................................................16
4.5.3. Test Case Module-1: - Venue Booking ............................................................................... 18
4.5.3. Test Case Module-1: - Food item Added ............................................................................ 18
CHAPTER 5: USER MANUAL ................................................................................................................. 19
5.1 Home Page ........................................................................................................................................ 19
5.2 Login page ........................................................................................................................................ 20
5.3 User Registration Page ...................................................................................................................... 20
5.4 Search Venue .................................................................................................................................... 21
5.5 Booking Page .................................................................................................................................... 21
5.6 Booking Confirm .............................................................................................................................. 22
CHAPTER 6: CONCLUSION .................................................................................................................... 23
5.1 Critical Evolution and Team Attainment ........................................................................................ 23
5.2 Limitations ........................................................................................................................................ 23
5.3 Future Scope ..................................................................................................................................... 23
5.4 Final Synopsis ................................................................................................................................... 23
Chapter 7: References ................................................................................................................................. 24

ix ©Daffodil International University

 LIST OF TABLE
Table No Name Page
1.1 User Description 02
2.1 Project Schedule 03
3.1 Functional Requirement 05
3.2 Software Requirement Specification 06
4.1 Test Case Module - 1 15
4.2 Test case - 1 15
4.3 Test Case Module - 2 16
4.4 Test Case - 2 16
4.5 Test Case Module - 3 17

4.6 Test Case - 3 17

4.7 Test Case Module - 4 18
4.8 Test Case - 4 18

x
 LIST OF FIGURE
Figure No Figure Name Page
3.1 Entity Relationship Diagram 7
3.2 Use Case Diagram. 8
3.3 Context Diagram 9
3.4 Data Flow Diagram 9
3.5 Sequence Diagram 11
3.6 Activity Diagram 12
3.7 Database schema Diagram 13
5.1 Home Page 19

5.2 Login page 20

5.3 Create Account 20
5.4 Search venue 21
5.5 Booking Page 21
5.6 Booking Confirm 22

xi
 Chapter 1: Introduction
Online Venue Reservation and Event Management System is a place for building an online
venue reservation and food item serve system. In this platform user can booking his/her preferred
location of venue also he can be taking food service what he wants. With Online Venue
Reservation and Event Management System, user get both an eye-catching mobile friendly
storefront and an admin panel with tons of features and as a result, that’s the project want to
make this vision.

1.1 Purpose
Web based reservation system make easier to user choosing venue via online. Online constructed
venue reservation in light of the web is no exceptional case. The goal of this application is to
develop an electronic interface for on the web retailers. The system would be anything besides
hard to use and from this time forward make the purchasing information flawless for the
customers. The goal of this application is:

• To develop an easy to use electronic interface where client can search for venue, venue
location, booking costs, see a whole depiction of the things and reserving for the things.
• A web look instrument that gives a basic and supportive way to deal with output for
venue specific to their prerequisites. The web searcher would list a plan of venue and
food item in perspective of the look term and the customer can also direct the once-over
in light of various parameters.
• A user can see the aggregate detail of the venue close by various pictures and moreover
observe the client's studies of the thing. They can moreover make their very own studies.
• User can drive for test. He can apply for driving test to know what he want.

1.2 Stakeholder
Situation is a methodology used in the midst of need examination to delineate the usage of
proposed system. Scenario is a tale about proposed system which depicts an audit of whole
structure. The Scenario of proposed system is given underneath:

1 ©Daffodil International University

 There are three types. Admin, Customer and Venue Manager.
• Customer
• Venue Manager
• Admin

Users Description:

User Description
Admin has all entrance. He/she can oversee venue and food item
and also Role and everything. He can approved all thing that user
Admin want to do.
Venue Manager add his venue information and food item and
Venue Manager also approved all type of confirmation.

The user can visit the website and search for their desired venue
User and can booking also. User can apply for food service.

1.3 Technologies
Here, some tools are used for this project. Now, that is given below:

• Hardware Requirement Tools:

• Processor: Core i2 or upper

• Ram: 2 GB or upper
• Hard Drive: 128GB or upper

• Software Requirement Tools:

• Web-Technology: Asp.net MVC 5

• Database: SQL Server
• IDE: Visual Studio
• UI : HTML5, CSS3, Bootstrap 3.7, JavaScript
• Web-Server: IIS Server

2 ©Daffodil International University

 1.4 Project Schedule

Figure 1.1: Project Schedule

3 ©Daffodil International University

 Chapter 2: Requirement Analysis and Design

2.1 Requirement Collection

Necessities are the commence of all item applications that tell what the structure does. For all
venture it require great prerequisite detail. On the off chance that a prerequisite isn't great, this
undertaking can be crush. For a decent application great prerequisite need. There are some
prerequisite that utilization for this application. It require practical and non-useful prerequisites.
Since this prerequisite based with this framework.

2.2 Requirement Analysis

After gathering requirement from User and analysis that requirement, which is really necessary.
Software requirement analysis is essential piece of out undertaking. In the event that prerequisite
of venture is clear, an undertaking should be possible effortlessly. Without requirement analysis a
system cannot get proper platform. If requirement is not good for any system will be crashed. In
this project we make good analysis of our requirements and check what user want and why. How
can solve their necessity.

Methodology: I used agile model. Because, I collected requirement and change it any time as
per changing requirement.

4 ©Daffodil International University

 2.2.2 Functional Requirements

Table 2.1: Functional Requirement

No. Description
1 Signup Customer and venue Manager account
2 venue should be categorically viewed (Name, location, Price, Image,
availability)
3 Admin can view all venue and food item, resources, User information
4 Admin can add, delete or edit any resources
5 Venue Manager can approve request that what user apply for
6 Venue Manager can approved his venues booking
7 Admin can add, or edit any information of Customer
8 Customer can booking venue with food item.
9 Customer can see all available venue and food item on the website
10 Customer can search venue or Food Item
11 Customer must be paid 20% amount of total cost of reservation when he confirm
booked venue.

2.3 Software Requirement Analysis

2.3.1 Objective/Goals
• Automatically handle all process
• Admin can handle all thing
• Add to View available venue on the site
• Add to Search desired venue and food item by its Name, location, Price, category.
• Add to new venue information.
• Add to new resources
• Add to update resource, venue and customer information automatically in the database
• Add to new user.

5 ©Daffodil International University

 2.4 Software Requirement Specification
Software Requirement Specification is a depiction of full software framework requirements.
Software Requirement Specification depicts the conduct of software from client's perspective.
The predetermined requirements are appeared in following table dependent on module.

Table 2.2: Software Requirement Specifications

No. Name Description Type

1 Login & Registration All User Must Be Registration before login Functional

2 Venue Booking User Booked their choosing venue Functional

3 Add/Edit Venue Info Venue Manager Add / Edit His venue info Functional

4 Food Booking Used Booked food desired venue Functional

5 Add/Edit Food Info Venue Manager Add/Edit Food Info Functional

6 Online Payment User Pay of booking money through online Functional

7 Responsive Web Page Design Must be Responsive Non-

Design Functional
8 Speedy Page Loading All Page Load should be minimal time Non-
Functional
9 Security System Must be Secure Non-
Functional

6 ©Daffodil International University

 CHAPTER 3: SYSTEM DESIGN AND DEVELOPMENT

3.1 Entity Relationship Diagram (ERD)

An entity relationship model, also called an entity-relationship (ER) diagram, is a graphical
representation of entities and their relationships to each other, typically used in computing in
regard to the organization of data within databases or information systems.

Figure 3.1: Entity Relationship Diagram

7 ©Daffodil International University

 3.2 Use Case Diagram (UCD)

Figure 3.2: Use Case Diagram.

8 ©Daffodil International University

 3.3 Data Flow Diagram (DFD)
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modelling its process aspects. A DFD is often used as a preliminary step to
create an overview of the system, which can later be elaborated.

Context Diagram:

Figure 3.3: Context Diagram

Context level diagram just show the task happening in the whole system, it’s actually shows the
input what is the output for the input.

9 ©Daffodil International University

 First Level DFD:
First level DFD shows the major steps that have to complete to buy a product. Initially customer
visit the website, search the product by category, manufacturer and top selling, show the details
of the product, select payment method, finally the product delivere
d by the company agent.

Figure 3.3: Data Flow Diagram

10 ©Daffodil International University

 3.4 Sequence Diagram

Figure 3.5: Sequence Diagram

11 ©Daffodil International University

 3.5 Activity Diagram

Figure 3.6: Activity Diagram

12 ©Daffodil International University

 3.6 Database Schema Diagram

Figure 3.7: Database schema Diagram

13 ©Daffodil International University

 CHAPTER-4: TESTING

4.1 Importance of Testing

• Testing is discover mistakes on this application program
• It is utilized for both approval and confirmation to build up an item
• It is utilized for powerful blunder recognizable proof
• It ensure client unwavering quality and fulfillment
• Make beyond any doubt nature of this application
• Make beyond any doubt incredible execution of this application
• Required to remain in software business

4.2 Testing Parts

• Sign Up
• Sign In
• Venue Booking
• Food item service

4.3 Testing Environment

• Test data
• Requirements
• Application
• Operating System(OS)
• Database server
• Browser

4.4 Test Plan Strategy

A testing technique is a general way to deal with the testing procedure as opposed to a strategy
for contriving specific framework or part tests. Diverse testing techniques might be embraced
relying upon the sort of framework to be tried and the improvement procedure utilized.

14 ©Daffodil International University

 4.5 Test Cases

4.5.1 Test Case Module-1: - Sign Up

Table 4.1: Test Case Module - 1

Test Case ID: TC1 Test Design by: Somaia Sultana Bithy

Test Priority: High Test Design Date: 24-11-2018

Module Name: Sign Up Test Execute by: Somaia Sultana
Bithy
Description: This section covers the functionality
of registering new users. Test Execute Date: 26-11-2018

Precondition: User has no precondition

Dependencies: Enter input required information

Table 4.2: Test case - 1

Step Test cases Test Data Expected result P/f Actual result

Enter empty value for Display error

01 any required Field Message Pass Display error message

Enter non-numeric Display error message Display error message

value in Contact “Enter valid contact “Enter valid contact
02 Number field Rdfghb number” Pass number”

Enter password less Display error message Display error message

than 6 characters “Password length “Password length must
03 Long 123456 must be 6 characters” Pass be 6 characters”

Enter different email Display error message

format instead of gmail.com. “Invalid email Display error message
04 [email protected] sg address” Pass “Invalid email address”

Display message Display message

New user “Submitted “Submitted
05 Registration Successfully’’ Pass Successfully’’

15 ©Daffodil International University

 4.5.2. Test Case Module-2: - Sign In

Sign In
Table 4.3: Test Case Module - 2

Test Case ID: TC2 Test Design by: Somaia Sultana Bithy

Test Priority: High Test Design Date: 24-11-2018

Module Name: Sign In Test Execute by: Somaia Sultana Bithy
Description: Test login process of Infrastructure
Assistant Test Execute Date: 24-11-2018

Precondition: User must be registered already

Dependencies: Input correct user name & password.

Table 4.4: Test Case - 2

Step Test cases Test data Expected result Actual result P/F
Enter empty value
for user name & The Email field Is The Email field
01 Password Required Is Required Pass
Enter correct value
for user name & User name
02 Password & Password Accept Accept Pass
Enter wrong value
for user name & User name Invalid Login Invalid Login
03 Password & Password Attempt Attempt Pass
Clicking on Clicking on
submit button submit button
After giving input directed on directed on
04 click submit Button another page another page Pass

16 ©Daffodil International University

 4.5.3. Test Case Module-1: - Venue Booking

Table 4.5: Test Case Module - 3

Test Case ID: TC3 Test Design by: Somaia Sultana

Bithy
Test Priority: High Test Design Date: 24-11-2018
Test Execute by: Somaia Sultana
Module Name: Test Drive Apply Bithy
Description: Test the Infrastructure creation
process. Test Execute Date: 26-11-2018

Precondition: User must be logged in already.

Dependencies: input required field and write event

query.

Table 4.6: Test Case - 3

Test
Step Test cases data Expected Actual result P/F
result
Enter empty value This field is This field is
01 for any required Required Required Pass
Field
Enter correct
02 value accept Accepted Pass
for all required
field
Write Apply Accept any type Accept input
03 Description of input method Pass
method
Clicking submit Clicking on
Write all query & button directed submit button
04 click submit on another page directed on Pass
button another page

17 ©Daffodil International University

 4.5.3. Test Case Module-1: - Food item added

Table 4.7: Test Case Module - 4

Test Case ID: TC3 Test Design by:Somaia Sultana

Bithy
Test Priority: High Test Design Date: 24-11-2018
Test Execute by:Somaia Sultana
Module Name: Test Drive Apply Bithy
Description: Test the Infrastructure creation
process. Test Execute Date: 26-11-2018

Precondition: User must be logged in already. User also must have booked any
venue for reservation.
Dependencies: input required field and write event query.

Table 4.8: Test Case - 4

Tes
Step Test cases t Expected result Actual result P/F
dat
a
Enter food item
search without Item page
01 any venue not Item page not Pass
reservation found found
Cancel reservation Food Item Food Item service
02 venue service Automated cancel Pass
Automated
cancel

18 ©Daffodil International University

 CHAPTER 5: USER MANUAL

5.1 Home Page

This page will appear first to the users. From this page client can find their desire
product. If the client can’t his desire product then he can search his desire
product by typing the product name in the search bar.

Figure 5.1: Home Page

19 ©Daffodil International University

 5.2 Login page

Figure 5.2: Login page

5.3 User Registration Page

Figure 5.3: Create Account

20 ©Daffodil International University

 5.4 Search Venue

Figure 5.4: Search venue

5.5 Booking Page

Figure 5.6: Booking Page

21 ©Daffodil International University

 Figure 5.7: List of Food

5.6 Booking Confirm

Figure 5.8: Booking Confirm

22 ©Daffodil International University

 CHAPTER 6: CONCLUSION
5.1 Critical Evolution and Team Attainment

On the chance that client isn't happy with this venue booking system he/she
ought to have issue with this application. Client must know English since
entire application is in English. He/she ought to have great information of web
surfing.

5.2 Limitations
We are endeavoring to satisfy all requirements of users. A few things are not
done here. Something like voice, visiting and video conferencing are not done.
The framework is produced for just booking venue reservation and food item
service strategy and after booking almost everything are manual. There is no
service that enables user to pay, send money, and accept payments. The person
have to have web get admission to with a purpose to use the machine. The main
hazard behind enforcing the project is security. If anyone hacks the system then
it'll be a total ailment. So throughout improvement it'll be considered one of our
fundamental worries.

5.3 Future Scope

Every system has future scope. In this system we have some features that users
like comfortably. But we want to increase its performance and other things.
This system will use SMS confirmation in future. Booking is easier and
smooth for user. User satisfaction is everything for this system. System will
get users response what they feel about this system and how it improved. If
user get help from this it can be improve in future.

5.4 Final Synopsis

It has been a splendid pleasure to paintings in this assignment. This challenge
assist to understand new generation. This assignment element is a few kind of
bizarre factor but this is supporting college students. Helping human beings
with developing an application make a higher world.

23 ©Daffodil International University

 Chapter 7: REFERENCES

[1] Database System Concept By Silberschartz, koth, Sundarshan

ISBN 007124476-X

[2] www.w3schools.com (30.11.2018)

[3] http://www.tutorialsteacher.com/mvc/asp.net-mvc-tutorials (30.11.2018)

[4] https://docs.microsoft.com/en-us/aspnet/(11.12.2018)
[5] https://www.asp.net/mvc (25.09.2018)

[6] https://en.wikipedia.org/wiki/Loan (30.09.2018)

[7] https://onlinelendingsoftware.com/?gclid=EAIaIQobChMI74OI
va- 92wIV2CMrCh2kvwSDEAAYAiAAEgIFaPD_BwE
(30.09.2018)

[8] Draw.io, ‘Design system diagram’, [Online]. Available:

https://www. draw.io/ (10.11.2018)

24 ©Daffodil International University