Table of Contents
Introduction............................................................................................. 2
Entity Relationship Diagram....................................................................3
Normalization..........................................................................................5
Database Schema.....................................................................................5
Introduction
In today’s digital academic environments, managing, organizing, and delivering information
related to college events has evolved from cumbersome manual systems to advanced software
platforms. A Database Management System (DBMS) serves as the backbone for these platforms,
enabling secure, efficient, and scalable handling of vast amounts of structured data that represent
events, users, ticketing, venues, and more.
Figure 1 Event Planning and Scheduling Flowchart.
The College Event Portal is designed as a sophisticated web application that leverages the
capabilities of a modern DBMS to track, store, and manipulate data relevant to the lifecycle of
campus events. The portal is intended to address critical needs for students, organizers, and
administrators by offering a centralized solution for event registration, ticket management,
automated QR ticket generation, and real-time data retrieval. In traditional systems, event
management is prone to errors such as data duplication, loss of information, and lack of up-to-
date visibility. The DBMS-based portal efficiently resolves these issues by integrating robust
modules for event listings, user registration, ticketing, and attendance management using
relational databases.
A well-designed DBMS allows users to interactively query available events, register, and receive
digital tickets. All user transactions, event updates, and ticket generation processes are
transparently logged in the database, ensuring data integrity and security across all operations.
These records can be referenced by event organizers and administrative staff for planning,
reporting, or auditing purposes, supporting concurrent user access and maintaining consistency.
Centralizing college event information within a DBMS offers several advantages:
Reduced data redundancy due to normalization and relational integrity.
Improved data consistency and accuracy, as the system enforces unique constraints on
user registrations and ticket generation.
Enhanced user experience through real-time search and filter functionalities.
Security for sensitive event and user information via role-based access control.
Reliable data backup and recovery to safeguard against failures or unauthorized access.
In addition, the system supports modularity and scalability, accommodating new event
categories, expanding user bases, and integrating additional features like analytics dashboards or
automated notifications. The DBMS is vital for the automation of operations such as ticket
allocation, attendance monitoring via QR code scanning, and generation of event participation
reports.
In summary, the College Event Portal project, underpinned by a robust DBMS, streamlines event
organization and participation in academic institutions. By transitioning from disconnected,
manual processes to an integrated database platform, the portal empowers students and staff,
enhances operational efficiency, and strengthens the digital backbone of college event
management.
Entity Relationship Diagram
An ER diagram (Entity Relationship Diagram) is a visual tool used to model the structure of a
database. It shows:
The main entities (tables) in the system,
The attributes (fields) those entities have,
And the relationships (connections) between those entities.
For this college event portal project, the ER diagram includes:
User: stores student, organizer, and admin details.
Category: types of events (tech, fun, etc.).
Event: event information, linked to Category and Organizer.
Ticket: registration for an event, assigned to User and Event.
Feedback: comments/ratings from User about Event.
Attendance: tracks whether User attended Event.
Notification: messages sent to User.
Attachment: event files (banners, documents).
Relationships show, for example:
A User can book multiple Tickets
An Event belongs to one Category, but many Events can be in a Category
An Event can have many Attachments and Feedback entries
This diagram guides how tables connect and helps keep data organized and consistent.
Figure 2 ER Diagram for Event management System.
Advanced Features Included:
Event approval workflow and status.
Event banners/flyers.
Notification system for users.
Digital attendance and ticket QR code.
Waitlist capacity via max_seats (add more logic if needed).
Event feedback/rating system.
Attachments for files/certificates/post-event reports.
Normalization
Normalization in this project follows the common database normalization forms to ensure
efficient and reliable data storage:
First Normal Form (1NF):
Each table column holds atomic, indivisible values, with no repeating groups or arrays.
For example, event categories are stored in a separate categories table rather than
multiple category columns within the same table.
Second Normal Form (2NF):
All non-key attributes fully depend on the entire primary key. For instance, in tables with
composite keys, such as ticket details linked by both user_id and event_id, data is
organized so that no partial dependency exists.
Third Normal Form (3NF):
No transitive dependencies exist; non-key attributes depend only on primary keys. For
example, user and event details are separated, avoiding redundant or dependent
information stored across tables.
Advanced normalization avoids data redundancy and update anomalies, supports data integrity,
and improves query performance in the College Event Portal’s complex relations among users,
events, tickets, and feedback.
Additional normalization levels (4NF and 5NF) are generally not required at this scale but ensure
multi-valued dependencies and join dependencies are well managed if the system expands
significantly.
Database Schema
A database schema is the blueprint or structure that defines how data is organized in a database.
It specifies the tables, their columns (attributes), data types, keys, constraints, and relationships
among the tables to ensure data integrity and efficient retrieval.
Database Schema in This College Event Portal Project
The database schema consists of several interconnected tables that represent entities such as:
Users: Stores registration details, roles (student, organizer, admin), and contact
information.
Categories: Defines types of events (tech, fun, seminars).
Events: Contains event-specific data like title, description, date, venue, organizer, and
status for approval workflow.
Tickets: Tracks which users booked which events along with unique QR codes and
attendance.
Feedback: Stores users' ratings and comments for events.
Attendance: Logs user check-ins and check-outs for events.
Notifications: Messages for users regarding event updates or ticket status.
Attachments: Event-related documents such as banners, flyers, or certificates.
Each table has primary keys to uniquely identify rows and foreign keys to enforce referential
integrity and model relationships (e.g., an event belongs to a category; tickets link users to
events).
This schema supports complex queries needed for event management like filtering events by
category, managing event registration, generating tickets with QR codes, collecting feedback,
and tracking attendance efficiently.
