INTERNSHIP/PROJECT REPORT

Submitted By

Mandaliya Aayushi .D.

(226090307072)

To
COMPUTER ENGINEERING DEPARTMENT
C U SHAH (GOVT.) POLYTECHNIC – SURENDRANAGAR

GUJARAT TECHNOLOGICAL UNIVERSITY – AHMEDABAD

JUNE-AUGUST – 2024
 INDEX
Sr No Content

1 Student Registration Form

2 Attendance Sheet

3 Daily Log with Topic Learned (Day or Week wise)

4 Feedback from Industry

5 Completion Certificate from Industry

6 Certificate from Institute

7 Project Introduction

8 Project advantages and limitations

9 Project application(s)

10 Frontend and Back-end Technologies of project

11 Hardware and software requirements of project

12 Functional and Non-Functional requirements of project

13 List of Users and Use case Diagrams for each user of project

14 Data Dictionary of project

15 Sample coding of project

16 Screen shot of various output pages of project

17 Testing strategies of project

18 Conclusion and Future work

19 References

20 PPTs of Project presentation

21 Screen shot of Project Poster

22 Source code, Database, PPTs, Final report of Project in DVD(s)

 Introduction

Project Name: Event Management System

My Project Event Management System is designed to simplify the way events are
organized and attended.

The platform supports three key user types:

Guest Users: These users can explore event details, view event galleries, and have the
option to sign up or log in to book events.

Registered Users: Once logged in, these users can book events they are interested in,
making the process more personalized and efficient.

Admin Users: Admins have full control over the system, including the ability to add
new events, create and manage event categories, and oversee overall event
management.

The goal of this project is to provide a robust and intuitive system that enhances both
the event booking experience for users and the event management process for
administrators.
 Advantages and Limitations

Advantages:
ü Easy Event Management: Admins can quickly add and manage events,
making the process more efficient.
ü Better User Experience: Registered users can book events easily, while
guest users can view event details without signing up.
ü Accessible Information: The system helps users find and book events more
easily.
ü Centralized Control: Admins have all event-related tasks and categories in
one place.
ü Improved Communication: The system can send updates to keep users
informed.

Limitations:
ü Privacy Issues: Collecting personal data from users might lead to privacy
concerns.
ü System Complexity: Managing different types of users and their
permissions can be complicated.
ü Tech Dependence: Users need to be comfortable with technology to use the
platform effectively.
ü Ongoing Maintenance: The system needs regular updates and maintenance,
which can be costly.
ü Performance Risks: The system might slow down or face issues if there are
too many events or users.
 Project Application(s)

1. Event Viewing: Guests can only browse events; registered users can view more
details and book.

2. Event Booking: Registered users can book events and track their bookings.

3. User Management: Admin manages registered users and their access.

4. Event Management: Admin creates, updates, and deletes events.

5. Category Management: Admin organizes events into categories.

6. Booking Confirmation: Admin confirms or rejects event bookings made by

users.
 Frontend and Backend Technologies

Frontend Technologies:
1. React JS
2. HTML, CSS, JS

Backend Technologies:
3. Mongo DB
 Hardware and Software Requirements

Hardware Requirements:
Processor: Dual-core or higher

RAM: 4 GB minimum (8 GB recommended)

Storage: 20 GB available (SSD preferred)

Internet: Stable connection

Software Requirements:

OS: Windows 10/11, macOS, or Linux

Node.js: Latest LTS version for React

MongoDB: Local or cloud (MongoDB Atlas)

Code Editor: Visual Studio Code (recommended)

Version Control: Git

Browser: Chrome or Firefox

API Tool: Postman (for testing APIs)

 Functional Requirements

Functional requirements:

1. Guest User

• View all available events without registering

• Register an account to become a registered user

2. Registered User

• Log in to access additional features

• View and filter events based on categories
• Book events
• Make payments for booked events

3. Admin User

• Log in to access admin functionalities

• Update existing events
• Delete events
• Add new event categories
• Edit existing event categories
• Delete event categories
• Manage User Requests
 Non-Functional Requirements

Non-Functional Requirement:

• Performance

o The system should handle many concurrent users without significant

performance degradation.
o Event pages should load within 3 seconds under normal load conditions.

• Scalability

o The system should be scalable to accommodate an increasing

number of users, events, and categories.
• Usability

o The user interface should be intuitive and easy to navigate for all user
types (guest, registered user, and admin).
o The registration and booking processes should be simple and quick.

• Availability
o The system should be available 99.9% of the time, with minimal
downtime for maintenance.
• Reliability

o The system should consistently perform its intended functions

without failure.
• Compatibility

o The system should be compatible with modern web browsers and

responsive across various devices (e.g., desktops, tablets,
smartphones).
 List of Users and Use case Diagrams for each user of project

USERS:

1. Guest User
These users can explore event details, view event galleries, and have the
option to sign up or log in to book events.
2. Registered User

Once logged in, these users can book events they are interested in,
making the process more personalized and efficient.
3. Admin User

Admins have full control over the system, including the ability to add
new events, create and manage event categories, and oversee overall
event management.
 View events

Register to
become
Registered user

View Events

Guest user
Book events

Make Payment for

booked payments

Register himself

Filter based on
category

Registered user CRUD event

CRUD event category

Filter event

Manage bookings

Manage Users

Admin
 Data Dictionary of project

Admins Collection:

• email: String - Admin's email address (required, unique)

• password: String - Admin's password (required)

Category Collection:

• name: String - Name of the event category (required)

• image: String - URL of the category image (optional)

Contact Collection:

• name: String - Contact person's name (required)

• email: String - Contact person's email (required)
• country: String - Contact person's country (required)
• phone: String - Contact person's phone number (required)
• password: String - Contact person's password (required)

Events Collection:

• image: String - URL of the event image (required)

• date: Date - Event date (required)
• time: String - Event time (required)
• price: Number - Price of the event (required)
• category: String - Event category (required)
• capacity: Number - Maximum number of participants (required)
• location: String - Event location (required)
• description: String - Event description (required)

Gallery Collection:

• imageUrl: String - URL of the gallery image (required)

• eventName: String - Name of the related event (required)
•
Users Collection:

• name: String - User's full name (required)

• email: String - User's email address (required, unique)
• password: String - User's password (required)
 Sample Coding

AdminInfo.js-
AdminLogin.js-
UserList.js
User Side-

Login.js
Profile.js
Events.js
Screen shot of Project Poster
 Testing strategies of project

1. Unit Testing:

• Test individual components of the system, such as user registration,

event booking, payment processing, and event category

management.

• Ensure that each function or module works as expected in isolation.

2. Integration Testing

• Test the interaction between different modules, such as the

interaction between the registration module and the user

authentication module.

• Verify that the system components work together smoothly (e.g.,

booking an event triggers payment processing and updates the

event availability).

3. Functional Testing

• Verify that the system's functionalities meet the specified

requirements.

• Test all user actions (guest viewing events, registered user booking

and paying for events, admin managing events and categories) to

ensure they perform as expected.

 Conclusion and Future work

Conclusion:

The event management system designed here effectively caters to three distinct
user types: guests, registered users, and admins. It provides a seamless
experience for viewing, booking, and managing events, with robust functionality
for event categorization and payment processing. By implementing a thorough
set of functional and non-functional requirements, and applying comprehensive
testing strategies, the system ensures reliability, security, and user satisfaction.

Future Work:
• Advanced Analytics and Reporting: Introduce analytics features for admins to
track event popularity, user engagement, and financial metrics, helping them
make data-driven decisions.
• Social Media Integration: Allow users to share events on social media
platforms, increasing visibility and engagement.
• Personalized Recommendations: Implement a recommendation engine that
suggests events to users based on their past bookings and preferences.
• Integration with External Systems: Consider integrating with external
calendars (like Google Calendar) and payment systems for a more streamlined
user experience.
These future enhancements can further improve the system’s functionality, user
engagement, and overall satisfaction, ensuring that it remains competitive and
relevant in the dynamic landscape of event management solutions.
 References

• https://youtu.be/mUFIA5OOcUI?si=cdiBScvoxPUmYil3
• https://youtu.be/J6mDkcqU_ZE?si=9fIUXGtJKGjNdXoG
• https://youtu.be/Kvb0cHWFkdc?si=n8czL6jjhqIFsslY
PPTs of Project presentation