Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

DBMS Project Report Edited 2

Download as pdf or txt
Download as pdf or txt
You are on page 1of 40

P R O J E C T R E P ORT

ON

Event Management

Submitted In Partial Fulfillment of the Requirement for the Award of

Third Year

B a c h e l o r o f Te c h n o l o g y

in

COMPUTER ENGINEERING

BY

Krushna Narayan Khedkar 2130331245010

Aditya Gajendra Nanaware 2130331245041

Yash Chandrakant Malap 2130331245039

DEPARTMENT OF COMPUTER
ENGINEERING
DR.BABASAHEB AMBEDKAR
TECHNOLOGICAL UNIVERSITY
LONERE-402103
Tal.Mangaon,Dist-Raigad(MS) INDIA
Acknowledgement

Apart from our own, the success of this report depends largely on the encouragement and
guidelines of many others. We are especially grateful to our Prof. Tejas Bhaise and also Prof.
A.Kiwlekar the Head of Computer Engineering Department, DBATU who has provided
guidance, expertise and encouragement. We are thankful to the staff of Computer Engineering
Department for their cooperation and support.

We would like to put forward our heartfelt acknowledgement to all our classmates, friends and all
those who have directly or indirectly provided their overwhelming support during our project
work and the development of this report.

Krushna Khedkar 2130331245010

Aditya Nanaware 2130331245041


Yash Malap 2130331245039
Abstract

Event Diary is an online event management system software project


that serves the functionality of an event manager. It is used to manage all the
activity related to event. The system allow registered user login and new
user are allowed to register on the application. The system helps in the
management of events, users and the aspects related to them. This proposed to
be a web application. The project provides most of the basic functionality
required for an event type .Event management is a process of organizing a
professional and focused event, for a particular target audience. It involves
visualizing concepts, planning, budgeting, organizing and executing events
which held in colleges.

ii
C o n tents

1 Synopsis 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Pro ject Idea . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
3. Motivation of the Pro ject . . . . . . . . . . . . . . . . . . . 1
4.Ob jective of the Pro ject . . . . . . . . . . . . . . . . . . . . 1
1.5 Module Description . . . . . . . . . . . . . . . . . . . . . . . 2
1.6 F unctionalities provided by Pro ject . . . . . . . . . . . . . . 3

2 P r o b l e m and Solution Definition and Scope 4


2.1 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Solution Statement . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Scope of the Pro ject . . . . . . . . . . . . . . . . . . . . . . 4

3 Functional and Non-Functional Requirements 6


1 . F unctional Requirements . . . . . . . . . . . . . . . . . . . . 6
2. Non-F unctional Requirements . . . . . . . . . . . . . . . . . 6

4 Research Methodology 8
4.1 Student’s Registration . . . . . . . . . . . . . . . . . . . . . 8
4.2 Student’s Login . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3 Teacher’s Login . . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Add E vents and F und Provider Information . . . . . . . . . 8
5.View E vents and F und Provider Information . . . . . . . . . 8
4.6 Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 Requirement Specification 9
5.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . 9
5.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . 9

6 U M L D i a g ra m s 10
6.1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . 10
6.2 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.3 E R Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

iii
6.4 Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
6.5 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . 14

7 T ools 16
7.1 H T M L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.2 C S S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.3 P H P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.4 M y S Q L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

8 A b o u t X a m p p Server 23

9 Implementation 26

1 0 A d vantages and D i s a d vantages 32


10.1 Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
10.2 Disadvanges . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

11 Conclusion 33

Bibliography 34

iv
L i s t of Figur es

6.1 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . 10


6.2 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.3 E R Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.4 Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5. Data Flow Diagram Level-0 . . . . . . . . . . . . . . . . . . 14
6. Data Flow Diagram Level-1 . . . . . . . . . . . . . . . . . . 14
7. Data Flow Diagram Level-2 . . . . . . . . . . . . . . . . . . 15

9.1 Teacher’s Login P age . . . . . . . . . . . . . . . . . . . . . . 26


9.2 Teacher Dashboard . . . . . . . . . . . . . . . . . . . . . . . 26
9.3 Add E vents . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.4 E vent Added . . . . . . . . . . . . . . . . . . . . . . . . . . 27
9.5 Database for E vents . . . . . . . . . . . . . . . . . . . . . . 28
6. Add F und Provider Information . . . . . . . . . . . . . . . . 28
7. Database for F und Information . . . . . . . . . . . . . . . . 29
8.Student’s Registration P age . . . . . . . . . . . . . . . . . . 29
9.9 Student’s Login P age . . . . . . . . . . . . . . . . . . . . . . 30
9.10 Student’s Dashboard . . . . . . . . . . . . . . . . . . . . . . 30
9.11 View Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
9.12 View Fund Provider Information . . . . . . . . . . . . . . . . 31

v
C h a pte r 1
Synopsis
1. I n t ro d u c t i o n

Event Diary is a site which will be used for maintaining records and up- gradation
of events taking placed in colleges and institutions. The purpose of Event Diary is to
automate the existing manual system by the help of computerized equipment’s, fulfilling
student requirement. So their valuable data/information can be stored for a longer period
with easy accessing and manipulating. Event Diary can lead to error free, secure, reliable
and fast management system. It can assist the student to concentrate on their other
activities rather than to concentrate on the record keeping. It will help organization in
better utilization of resources.

2. P r o j e c t Id ea

The project idea is to develop a system which will useful for any in- formation
regarding particular event can easily access to the event staff coordinators, H O D ,
student coordinator and participants.

3. Moti vati on of the P r o j e c t

The motive behind the project is to develop an application which will dedicated for
the purpose, Event organizers create schedules for events us- ing website interface and
assign student coordinators at the time of creation of schedule. The students can register
on the application and some of them register as coordinators. Only events organizers and
coordinators can up- load event related information on the application. The participants
can view events on application.

4. O b j e c t i v e of the P r o j e c t

The aim of the Event Diary Process is identifying events and determining
1
corresponding control measures. There can be several updates or changes in a service or
configuration item. Some of these changes can be critical while some changes can be
minor without impacting other aspects of the I T services. The categorization of these
events and defining appropriate control measures for these different events is an objective
of the Event Diary Process. Event Diary Process is providing a basis for service
assurance, reporting and service improvement. I T service providers aim for service
improvement to improve the provided services consistently to increase the value provided
to the students. The Event Diary Process helps to increase this value delivered to the
students.

5. Module Description

Event Management System is divided into following Modules:

1 . R e g i s t r a t i o n or L o g i n Mod u l e : In this module, user can first reg- ister


themselves. The registration module is aimed to help the users register to the events
of their choice. It is achieved by the help of a Registration form that asks users the
information such as their Name, Email, Mobile, Event to register, Class, Section
and Address. The user will submit the form after filling their details using the
submit button. The submit button will trigger the back-end code and will store the
user information in the user database. In this way, a user can successfully register in
the events if their choice.

2 . E v e n t Mod u l e : Events module contains in detailed information of various events


that are added to the Database. Various categories or types of events such as the
Technical, Non-Technical events, Cultural events, etc. can be listed in the
documentation module. And the orga- nized events can be listed under the type of
events as per their category. This module will contain names of the events,
registration links, price of registration (if applicable), posters of the events, and more
information about each of the events.

3 . A d m i n Mod u l e : The admin module is implemented by making use of the


concept of abstraction. The admin module will not be visible to the end users. It can
only be accessed by the admin and will contain information about the user analytic.
The admin will be able to add new events and modify or delete the existing events.

2
These changes will be reflected in the events module that is accessed by the end
users. The admin module is important to make overall changes to the events di-
rectly from the web application and is used by the students or faculties who are in
charge of organizing the events.

4. F u n d In f ormati on Mod u l e : Fund module contains detailed infor-


mation regarding Fund Provider or Sponsors.

6. Functional i ti es provided b y P r o j e c t

• Provides the searching facilities based on various factors such as college, student,
registration, etc.

• Project also manages the service details online for registration, college, etc.

• It tracks all the information of events, services, etc.

• Shows the information and description of the college, student.

• To increase efficiency of managing the college event.

• It deals with monitoring the information and transactions.

• Editing, adding and updating of records is improved which results in proper


resource management of college data.

3
C h a pte r 2

Problem and Solution Definition and


Scope
1. P r o b l e m S tatemen t

Events are held in all colleges and institutions. But it’s Management and Maintenance is
quite burdensome. Following are the difficulties faced by the colleges and
Committees:-

• Maintaining the list of events took placed or to be organized, with all those notes
and papers.

• Records of the Winners of the competitions and events. Usage of funds particularly
on the things and other expenditures can’t be explained properly to other students.

• Obtaining a proper feedback and Reviews or other suggestions from students is also
difficult.

2. S ol u ti on S tatemen t

Al l the problems and difficulties faced by colleges and committee members can be
resolved by using one site i.e Event Diary.
Event Diary site will help to maintain all the records regarding events, funds and other
things only at one place.
It will reduce the paper work so the problem of losing any kind of data will be reduced.
It will become easy for the teachers and committee members to organize and handle
the events.

3. S cop e of the P r o j e c t

1. The scope of the project is to build an Event Management System without any
issues that is designed to facilitate managing events without any trouble.

4
.

2. To assist the staff in capturing the efforts spent on their respective working areas.

3. To utilize resources in an efficient manner by increasing their produc- tivity


through automation.

4. It satisfy the User requirements.

5. Easy to understand by the User and Operator.

6. Easy to operate.

7. Have a Good user interface.

8. Expandable.

9. Delivered on schedule within a budget.

Goal: The goal of this project is to deploy proposed project, that is Event
Management System successfully.

Benefits:

• Manage College-level events with ease.

• Secured registration system.

• Provide abstraction of implementation details.

5
C h a pte r 3

Functional and Non-Functional


Requirements

1. Fu n cti on al Req u i remen ts

• Regi s tra ti on :
The user must correctly fill the registration form. The website must allow users to
log into their account by entering their email address and password.

• Admin:
The admin must enter only the admin username and password to ac- cess the admin
module. Already Set Username and Password for Staff Members. Only the staff
members can edit or add Events and Funds Information.

• E v e n t Man agemen t :
Only admin should be able to make changes to the events. Users should only be able
to view the listed events that were added by the admin.

• Logout:
The system provides the facility to logout from the site.

2. N o n - Fu n c t i o n a l Req u i reme n ts

• Operating System:
Website will be run on all Operating Systems like Windows 7, windows 10, and
others.

• S ecu ri ty :
Secured Website. No one can use this website without registration. We will use the
facility secure database to store student information. It is recommended that you
update the plugins in the Internet agent before the program is launched.

6
• Availa b i l i ty :
The Event Management System should never be down and should al- ways be
accessible.

• Accuracy:
The accuracy of the information published about the events in the ap- plication is
guaranteed, the admin or event organizers are responsible for it.

• Flexibility:
The Event Management System is flexible to develop new models and changes.

• Main ta i n a b i l i ty:
The Event Management System is easy to maintain and should be easy to fix bugs
in case any issues arise.

• Rel i a b i l i ty :
The application website guarantees the integrity of the data so it should be reliable.

• Observabil ity :
Only logging useful information and fixing errors as they are identified and
Implementing third-party monitoring services for crucial areas of the website.

• Perfo rman ce :
The website should be designed and built with an acceptable standard of
performance as a minimum.

• Acces s :
The website will be accessible everywhere through the internet.

• E n v i ro n me n t :
The environment includes external factors that impact how your system performs.

7
C h a pte r 4

Research Methodology
1. S tu d en t’s R e g i s t r a t i o n

To view events register on website. student’s registration details includes student name,
email, mobile number, department, year, P R N and password.

2. S tu d en t’s L o g i n

After registration login with your username that is email id and password.

3. Teacher ’s L o g i n

Teachers will login to their username and password that is already saved on the system.

4. A d d E v e n t s an d F u n d P ro v i d e r In f ormati on

Once logged in, teachers can manage event information and fund provider information.
They have the option to add new events and associated fund provider details where the
details, such as name, date, description, are en- tered into the system.

5. Vi e w E v e n t s an d F u n d P ro v i d e r In f ormati on

After logging in, the student will reach the dashboard on the student’s side. Options
include view events, view fund provider information, and logout.

6. Logout

On the teacher’s side, teachers can log out after adding event or fund provider
information. On the student side, students can log out after view- ing the event or fund
provider information.

8
C h a pte r 5

Requirement Specification

1. H a r d w a re Req u i reme n ts

• A Window P C

• Mac or Linux computer Or laptop

• Android mobile with a minimum Version 5.3

• Processor is not less than 500 M H Z

• R A M is not less than 700MB.

• Memory Required: Hardly 500MB-1GB

2. Software Req u i re men ts

• Mobile Operating System: Android 4.5 or later.

• Server Operating System: Windows 8/9/10/11.

• Platform for Coding: Sublime Text, visual code.

• Platform for Run the Project: Any Browser like Microsoft Edges, Chrome, Firefox.

• Available in Languages: H T M L , C S S .

• Back-end Language: P H P.

• Database: M yS Q L

9
C h a pte r 6

U M L Diagrams
1. Use Case Diagram

We have two types of Users for the website:

• Students

• Admin

Figure 6.1: Use Case Diagram

10
6.2 C l a s s D i a g ra m

Figure 6.2: Class Diagram

Class Diagram Description:

• S y s t e m: The system contains two attributes, student and teacher.

• S tu d en t : The student has qualities such as P R N , name, mail I D , mo- bile


number, year, password for registration and login to access the website.

• Tea cher: Teachers have their own username and password. Teacher adds
information like events and fund providers information.

• Vi e w Info rma tion : Students will view event information and fund provider
information.

• A d d Informa tion : Teacher will added event information and fund provider
information.

11
6.3 E R D i a g ra m

Figure 6.3: E R Diagram

E R Diagram Description:

• S tu d en t : Students consists attributes like P R N that is primary key (unique for


each student), name, mail id, department, year, mobile number (The student may
have more than one mobile number, therefore mobile number denoted by double ellipse
that is multi-values attribute).

• E v e n t s a n d Fu n d s : Events and Funds consists attribute name, date, description.


Students will view the events and fund provider infor- mation. Teacher will add and
manage the events and fund provider information.

• Teacher: Teacher consists attributes like username and password.

12
6.4 F l o wchart

Figure 6.4: Flowchart


Flowchart Description:

• Tea ch e r L o g i n : Teachers will login to their username and password that is


already saved on the system.

• Tea ch e r D a s h b o a rd : Options include add events to the dashboard, add fund


provider information, and logout.

• A d d E v e n t or F u n d Informa tion : Teachers can manage and add events and


fund provider information which includes name, date and description.

• Save Info rma ti on: After adding details, the details are added to the database
when the save button is clicked.

13
• S t u d e n t Regi strat i on : Register on the website first, to view the events.
The registration form has been added for security purposes.

• S t u d e n t L o g i n : The student will view events and fund provider infor- mation.

• Vi e w E v e n t s or F u n d Informati on : The student will view events and fund


provider information.

6.5 Data Flow Diagram

D F D Level - 0:

Figure 6.5: Data Flow Diagram Level-0

D F D Level - 1:

Figure 6.6: Data Flow Diagram Level-1

14
D F D Level - 2:

Figure 6.7: Data Flow Diagram Level-2

15
C h a pte r 7

T ools
1. HTML

H T M L stands for Hypertext Markup Language. It is the standard


markup language used for creating web pages and web applications. H T M L provides the
structure and presentation of content on the World Wide Web. H T M L documents are
typically saved with a .html or .htm file extension and can be viewed in a web browser.
The browser interprets the H T M L code and renders the web page according to the
defined structure and presenta- tion instructions. H T M L is often used in conjunction
with C S S (Cascading Style Sheets) and JavaScript to create interactive and
visually appealing web pages. C S S is used for styling and layout, while JavaScript is
used for
adding dynamic behavior and interactivity to web pages.

Here’s some more detailed information about H T M L :

• S t r u c t u re : H T M L documents are structured using H T M L tags. Tags are


enclosed in angle brackets ( < > ) and are used to define the structure and elements of
a web page. The basic structure of an H T M L document includes opening and
closing tags for the < html > , < head > , and
< body > elements.

• E l e men ts : H T M L elements are the building blocks of web pages. They define the
different parts of a document, such as headings, paragraphs, images, links, lists,
tables, forms, and more. Each element is represented by a tag, such as < h1 > for a
heading, < p > for a paragraph, < img > for an image, and so on.

• Ta gs : H T M L tags define the purpose and meaning of different parts of the content.
They can be used to format text, create headings, insert images, add links, create
lists, and more. Some common tags include
< h1 > to < h6 > for headings, < p > for paragraphs, < img > for
images, < a > for links, < ul > and < ol > for lists, etc.

16
• A t t r i b u t e s : H T M L elements can have attributes that provide addi- tional
information about them. Attributes are placed within the open- ing tag and consist
of a name and a value. For example, the < img > element has attributes like src
(specifying the image U R L ) and alt (pro- viding alternative text for the image).

• Nesting: H T M L elements can be nested inside one another to create a


hierarchical structure. This means that elements can be placed in- side other
elements, forming parent-child relationships. For example, a paragraph ( < p > )
can contain a link ( < a > ) or an image ( < img > ) .

• H y p e r l i n k s : H T M L allows you to create hyperlinks that connect web pages or


specific parts of a page. The < a > tag is used to define links, and the href
attribute specifies the destination U R L . Users can click on the link to navigate to
the specified U R L or location within the same document.

• Te x t F o r m a t t i n g : H T M L provides tags for formatting and styling text. For


example, the < b > tag is used to make text bold, the < i > tag is used for
italicizing text, the < u > tag is used for underlining text, and the < em > tag
is used for emphasizing text. There are many more formatting tags available in
HTML.

• Fo r ms : H T M L provides form elements ( < f o r m > , < input > , < select
> , etc.) for creating interactive forms on web pages. Forms allow users to input
data and submit it to a server for processing. Var- ious types of input fields are
available, such as text fields, checkboxes, radio buttons, dropdown lists, and
buttons.

• S t y l i n g : While H T M L is primarily concerned with content structure, you can


apply styles to H T M L elements using C S S (Cascading Style Sheets). C S S
allows you to control the visual presentation of H T M L el- ements, including
properties like colors, fonts, sizes, margins, and more.

7.2 CSS

C S S (Cascading Style Sheets) is a style sheet language used for describing the
presentation and visual appearance of H T M L and X M L documents. It

17
defines how elements should be displayed on a web page, including their layout, colors,
fonts, spacing, and other visual properties.
There are three main types of C S S :

1 . I n l i n e C S S : Inline C S S involves placing the C S S directly within the H T M L


elements using the ”style” attribute. With inline C S S , you define the styles for a
specific H T M L element within the element itself.

2 . I n t e rn al C S S :Internal C S S is defined within the < style > tags in the <
head > section of an H T M L document. Styles defined here apply to the entire
document or specific sections of it. Internal C S S allows for more organization and
reusability than inline C S S , as multiple elements can share the same styles.

3 . E x t e r n a l C S S :External C S S involves placing the C S S code in a sep- arate


file with a .css extension. This file is then linked to the H T M L document using
the < l i n k > tag in the < head > section. Exter- nal C S S offers the most
flexibility and maintainability, as styles can be reused across multiple H T M L
documents, making it easier to manage and update the styles.

Here are some key points about C S S :

1. Selector: C S S selectors are used to target specific H T M L elements for styling.


Selectors can be based on element names, class names, IDs, attributes, and more. For
example, you can target all < h1 > elements by using the selector h1, or target
elements with a specific class by using the selector .classname.

2 . P ro p e r t i e s an d Values: C S S properties define the specific visual char-


acteristics of an element, such as color, font, size, margin, padding, background, and
more. Properties are paired with values to specify the desired styling.

3 . C a s c a d i n g an d Specifi ci ty: C S S follows the cascading principle, which


means that multiple styles can be applied to an element, and their effects will be
combined. If conflicting styles are applied, C S S uses the concept of specificity to
determine which style takes precedence. Speci- ficity is based on the type of selector
used and any additional qualifiers like classes, IDs, or inline styles.

4 . B o x Mod el : The C S S box model describes how elements are rendered in terms of
their content, padding, borders, and margins. Each element is considered as a
rectangular box, and you can control the size and

18
spacing of these boxes using properties like width, height, padding, border, and
margin.

5 . Res p on s i v e D e s i g n : C S S allows you to create responsive web designs that adapt


to different screen sizes and devices. Media queries can be used to apply different
styles based on the viewport width, allowing you to create layouts optimized for
desktop, tablet, and mobile devices.

6 . C S S Prep rocessor s : C S S preprocessors like Sass and Less provide ad- ditional
functionality and features to enhance the C S S development pro- cess. They introduce
variables, mixins, nesting, and other programming- like constructs that make C S S
more powerful and maintainable.

7 . C S S Fra mew o rk : C S S frameworks like Bootstrap, Foundation, and Bulma


provide pre-written C S S and JavaScript components that can be used to quickly
build responsive and visually appealing web interfaces. These frameworks offer a set
of standardized styles and components, reducing the amount of custom C S S you
need to write.

3. PHP

P H P (Hypertext Preprocessor) is a popular server-side scripting lan- guage that is


widely used for web development. It is embedded within H T M L code and executed on
the server, generating dynamic web pages and interacting with databases.

Here are some key points about P H P :

• S e rv e r- S i d e S c r i p t i n g : P H P is primarily used for server-side script- ing,


meaning it is executed on the web server before the H T M L is sent to the client’s
browser. This allows P H P to perform various server-side operations, such as
generating dynamic content, processing form data, interacting with databases, and
more.

• E a s y In tegra ti on w i th H T M L : P H P code can be embedded directly within


H T M L files, using special tags such as ′ <?php ′ and ′ ? > ′ to delineate P H P code
blocks. This integration enables the mixing of P H P logic with H T M L markup,
making it easy to generate dynamic content based on data or user input.

19
• Dat ab as e In teracti on : P H P has extensive support for interacting with
databases, particularly M yS Q L. It provides functions and exten- sions that allow
you to establish database connections, execute queries, retrieve data, insert/ update/
delete records, and handle transactions. This capability enables the creation of
database-driven web applica- tions.

• W i d e R a n g e of Fu n cti on al i ty : P H P offers a rich set of built-in functions for


various tasks, including string manipulation, file handling, regular expressions,
date/time processing, and more. Additionally, P H P supports object-oriented
programming ( O O P ) concepts, allowing you to create reusable classes and objects
for structured and modular code.

• We b A p p l i c a t i o n Devel op men t : P H P is well-suited for building web


applications of varying complexity. It can handle user authentication and session
management, process form submissions, validate user input, and manage stateful
interactions with users. With P H P frameworks like Laravel, Symfony, and
CodeIgniter, you can expedite development and follow best practices.

• C r o s s - P l a t f o r m C o m p a t i b i l i t y : P H P is a cross- platform language, which


means it can run on various operating systems like Windows, ma- cOS, Linux, and
Unix. This flexibility allows developers to deploy P H P applications on different
web servers and host environments without major compatibility issues.

7.4 MySQL

M yS Q L is an open-source relational database management system ( R D B M S ) that is


widely used for storing, managing, and retrieving data. It is one of
the most popular and widely used database systems in the world. M yS Q L is known
for its scalability, performance, and ease of use. Its performance, flexibility, and
compatibility with various programming languages make it a popular choice for storing
and retrieving event-related information effi- ciently.

Here are some key features and aspects of M yS Q L:

20
• Re l a t i o n a l Da ta b a se M a n a g e me n t S y s te m: M y S Q L follows the relational
model, which means it organizes data into tables consisting of rows and columns. It
allows users to define relationships between tables using primary and foreign keys,
ensuring data integrity and enabling efficient data retrieval.

• S t r u c t u re d Q u e r y L a n g u a g e ( S Q L ) : M y S Q L uses S Q L as its query


language. S Q L provides a standardized way to interact with the database, allowing
users to create, modify, and query data. With S Q L , you can perform operations like
creating tables, inserting, updating, and deleting data, and retrieving data based
on various conditions.

• I n teg ra ti o n w i th We b A p p l i c a t i o n : M y S Q L can be integrated into the


backend of a web application that powers the college event manage- ment system.
The application can utilize S Q L queries to interact with the database, retrieve and
update data, and perform various operations.

• C ro s s - P l a t f o r m C o m p a t i b i l i t y : M y S Q L is compatible with multi- ple


operating systems, including Windows, macOS, Linux, and various Unix-like
systems. This makes it versatile and allows it to be deployed in different
environments.

• S ca l a b i l i t y a n d Pe r fo rman ce: M y S Q L is designed to handle large amounts of


data and high traffic loads. It supports techniques like replication, sharding, and
partitioning to distribute data across multiple servers, improving performance and
scalability.

• S e cu ri t y : M y S Q L offers various security features to protect the database and its


data. It includes user authentication and authorization, access control through user
privileges, encryption for secure data transmission, and support for secure
connections using S S L / T L S .

• I n teg ra ti o n and Compatibility: M y S Q L integrates well with many


programming languages and frameworks, making it a popular choice for web
development. It offers client libraries and connectors for languages such as P H P,
Python, Java, Node.js, and more. M y S Q L is also com- patible with various
popular tools, frameworks, and platforms in the software development ecosystem.

21
• A d m i n i s t r a t i o n and Man age men t : M yS Q L provides a range of tools for
database administration and management. These include command-line tools like
the M yS Q L shell, graphical user interfaces ( GU Is ) such as M yS Q L Workbench,
and web-based management tools for tasks like creating databases, managing users,
optimizing queries, and monitoring performance.

• E v e n t Regi strati on s : M yS Q L can track event registrations by asso- ciating


participants with specific events. This helps in managing par- ticipant lists,
checking attendance, and ensuring event capacity limits are respected.

M yS Q L is widely used in various applications, ranging from small web- sites and
personal projects to large-scale enterprise systems. Its combination of performance,
scalability, ease of use, and community support has made it a popular choice for
developers and organizations seeking a reliable and powerful database management
system.

22
C h a pte r 8

A b o u t X a m p p Server

X A M P P is a widely used open-source software package that provides a local


server environment for web development and testing. It stands for Cross-platform(X),
Apache(A), M yS Q L( M), P H P ( P ) , and Perl(P), which are the components included
in the package.

Here is some information about X A M P P :

1 . L o c a l S e r v e r E n v i ro n m e n t : X A M P P creates a local server envi- ronment on


your computer, allowing you to run and test web appli- cations locally without the
need for a live web server. It provides a self-contained environment with all the
necessary components to run a web application.

2 . We b A p p l i c a t i o n Develop men t: X A M P P ’s Apache web server en- ables the


hosting of the event management system’s web application. Developers can create
and test web pages using H T M L , C S S , JavaScript, and server-side scripting
languages like P H P. This allows them to build the user interface, implement
functionalities, and test the application locally.

3 . M y S Q L Datab as e Server : X A M P P includes the M yS Q L database server,


which is a widely used relational database management system (RDBMS).
M yS Q L allows you to create and manage databases, store and retrieve data, and
interact with the data using S Q L queries.

4 . P H P P r o g r a m m i n g L a n g u a g e : X A M P P bundles P H P, a popular server-


side scripting language used for web development. P H P enables dynamic web page
generation, processing of form data, database con- nectivity, and other server-side
functionalities.

5 . E a s y Instal lation a n d Con f i gu r at i on : X A M P P offers a straight- forward


installation process, typically involving downloading the pack- age from the official
website and running the installer. Once installed, X A M P P provides a control
panel interface that allows you to start and stop the server components, configure

23
settings, and manage the server environment easily.

6. C o m m u n i t y S u p p o r t an d Docu m en ta ti on : X A M P P has a large and


active community of users and developers. There are extensive online resources,
forums, and documentation available to help users troubleshoot issues, learn how to
use X A M P P effectively, and explore advanced features.

To install X A M P P (a popular software package that includes Apache, M yS Q L, P H P, and


Perl), follow these steps:

1 . Dow n l oad X A M P P :
Visit the official X A M P P website (https :/ /www.apach ef ri en ds .org/ ) and
download the appropriate version of X A M P P for your operating system (Windows,
macOS, or Linux).

2 . R u n the Installer:
Once the download is complete, run the X A M P P installer file. You may be
prompted for administrator privileges if you’re installing on Windows or macOS.

3. Select C o mp o n e n t s :
The installer will display a list of components available for installation. By
default, Apache, M yS Q L, P H P, and phpMyAdmin are selected. You can choose to
install additional components if needed. Click ”Next” to proceed.

4 . C h o o s e Installation Folder:
Select the destination folder where you want to install X A M P P. The default
location is usually fine, but you can choose a different folder if desired. Click
”Next” to continue.

5 . S t a r t M e n u Folder:
Specify the folder name for the X A M P P shortcuts in your Start Menu. You can
keep the default name or choose a custom name. Click ”Next” to proceed.

6 . B i t n a m i for X A M P P :
The installer may ask if you want to install Bitnami for X A M P P, which provides
additional software applications. You can choose whether to install Bitnami or skip
it. Click ”Next” to continue.

24
7 . R e a d y to Install:
Review the installation settings you have chosen. If everything looks
correct, click ”Next” to start the installation process. The installer will copy the
necessary files to your computer.

8. Installation Progress :
Wait for the installation process to complete. This may take a few minutes.

9 . C o m p l e t e the Installation :
Once the installation is finished, you will see a screen indicating that X A M P P has
been successfully installed. Optionally, you can choose to start the X A M P P
Control Panel immediately. Click ”Finish” to exit the installer.

1 0 . S t a r t X A M P P C o n t ro l Pan el :
If you didn’t choose to start the Control Panel during the installation, you can find
it in the installation folder. Open the X A M P P Control Panel and start the Apache
and M yS Q L services by clicking the ”Start” button next to each.

1 1 . Ve r i f y Installation :
Open a web browser and visit h ttp :/ / l o cal h ost/ . You should see the X A M P P
default page if everything is set up correctly.

25
C h a pte r 9

Implementation

Teacher ’s Lo gi n :

Figure 9.1: Teacher’s Login Page

Teacher ’s Dashboard:

Figure 9.2: Teacher Dashboard

26
A d d Events:

Figure 9.3: Add Events

Eve n t A d d e d Successfully:

Figure 9.4: Event Added

27
D a t a stored in database:

Figure 9.5: Database for Events

A d d F u n d Pro vi der Information:

Figure 9.6: Add Fund Provider Information

28
D a t a stored in database:

Figure 9.7: Database for Fund Information

Student ’s Registration Page:

Figure 9.8: Student’s Registration Page

29
Student ’s L o g i n Page:

Figure 9.9: Student’s Login Page

Student ’s Dashboard:

Figure 9.10: Student’s Dashboard

30
V i e w Events:

Figure 9.11: View Events

V i e w F u n d Pro vi der Information:

Figure 9.12: View Fund Provider Information

31
C h a pte r 10

Advantages and Disadvantages

1. Ad van tages

• This system reduces manual efforts, and it saves time and lowers costs.

• It enhances the overall attendee experience by offering convenient event registration.

• The system facilitates effective communication between student and teacher.

• It enables the real-time monitoring of events.

• It captures and stores event and fund-related data, such as name of the event, date
and description.

• It provide the centralized platform for planning and organizing events.

2. Di sad van ges

• This system may require significant effort and resources.

• It depends on costs such as licensing fees, maintenance fees, and addi- tional
charges for customization or advanced features.

• Integrating an event management system with existing organizational systems or


third-party applications can sometimes be complex.

32
C h a pte r 11

Conclusion

In conclusion, the event management system allows teachers to man- age and add
event and fund provider information, while students can view events. The system
provides a platform for teachers to organize events and collaborate with fund providers,
enabling seamless event planning and exe- cution. Meanwhile, students can stay informed
about upcoming events and access event details.
B y incorporating features such as teacher login, event creation, fund provider
management, and event viewing, the system facilitates efficient communication and
coordination between teachers and students. Teachers can easily add and update event
information, ensuring accurate and up- to-date details for students. Students, on the other
hand, can access the system to stay informed about various events, including event names,
dates, locations, and descriptions.
This event management system enhances the overall event management process by
streamlining event organization, improving accessibility to event information, and
promoting effective communication between teachers and students. With the ability to
manage events and fund provider information, as well as view events, the system provides
a comprehensive solution for effective event planning and execution within an educational
institution or any similar context.

33
Bibliography

1 Robin Nixon. “Learning P H P , M y S Q L JavaScript: With jQuery, C S S


H T M L 5 “ , fifth addition, October 2018, 832 pg.

2 Luke Welling, Laura Thomson. “ P H P and M y S Q L Web Development“, fifth


addition, November 2016, 688 pg.

3 Robin Nixon. “ M y S Q L Crash Course“, fifth addition, Oct 2018, 832 pg.

4 Ben Forta. “Learning P H P , M y S Q L JavaScript: With jQuery, CSS


H T M L 5 “ , fifth addition, November 2005, 336 pg.

5 https://dev.mysql.com/doc/

6 https://stackoverflow.com/

34

You might also like