GYMKHANA MANAGEMENT SYSTEM

PROJECT SUPERVISOR- DR. VINOD KUMAR JAINSUBMITTED BY-2014139 Richa Sharma2014168 Shreya Pareek2014197 Vaishali Kushwaha2014114 Nimish Maravi

INDIAN INSTITUTE OF INFORMATION TECHNOLOGY DESIGN AND MANUFACTURING JABALPUR

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.

OBJECTIVE

Objective of the project is to bring about a relationship among the students registered inGymkhana and the clubs associated with it.

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.

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.

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.

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.

Conversion in 1NF

Student_name

First_name Last_name

Now the domain will be atomic.

Conversion in 2NF

PRIMARY KEY (roll_no., club_name) for students entity set and there exists a functional dependencies such as

roll_no. email_idclub_name coordinator

Which implies it is not in 2NF.

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.

Schemas after decompositionStudents (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)

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.)

KEYS

Students Primary Keys- {roll_no} Candidate Keys- {roll_no}, {email_id} Any attribute in union with candidate keys will form

the super keys.

KEYS

SenatorPrimary Key-{roll_no}Candidate Key-{roll_no}Any attribute in union with candidate key will form the

super keys.

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.

KEYS

FestsPrimary Key-{fest_name}Candidate Key-{fest_name}Any attribute in union with candidate key will form the

super keys.

KEYS

TripsPrimary Key-{club_name , year }Discriminator-{year}Candidate Key- {club_name , year }Any attribute in union with candidate key will form the

super keys.

KEYS

EventsPrimary Key-{event_name}Candidate Keys-{event_name}Any attribute in union with candidate key will form the

super keys.

KEYS

StockPrimary Key-{club_name , item}Discriminator-{item}Candidate Key- {club_name , item }Any attribute in union with candidate key will form the

super keys.

KEYS

Member_ofPrimary 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.

KEYS

ConductsPrimary 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.

KEYS

OrganizesPrimary 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.

KEYS

Went_toPrimary 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.

KEYS

Has_aPrimary 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.

NORMALIZATION AND FUNCTIONAL DEPENDENCIES

In all the entity sets and relationship sets in the database, functional dependencies that hold are of the form

XAWhere X is a super key.

So, all the entity sets and relationship sets in the database are in Boyce Codd Normal Form.

Entity SetsStudents (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)

Relationship setsMember_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.)

STUDENT TABLEAttributes DescriptionRoll_no Integer values,PRIMARY KEY,cannot have NULL

valuesFname 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

CLUB TABLE

Attributes DescriptionName Varchar(40),PRIMARY KEY,cannot have NULL

valuesType 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

FEST TABLE

Attributes DescriptioonFest_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

STOCK TABLE

Attributes DescriptionItem Varchar(20),DISCRIMINATOR,cannot have NULL

valuesQuantity Varchar(10),cannot have NULL values

cost Integer,can have NULL values

Type(consumable/non-consumable)

Varchar(20),cannot have NULL values

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

TRIP TABLE

Attributes DescriptionYear integer.,DISCRIMINATOR,cannot have NULL valuesPlace Varchar(20),cannot havr NULL valuesAchievements Varchar(50),can have NULL valuesBudget Integer,cannot havr NULL valuesNo_people Integer,cannot have NULL values

MEMBEROF RELATIONSHIP SET

Attributes DescriptionRoll_no Integer,PRIMARY KEY(composite),cannot have NULL

valuesClub_name Varchar(20),PRIMARY KEY,cannot have NULL values

ORGANISES RELATIONSHIP SET

Attributes DescriptionClub_name Varchar(20),PRIMARY KEY(composite),cannot have NULL

valuesFest_name Varchar(20),PRIMARY KEY(Composite),cannot have NULL

values

WENTTO RELATIONSHIP SET

Attributes DescriptionClub_name Varchar(30),PRIMARY KEY (composite),cannot

have NULL valuesPlace Varchar(20),PRIMARY KEY(composite),cannot have

NULL values

HAS_A RELATIONSHIP SET

Attributes DescriptionClub_name Varchar(30),PRIMARY KEY(composite),cannot have

null valuesitem Varchar(20),PRIMARY KEY(composite),cannot have

null values

CONDUCTS RELATIONSHIP SET

Attributes DescriptionClub_name Varchar(20),PRIMARY KEY(composite),cannot

have NULL valuesEvent_name Varchar(30),PRIMARY KEY(composite),cannot

have NULL values

ER DIAGRAM

E

THANK YOU!