Project Report

On

HAPPY HAPPENINGS
By

Pranjal Kemkar

Enrolment No.: 194510307022

Semester: V

Diploma Engineering (Computer Engineering)

Guided By:

Drashti Bhavsar,
Lecturer,

SAL Institute of Diploma Studies

A Project Report Submitted to

Gujarat Technological University in Fulfilment of the Requirements for

The Degree of Diploma Engineering in Information Technology

October: 2021

SAL EDUCATION

SAL Institute of Diploma Studies

Opp. Science City, Sola, Ahmedabad, Gujarat: 380060

1|Page
 HAPPY HAPPENINGS
(A Wedding Planner Project)

2|Page
 CERTIFICATE

This is to certify that Project work embodied in this Project Report titled “
Happenings” was carried out by Pranjal Kemkar, Enrollment No. 194510307022
SAL Institute of Diploma Studies (451) for fulfillment of Diploma Engineering degree
Computer Engineering to be awarded by Gujarat Technological University. This Proj
work has been carried out under my guidance and supervision and it is up to m
satisfaction.

Date:

Place: SIDS, Ahmedabad.

Signature and Name of Guide Signature and Name of H.O.D

Drashti Bhavsar Kalpesh Patel
Lecturer, Head of the Department (C.E.),
Computer Engineering Department,
Diploma Engineering Departmen
SIDS (451), Ahmedabad.
SIDS (451), Ahmedabad.

Signature and Name of Principal

Dr. Monika Swami,
SIDS (451), Ahmedabad.

3|Page
 ACKNOWLEDGEMENTS

I am very obliged to Dr. Monika Swami, Principal of SAL Institute of Diploma Stud
for providing facilities to achieve the desire milestone.
I am also thankful to Kalpesh Patel H.O.D., Computer Department, SAL Institute
Diploma Studies, Ahmedabad for his continuous encouragement and m
I am grateful to my guide Drashti Bhavsar, Department of Computer Engineering, S
Institute of Diploma Studies, Ahmedabad, for the preparation of the present work towa
partial fulfillment of my project. It is due to her constant support and guidance that I co
pursue the present topic of my study. Without her treasonable advice and assistance
would not have been possible for me to attain this landmark. She has always been willin
present whenever I needed the slightest support from her. She not only guided me at cruc
points but also helped me to sharpen my skills at various stages of progress of this stu
Her continuous guidance and support will be of great help to complete the final work th
have undertaken.
I am very obliged to all my dear friends for their continuous livelihood and comfort in e
and every phase of my life. I would like to thank all of them whose name are not mention
here but have played a significant role in any way to accomplish the work.
Grace of the almighty God and blessings of my parents have formed the path to reach
desire goal.

Pranjal Kemkar
(194510307022)

4|Page
 Happy Happenings

Enrolment No.: 194510307022

Pranjal Kemkar

SAL Institute of Diploma Studies (451)

Semester: V, Diploma Engineering (C.E.)

Abstract

This Happy Happenings is a wedding planner system which will be a java-based web
application that will help the users to organize successful wedding events. This
application will provide an easy way to plan all of their special events. The user can add
all the details of the event to get the service. The user can select the type of event, type of
food to be served, type of decoration, venue, estimated budget, etc. All the details given
by users will be verified. A list of suitable requirements will be shown out of which the
user the select the preferred selections as per their choice. The vendor will verify and send
his response with a confirmation mail. The user needs to complete the payment process to
confirm the order.

Keywords: Online, Wedding, Planner, Client, Password, Records, Vendor, Customer/user and
Budget.

5|Page
TABLE OF CONTENTS:
INTRODUCTION 01

1.1 Introduction of the Project

1.2 Purpose of the Project

1.3 Function Requirements

1.4 Problems in Existing System

1.5 Main Modules

SYSTEM REQUIREMENTS 02

2.1 Hardware & Software Requirements

2.1.1 Server Side Requirements

2.1.2 Developer Side Requirements

2.1.3 User Side Requirements

SYSTEM ANALYSIS AND DESIGN 03

3.1 System Analysis and Design

3.2 System Development Life Cycle (SDLC)

3.2.1 Needs of SDLC

3.2.2 SDLC Cycle

3.3 Spiral Model

3.4 Feasibility Study

FRONT END OF SYSTEM 04

4.1 About Front End

4.1.1 about PHP

4.1.2 about HTML

4.1.3 about CSS

4.1.4 about JavaScript

4.2 Why Use PHP

BACK END OF SYSTEM 05

5.1 About Back End

5.1.1 about MySQL

6|Page
5.1.2 How MySQL Works

5.1.3 MySQL Features

5.2 Why use MySQL

SYSTEM DESIGN 06

6.1 Data Flow Diagram

6.2 Use Case Diagram

6.3 Activity Diagram

6.4 E-R Diagram

DATA DICTIONARY 07

7.1 Introduction

7|Page
 CHAPTER 1
INTRODUCTION

8|Page
1.1 INTRODUCTION OF THE PROJECT

• The wedding planner system will be a java based web

application which will help the users to organize
successful wedding events. This application will provide
an easy way to plan all of their special events. The user
can add all the details of the event to get the service. The
user can select the type of event, type of food to be
served, type of decoration, venue, estimated budget, etc.
All the details given by users will be verified.
• A list of suitable requirements will be shown out of
which the user the select the preferred selections as per
their choice. The vendor will verify and send his
response with a confirmation mail. The user needs to
complete the payment process to confirm the order.

9|Page
1.2 PURPOSE OF THE PROJECT

• To help people easily plan their wedding.

• To reduce physical efforts.

• To visualize their thoughts about their decorations.

• To help users stay in budget without others forcing them

to extend their budget.

10 | P a g e
1.3 FUNCTION REQUIREMENTS

• Social Signup and Login

• View Event organizers/vendors

• Filter event organizers/vendors/service providers based

on location/price

• Refine the search based on service needed (makeup,

catering, etc.)

• View vendors profile, reviews, ratings, and portfolio Call

and Chat with Vendors

• Vendor profile sharing

• Search wedding venues based on location

• Filter through wedding styles

• Create a wedding checklist

• Wedding Budget calculator

• Create/Manage the guest list.

• Send online invitations to guests

• Multiple payment options

11 | P a g e
• Map for the location for vendors

• Wedding countdown

• Write reviews and ratings

12 | P a g e
1.4 PROBLEMS IN EXISTING SYSTEM

• There are many types of problems in the wedding

planner apps like the main problems are the application
glitches and what would be the wither or the payment
gateway issue and the improper organization and many
more things are there.

• Dress management and all the thing like the food and the
weather disaster payment issue and the bugs which are
not fixed in proper updates which had be fix are taken
care in this app . The way of presenting thing are mostly
not in order so better to put in order and all the wedding
planner apps have the same boring procedure and not
much of a fun apps so mostly peoples get bored while
designing there wedding so they don’t prefer wedding
apps and they don’t trust this types of apps .

13 | P a g e
1.5 MAIN MODULES

Admin needs to get logged in by entering valid credentials.

Admin can view all the details of the registered users and can
authorize them. Admin can add planners. Admin can view
users request and will send to the planner. Admin can view
planner response and will confirm users request for a venue
with a confirmation mail to users.

Planner:-

The planner will be added by admin and will get his/her

credentials to their mail id. The planner needs to give valid
username and password. The planner can view request sent by
admin and can give a response to admin.

USER:-

The user needs to get registered with the applicant by entering

all the details in the registration form. Every registered user
should be activated by the admin. The user can get login by
entering unique username and password. The user can add all

14 | P a g e
the details in the application regarding the event like the type
of event, decoration, and budget. Users will get a confirmation
mail to his mail id. Users order will be booked after
completing the payment process.

15 | P a g e
 CHAPTER 2
SYSTEM REQUIREMENTS

16 | P a g e
2.1 SOFTWARE REQUIREMENTS

1. All Seated

2. Aisle Planner

3. Planning Pod

4. Accounting software

5. App development software

6. Document management software

7. Animation software

17 | P a g e
2.1.1 SERVER SIDE SIDE REQUIREMENTS

18 | P a g e
2.1.2 DEVELOPER SIDE REQUIREMENTS

• The developers side requirement will be very simple as

also explained above.

• The developer would require the jingo and the JavaScript

server handy.

• A proper knowledge about jingo and javascript is must.

• The basic knowledge of the jingo and the JavaScript.

19 | P a g e
2.1.3 USER SIDE REQUIREMENTS

• Name of Groom.

• Groom Mobile Number.

• Email Id

• Bride Name

• Bride Mobile Number.

• Peoples Numbers.

• Place

• A proper device that supports android and windows

applications.

• The device should have internet connections.

• Online payment methods or precisely netbanking.

20 | P a g e
 CHAPTER 3

SYSTEM ANALYSIS AND DESIGN

21 | P a g e
3.1 SYSTEM ANALYSIS AND DESIGN

• In the existing Wedding Planner system, users need to

waste a lot of time and physical effort in finding the
place for the event and no proper information is provided
to the user regarding the event details like food,
decoration, and budget.
• All the information is maintained in records which are
difficult to view or modify.
• Sometimes the users themselves are not able to make the
selection according to their own choices, but in this
application the user will directly make all the choices to
their likings and no mediator will be placed between the
vendor and the user.
• The user will always stay in their budget and all of
his/her choices will be maintained neatly.
• Includes the design of application, network, databases,
user interfaces, and system interfaces.

22 | P a g e
3.2 SYSTEM DEVELOPMENT LIFE CYCLE

Not the exact cycle just a general idea of the sdlc.

23 | P a g e
3.2.1 NEEDS OF SDLC

An effective System Development Life Cycle (SDLC) should

result in a high quality system that meets customer
expectations, reaches completion within time and cost
evaluations, and works effectively and efficiently in the
current and planned Information Technology infrastructure.

System Development Life Cycle (SDLC) is a conceptual

model which includes policies and procedures for developing
or altering systems throughout their life cycles.

24 | P a g e
3.2.2 SDLC CYCLE

Just a prototype:

25 | P a g e
3.3 SPIRAL MODEL

Prototype Model:

Spiral model has 4 stages which keep going on as a loop. The

stages are as follows:

1. Planning
2. Designing
3. Constructing
4. Evaluation

Planning:

This includes the rough idea of the project. This application

helps to organize successful wedding events for users. This

26 | P a g e
application provides an easy way to plan their special events.
The user can add all the details of the event and can get the
service. The user can select the type of event, type of food to
be served, type of decoration and estimated budget. The user
can visualize how the venue will look according to the
decorations he/she has selected. The users can also arrange a
meeting in the meeting section with the vendors.

Designing:

For the designs I have attached some snap shots of the basic
design that has been created till now.

27 | P a g e
One:

28 | P a g e
Two:

29 | P a g e
Three:

30 | P a g e
Four:

31 | P a g e
Five:

32 | P a g e
Construction:

Evaluation:

33 | P a g e
3.4 FEASIBILITY STUDY

• Defining the problem and scope of existing system.

• Overviewing the new system and determining its

objectives.

• Confirming project feasibility and producing the project

Schedule.

• During this phase, threats, constraints, integration and

security of system will also be considered.

• The final feasibility report for the entire project will be

created at the end of this phase.

34 | P a g e
 CHAPTER 4
FRONT END OF THE SYSTEM

35 | P a g e
4.1 ABOUT FRONT END

API

Data management

Data pull and push

Object Oriented designs

Information about vendors and all that

36 | P a g e
 4.1.1 ABOUT PHP

Php is an open source and powerful language for web

development. Php based projects are quite user friendly for
development as well as database processing functions. These
php based systems are provided for php development learning
and understanding through hands on project learning kit.

37 | P a g e
4.1.2 ABOUT HTML

 A tribute page. This is one of the simplest HTML

projects you can make.
 A survey forms. Websites often include forms as a part
of their customer data collection strategy.
 Technical documentation page.
 Landing page.
 Event page.
 Parallax website.
 Personal portfolio page.
 Restaurant website.

38 | P a g e
4.1.3 ABOUT CSS

 Revamp an existing site using modern CSS themes. You

need not design a website from scratch.
 Transform a website into a printer-friendly version.
 Change the layout of a form.
 Improve the speed of a website.
 Solar system animation.
 Pure CSS minesweeper.
 Day-night toggles.
 Custom map creator.

39 | P a g e
 4.1.3 ABOUT JAVASCRIPT

One of the most popular scripting languages, JavaScript is

used in all the web applications for validation, rendering
dynamic content, interactive graphics and maps, and much
more. Along with HTML and CSS, JS has the power to build
complete, robust web applications.

40 | P a g e
 4.2 WHY USE PHP?

PHP is mainly used for web development, and it truly excels

in this area. Though initially it was used to create dynamic
web pages, developers prefer to use this scripting language for
building the server side of web applications. However, PHP is
originally a general-purpose language, so it may have other
implementations if needed. For example, it is possible to
build desktop applications using PHP. Moreover, starting
from version 5, PHP supports object-oriented
programming offering a whole new set of capabilities.

41 | P a g e
 CHAPTER 5
BACK END OF THE SYSTEM

42 | P a g e
5.1 ABOUT BACK-END

API management

API server management

Push and pull managements

Server will link to google and it will give commands to the

google.

43 | P a g e
5.1.1 ABOUT MYSQL

MySQL Database Projects greatly help database development.

They categorize your scripts in one reasonable structure,
suitable for routing and organization, propose offline database
expansion with a set of functional features, such as and code
completion in SQL code, refactoring, syntax check, etc.

44 | P a g e
5.1.2 HOW MYSQL WORKS
To create a project in a repository on MySQL 5, you work
through these stages:
Stage 1: Create an empty database repository and set up the
data tables. ...
Stage 3: Perform a project integrity check on the project file
you are using as a base (optional, but recommended)
Stage 4: Transfer the data.

45 | P a g e
5.1.3 MYSQL FEATURES

 Relational Database Management System (RDBMS)

MySQL is a relational database management system. ...
 Easy to use. MySQL is easy to use. ...
 It is secure. ...
 Client/ Server Architecture. ...
 Free to download. ...
 It is scalable. ...
 Speed. ...
 High Flexibility.

46 | P a g e
5.2 WHY USE MYSQL?

MySQL Database Projects greatly help database development.

They categorize your scripts in one reasonable structure,
suitable for routing and organization, propose offline database
expansion with a set of functional features, such as and code
completion in SQL code, refactoring, syntax check, etc.

47 | P a g e
 CHAPTER 6
SYSTEM DESIGN

48 | P a g e
6.1 DATA FLOW DIAGRAM

 Below given flowchart shows just the flow of the main

features of the application, excluding the basic flow of
logging in, signing up, forgetting password, making
payment, etc.

49 | P a g e
50 | P a g e
6.2 USE CASE DIAGRAM

51 | P a g e
6.3 ACTIVITY DIAGRAM

6.4 E-R DIAGRAM

52 | P a g e
53 | P a g e
 CHAPTER 7
DATA DICTIONARY

7.1 INTRODUCTION
54 | P a g e
A data dictionary is a collection of the names, definitions, and
attributes for data elements and models. The data in a data
dictionary is the metadata about the database. These elements
are then used as part of a database, research project, or
information system.
These are some of the most common elements used in a data
dictionary, though there’s variation: 
 Username
 Login id
 Password
 Budget information
 Countdown for the final date
 Venue
 Florists
 Caterer
 Theme
 Dresses
 Jewellery

55 | P a g e