CONTENTS

SL.NO CHAPTER NAME PAGE NO

1 Introduction 01-03

1.1 Problem Statements 02

1.2 Objectives of Project 03
1.3 Scope 03
1.4 Advantages 03

2 Literature Survey 04-05

2.1 Existing System 04

2.2 Proposed System 05

3 System Requirements Specification 06

3.1 Hardware Requirements 06

3.2 Software Requirements 06
3.3 Development Platform 06

4 System Design 07-13

4.1 System Architecture 07

4.2 ER-Diagram 08
4.3 ER-Relational Mapping 10
Algorithm
4.4 Schema Diagram 12
13
4.5 Normalization

5 Implementation 14

5.1 Modules 14

6 Snapshots 15-19

Conclusion 20

Bibliography 21
 Student Information Management System

CHAPTER 1

INTRODUCTION
The college is responsible for handling student information and gathering them during
enrolment. This information includes each student’s background information, courses taken
student status at lectures grades, performance record, and other information needed by the
college.
Today, the success of college depends on its ability to acquire accurate and timely
data about its operations, to manage this data effectively, and to use it to analyze and guide its
activities.
Several forms and reports are used in day to day processing of results. A database can
integrate these several components hence resulting in improved and more efficient
operations. Student Database System deals with all kind of student details, academic related
reports, college details, course details, curriculum, batch details and other resource related
details too. It tracks all the details of a student from the day one to the end of his course
which can be used for all reporting purpose, tracking of attendance, progress in the course,
completed semesters years, coming semester year curriculum details, exam details, project or
any other assignment details, final exam result; and all these will be available for future
references too.

1.1 PROBLEM STATEMENT

Information plays a vital role in the development and growth of every organization.
Currently, the various departments manage student information independently in their own
ways. There are no common, standardized process and program for capturing, processing and
storing student’s information.
The various departments have systems in place to store and process student data but
the systems are not able to talk to each other (Interoperability). This makes it difficult for the
college to collate information of students across departments. For instance, if the college
wants information about students with respect to their academic performance urgently, he
must go to all the departments and collect the required data. On occasions where the
department is not able to produce the needed information immediately, the business or
activity at that particular time would come to a standstill.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

1.2 OBJECTIVES OF PROJECT

The main objective is to develop a robust Student Database Management System for
the college. Specific Objectives to identify the problems involved in the implementation of
the current student information system,
1. To develop a database system that allows the Institution to list and update students’
information.
2. To develop a system that enables self-service for students to perform the basic
administrative functions.
3. To develop the prototype of an integrated Student Database System.
4. Support the retention of students and encourage a strong and positive relationship
with university and institution.
5. Ensure data integrity, privacy and security in an open access environment.
1.3 SCOPE
The proposed system is intended to manage specific information of students such as
personal details, course details, status and exam details etc. It is not Student Information
Management System which has a broader application. It is only a part of Student Information
Management System. This project when completed will provide comprehensive Student
Database System for the Institutions. The system should be able to capture, validate, sort,
classify, calculate, summarize, store, retrieve, reproduce and communicate operational data.
Student Database System will store semester details, course details, department details and all
the details of students including their background information, educational qualifications and
personal details etc.
Without a student information system, managing and maintaining the details of the
student is a tedious job for any organization.
1.4 ADVANTAGES
1. Hassle free recruitment/enrolment processes.
2. Managing student information.
3 .Student portal.
4. Academics advising.
5. To foster efficiency.
6. Redundant human errors.
7. No more data breaches.
8. Effortless communication.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CHAPTER 2

LITERATURE SURVEY
Most of the Institutions today use some type of system software to maintain the
Student information (Student information system) to help manage the ongoing function of a
typical institution course, enrolment, grades, schedule etc. The traditional student information
system no longer can be limited to just tracking student information, but must provide a
means of using data to help drive better, evidence-based decisions on the part institution and
family regarding the educational goals of student (Finkel 2012).

“Without the availability of high-quality data and perhaps technical assistance , data
may become misinformation or lead to invalid inferences ”(Marsh ,pane and Hamilton,2009).

Additionally minimizing points of failure and increasing the timeliness of information

will aid in servicing the Institution’s consumer of the system. As the team looks to the value
of the institution’s data and future trends in utilizing it, the proposed project will seek out a
SIMS that meets the current requirements as well as potential future specification considered
for Atonement Lutheran Institution.

2.1 EXISTING SYSTEM

An Existing System refers to the system that is being followed till now. The creation
and maintenance of records relating to the students of an institution are essential to:
1) Managing the relationship between the institution and the student.
2) Providing support and other services and facilities to the student.
3) Controlling the student’s academic progress and measuring their achievement, both at
the institution and subsequently.
Educational institutions and agencies are required to confirm to fair information
practices. This means that persons who are subjects of data systems (i.e. students at an
institution) must:
1) Be informed of the existence of such systems have identified for them what data
about them are on record.
2) Be given assurances that such data are used only for intended purposes.
3) Be given the opportunity to request an amendment or correction to their record.
4) Be certain that those responsible for data systems take reasonable precautions to
prevent misuse of the data.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

2.2 PROPOSED SYSTEM

Student information systems must meet the following objectives:

1. Enable self-service for students to perform basic administrative functions and tasks in a
“one-stop” service and access environment.

2. Integrate data sources and process them through a single function that supports one-time
entry of student data.

3. Support the retention and recruitment of students and encourage a strong and positive
relationship with the university, alumni, donors, and other constituencies.

4. Integrate and support new learning and teaching opportunities and technologies for
students and faculty.

5. Support open interfaces and integration with other campus applications and database
systems.

6. Ensure data integrity, privacy, and security in an open-access environment.

7. Support faculty and staff who perform both basic and complex functions through
simplified work processes and procedures.

8. Enable ongoing, flexible reconfiguration of the application to extend its life cycle and to
meet the changing business processes of the university.

9. Include implementation and support services that meet university needs.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CHAPTER 3

SYSTEM REQUIREMENT SPECIFICATION

3.1 HARDWARE SPECIFICATION
 Processor - Pentium 4
 RAM - 1GB
 Hard Disk - 40GB
 Mouse - Standard Mouse
 Key board - Logitech Keyboard
 Processor Speed - 2.4GHZ

3.2 SOFTWARE SPECIFICATION

 Front end – PHP
 Back end –MYSQL
 Operating system- Windows 7/Window 8
 Other Tools- HTML,BOOTSTRAP

3.3 DEVELOPMENT PLATFORM

 Notepad ++
 Phpmyadmin , Xampp
 Google Chrome

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CHAPTER 4

SYSTEM DESIGN
4.1 SYSTEM ARCHITECTURE
Students of college have to complete their pre-advisional advising each semester to
take courses for upcoming semester. The decision support system assist students in choosing
the best set of course in a semester. To be able to do that the system must have access to
student data as course, section, enrolment Level the whole software acts as a intermediary
model that links the pre-advising and admin’s office and students as well portraits the idea
how the advising is bridged with intermediary software to overcome the challenge.

Login

Admin adds
Student

Update Student
Admin Information

Course
Lists Student
Section

View Student Enrollment

Information

Level
Student Management Mode

Fig 4.1: System Architecture

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

4.2 ER- DIAGRAM

An entity-relationship diagram (ERD) is a graphical representation of an information
system that shows the relationship between people, objects, places, concepts or events within
that system. In software engineering an ER model is commonly formed to represent things
that a business needs to remember in order to perform business processes. Consequently, the
ER model becomes an abstract data model that defines a data or information structure that can
be implemented in a database, typically a relational database.
 Entities and their attributes.
 Relationships among entities.

Symbols used in ER Diagram:

 Entity: Entity is a “thing” in the real world with an independent existence. An entity
may be an object with a physical existence such as Admin, Car and Client. Entity
Symbol is as follows:

 Attribute: Attribute is a particular property that describes the entity. Attribute symbol
is as follows:

 Relationship: Whenever an attribute of one entity refers to another entity type some
relationship exist. Relationship symbol is as follows:

 Key attributes: An entity type usually has an attribute whose values are distinct for
each individual entity in the collection .Such an attribute is called key attribute. Key
attribute symbol is as follows:

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

ER-Diagram

Status_id
Status_name

Status Name Email

Admin_ id
1
Position Password
Type Admin

N N Course_id
Stu_id Enters
1 Name Adds

N N Name
Email
Student Attends Course
Course_id 1 1
Level_id description

belongs
belongs
M 1

1
Section_id Section
Enrolls
Level

Course_id
N
Name
Level_id
Year_Lev
-id Enrollment
el
Course_id
Date_of_enrollment
Student
Enrollment_id

Fig 4.2: ER Diagram

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

4.3 ER RELATIONAL MAPPING ALGORITHM

We now describe the steps of an algorithm for ER-to-relational mapping.

STEP 1:

For each regular (strong) entity type E in the ER schema, create a relation R that
includes all the simple attributes of E. Include only the simple component attributes of a
composite attribute. Choose one of the key attributes of E as a primary key for R. If the
chosen key of E is composite, the set of simple attributes that form it will together form the
primary key of R.

Ex: user_data, time_table, health status.

STEP 2:

For each weak entity type W in the ER schema with owner entity type E, create a
relation R, and include all simple attributes (or simple components of composite attributes) of
W as attributes of R. In addition, include as foreign key attributes of R the primary key
attributes(s) of the relation(s) that correspond to the owner entity type(s).

STEP 3:

For each binary 1:1 relationship type R in the ER schema, identify the relations S and
T that correspond to the entity types participating in R. Choose one of the relation and
include as foreign key in S the primary key of T. It is better to choose an entity type with total
participation in R in the role of S. Include all the simple attributes of the 1:1 relationship type
R as attributes of S.

Ex:

1 1
has
user_data Time_table

STEP 4:

For each regular binary 1:N relationship type R, identify the relations S that represents
the participating entity type at the N-side of the relationship type. Include as foreign key in S
the primary key of the relation T that represents the other entity type participating in R.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

Ex:

1 Member N
User_data mem_types
of

STEP 5:

For each binary M:N relationship type R, create a new relation S to represent R.
Include as foreign key attributes in S the primary keys of the relations that represent the
participating entity types; their combination will form the primary key of S. Also include any
simple attribute of M:N relationship types has attributes of S. Notice that we cannot represent
an M:N relationship type by a single foreign key attribute in one of the participating relations
as we did for 1:1 or 1:N relationship types because of the M:N cardinality ratio.

Ex:
contain N
user_data M Health status
s

STEP 6:

For each multivalued attribute A, create a new relation R this relation R will include
an attribute corresponding to A, plus the primary key attribute K as foreign key in R of the
relation that represent the entity type or relationship type that has A as an attribute.

4.4 SCHEMA DIAGRAM

The database schema of a database is its structure described in a formal language

supported by the database management system (DBMS) .The term “schema” refers to the
organization of the data as a blueprint of how the database is constructed(divided into
database tables in the case of relational databases).the formal definition of a database schema
is a set of formulas called integrity constraints imposed on a database.

STUDENT Table: Examine the STUDENT schema diagram and locate the STUDENT table.
This table contains data about individual students, such as their name, stu_id , email, course,
level .

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

COURSE Table: The COURSE table lists all the available courses tat a student may take.
The primary key of table is the course_id column.

ENROLLMENT Table: The ENROLLMENT Table is an intersection table between the

STUDENT and the COURSE table. It lists the student enrolled in various courses. The
primary key of the table is composite primary key consisting of the stu_id and course_id .

SECTION Table: The SECTION table includes all the individual section a course may have.
An individual course may have zero, one or many sections.

STATUS Table: The STATUS table lists the Status_id and status_name. The primary key
of the table is status_id.

STUDENT

Stu_id Name Email Course_id Level_id

ADMIN
Id Name Email password Position
COURSE
Course_id Name description

ENROLLMENT
Date_of_enrollment enrollment_id Stu_id Course_id

SECTION
Section_id Name Course_id

STATUS
Status_id Status_name

LEVEL
Year_Level Level_id

Fig 4.4: Schema Diagram

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

4.5 NORMALIZATION
Here are the most commonly used normal forms:
 First Normal form (1NF)
 Second Normal form (2NF)
 Third Normal form (3NF)
First Normal form (1NF):

It was defined to disallow multivalued, composite attributes and their

combinations. It states that the domain of an attribute in a tuple must include atomic
values. As we are not having atomic values so, this normal form is not applicable.

Second Normal form (2NF):

It is based on full functional dependency. A functional dependency X-> Y is

full functional dependent if every attribute ‘A’ in ‘R’,X-{A}-> Y. A table said to be in
2NF if both the following condition hold:

 Table is in 1NF (First normal form).

 No non-prime.

Third Normal form (3NF):

A table design is said attributes is dependent on the proper subset of any candidate key
of table. An attribute that is not part of any candidate key is known as non-prime
attributes.

However, it is not in 2NF because non prime attribute to be in 3NF if both the
following condition hold:

 Table must be in 2NF

An attribute that is not part of any candidate key is known as non-prime attribute. In
other words 3NF can be explained like this: A table is in 3NF if it is in 2NF and for
each functional dependency X->Y at least one of the following condition hold.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CHAPTER 5

IMPLEMENTATION
5.1 MODULES
Login module:

 Login module will help in authentication of user accounts. Users who have valid
login id and password can only login into their respective accounts.

Search module:

 This model allows one to search for a particular student or group of students using
search criteria such as name of student id, name, course id etc.

Course module:

 Each module will be able select various courses present in the system. It will be
published by administration under the specific department.

Registration Module:

 This module will help the student get registered from anywhere if internet is present.
This module will really simplify the task of the manual registration. Also after
successful registration the user can update information and change their password as
and when required.

Admin Module :

 This module will help the college in enabling/disabling a user account and updating
user information as required.

Level Module :

 This module is one of the essential parts of the system as this will act as the official
document of student at what level his/her year level in the institution. It will show the
pass out level of the student .

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CHAPTER 6

SNAPSHOTS

6.1 REGISTER PAGE: Register by giving UserID and password.

Fig 6.1: Register Page

6.2 LOGIN PAGE: Login by using UserID and password.

Fig 6.2: Login Page

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

6.3 HOMEPAGE: It gives the introductory information of student information management

system.

Fig 6.3: Homepage

6.4 STUDENT PAGE: It gives the information about the student details.

Fig 6.4: Student Records Page

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

6.5 COURSE PAGE: It gives the information about the student choosen course details.

Fig 6.5: Course Page

6.6 SECTION PAGE: It gives the information about the student section & course details.

Fig 6.6: Section Records Page

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

6.7 ENROLLMENT PAGE: It gives the information about the students enrolled to which
course, year level, status etc.

Fig 6.7: Enrollment Records Page

6.8 YEAR LEVEL PAGE: It gives the information about the year level of the student.

Fig 6.8: Level Records Page

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

6.9 STATUS PAGE : It gives the information about the status of student whether he/she is
old, new , transferee, returnee.

Fig 6.9: Status Records Page

6.10 LOGOUT PAGE :

Fig 6.10: Logout Page

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

CONCLUSION
“Student Information Management System” Is very useful in an academic
institution. There is no hard paper work in this developed system. Supervision can be done
from anywhere over online. This project especially minimizes human effort necessary. This
application is been completely managed by the college so there is no information leak and
data will be secured. Since this application is available locally within the campus it can be
flexibly modified or updated without the upfront investment, and the system will be more
secure when it is handled by the own college.

Dept. of CSE, KLECET, Chikodi 2019-20 Page2

 Student Information Management System

BIBLIOGRAPHY
[1] www.wikipedia.com

[2] www.tutorialspoint.com

[3] https://www.apachefriends.org/download.htmp

[4] https://jquery.com

Dept. of CSE, KLECET, Chikodi 2019-20 Page2