Premier University

Department of Computer Science & Engineering

Final Year Project Report

On

“Online Platform for Event Management”

Supervised By:
Md. Ariful Islam Bhuyan
Lecturer
Department of Computer Science & Engineering
Premier University, Chattogram

Submitted By:
Muhammad Muktiar Hossen (1603110201249)
Emon Paul (1603110201250)
Mohammad Karim (1603110201253)

Submitted as partial fulfillment for the degree of

Bachelor of Science in Computer Science & Engineering
1
 Premier University
Department of Computer Science & Engineering

DECLARATION

This Project report is submitted to the Department of Computer Science & Engineering, Premier
University, Chattogram, in partial fulfilment of the requirements for the degree of Bachelor of
Science. So, we hereby, declare that this project work entitled “Online Platform for Event
Management” is our original work. This project report, neither in whole, nor in part, has been
previously submitted for any degree.

Muhammad Muktiar Hossen Emon Paul

ID: 1603110201249 ID: 1603110201250
Email: muktiarh02@gmail.com Email: emonpaul0302@gmail.com

Mohammad Karim
ID: 1603110201253
Email: kmd4890@gmail.com

2
 Premier University
Department of Computer Science & Engineering

CERTIFICATE OF APPROVAL

This project titled “Online Platform for Event Management” submitted by Muhammad
Muktiar Hossen (1603110201249), Emon Paul (1603110201250), Mohammad Karim
(1603110201253) has been accepted as satisfactory in fulfillment of the requirements for the
degree of Bachelors of Science in Computer Science and Engineering (CSE) to be awarded By
Premier University, Chattogram.

Prof. Dr. Taufique Sayeed

Chairman
Department of Computer Science & Engineering
Premier University, Chattogram (Signature and Date)

Md. Ariful Islam Bhuyan

Lecturer
Department of Computer Science & Engineering
Premier University, Chattogram (Signature and Date)

3
 ACKNOWLEDGEMENT

Firstly, we would like to thank the Almighty God who provided us the opportunity to study in
Premier University, Chattogram and then blessed us the with the most precious gift of physical
and mental health during the whole study period.

We would like to take the opportunity to express our humble gratitude to our honorable chairman
Department of CSE Prof. Dr. Taufique Sayeed and, supervisor Md. Ariful Islam Bhuyan.
Premier University, Chattogram. Under those supervision, we have completed this project
successfully. Their constant guidance and willingness made us understand this project and its
manifestation in great depth of knowledge also helped us to complete the assigned task. Their
endless support, cooperativeness, inspiration, outstanding guidance, constructive criticism and
fantabulous suggestions throughout the progress of our work which helped us make this work far
better. We are cordially grateful to having them as our teacher and supervisor.

Last but not the least we would like to thank our parents. We thank our family for their love,
their moral and financial support they had given us. We are really grateful to our friends,
classmates, seniors and lab assistant, who gave us their unlimited support and help in each and
every aspect. We are really fortunate to have nice human being like them beside us.

4
 ABSTRACT

Event Management is a project management application for creating and developing large and
small events. Events such as conferences, ceremonies, formal parties, concerts, and conferences.
The last few years have passed rapidly growth of the event management industry. In light of
existing system issues related to event management, we developing web applications for event
management. Users can access this application from any device. The application is mainly
focused on birthday parties, wedding parties, and social events. The application will be
developed using HTML, CSS, Bootstrap and the back end will be managed in PHP and SQL
databases. The application will have an easy and feasible UI for all types of users. Users need to
Login at the initial phase. The core phase of the application will display a list of the event`s
service details. Users can select various packages under various services, according to their
desires. They can also know how much cost if they want to organize their desired event. These
details will further contain a description of the event, its exact location, date & time. After that,
the user can place the order. These details are first checked by the administrator to comply with
the security protocol. In this project, we present a web application to make it easier for a layman
to plan an event in a hassle-free manner. This application will assist them in planning a
successful and fun event.

5
 Table of Contents

Chapter Page
Chapter 1: Introduction 11

Introduction 11

1.2 Motivation 11

1.3 Objective 12

Chapter 2: Literature Review 13

2.1 Related Work 13

Chapter 3: Methodology 14

3.1 Flow Chart 14

3.1.1 Purpose of Flow-Chart 14

3.1.2 Flow-Chart for Admin 15
3.1.3 Flow-Chart for User 16
3.1.4 Flow-Chart for Company User 17
3.1.5 Flow-Chart for Dealer 18

3.2 System Requirements 19

Chapter 4: Design and Analysis 20

4.1 Waterfall Model 20

4.2 Data Flow Diagram 22

4.3 Use Case Diagram 26

4.4 Activity Diagram 28

4.5 Class Diagram 32

4.6 ER Diagram33

6
Chapter Page
Chapter 5: Implementation 35

5.1 Web Development & Design Module 35

5.1.1 Frontend 35
5.1.2 Backend 35

5.2 Implementation 36

5.2.1 Home Page 36

5.2.2 Sign Up Page 37
5.2.3 Login Page 38
5.2.4 Service Page 40
5.2.5 Package Page & Cart 41
5.2.6 Checkout Page 42
5.2.7 Your Orders Page 43
5.2.8 Admin Dashboard 43
5.2.8.1 Add Service Category 44
5.2.8.2 Add Service 45
5.2.8.3 All Service 46
5.2.8.4 Add Package 47
5.2.8.5 All Packages 48
5.2.8.6 All User (Customers) Orders 49
5.2.8.7 Add Users (Customers) 50
5.2.8.8 All Users (Customers)51
5.2.8.9 Add Company Users 52
5.2.8.10 All Company Users 53
5.2.8.11 Add Dealer Category 54
5.2.8.12 Add Dealer 55
5.2.8.13 All Dealer 56
5.2.8.14 All Dealer Services & Place a Dealer Order 57
5.2.8.15 All Dealer Orders 58
5.2.9 Company Users Orders 59
5.2.10 Dealer Order Handle 60
5.2.11 Change Status 61
5.2.12 Results 61

Chapter Page

7
Chapter 6: Conclusion & Future Work 62

6.1 Conclusion 62

6.2 Future Work 62

References 63

Appendix 64

8
 List of Figure

Figure 3.1.2 Admin’s Flowchart 15

Figure 3.1.3 User’s Flowchart 16

Figure 3.1.4 Company User’s Flowchart 17

Figure 3.1.5 Dealer’s Flowchart 18

Figure 4.1 Waterfall Model 21

Figure 4.2.1 DFD Level 0 23

Figure 4.2.2 DFD Level 1 24

Figure 4.2.3 DFD Level 2 25

Figure 4.3.1 Use Case Diagram 27

Figure 4.4.1 Activity Diagram for Admin 28

Figure 4.4.2 Activity Diagram for User 29

Figure 4.4.3 Activity Diagram for Company User 30

Figure 4.4.4 Activity Diagram for Dealer 31

Figure 4.5.1 Class Diagram 32

Figure 4.6.1 ER Diagram 34

Figure 5.2.1 Home Page 36

Figure 5.2.2 Sign Up Page 37

Figure 5.2.3.1 User (Customer) Login Page 38

Figure 5.2.3.2 Admin & Company User Login Page 38

Figure 5.2.3.3 Dealer Login Page 39

Figure 5.2.4 Service Page 40

Figure 5.2.5 Food Package Page under Food Service and Cart 41

Figure 5.2.6 Checkout Page 42

9
Figure 5.2.7 Your Orders Page 43

Figure 5.2.8 Admin Dashboard Page 43

Figure 5.2.8.1 Add Service Category Page 44

Figure 5.2.8.2 Add Service Page 45

Figure 5.2.8.3 All Service Page 46

Figure 5.2.8.4 Add Package Page 47

Figure 5.2.8.5 All Packages Page 48

Figure 5.2.8.6 All Users (Customer) Orders Page 49

Figure 5.2.8.7 Add Users (Customer) Page 50

Figure 5.2.8.8 All Users (Customer) Page 51

Figure 5.2.8.9 Add Company Users Page 52

Figure 5.2.8.10 All Company Users Page 53

Figure 5.2.8.11 Add Dealer Category Page 54

Figure 5.2.8.12 Add Dealer Page 55

Figure 5.2.8.13 All Dealer Page 56

Figure 5.2.8.14 All Dealer Services Page 57

Figure 5.2.8.15 Place Order to Dealer 57

Figure 5.2.8.16 All Dealer Order Page 58

Figure 5.2.9 All Users (Customer) & Dealers Orders Handle Page 59

Figure 5.2.10 Dealer Order Handle Page 60

Figure 5.2.11 Take Action Page 61

10
 Chapter 1: Introduction

1.1 Introduction

Web-based online event management systems are here to manage all activities of online event
management agencies. A few years ago, all the activities of event agencies were performed in
pencil or paper. When managing various events, including event packages such as decoration,
food preparation, catering, conference room reservations, and making payments was time-
consuming and challenging, there was the potential for errors.

The “Online Platform for Event Management” is designed to address issues that arise in the
Practical Guide system. This website was created to remove some issues that reduce the issues
that existing systems encounter. This website is also designed to be easy to use, so no prior user
knowledge is required to use the website.

1.2 Motivation

The event management system is used to keep track of all of the event's activities. In any case,
several service providers are working at the same time, making it difficult to manage them. It is
also critical for event organizers to have all of these service providers' contact information on
hand so that they can contact them at any moment to plan an event at a specific time. This
website was created to organize all of these activities. Users should have solid network contracts
with service providers to succeed in the event management business. These contacts are
essentially service providers who can be swiftly summoned to take part in any particular event.

The event planner will need a number of service providers, such as sound system services,
lighting services, decoration services, stage design, and so on, to make any event a success. The
current method requires Event Company to perform all management tasks manually. All
payment information is kept on paper. There is no system in place to check previous event
expenses. To do so, they must check the payment register, which is a time-consuming and
exhausting operation. This system was created with this entire problem in mind. This technology

11
enables the event management business to manage their documentation online, as well as obtain
reports from previous events.

1.3 Objective

The main objectives of the project are to develop a “Online Platform for Event Management”

 Here are the specific features:

• Customer book order for an event.
• Admin accepts or rejects customer's order.
• Admin assigns Company user to organize an event.
• Admin places an order to the dealer if he/she has an insufficient element.

12
 Chapter 2: Literature Review

2.1 Related Work

There are many online event sites around the world, but the websites are not very effective at
best. We visited many sites and researched them to investigate, we found the cons below:

Eventbrite.com [1] is one of the online-based “Event Management System” which organizes
many events worldwide.

Limitation of this website:

• Customer can't choose his/her desired packages.

• Customer can't manipulate package quantity according to his/her desire.
• Customers haven't found out the price rate to organize an event with their desired
package

Machinaarts.org [2] is one of the online event management systems that organizes many events
around the world.

Limitation of this website:

• Customer has to write their whole impulse package manually in a form.

• The client can't manipulate the quantity of the package according to his wish.
• The pieces of information are static.
• It only can afford the small event nicely.

Bdweddingplanners.com [3] is one of the online event management systems that organize
many events across our country.

Restrictions on this website:

• Customer just show the category list (wedding, birthday, party etc.)
• Customer direct call the organizer to ask for detail to manage the event.
• To know about the price customers, need to call the organizer.

13
 Chapter 3: Methodology

3.1 Flowchart

The flow chart is a graphical representation of the algorithm. Programmers often use it as a
programming tool to solve problems. Use interconnected symbols to indicate the flow of
information and processing. Drawing a flow chart of an algorithm is called a "flow chart".

3.1.1 Purpose of Flowchart

• Develop an understanding of how the process is carried out.

• Study the improvement process.
• Inform others about how the process has been carried out.
• Demand better communication between those involved. Same process.
• Document process.
• When planning a project.

14
3.1.2 Flowchart for Admin

First admin will log in. Admin needs to register before log in. If logged in successfully, admin
will view the admin dashboard. From the dashboard, admin can add services, add packages, add
company users, add dealers and add users. Admin can also accept or reject user's orders and
admin can also place an order to dealer.

Figure 3.1.2 Admin’s Flowchart.

15
3.1.3 Flowchart for User

At first, users need to register their accounts. After that, users can log in with those accounts. If
they have an account already, they can log in directly. If the authentication process remains
unsuccessful, users back to the login process again. After the login and authentication process
did, the user can select services & packages according to their desire and make payment to place
an order auspiciously. They can also view their orders.

Figure 3.1.3 User’s Flowchart.

16
3.1.4 Flowchart for Company User

First, company users must register their accounts. Company users can then log in to these
accounts. If they already have an account, they can log in immediately. If the authentication
process is still unsuccessful, company users will return to the login process. After the login and
verification process, the company users can view user orders & dealer orders and make payment
to the dealer to place an order successfully. They can also view their orders.

Figure 3.1.4 Company User’s Flowchart

17
3.1.5 Flowchart for Dealer

The dealer must first register their accounts. The dealer can then log in to this account. If they
already have an account, they can log in immediately. If the verification process continues to fail,
the dealer will return to the login process. After the login and verification process, dealers can
see their profile & admin orders and change status to confirm orders. They can also view their
progress.

Figure 3.1.5 Dealer’s Flowchart.

18
3.2 System Requirements

• Services:  Admin can add different services. Users can select their required services.
Dealers can accept or reject different service orders from the admin. At some time,
company users can play the admin's role.
• Package:  In the package section, the user can select his/her desired package which adds
from the admin. If the admin/company can’t afford the user's package order then they
place an order to the dealer to manage user's order.
• Cart-List: The user can show his /her event plan though he/she can't place an order by
this cart list. After adding an event, users can show their total cost in the cart list. So, they
can realize what costs happen to organize their favorite event.
• Order: Users can place orders. Admin or Company users can see users' orders. Admin
will accept or reject users' orders according to their requirements. If any requirements are
missing, the admin will be contacted by the dealer for their missing requirements. Dealers
can accept or reject admin orders according to their availability.
• Payment: Users can pay their payment corresponding to their order by using mobile
banking and they will provide their transaction id to the admin. In addition, users can
print or download invoices. Admin can accept users' payments. If needed, the admin can
pay the dealer for their orders. Admin or Dealer simultaneously prints or downloads the
invoice.
• Status: The users can track their orders after payment to the admin/company. If the
admin/company cancels the user's order then users can delete the order. The same role
applies when the admin orders to the dealer but the dealer can't delete their orders.

19
 Chapter 4: Design and Analysis

Design and analysis are the organized, theoretical analysis of methods practical to a field of
study. It consists of the theoretical analysis of the body of methods and rules regulations
associated with branch of knowledge. Typically, it comprehends concepts such as paradigm,
theoretical model, phases and quantitative or qualitative techniques. A methodology can be
considered to add multiple methods and rules, each as applied to various facts of the whole
extent of the methodology. The research can be divided between two parts: they are qualitative
exploration and quantitative exploration.

4.1 Waterfall model

The classic waterfall model is the basic model for the life cycle of a program. Very simple but
perfect. This model was very popular but is now obsolete. But this is important because other
software development lifecycle models of them are based on the classic waterfall model. The
classic waterfall model divides the life cycle into a number of phases. This model assumes that
the step can be started after the previous step. This means that the output of one stage will be the
input of the next stage. Thus, the development process can be thought of as a gradual flow in a
waterfall. The steps do not intersect here.

Process of waterfall model

• Requirements: Potential requirements, timelines, and recommendations for the project

are analyzed and put into a functional specification. This process handles project
definition and planning without mentioning specific processes.
• Analysis: System specifications are analyzed to create product models and business
logic that will guide production. It is also when the feasibility of financial and
technical resources is checked.
• Design: Project details are documented to describe technical design requirements
such as programming language, hardware, data sources, architecture, and services.

20
• Coding / Execution: The source code is developed using the patterns, logic, and
requirements defined in the previous steps. Systems are typically designed into
smaller components or units before being deployed together.
• Test: This is the case when quality, device, system, and beta testing is performed to
report problems that may need to be addressed. This may force you to repeat the
coding phase for debugging. If the system passes the test the waterfall will continue.
• Operation/Application: The product or application is considered fully functional
and is used in a real environment.
• Maintenance: Corrective, adaptable, and perfect maintenance is carried out
endlessly to improve, update and enhance the final product. This may include the
release of a hotfix update or the release of a new version.

Figure 4.1 Waterfall model.

21
Why do we use the Waterfall model?

• It's easy to understand, track, and organize tasks.

• Easily make early design or specification changes.
• Strengthens systematic and disciplined organizations.
• Waterfall model is a simple model which can be easily understood and where all phases
are done step by step.
• It's small project friendly.

4.2 Data flow Diagram

A Data Flow Diagram (DFD) models a perspective on the system in a way that is easier for users
to understand - the flow of information through the system and the activities that process that
information.

Data flow diagrams provide a visual representation of the system intended to be equally
accessible to computer experts and non-expert users. Models allow software engineers,
customers, and users to work effectively together to analyze and specify requirements. While this
means that our clients need to understand modeling techniques and architectures, only a limited
number of constructs are used in data flow modeling, and the rules applied are designed to be
simple and easy to follow. The same principles and constructs apply to all data flow diagrams
(i.e., to each of the different software processing activities in which DFD can be used).

22
Figure 4.2.1 DFD Level 0.

23
Figure 4.2.2 DFD Level 1.

24
Figure 4.2.3 DFD Level 2.

25
4.3 Use Case Diagram

UML usage diagrams are the basic form of systems/software needed for new, undeveloped
applications. Use cases define the expected behavior (what), not the proper way to do it (how).
Cases, once described, can be represented in the form of text and images (for example, using a
case diagram). The basic concept of use case modeling is to help design the system from the
perspective of the end-user. This is an effective technique for reporting system behavior in the
form of users who define the behavior of the entire system as seen from the outside. The design
is generally user-friendly. Don't show usage issues details.

Summarizes just some of the relationships between usage issues, actors, and systems. Does not
indicate the sequence of actions taken to achieve the objectives for each use case. As already
mentioned, use case diagrams must be simple and consist of several forms. If you have more
than 20 use cases, you can abuse the use case diagram.

The Platform provides the admin with Ten functionalities: Manage all users; Add Service, add
package for the users. Add dealer for placing specific order by admin. Admin can pay the dealer
for their order. Add Company users who will play alternative roles of admin in some time. The
platform provides the user with six functionalities: Registration, Login, Select Service, Select
Package, make payment and logout. The platform provides the dealer with three functionalities:

Login, Dealer profile, Log out. The platform provides the company user with three
functionalities: Login, Company user profile, Log out.

Purpose of Use Case Diagram

Use case diagrams usually develop in the early stages of development. The permit model is used
for the following purposes:

• Determine system context

• Collect system requirements
• Review system architecture
• Distribution of units and test status versions
• Collaborative analysts with experts in the development industry.

26
Admin [Fig: (a)] will login first. Once login is completed the admin will dive into his own
dashboard. Admin will be able to add services, packages, company users, dealers. Admin can
view the dealer’s profile and place orders to the dealer and make payment to the dealer.
Company user [Fig: (b)] will login first. Once login is completed, company user will be able to
view his profile.
The user [Fig: (c)] will first register, then login. The user will be able to select the service and
package of his choice. Users will be able to place orders and payments.
Dealer [Fig: (d)] will login first. Once login is completed, dealer will be able to see his own
profile.

Fig(a): Admin. Fig(b): Company User.

Fig(c): User. Fig(d): Dealer.

27
 Figure 4.3.1 User Case Diagram.

4.4 Activity Diagram

Activity diagrams are another important UML graph that describes the dynamic aspects of the
system. An activity diagram is a flow chart that shows the transition from one activity to another.
The action can be described as a systemic action. The flow of control is passed from one
operation to another. This stream can be sequential, branched, or synchronous. Control activity
diagrams for all types of flow controls using elements such as sockets, connections, etc.

In the admin's activity diagram, the first admin needs to log in and check the authentication. If
the authentication process is unsuccessful, admin return to the login. Otherwise, the admin can
add service category, service, package, user, company-user, dealer, etc. He/She can manage
orders for dealers and users. He/She can also view and edit their progress. At last, he/she can log
out from the site.

28
 Figure 4.4.1 Activity Diagram for Admin.

In the user activity diagram, the first user must log in and verify authentication. If the
authentication process fails, the user will return to log in. In different circumstances, the user can
select services and packages. He/She can place orders to the organizer. He/She can also show
their progress. Finally, he/she can log out of the site. The user can follow the whole workflow
like this

Figure 4.4.2 Activity Diagram for User.

29
In the company user activity diagrams, the first company users must log in and verify the
approval. If the authentication process fails, the company users go back to logging in. In various
situations, company users can view user orders and edit user order status. They can only see
admin orders. They can also view dealer orders and make payments based on dealer status.
Finally, they can leave the site. In this way, the company user can monitor the entire workflow.

Figure 4.4.3 Activity Diagram for Company User.

30
In the dealer activity diagram, the first dealer must be logged in and authenticated. If the
approval process fails, the dealer will return to login. In most cases, dealers only display orders
from admins/company-users. They can change order status for admin/company users. They can
also show progress. Finally, they can log out of the site. The dealers can follow the entire
workflow in this way.

Figure 4.4.4 Activity Diagram for Dealer.

31
4.5 Class Diagram

The class diagram describes the static width of the application. A class consists of its own
members and can be inherited by other classes. The program displays attributes, classes,
functions, and relationships to provide an overview of the system.

Purpose of Class diagrams

The main purpose of a class diagram is to create a static representation of an application. It can
be installed using an object-oriented language. The objectives of the class planner are as follows:

• Analyze and design the static appearance of the application.

• Describe the main responsibilities of the system.
• Which forms the basis for its preparation and action plan?

Figure 4.5.1 Class Diagram.

32
4.6 ER Diagram

An entity-relationship (ER) chart is a type of flowchart that shows how "objects" such as people,
things, or concepts are related in a system. ER diagrams are often used to design or troubleshoot
relational databases during software development.

ER diagram of computer systems for business, education, and research showing the relationship
between the tools. A device set is a collection of similar devices that can contain

features. From a DBMS perspective, the modules in the database contain the properties of the
tables, so the ER schema shows the general logical structure of the database and shows the
relationships between the tables and the properties. These are the geometric shapes and their
meanings on an ER diagram.

Purpose of ER diagrams

• Preview how all your tables are connected. And which fields should be included in each
table
• Help explain terms related to entity and relationship modeling.
• Helps describe entities, attributes, and relationships.
• ER graphs can be translated into relative tables to create real-time databases.
• Database developers may use ER diagrams as a data implementation plan in some
applications.
• Database designers use ERP diagrams to get a better understanding of what data should
be in the database.
• The ERD schema allows users to communicate the logical structure of a database.

33
ER Diagram

Figure 4.6.1 ER Diagram.

34
 Chapter 5: Implementation

5.1 Web Development & design module

Creating a web site requires multiple steps which includes the following:
Creating a UI (User Interface)

• Frontend
• Backend

5.1.1 Frontend

Technologies that are mostly used to evolve a Frontend are:

• HTML5
• CSS3
• Bootstrap
• JavaScript

5.1.2 Backend

We use technology for backend are:

• PHP
• Database: MySQL

35
5.2 Implementation

5.2.1 Home Page

This is our Home Page. Any User (Customer) can view & choice their required service from
here.

Figure 5.2.1 Home Page.

36
5.2.2 Sign Up Page

User (Customer) must sign up by filling required information before login. Otherwise User
(Customer) can’t login and place order.

Figure 5.2.2 User (Customer) Sign Up Page.

37
5.2.3 Login Page

User (Customer), Admin, Company User and Dealer can login using them personal
information. Username and password are required which will be verified by our system.

Figure 5.2.3.1 User (Customer) Login Page.

38
Figure 5.2.3.2 Admin & Company User Login Page.

Figure 5.2.3.3 Dealer Login Page.

39
5.2.4 Service Page

This page shows all services. User (Customer) view and select their required service from this
page.

Figure 5.2.4 Service Page.

40
5.2.5 Package Page & Cart

User can select different packages under one service. For example, user (Customer) can select
Food Packages under Food Service. After selected all desired packages, User (Customer) can
show a list of desired package and total cost in Cart section.

Figure 5.2.5 Food Package Page under Food Service and Cart.

41
5.2.6 Checkout Page

After add to cart desired packages, User (Customer) can place order use this page.

Figure 5.2.6 Checkout Page.

42
5.2.7 Your Orders Page

In this page, User (Customer) can view their previous and present orders, check order status.

Figure 5.2.7 Your Orders Page.

5.2.8 Admin Dashboard

After Admin could login, he/she can view this Admin Dashboard Page. This page contains all
Services, Packages, Customers and Orders. Admin can manage Users, Dealer, Company User
and Admin from this page.

43
 Figure 5.2.8 Admin Dashboard Page.

5.2.8.1 Add Service Category

In this page, Admin can add, edit and delete different Service Category.

Figure 5.2.8.1 Add Service Category Page.

44
5.2.8.2 Add Service

Admin can add different Service under different Service Category using this page.

Figure 5.2.8.2 Add Service Page.

45
5.2.8.3 All Service

Admin can view, edit and delete services from this page.

46
 Figure 5.2.8.3 All Service Page.

5.2.8.4 Add Package

In this page, Admin can Add Packages under different Service.

Figure 5.2.8.4 Add Package Page.

47
5.2.8.5 All Packages

Admin can view, edit and delete All Packages using this page.

48
 Figure 5.2.8.5 All Packages Page.

5.2.8.6 All User (Customers) Orders

Admin can view and take action All Users (Customers) Orders using this page.

Figure 5.2.8.6 All Users (Customer) Orders Page.

49
5.2.8.7 Add Users (Customers)

By using this page, Admin can add a User (Customer).

Figure 5.2.8.7 Add Users (Customers) Page.

50
5.2.8.8 All Users (Customers)

In this page, Admin can view, edit and delete Users (Customers) who login in this Web
Application.

Figure 5.2.8.8 All Users (Customers) Page.

51
5.2.8.9 Add Company Users

Admin can add a Company User by using this page.

Figure 5.2.8.9 Add Company Users Page.

52
5.2.8.10 All Company Users

In this page, Admin can show, edit and delete all Company Users.

Figure 5.2.8.10 All Company Users Page.

53
5.2.8.11 Add Dealer Category

Admin can insert a Category for a Dealer. After adding Dealer Category, Admin can edit and
delete Dealer Category from this page.

Figure 5.2.8.11 Add Dealer Category Page.

54
5.2.8.12 Add Dealer

By using this page, Admin can add different Dealer for different Services.

Figure 5.2.8.12 Add Dealer Page.

55
5.2.8.13 All Dealer

Below the page, Admin can view All registered Dealer. In addition, Admin can edit and delete
registered Dealer.

Figure 5.2.8.13 All Dealer Page.

56
5.2.8.14 All Dealer Services & Place a Dealer Order

In this section, Admin can view All Dealer Services.

Figure 5.2.8.14 All Dealer Services Page.

After clicking on “Order Now” button, Admin can place an order to Dealer.

57
 Figure 5.2.8.15 Place Order to Dealer.

5.2.8.15 All Dealer Orders

After placing a Dealer Order, Admin can All Dealers present and previous order within that
page.

Figure 5.2.8.16 All Dealer Orders Page.

58
5.2.9 Company Users Orders

In this section, Company User can manage orders from Users (Customer) and Dealers.

Figure 5.2.9 All Users (Customer) & Dealers Orders Handle Page.

59
5.2.10 Dealer Order Handle

Dealer can view and manage (accept or reject) Admin’s Order by using this page.

Figure 5.2.10 Dealer Order Handle Page.

60
5.2.11 Change Status

In this subsection, Admin/Company User or Dealer can Take Action about their orders. They can
also view details about orders.

Figure 5.2.11 Take Action Page.

5.2.12 Results

61
Completion: We have completed our project 100%. We have met all the functional requirements
that we discussed.

Accuracy: Our project is working 100% accurate. It fulfills all the functional and non-functional
requirements as we promised.

Chapter 6: Conclusion & Future Work

6.1 Conclusion

Now our project has terminated successfully. More features will be included as discussed in the
future work section. In this web application, it is easy for the users to get event quotations
according to their required services. And users will be able to confirm the service as per their
requirements. It is very helpful for online event management agencies. The whole system is
responsive to make it accessible from all devices. We try our best to introduce an Online
platform for an event management system that everyone can use easily and it will help to
complete the entire activities of an event management agency.

6.2 Future Work

Due to time constraints, many different adaptations and experiments have been left for the future.
Future work includes a deeper analysis of individual ideas, new proposals to try different
methods, or simply curiosity. Some of the ideas and possible improvements in this system are: 

• In the future we want a section that delivers the user to find out the event (wedding,
birthday, party) summary of what the organizer organized. So that users know about
organizer arrangement quality shortly. We will integrate it later.
• The payment method will be online not manually for the user and admin. We will include
it later.
• If the organizer has any "special offers", the user can visit them. We will add it later.
• Users can take sit tokens per person from the organizer who attains their event. We'll put
it on later. 
• User can select their favorite venue with area code. We will use it later. 

62
• User can give a review about the event organized by the organizer. We will add the last
one.

References

1. https://www.eventbrite.com/
2. https://www.machinaarts.org/
3. http://www.bdweddingplanners.com
4. https://app.diagrams.net/
5. https://www.youtube.com/watch?v=aBiIgUhe0Jk&t=218s
6. https://www.youtube.com/watch?v=vp58EDJJ3uc
7. https://www.youtube.com/watch?v=K6tH5eCLZoo
8. https://meeraacademy.com/activity-diagram-for-student-attendance-management-
system/?
fbclid=IwAR2HJu0KcTrFLqTrvZLmFAArIZt0cHbDipe0kqAU5CYtqNJdEf78Auef8e4
9. https://www.youtube.com/watch?v=CCK4g8KzIvI

63
 Appendix

Basic Symbols used in Flowchart Designs

• Terminal: The oval represents the beginning, end, and end of the program's logical flow.
Pause / Stop is usually used in program logic under certain error conditions. The terminal
block is the first and last symbol on the diagram.

Figure Terminal.

• Input / Output: Specifies the Input / Output function of the parallelogram. Program
instructions that receive input from an input device and display output to an output device
are marked on the diagram with a parallelogram.

Figure: input/output.

• Processing: Frames represent mathematical assignments. All arithmetic operations such

as addition, subtraction, multiplication, and division are represented by a process or
operation symbol.

Figure: Processing.

64
 • Decision: Solution The diamond symbol indicates the decision point. Actions based on
decisions such as yes / no or true/false are represented by diamonds in the graph.

Figure: Decision.

• Connectors: We recommend using links to avoid confusion when a diagram becomes

confusing or spans more than one page. It is represented by a circle.

Figure: Connectors.

• Flow lines: Flow lines indicate the exact order in which an order is completed. Arrows
indicate the relationship between the direction of the control stream and other symbols in
the flowchart.

Basic Activity Diagram Notations and Symbols

• Initial State or Start Point: A small full circle followed by an arrow indicating the start
of an activity or the start of an activity graph. For time sheets that use the third line, make
sure the starting point in the top left corner of the first column is.
• Activity or Action State: The action state represents the uninterrupted work of the
object. In Smart Draw, you can draw action states using a rounded rectangle.
• Action Flow: The action flows, also called edges and lanes, show the transition from one
state of motion to another. They are usually drawn as broken arrows.
• Object Flow: Object flow refers to creating and modifying objects through actions. An
arrow that moves an object from an action to an object means that the action creates or
affects the object. The object-action flow arrow indicates that the focus is using the
object. 

65
 • Decisions and Branching: Diamonds are another option. Whether one activity should be
decided before moving on to the next activity. Give more diamonds in both events. The
output selector must be marked with a protection mode or expression. You can also name
any street as 'else'. 
• Guards: In UML, there is a written statement before the decision of Periodicity Diamond
which should be correct before going to the next stage. Not required, but useful when a
specific response is required, such as "Yes, please enter three badges" before continuing. 
• Synchronization: A fork node is used to split an incoming stream into multiple parallel
streams. It is represented by straight lines that are slightly thicker on the activity chart. A
switch node combines multiple synchronous streams into one output stream. Fork and
grip modes used together are often referred to as synchronization. 
• Merge Event: Merge events bring together multiple non-concurrent streams.

Coding Background

HTML5: HTML5 is a name used to describe a group of modern web technologies. JavaScript
APIs for storage, multimedia, and device access is included, as well as the HTML Living
Standard. "New HTML5 components" or HTML5 being referred to as a new version of HTML
are terms you'll encounter from time to time. HTML5 was the language's successor to previous
versions, bringing new features and capabilities while also upgrading or removing some existing
functionality. HTML, on the other hand, does not have a Living Standard version.
http://html.spec.whatwg.org/ has the most recent version of the standard. Any modern website
should utilize the HTML doctype to ensure that it is using the most recent version of HTML.

CSS3: The acronym CSS stands for Cascading Style Sheets that are used to enhance the
capability and versatility. and green overall performance of web website online content. It lets in
for the advent of content-wealthy websites that don't require lots of weight or codes; this
interprets into extra interactive snapshots and animation, advanced person interface, and
appreciably extra enterprise and speedy download time.

66
This new technology offers some interesting features that improve the overall look of your site.
The page doesn't have to work. However, online users will find that such pages look good, are
simple, navigable, and work fine. This allows developers to easily design pages that make a
lasting impression on visitors and potential buyers who enjoy browsing online.

Use it in HTML to create the content structure and use CSS3 to format the structured content.
Responsible for font properties, colors, text placement, graphics, background images, tables, and
other components. This tool provides additional features such as absolute, fixed, and relative
positions for various elements. The growing popularity of CSS3 used by Texas web design
companies encourages major browsers such as Google Chrome, Firefox, Safari, and IE9 to adopt
and use this programming language.

Bootstrap: Bootstrap is a free open-source frontend development framework for building

websites and web apps. The Bootstrap framework, built on HTML, CSS, and JavaScript (JS),
makes it easy to develop responsive, mobile-first sites and apps.

The responsive layout makes it viable for an internet web page or app to hit upon the visitor`s
display screen length and orientation and mechanically adapt the show accordingly; the mobile-
first technique assumes that smartphones, tablets, and task-particular Mobile apps are
employees` number one equipment for buying paintings performed and addresses the necessities
of this technology in layout.

On a computer, the word bootstrap means to boot. Load the program into your computer with a
much smaller initial program to load the desired program (usually the operating system).

In the physical world, bootstraps are small straps or loops behind leather boots that allow you to
wear the entire boot. In general, bootstrap is about turning a small initial effort into something
bigger and more meaningful. There is also the general expression "pull yourself up with a
bootstrap". This means helping you succeed from a small start.

67
PHP: A very popular scripting language is used to create dynamic web pages. Combine C, Java,
and Perl language syntax to embed PHP code in HTML pages for server-side execution. It is
typically used to extract data from a database on a web server and render it into a web page.
Originally known as the Personal Home Page, PHP is supported on all web servers and is
commonly used in MySQL databases.

Where did php come from?

PHP was invented by Rasmus Leadoff in the fall of 1994. On his home page, an early
unpublished version was used to track who viewed his online resume. The first version used by
others was available in early 1995 and was called the Personal Home Page Tool. It consisted of
some special macros and a very simple parser engine that only understood a set of utilities that
were common on homepages at the time. Guestbooks, counters, etc. The parser was rewritten in
mid-1995 and was called PHP / FI Version 2. The FI is from another package created by Rasmus
by interpreting the HTML form data. He combined the Personal Home Page Tools script with
Form Interpreter, added MySQL support, and PHP / FI was born. PHP / FI has grown at an
alarming rate and people have begun to provide code for it.

How popular are PHP?

One of the main reasons PHP has become so popular is that it's relatively easy to get started.
Most people can create a website using a single PHP file in a relatively short amount of time,
without extensive knowledge or experience in web development. PHP is easier to learn
than many other languages   because of its simple syntax and easy-to-learn command functions.

MySQL: MySQL is a relational database management system developed by Oracle and based
on a structured query language. The database is a structured collection of data. It can be anything
from a simple shopping list to an image gallery or a place to store a huge amount of information
on your corporate network. Relational databases, in particular, are digital stores that collect data
and organize it according to a relational model. In this model, the table consists of rows and

68
columns, and all relationships between data items follow a strict logical structure. An RDBMS is
a set of software tools used to actually implement, manage, and query such a database.
 
MySQL is an integral part of many of the most popular software stacks for building and
managing everything from custom web applications to powerful data-driven B2B services. Due
to its open-source nature, stability, rich feature set, and continuous development and support
from Oracle, Internet-critical organizations such as Facebook, Flickr, Twitter, Wikipedia, and
YouTube all use the MySQL backend.

How it works?

Like most database management systems, MySQL has a client-server architecture that you can
use in a networked environment. The server program is on the same physical or virtual system
where the database files are stored and are responsible for all interactions with the database.
 
Various client programs, such as MySQL database management tools and applications written in
other programming languages, can connect to the server and execute database queries. The
server processes the client request and sends the result back to the client. The client resides on
either the same system as the server or on a remote host and can send database requests to the
server over a network or internet connection. The important thing is that the MySQL server
needs to be running so that the client can connect to it.

69