Chembur-Trombay Education Society’s

N.G Acharya & D. K. Marathe

College
Of Arts, Commerce, Science & Professional Courses
N.G Acharya Marg, Chembur (E), Mumbai-400071

PROJECT REPORT ON

College Event Registration System

SUBMITTED BY

Pooja Sanjay Jagdale

UNDER THE GUIDANCE OF

Mrs. Sunita Koli

TO
UNIVERSITY OF MUMBAI
SUBMITTED IN PARTIAL FULFILLMENT OF REQUIREMENT
FOR QUALIFYING
B.Sc(C.S.) (SEM V) EXAMINATION
ACADAMIC YEAR 2019-20

1
 Chembur-Trombay Education Society’s
N.G Acharya& D. K. Marathe College
Of Arts, Commerce, Science & Professional Courses
N.G AcharyaMarg, Chembur (E), Mumbai-400071

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE
This is to certify that the project entitled
“College Event Registration System”
Under the guidance of Mrs.Sunita Koli is successfully completed by Pooja Sanjay
Jagdale . College Roll No.CS11, Seat No:….......………. During the period of 2019-20,
as per the syllabus and fulfilment for the completion of the BSc-CS of University of
Mumbai. This certifies that this is the original work of the Candidate done during
the academic year 2019-20.
DATE:

_______________ __________________ _________________

Project Guide Head of Department External

(Mrs. Sunita Koli) (Mrs. Archana Jadhav) Examiner

2
 Acknowledgement
“An act of gratitude is that which acknowledges the blessings
of well-wishers and supporting guidance of their rich experience,
which enlighten, inspires and motivates to do something valuable.”
I would like to and acknowledge kind support, facilities
specially made available to us by management of our institute
N.G.ACHARYA& D.K. MARATHE COLLEGE. We would not have
completed it without their whole hearted support.
I would like to thank our Honourable Principal -
Dr.Vidyaguari Lele for granting us different facilities to do the
project under the guidance of our faculty. Due to their indeed
support this project was possible.
I sincerely acknowledge with deep sense of gratitude and
indebtedness the support given by our HOD – Ms. Archana Jadhav,
for her kind hearted cooperation, guidelines and various
suggestions.
Last but not the least, I would also like to thank all the Faculty
members of the Computer Science Department for their generous
support and all the Lab Attendants for all their timely help.

Sincere Thank From,

(Pooja Sanjay Jagdale)

3
College Event Registration System

4
 INDEX

Sr. No Topic Page No.

1) Preliminary Investigation
1.1 Introduction
1.2 Description of System
1.3 Limitation of the Previous System
1.4 Proposed System
1.5 System Requirement Specification
1.6 Feasibility Study
1.7 Stake Holders
1.8 Gantt Chart
2) System Analysis
2.1 Fact Finding Techniques
2.2 Event Table
2.3 Entity Relationship Diagram
2.4 Class Diagram
2.5 Usecase Diagram
2.6 Scenario
2.7 Activity Diagram
2.8 Sequence Diagram
3) System Design
3.1 Converting ERD to Tables
3.2 Component Diagram
3.3 Deployment Diagram
3.4 Website Site Map

5
4) System Layout and System Coding
4.1 System Layout
4.2 System Coding
5) Implementation
5.1 System Implementation
5.2 Test Cases
5.3 Future Enhancement
6) Conclusion
7) References

6
PRELIMINARY INVESTIGATION

7
 1.1 INTRODUCTION
College Event Registration System

 The “College Event Registration System” is developed to make the

college event registration more easier and convenient
 The System has Admin View in which Admin will be able to View
the Details of the Users who have registered for the event

8
 1.2 DESCRIPTION OF SYSTEM

 I have done a project on College event registration System.

 The College event registration System allows the administrator to

view the data as required.

 This system provides simple and user-

 friendly Graphical User
 interface for user simplicity.

9
 1.3 LIMITATIONS OF THE PREVIOUS SYSTEM

 Time consumption:

As the records are to be manually maintained it consumes a lot of

time.

 Paper work:

Lot of paper work is involved as the records are maintained in the

files and registers.

 Storage Requirement:

As files & registers are used the storage space requirement is

increased.

 Less Reliable:

Use of papers for storing valuable data information is not at all

reliable.

10
 1.4 PROPOSED SYSTEM

Advantages of Proposed System:

 Time saving since all the detail information is stored in this system it
enables in significant reduction in the number of man-hours taken up
for the storage and the retrieval information as it removes the large
registers from the scene.

 Accuracy and Reliability.

 Users friendly, accurate and robust system.

 Security of data and Integration of all function in to one system.

 Remove redundancy & inconsistency of data.

11
 1.5 SYSTEM REQUIREMENT SPECIFICATION

Hardware Requirements:
 1GHz Processor Intel corei5 or Other Compatible.

 512Mb - 1GB RAM.

Software Requirements:
 Platform: Microsoft Windows or Linux (Ubuntu )

 Application Software :Python-flask, HTML,CSS[Front End]

SQLite3[Back End]
 Browser :Chrome (Version 31 or Above)
Firefox(Version28orAbove) (Recommended)
IE (Version 10.0 or Above

12
 1.6 FEASIBILITY STUDY

It is the step-in requirement investigation whether our system feasible to

organization.

A. Economic Feasibility
B. Technical Feasibility
C. Operational Feasibility

 Economic feasibility:
The proposed system would be economically beneficial for the
organization because of less of manual power & no time could be
consumed & less use of stationary less people the entries.

 Technical feasibility:
My project is internally feasible as works present equipment current
procedure & existing software technology. Hardware & Software
Requirement is already available in present system. Then my project
is technical feasible.

 Operational feasibility:

Our system save time it also provides data security there is no any
loss of data.

13
 1.7 STAKE HOLDERS

Stake holders are the person who success in the system. Stake holders
are main source of information.

Following are the stake holders of the organization:

1. Admin: -
Admin is the main person of the system. Admin knows all
information about the system.

2. Student:-

The Student is important entity that will register in college events.

14
 1.8 GANTT CHART

A Gantt chart is a graphical representation of the duration of tasks

against the progression of time. A Gantt chart is a popular type of bar
chart that aims to show the timing of tasks or activities as they occur
over a period of time. Although the Gantt chart did not initially indicate
the relationship between activities this become has become more
common in current usage as both timing and interdependences can be
identified.
In project management a Gantt chart can show when the project terminal
elements start and finish, summary elements (shown) or terminal
element dependences (not shown). A terminal element is defined as the
smallest task tracked as part of the project effort.

Since the initial introduction of Gantt charts, they have become an

industry standard as a key project management tool for representing the
phases, tasks and activities that are scheduled as a part of a Project Work
Breakdown Structure or timeline of activities.

15
16
SYSTEM ANALYSIS

17
 2.1 FACT FINDING TECHNIQUES

 Time Saving: Since all the detail information is available on site.

Providing time saving for customers to find information of products
instead and can do shopping from the comfort of home without
having to run around.

 Accuracy and Reliability: Problems related with human error, data

loss and inconsistency can be eliminated, thus making the system
more accurate and reliable.

 Information Maintenance: Information Maintenance can now be an

easy task as it removes the large registers from the scene.

 Availability of Reports, Query and Chart: Reports, Query and Chart

can be generated as per the Management requirements.

 Easy To Use: The system is a user friendly and easy to use System
with Graphical User Interface features.

18
 2.2 EVENT TABLE

Event Trigger Source Activity Response Destination

Admin Sign in Admin Admin Sign Sign in Admin

sign in request in acknowled
gement
View View Admin Viewing details Admin
details details details
Request
View View Membe Viewing List of Member
previous previous r previous previous
Booking Booking Bookings. Bookings.
s request
Student Confirm Student Confirming Student
confirms request Registration
registrati
on
Admin sign-out Admin Admin Sign Sign-out Admin
sign-out request out acknowled
gement
View all View Admin Viewing List of Admin
registrati registrati registration registratio
on on details of ndetails of
details details all events all event.

19
2.3 ENTITY RELATIONSHIP DIAGRAM

20
 2.4 CLASS DIAGRAM

Class diagrams express, in a general way, the static structure of a

system, in terms of classes and relationships between those classes. Just
as a class describes a set of objects, an association describes a set of
links; objects are class instances and links are association instances.

21
 2.5 USECASE DIAGRAM

Use case diagrams represent use cases, actors and relationships between
use cases and actors.

22
 2.6 SCENARIO

 Use case name – Add new student details

 Scenario – Add new student
 Trigger – New student
 Flow of activity –
 System invokes add new student
 System asks for details
 Admin Enters the details
 System verifies &add a new student to the system
 student gets validated student

 Use case name – show Details

 Scenario – show Student details to admin
 Trigger – show details
 Flow of activity –
 System invokes details
 admin selects details from list.
 System shows the data

23
 2.7 ACTIVITY DIAGRAM

An activity diagram is a variant of state chart diagrams organized

according to actions, and mainly targeted towards representing the
internal behavior of a method or a use case.

24
 2.8 SEQUENCE DIAGRAM

Sequence diagrams display interactions between objects from a temporal

standpoint. Unlike collaboration diagrams, the context of the objects is
not represented explicitly. The representation focuses on expressing
interactions.

25
SYSTEM DESIGN

26
 3.1 CONVERTING ERD TO TABLES

Table name:-phoneix
Name Type Key
Firstname Text -
Lastname Text -
Contactno Integer -
Email Text -
College Text -
Event TEXT -
Mainevent -

Table name: - pixel

Name Type Key
Firstname INTEGER -
Lastname TEXT -
Contactno Integer -
Email TEXT -
College TEXT -
Event Text -
Mainevent Text -

27
Table name:-physics
Name Type Key
Firstname Text -
Lastname TEXT -
Conatactno Integer -
Email TEXT -
Contactno Integer -
Email TEXT -
College TEXT -
Project TEXT -
Mainevent TEXT -

Table name:-techage
Name Type Key
Firstname Text -
Lastname Text -
Contactno Integer -
Email Text -
College Text -
Event Text -
Mainevent Text -

28
3.2 COMPONENT DIAGRAM

29
3.3 DEPLOYMENT DIAGRAM

30
3.4 WEBSITE SITE MAP

31
SYSTEM LAYOUT
AND
SYSTEM CODING

32
4.1 SYSTEM LAYOUT

Homepage:-

Event page:-

33
Event info page:-

Registration page:-

34
 Admin Login:-

Admin Home Page:-

35
Display Registered event list:-

36
 4.2 SYSTEM CODING

Main.py
from flask import Flask,render_template,request,redirect,url_for,session
import sqlite3 as sql
app=Flask(__name__)
@app.route('/')
def home1():
return render_template('home1.html')
@app.route('/home')
def home():
return render_template('home.html')
@app.route('/event')
def event():
return render_template('event.html')
@app.route('/admin/event')
def adminevent():
return render_template('adminevent.html')
@app.route('/phoniex')
def phoneix():
return render_template('phoneix1.html')
@app.route('/pixel')
def pixel():
return render_template('pixel1.html')
@app.route('/physicsfair')

37
def physicsfair():
return render_template('physicsfair1.html')
@app.route('/techage')
def techage():
return render_template('techage1.html')
@app.route('/list')
def list():
return render_template('list.html')
@app.route('/phoneixlist')
def phoneixlist():
return render_template('phoneixlist.html')
@app.route('/physicslist')
def physicslist():
return render_template('physicslist.html')
@app.route('/pixellist')
def pixellist():
return render_template('pixellist.html')
@app.route('/techagelist')
def techagelist():
return render_template('techagelist.html')
@app.route('/phoneixregis')
def phoneixregis():
return render_template('phoneixregis.html')
@app.route('/pixelregis',methods = ['POST', 'GET'])
def pixelregis():

38
 return render_template('pixelregis.html')
@app.route('/physicsfairregis',methods = ['POST', 'GET'])
def physicsfairregis():
return render_template('physicsfairregis.html')
@app.route('/techageregis',methods = ['POST', 'GET'])
def techageregis():
return render_template('teckageregis.html')
@app.route('/adminhome',methods = ['POST', 'GET'])
def adminhome():
return render_template('adminhome.html')
@app.route('/adminlogin',methods=['POST','GET'])
def adminlogin():
error = None
if request.method =='POST':
if request.form['username'] != 'admin' or request.form['password'] != 'admin':
error = 'Invalid Credentials. Please try again.'
else:
return redirect(url_for('adminhome'))
return render_template("adminlogin.html",error=error)
@app.route('/addrecphoneix',methods=['POST', 'GET'])
def addrecphoneix():
if request.method=='POST':
try:
firstname=request.form['firstname']
lastname=request.form['lastname']

39
 contactno=request.form['contactno']
email=request.form['email']
college=request.form['collegename']
event=request.form['phoneix']
mainevent='phoneix'
with sql.connect("database.db")as con:
cur=con.cursor()
cur.execute("INSERT INTO
phoneix(firstname,lastname,contactno,email,college,event,mainevent)VALUES(?,
?,?,?,?,?,?)",(firstname,lastname,contactno,email,college,event,mainevent))
con.commit()
msg1="record successfully added"
# session['firstname']=firstname
#session['lastname']=lastname
#session['contactno']=contactno
#session['email']=email
#msg1= "In the basket are %s and %s" %
(session['firstname'],session['lastname'])
except:
con.rollback()
msg1="error in insert operation"
finally:
return render_template('result.html',msg1=msg1)
con.close()
@app.route('/addrecpixel',methods=['POST', 'GET'])
def addrecpixel():

40
 if request.method=='POST':
try:
firstname=request.form['firstname']
lastname=request.form['lastname']
contactno=request.form['contactno']
email=request.form['email']
college=request.form['collegename']
event=request.form['pixel']
mainevent='pixel'
with sql.connect("database.db")as con:
cur=con.cursor()
cur.execute("INSERT INTO
pixel(firstname,lastname,contactno,email,college,event,mainevent)VALUES(?,?,?,
?,?,?,?)",(firstname,lastname,contactno,email,college,event,mainevent))
con.commit()
msg1="record successfully added"
except:
con.rollback()
msg1="error in insert operation"
finally:
return render_template('result.html',msg1=msg1)
con.close()
@app.route('/addrecphysicsfair',methods=['POST', 'GET'])
def addrecphysicsfair():
if request.method=='POST':
try:

41
 firstname=request.form['firstname']
lastname=request.form['lastname']
contactno=request.form['contactno']
email=request.form['email']
college=request.form['collegename']
project=request.form['project']
mainevent='physicsfair'
with sql.connect("database.db")as con:
cur=con.cursor()
#(name Text,contactno TEXT,email TEXT,college TEXT,project
TEXT,mainevent TEXT)
cur.execute("INSERT INTO
physics(firstname,lastname,contactno,email,college,project,mainevent)VALUES(?,
?,?,?,?,?,?)",(firstname,lastname,contactno,email,college,project,mainevent))
con.commit()
msg1="record successfully added"
except:
con.rollback()
msg1="error in insert operation"
finally:
return render_template('result.html',msg1=msg1)
con.close()
@app.route('/addrectechage',methods=['POST', 'GET'])
def addrectechage():
if request.method=='POST':
try:

42
 firstname=request.form['firstname']
lastname=request.form['lastname']
contactno=request.form['contactno']
email=request.form['email']
college=request.form['collegename']
event=request.form['techage']
mainevent='techage'
with sql.connect("database.db")as con:
cur=con.cursor()
#(name Text,contactno TEXT,email TEXT,college TEXT,event
TEXT,mainevent TEXT)
cur.execute("INSERT INTO
techage(firstname,lastname,contactno,email,college,event,mainevent)VALUES(?,?
,?,?,?,?,?)",(firstname,lastname,contactno,email,college,event,mainevent))
con.commit()
msg1="record successfully added"
except:
con.rollback()
msg1="error in insert operation"
finally:
return render_template('result.html',msg1=msg1)
con.close()
@app.route("/desrecphoneix")
def desrecphoneix():
con=sql.connect("database.db")
con.row_factory=sql.Row

43
 cur=con.cursor()
cur.execute("select * from phoneix")
rows=cur.fetchall()
print (rows)
return render_template("phoneixlist.html",rows=rows)
@app.route("/desrecpixel")
def desrecpixel():
con=sql.connect("database.db")
con.row_factory=sql.Row
cur=con.cursor()
cur.execute("select * from pixel")
rows=cur.fetchall()
print (rows)
return render_template("pixellist.html",rows=rows)
@app.route("/desrecphysicsfair")
def desrecphysicsfair():
con=sql.connect("database.db")
con.row_factory=sql.Row
cur=con.cursor()
cur.execute("select * from physics")
rows=cur.fetchall()
print (rows)
return render_template("physicslist.html",rows=rows)
@app.route("/desrectechage")
def desrectechage():

44
 con=sql.connect("database.db")
con.row_factory=sql.Row
cur=con.cursor()
cur.execute("select * from techage")
rows=cur.fetchall()
print (rows)
return render_template("techagelist.html",rows=rows)
#patil998707@gmail.com
if __name__ == '__main__':
app.run(debug = True)

45
IMPLEMENTATION

46
 5.1 SYSTEM IMPLEMENTATION

Following are the steps to be followed for implementing the system:

 Install the Python-flask software in your machine
 Create virtual environment using command line
 Run the python code
 Copy the URL to the browser

47
 5.2 TEST CASES

REQ TESTCASE FIELD MODU POST TEST EXPEC- ACT

-ID -ID NAME LE CONDITI STEP TED UAL
NAME ON RESULT RES
ULT

1 User01 Firstname Registera Data First Error: pass

tion should be name Field is
success field empty
empty

2 User02 lastname Registrat Data Last Error: pass

ion should be name Field is
success field empty
empty
3 User03 Contactno Registrat Data 1.field 1.field pass
ion should be empty. empty.
sucess 2.contact 2.there
no not should be
less than 10
10. 3.no
3.Is not should
starting start
from from7,8,9
7,8,9.. .

4 User04 Email Registrat Data 1.Field Error: pass

ion should be empty It should
successful 2.email id be in
add. should in email id
Example format
@exam.c

48
 om form
5 User05 College registrati Data College Error: Pass
name on should be name Field
successful empty empty
add
Admin page
REQ- TESTCASE FIELD MODU PRE TEST EXPEC ACT
ID -ID NAME LE CONDITI STEP TED UAL
NAME ON RESULT RES
ULT
1 admin01 Username Login Login page 1.enter Input Login
should get username should be succe
open 2. enter accepted ssfull
password & next y
3.click page
login In should
get
opened

2 admin02 Password Login Login page 1.enter Input Login

should get username should failed
open 2. enter not be
wrong accepted
password
3.click
login In

49
 5.3 FUTURE ENHANCEMENT

1. The system can be improved to make it more generalized.

2. The system can be making to work on a distributed system.

3. This system can be provided with an interactive help menu for the
new users

50
 CONCLUSION
“College Event Registration System” was made such that the problem
fixed by the consultancy with its meeting the requirements would be
over. The burden of the manually done activities was made easy with the
development of site. The admin can view data and performance analysis
can be done.

This main aim of the project was to provide required amount of

reporting tools with a back end larger amount of data.

The developed system:

 Maintains a record of student.
 Export data about Records inserted in database.
 Admin can manage records.
.

51
 BIBLOGRAPHY

Websites Referred:

 www.google.com
 www.w3schools.com
 www.youtube.com
 stackoverflow.com
 flask tutorial.com

Book Referred:

 Flask Web Development by Miguel Grinberg

 Flask Tutorial

 Python Tutorial

52