TABLE OF CONTENTS:-

1. Objective
2. Introduction
3. Overview
4. Entities and Table
5. ER Diagram
6. Normalization
7. Conclusion
8. References

ACKNOWLEDGEMENT
The satisfaction that accompanies the successful completion of any task would
be incomplete without the mention of people whose ceaseless cooperation made
it possible, whose constant guidance and encouragement crown all efforts with
success.

I would like to express my gratitude to my subject teacher Mr.Vipin Kumar for

the guidance, inspiration and constructive suggestions that has help in
completion and final execution of my case study.

I would also like to thank the almighty god,my parents and all those who
guided and supported me.

Firoz Alam
OBJECTIVE:-

Main aim in developing

Database:-
To provide an easy way not only to automate all functionalities
of a college, but also to provide full functional reports to top
management of college with the finest of details about any
aspect of college.

College Management System is software has the perspective of

attaining attraction of those colleges which don’t have
onegood performingsoftware for keeping their information
secure and make their management easier. College
Management System provides one attractive environment
where you can manipulate data and information about
students and staff easily. So we can say the Core purpose of
designing “College Management System” is to manage the
task related to the college students/employees and to reduce
time to searching of appropriate candidates in college view.

The software helps you with the daily routine of college

management and reduces the paper work to zero, not only this
the software saves your time, helps in proper utilization of
time and most important, helps you to have complete control
on your college
INTRODUCTION:
-

College management is an integrated web application to

handle various academic and non -academic activities of
college. The system can access by every
student/faculties/employees of the institution through internet
connected computers. This system provides the detail structure
of the college campus and its departments. College
Management System synchronizes the working of all the
departments. It looks on all aspects of a college, its students,
faculties, Departments, marks and other co –curricular
activities.

CMS is the easiest way to manage all functionalities of a

college. It is a value-added service offered by NEURAL, which
facilitates colleges to maintain the functionalityrelated to
college employees and their students. College Management
Software is a simple yet powerful one joint integratedplatform
that connects all the various departments of an institution
likeAdministration, Attendance, Staff details and many more
specialized modules.

OVERVIEW OF CASE STUDY:-

The system COLLEGE DATABASE can be used to manage the
data ofall type of educational institutes. It will support both
stand alone and also networking environment.
Features of proposed system are:-

1. Student Admission

2. Student Fee Management

3. Student Attendance Management

4. Staff Attendance Management

5. Staff payroll Management

6. Library Management

7. User management

8. Hostel management

9. Security Management

10. Human resource

The main modules involved in thissystem are:

1. Login

2. Forms

3. Reports

4. WindowModule wise description

LOGIN:-

Login module is used to check whether the user is an

authorized person to use the systemor not.

For this the user should give the correct user name and
password.

The different types of users are:-

1. Admin

2. Student

3.Faculty

4.Parents

Admin:-It heads the entire college management system and

has the responsibility for setting up and maintaining the system
administrator.It m a y be me mbe r of an information technology
department.

It is responsible for following things:-

4. User access

5. Maintaining system

6. Verify that system works properly or not.

7. Regular update as new version of OS is easily available.

8. Create file system

9. Create a backup and recover for the software

10.Set up security policies for users.

Student:-

They have login facility to access all the information related to

their courses,marks,fee details.With the help of a userid and
password they can ensure all the relevant information.They are
assigned with an id that has all the data stored for a particular
facility.

Employee:-

They are of two types:-

1. Teaching staff

Under teaching staff faulty are there which are of different

departments.

It includes HOD, dean, HOS as well.

2. Non-teaching

Under non-teaching staff-security workers,

cleanliness, department, employees from other
department came.

They also have assigned one ID. This id contains all the
information related to them.

Forms

This module consists of the following sub modules:-

3. Student Registration Form

4. Student Fee Form

5. Student Marks Form

6. Student ID Form

7. Employee Detail Form

8. Employee Salary Form

9. Employee ID Form
8. Course Detail Form

->The Student Registration Form is designed for registering the

new student’s details andcourse details.

->The Student Fee Form is used to enter the student’s fee

details.The Student Marks Form is designed for

->Submitting the semester or e xam marks of thestudents for a

particular course or an individual student

->The Student Id Form is used to create the identity number for

each student for different course.

->The Employee details form is designed for entering the staff

details and other relevant details.

->The Employee Id used to create the identity number for each

student for different course.

->The salary form is used to derive the salary for employees.

->The Course details form is designed for entering the different

course available in the campus and other relevant details.

REPORTS:-

All the above mentioned data are stored in the back end and
can be retrieved as reports with filtering options.

The Following are the reports can be taken from this

system:-

1. Student Report

2. Employee Report

3. Course Detail Report

4. Fee Detail Report

PRIME Features of Our College
Management System Software:
 Simple and Efficient User Interface Design

Asall key elementstaken care of while designing and this makes

it User Friendly.

 The software is secure and reliable

As all major threats areconsidered and all preventive measures

are taken in the software.

 Smart User Management

As it assigns different privileges to thedifferent users. Not only

this, you can manually set theparameters for different users.

 Wide Range of Modules

Keepingin mind all the requirements withseparate login for

students, teachers, parents and administrator.

 The software is Flexible and Customizable

As per your needs.

 Low cost of ownership.

ENTITIES AND TABLES FOR

COLLEGE DATABASE:-
Entity Attributes

As we define different entities, we find that we are digging

deeper and deeper into details.

It is also a good idea to keep track of entity attributes as we

keep researching the business model.

Entity attributes become table columns when the actual

database tables are created. For example,

1. Enrolment

*ID

AcademicYear

Term: Spring/Summer/Fall

SectionID

StudentID

DateEnrolled

Midterm G rade

FinalGrade

2. Student

*ID

First Name

Last

Name

College ID

Email

3. Instructor

*ID
 College ID

First Name

Last

Name

Rank: I=Instructor, P=Professor C=Dept. Chair

Type: F=Full Time, A=Adjunct

Department ID

4. Department

*ID

Name

Chair ID: Department Chair's Instructor

ID Contact Phone

Contact Email

5. Course

*ID

Name

Description

Type: Online/Lecture/Hybrid

Term: Spring/Summer/Fall

6. Section

*ID

Name

Course ID
 Schedule ID

Instructor ID

Room

We spent some time analysing "College" database and

discovered a number of useful relationships between the
tables. In practice, these relationships are established
by creation of

Primary keys in each table, and

Foreignkeys pointing from one table toanother.

The following diagram shows some of these relationships on m y

computer:
 Fig1.1:-TABLES SHOWING RELATIONSHIP

(This example shows primary and foreign keys that exist in my own copy of Access
Database as a result of testing SQL statements from previously posted hand outs.
You can see your own diagram by clicking Database Tools, Relationships. By
default, the tables aren't aligned nicely, but you can visually rearrange them any
way you like.)

 Primary keys are marked by the key icons next to each ID column in every
table.
  Connecting lines show relationships between the tables. The lines have ∞
symbols next to theforeign key columns. The other side is marked by digit
"1", indicating relation to primary key in another table.
 Recall that during the database modelling stage we referred to each table as
entity. Hence the name of the above diagram - Entity Relationship
 The meaning of 1 and ∞ (∞ is like digit "8" on its side, indicating "infinity")
is that primary/foreign key pairs form one-to-many relationships. Each
primary key column can contain only one unique valueidentifying one row in
the table. On the other hand, there can be many non-unique values stored in
the foreign key column of another table. Those are the pointers back to the
table rows containing the primary key.

Connecting columns should have values that match or compare easily,

representing the same or similar data in each of the tables participating in the
join. For example, the Department.ID column matches the
Instructor.DepartmentID column:

The following SELECT query prints instructor names and their departments:

SELECT_Example
SELECT
Instructor.FirstName
,
Instructor.LastName,
Department.Name
FROM
Instructor, Department
WHERE
Instructor.DepartmentID = Department.ID

The result may look like this:

ENTITY RELATIONSHIP
DIAGRAM:-
Entity-relationship (ER) diagram, a graphical representation of
entities and their relationships to each other, typically used in
computing in regard to the organization of data within
databases or information systems. An entity is a piece of data-
an object or concept about which data is stored.

A relationship is how the data is shared between entities.

There are three types of relationships between entities:

1.One to One

2.OnetoMany

3.Many to One
Different books and design tools use different formats, symbols,
and notations to describe database design.

Relations are the bonds between entities. They tell about

certain rules that apply if you want to insert, update or delete
occurrences (rows) from what later becomes a table.
Relations also tell us much about the logic connections
between entities. In the physical design of the database,
relationships become constraints that govern how you are
allowed to manipulate data in different tables. The
relationships are there to enforce referential integrity.. In m y
diagrams, capitalized words (such as Student) identify
entities.

Primitive lines and arrows show relationships between

entities. The relationships also have descriptions.

For example, the diagram

Student ---enrolls-----> Course

Suggeststhat "Student enrolls in a course." Here, the Student

and Course are examples of entities, and "enrolls" is the
name of the relationship between them.

Alternatively,

Course ------has------> Students

Suggeststhe same thing:

"Course has [enrolled] students." Either way, the Course

and the Student are related.

There is a significant issue that makes the above relationships

between students and courses more complex:-

 Any student can be enrolled in multiple courses

  Any course can have multiple students.

Course ------has------> Section <-----enroll------

Students "Course has sections"

"Students enroll in sections"

Note that the arrows suggest the direction in which the

relationships apply. Direction helps to translate the diagram
into plain English sentences.The database table storing course
sections should have a column for the Instructor. Since
course can have multiple sections, different sections of the
same course can be taught by different instructors:

Section ------has------> Instructor

Fig 1.2-ER diagram of student database

NORMALIZATION
Database normalization is the process of organizing the fields
and tables of a relational database to minimize redundancy and
dependency. Normalization usually involves dividing large
tables into smaller (and less redundant) tables and defining
relationships between them. The objective is to isolate data so
that additions, deletions, and modifications of a field can be
made in just one table and then propagated through the rest of
the database using the defined relationships.

Normalization helps eliminate redundancies and

inconsistencies in table data. It is the process of reducing
tables to a set of columns where all the non-key columns
depend on the primary key column. If this is not the case, the
data can become inconsistent during updates.

This section briefly reviews the rules for first, second, third, and
fourth normal form:-

 First: - At each row and column position in the table, there

exists one value, never a set of values.

 Second:-Each column that is not part of the key is

dependent upon the key.

 Third:-Each non-key column is independent of other non-

key columns, and is dependent only upon the key.

 Fourth:-No row contains two or more independent multi-

valued facts about an entity.
At this early database design stage, when we say "Students
enroll in sections",

Section <-----enroll------ Students

Does it mean that the student record must keep a list of every
section where the student is currently enrolled? Maybe. But
how do we keep track of sections/students from previous
semesters?

The answer is: we need another table to make connection

between the academic year, the student, and the section
in which the student is enrolled. Potential name for such
new entity could be Enrolment. The diagram becomes

Section <------has------ Enrolment ------has------> Students

Discovering the need for Enrolment table is a step

towards database normalization.

Normalization procedures are design changes that follow

guidelines based on widely-accepted database organization
standards. Making your tables match these standards is called
normalization.

Typical normalization steps include:

1.Splitting tables into two or more tables with fewer columns
and well-defined primary key.

2. Reducing number of data redundancies within your tables.

CONCLUSION:-
This case study incorporate all activities required to access college database.It
provides all necessary information to the management as well as the student
with the use of this system. The user can simply sit in front of the system and
login using id and password to monitor each and every query related to college
without any physical movement of file.Database can service the student
faculty requests best in time.

The system provides quickly and valuable information.The modules have been
integrated for effective use for future forecasting and for the current need.

A self-driven module in the proposed system will accomplish the automated

tasks such as:-email alerts, sms alerts and notification to the administrator
etc.

SCOPE OF FURTHER
DEVELOPMENT
The system can be designed for further enhancement. This could also be
developed according to the growing needs.