The report submitted for DBMS project on Gymkhana Management System which is the management system College Clubs including Sports, Cultural and Technical Clubs. The report contains the description of project and its ER design and Relational database design

1. PROJECT SUPERVISOR- DR. VINOD KUMAR JAIN
SUBMITTED BY-
2014139 Richa Sharma
2014168 Shreya Pareek
2014197 Vaishali Kushwaha
2014114 Nimish Maravi
INDIAN INSTITUTE OF INFORMATION
TECHNOLOGY DESIGN AND MANUFACTURING
JABALPUR

2. ACKNOWLEDGEMENT
We are highly thankful to our project supervisor Dr. Vinod
Kumar Jain for guiding us so well on every step without
which, such a project would not have been possible.
We would also like to thank our college’s gymkhana for
motivating us.
Finally, we would thank our friends for bearing with us
late nights.

3. OBJECTIVE
Objective of the project is to bring about a
relationship among the students registered in
Gymkhana and the clubs associated with it.

4. Main Functions
 The idea behind the project is to develop a management system
of gymkhana website which stores the information about all the
gymkhana members and the clubs associated along with the
information about fests organized, events conducted, gymkhana
stock and the structure of student body all under same roof.

5. Main Functions
 The objective is also to ensure that students of all the
clubs are well informed in advance about the activities of
all the clubs including the clubs which they are not a part
of, which in turn will help all the clubs to avoid clashes.
 Easy accessibility.
 A STEP TOWARDS DIGITAL INDIA.

6. Assumptions
 Students’ names need not be unique.
 Each student has a unique email id.
 Each student has a single and unique phone number.
 Each club has at least one member.
 Each club can possess single Coordinator, Co-
coordinator and Council member.
 A student can opt for any number of clubs including
none.
 Stock belongs to gymkhana.
 Events conducted by clubs are unique.
 A person can hold only one position in clubs.
 A club can to go for only one trip per year.

7. Normalization
 Students(student_name,
roll_no,
email_id,
password,
course,
branch,
gender,
DOB,
batch,
post,
hall_of_residence,
phone_no.,
club_name,
type,
co-ordinator,
co-coordinator,
total_members,
budget,
council member)
 PRIMARY KEY(roll_no, club_name)
 Since student_name does not have atomic domain
so it is not in First Normal Form.

8. Conversion in 1NF
Student_name
First_name Last_name
Now the domain will be atomic.

9. Conversion in 2NF
PRIMARY KEY (roll_no., club_name) for students entity set and
there exists a functional dependencies such as
roll_no.  email_id
club_name  coordinator
Which implies it is not in 2NF.

10. DECOMPOSITION
 Students(student_name, roll_no, email_id, password,
course, branch, gender, DOB, batch, post,
hall_of_residence, phone_no.)
 Clubs(club_name , type, co-ordinator , co-coordinator,
total_members, budget, council member)
Then the entity sets are in second normal form.

11. Schemas after decomposition
Students (roll_no., first_name , last_name , email_id, password, course, branch, gender, DOB, post
, address , phone_no , batch )
Clubs(club_name, type, coordinator, co-coordinator, council_member, total members, budget)
Fests(fest_name, consellors, fest_budget, type, level, duration, year)
Senator( field_associated , post)
Trips(place, year, achievements, budget, number)
Events( event_name , coordinator, date, venue, participants)
Stock(item, quantity, price, type)

12. Schemas continued…
Member_of(roll_no., club_name)
Part of (club_name , fest_name)
Wentto(club_name , place)*
Has_a(club_name , item)*
Conducts(club_name , event_name)
(* Represents weak-strong relationship sets.)

13. KEYS
Students
 Primary Keys- {roll_no}
 Candidate Keys- {roll_no}, {email_id}
 Any attribute in union with candidate keys will form
the super keys.

14. KEYS
Senator
 Primary Key-{roll_no}
 Candidate Key-{roll_no}
 Any attribute in union with candidate key will form the
super keys.

15. KEYS
Clubs
 Primary Key- {club_name}
 Candidate Keys- {club_name}, {coordinator}, {co-
coordinator}, {council _member}
 Any attribute in union with candidate keys will form
the super keys.

16. KEYS
Fests
 Primary Key-{fest_name}
 Candidate Key-{fest_name}
 Any attribute in union with candidate key will form the
super keys.

17. KEYS
Trips
 Primary Key-{club_name , year }
 Discriminator-{year}
 Candidate Key- {club_name , year }
 Any attribute in union with candidate key will form the
super keys.

18. KEYS
Events
 Primary Key-{event_name}
 Candidate Keys-{event_name}
 Any attribute in union with candidate key will form the
super keys.

19. KEYS
Stock
 Primary Key-{club_name , item}
 Discriminator-{item}
 Candidate Key- {club_name , item }
 Any attribute in union with candidate key will form the
super keys.

20. KEYS
Member_of
 Primary Key-{ roll_no, club_name}
 Candidate Keys-{ roll_no , club_name}
 Foreign Keys-{roll_no }, { club_name }
 Any attribute in union with candidate key will form the
super keys.

21. KEYS
Conducts
 Primary Key-{club_name , event_name }
 Candidate Keys- {club_name , event_name }
 Foreign Keys- {club_name }, { event_name }
 Any attribute in union with candidate key will form the
super keys.

22. KEYS
Organizes
 Primary Keys-{club_name , fest_name}
 Candidate Keys-{club_name , fest_name }
 Foreign Keys-{club_name }, {fest_name }
 Any attribute in union with candidate key will form the
super keys.

23. KEYS
Went_to
 Primary Keys-{club_name , year}
 Candidate Keys-{club_name , year}
 Foreign Keys-{club_name }
 Any attribute in union with candidate key will form the
super keys.

24. KEYS
Has_a
 Primary Keys-{club_name , item}
 Candidate Keys-{club_name , item }
 Foreign Keys-{club_name }
 Any attribute in union with candidate key will form the
super keys.

25. NORMALIZATION AND FUNCTIONAL
DEPENDENCIES
In all the entity sets and relationship sets in the
database, functional dependencies that hold are of
the form
XA
Where X is a super key.
So, all the entity sets and relationship sets in the
database are in Boyce Codd Normal Form.

26. Entity Sets
Students (roll_no., first_name , last_name , email_id, password, course, branch, gender, DOB, post
, address , phone_no , batch )
Clubs(club_name, type, coordinator, co-coordinator, council_member, total members, budget)
Fests(fest_name, consellors, fest_budget, type, level, duration, year)
Senator( field_associated , post)
Trips(place, year, achievements, budget, number)
Events( event_name , coordinator, date, venue, participants)
Stock(item, quantity, price, type)

27. Relationship sets
Member_of(roll_no., club_name)
Part of (club_name , fest_name)
Wentto(club_name , place)*
Has_a(club_name , item)*
Conducts(club_name , event_name)
(* Represents weak-strong relationship sets.)

28. STUDENT TABLE
Attributes Description
Roll_no Integer values,PRIMARY KEY,cannot have NULL
values
Fname Varchar(30),cannot have NULL values
Lname Varchar(30),cannot have NULL values
Email_id Carchar(40),CANDIDATE KEY,cannot have NULL
values
Password Password,cannot have NULL values
Hall of residence Varchar(30),can have Null value
Post Varchar(20),can have NULL value
DOB Date,cannot have NULL values
Gender Char(1),cannot have NULL values
Branch Char(10),cannot have NULL values

29. CLUB TABLE
Attributes Description
Name Varchar(40),PRIMARY KEY,cannot have NULL
values
Type Varchar(20),cannot have NULL Values
Coordinator INTEGER,CANDIDATE KEY,cannot have NULL
values
Co-coordinator INTEGER,CANDIDATE KEY,cannot have NULL
values
Council member INTEGER,CANDIDATE KEY,cannot have NULL
values

30. FEST TABLE
Attributes Descriptioon
Fest_name Varchar(40),PRIMARY KEY,cannot have NULL values.
Budget Integer,cannot have NULL values
Type Varchar(30),cannot have NULL values
Level Varchar(30),cannot have NULL values
Duration Varchar(20),cannot have NULL values

31. STOCK TABLE
Attributes Description
Item Varchar(20),DISCRIMINATOR,cannot have NULL
values
Quantity Varchar(10),cannot have NULL values
cost Integer,can have NULL values
Type(consumable/non-
consumable)
Varchar(20),cannot have NULL values

32. EVENT TABLE
Attributes Description
Event_name Varchar(20),PRIMARY KEY,cannot have NULL values
Coordinator Integer,cannot have NULL values
Month Varchar(20),cannot havreNULL values
Venue Varchar(10),cannot have NULL values
No_participants Integer,can have NULL values

33. TRIP TABLE
Attributes Description
Year integer.,DISCRIMINATOR,cannot have NULL values
Place Varchar(20),cannot havr NULL values
Achievements Varchar(50),can have NULL values
Budget Integer,cannot havr NULL values
No_people Integer,cannot have NULL values

34. MEMBEROF RELATIONSHIP SET
Attributes Description
Roll_no Integer,PRIMARY KEY(composite),cannot have
NULL values
Club_name Varchar(20),PRIMARY KEY,cannot have NULL values

35. ORGANISES RELATIONSHIP SET
Attributes Description
Club_name Varchar(20),PRIMARY KEY(composite),cannot have NULL
values
Fest_name Varchar(20),PRIMARY KEY(Composite),cannot have NULL
values

36. WENTTO RELATIONSHIP SET
Attributes Description
Club_name Varchar(30),PRIMARY KEY (composite),cannot
have NULL values
Place Varchar(20),PRIMARY KEY(composite),cannot
have NULL values

37. HAS_A RELATIONSHIP SET
Attributes Description
Club_name Varchar(30),PRIMARY KEY(composite),cannot have
null values
item Varchar(20),PRIMARY KEY(composite),cannot have
null values

38. CONDUCTS RELATIONSHIP SET
Attributes Description
Club_name Varchar(20),PRIMARY KEY(composite),cannot
have NULL values
Event_name Varchar(30),PRIMARY KEY(composite),cannot
have NULL values

39. ER DIAGRAM

40. E

42. THANK YOU!