FESTPROBE

1. PROBLEM STATEMENT:
● College fest event organization application
2. INTRODUCTION :
● Definition of the project is college event scheduling and organization. This application
leads for handling and formation of event and its schedule. The project brings the entire
manual process of intercollegiate festival management online which is built using
Android studio as a frontend and Firebase database as a backend. The main purpose of
this project is to simplify the process of handling each event by providing an app for
admin and students. The admin part consists of multiple modules where admin or
authorized person is responsible for adding the type of event(technical / non-technical)
on the app. Also this module can view the student registration for a particular event and
lastly, viewing the results of all events held in college. Student module consists of
viewing and getting registered for the event of their choice, pay the event activity fees if
applicable and can view all the registered events.
3. MOTIVATION :

3.1 -> PROJECT PURPOSE

The purpose of making this application is to provide easiness in finding all the fests
held in the college premises and its schedule at one place. The invention satisfies the
forgeing needs and avoids the drawbacks and limitation and frustration of the prior
art, and provides a more better, more timely and effective process of communication
to schedule and coordinate events by utilizing internet –based –application.

3.2 ->SCOPE OF PROJECT

The scope of the project includes creating a user interface to android system as well
as a backend that will emulate some of its behavior, specifically for testing. Fest
management is the application of management, creation and development of
technical fests and events.
The application generally relates to a system and method to schedule events and
More particularly, to a system and method for scheduling technical events among
entities such as organization that may have limitations for scheduling ,such as
geographical requirements ,constraints by timing ,conflicts,availability,or other
factors.
The application leads to provide the user especially the student the reliability in
finding the schedule of events at one place rather to go for each of the college
websites. The admin just have post the event that can be viewed by the students

3.3 ->OBJECTIVE
 The process of travelling from one college to another to register students is time
consuming process and wastage of human efforts. To overcome this problem our
app provides a medium where one can get the schedule of an event by just
opening our application .

4. SYSTEM ARCHITECTURE:
Logout

REGISTER

Name

password

email

STAR
 5. Software and hardware requirements:

ADMIN Display the details

● OS : Android
of registered
● Frontend : Android studio 3.5.1 students in google
● Backend : Firebase Database admin form format
Not
● Hardware
Register :via
1 TB memory
Registered? 8GB RAM ******
Email Verification

Show password
6. PRODUCT
LOGIN FEATURES:
123456
email FUNCTIONAL REQUIREMENTS
6.1->
● The invention satisfies the foregoing needs and avoids the drawbacks and
password limitations and frustrations of the prior art, and providestechnical
a better, more timely
STUDENT
and effective process of communication to schedule and coordinate events by POSTER
utilizing Internet-based application.
This product contains twoemail
major Users. First the admin will allow the user for
Link to register through
accessing this application by giving the permission rights and access control. Google form
And lastly The End User i.e.******
Student, they can see the list of the events and
schedule of the event. Show password Non- For more

technical info(contact no)

USER CLASSES AND CHARACTERISTICS
● ADMIN
The admin will have all the access to this product. The Admin will
provide the access permission to the users which are students and
colleges.
● STUDENT
The student are the end-user entity, they will be having the access rights
to see the event schedule in poster format. And register their new
account providing their basic details.

6.2-> NON- FUNCTIONAL REQUIREMENTS

PERFORMANCE REQUIREMENTS

● Better performance will lead to better operating environment. For better

environment the user needs a high speed internet so that the upload and
download will be done better.
 SECURITY REQUIREMENTS
● The login details must be kept confidential so that other user may not login
using other's id and password. Especially the college login details must be kept
confidential so that other user may not post a fake event schedule.
6.3-> PROJECT PLAN
● At the beginning of the project, we scheduled meeting time for the group
to discuss on the design and implementation of the software and what
language to use for writing the software. We had several meetings to this
effect. We then developed a time-line for the project–when we would be
releasing the first version for scrutiny and the estimated time we thought
we would use for refactoring. We also pondered on a suitable name for
the project. The group was then divided that would work on parts of the
code. We kept in touch with each other and whenever we had difficulties,
we asked each other questions. On some occasions, we had to pretend we
were the customer so as to figure out some of the things that user
would desire, such as the friendliness of the user interface .

7. DESIGN:
7.1 ->E-R DIAGRAM
Entity-Relationship diagram is a detail & logical representation of entities and
data elements for an organization. This technique is used in database that helps
in an enterprise are related to each other. There are 3 types of E-R diagram:
one to one :
It is a one to one relationship is an association between 2 entities.
one to many:
One-to-many relationship exists when one entity related to one or more entity.
Many to many:
It describes entities that may have many relationships among each other.
The basic symbols for E-R diagram are as described below:
This rectangle represents entity set.

This arrow is known as flow line. It links attributes to entity set & entity
set to relationship.

This diamond represents relationship among entity set. The association

among several entities in E-R diagram is known as Relationship.

This oval represents various types of data items that describes an entity are
known as its attributes.
 7.2-> USE CASE DIAGRAM

Use Case for Admin: Use Case for Student:

 7.2-> ACTIVITY DIAGRAM
● Student Registration

● Student Activity
● Admin Activity
8. Advantages and disadvantages:
Advantages
● Overcomes the dependency of a single person handling all the activities.
● Students could easily register for the event of their choice.
● Multiple students can use the web interface to login and perform the desired task.
● Easy results generation and view rankings.
● Easy to access the system anywhere and anytime.

Disadvantages

● Requires an active internet connection.

● Makes humans idle and lazy as the job of registration is done through app.
9. USER INTERFACE:

● Loading Page: This page is shown at the starting of the application.

● Login Page: The below figure shows the login screen/activity of an application.

● Student Registration Page: This below given figure shows the user interface of the
registration activity of student
● Admin Page :Showing registered student information
● Student Page :
10.APPLICATIONS:

● This application provides an interface for displaying events held in college

.Also students can register through the app for an event.

11.REFERENCES:

● YOUTUBE -> PROFESSOR DK

● www.lucidchart.com
● www.scribd.com
● https://youtu.be/MeYmSdU_bOY

12.CONCLUSION:

● In this project, we created an application that would manage all the events
(technical/non -technical) held in the college premises. This provides an easy
path for students to register in an easy way.