PROJECT REPORT

OF

STUDENT INFORMATION MANAGEMENT SYSTEM

submitted to the
Biju Patnaik University of Technology
in partial fulfilment of the requirement for
the award of the Degree of
Master of Computer Application (MCA)
By
Rajeeb Lochan Jena
Regd. No. – 2205102066

Under the guidance of

SNIGDHA DWIVEDY

Department of Computer Science &

Engineering
INSTITUTE OF MANAGEMENT AND
INFORMATION TECHNOLOGY

CUTTACK, ODISHA – 753003

MAY, 2024

1
 D E C L A R A TI O N

I, Rajeeb Lochan Jena do hereby declare that, t he project work, “ST UDENT
INFORMATION MANAG EMNT SYST EM” which is being submit t ed to t he Biju
Pat naik Univer sit y o f Techno logy for t he award of Mat er in Co mput er Applicat io n
(MCA) Degree has not been submit t ed ear lier to any ot her Universit y/I nst it ut e for any
degree.

Date: Rajeeb Lochan Jena

Registration No. -22051020 66

(Name of Guide)
SNIGDHA DWIVEDY

2
 20th April 2024
Ref No: PJPL/HR/27/2024-25

Rajeeb Lochan Jena

Address: Aakash Lane,
Puri, Pin-752002
Phone No: 7327927648

TO WHOMSOEVER IT MAY CONCERN

This is to certify that the project entitled Student Information Management System
submitted to Biju Patnaik University of Technology, in partial fulfillment of the
requirement for the award of Degree of Mater in Computer Application (MCA) is a record of
original research work done by Rajeeb Lochan Jena (2205102066), under my
supervision and guidance and the project report has not formed the basis for the award of
any Degree/ Diploma/ Associateship/ Fellowship or other similar title to any candidate of
any University.

During his working period, he demonstrated skills with self-motivation to learn new skills.
His performance exceeded our expectations. He presented professional traits during the
internship and managed to complete all assigned tasks. He is a hard-working, dedicated, and
committed personality.

We wish him all the best for his upcoming career.

Thanking You,
Yours faithfully,
For Polo soft Technologies Pvt. Ltd.

Snigdha Dwivedy
(HR Executive)
Polosoft Technologies Private Limited
Registered Office Address: H. No-G92, SF Pratap Market, Village Munirka, South Delhi, New Delhi-110067
CIN NO-U72200DL2016PTC304086
Address: 109, First Floor, DLF Cyber City, Chandaka Industrial Area, Patia, Bhubaneswar-751024 Phone no
:0674- 2567025 Email: [email protected]

3
 CERTIFICATE BY EXTERNAL EXAMINER

This is to certify that the project entitled “STUDENT INFORMATION MANAGEMENT

SYSTEM” submitted by Mr. RAJEEB LOCHAN JENA, BPUT Registration No. 2205102066
to Biju Patnaik University of Technology, in partial fulfillment of the requirement for the award
of Degree of Mater in Computer Application (MCA) is examined.

Date :- External Examiner

4
 ABSTRACT
Name of the Project: Student Information Management System
Student Information Management System can be used by education institutes to maintain the records
of students easily. Achieving this objective is difficult using a manual system as the information is
scattered, can be redundant and collecting relevant information may be very time consuming. All
these problems are solved using this project. The objective of Student information System is to allow
the administrator of any organization to edit and find out the personal details of a student and allows
the student to keep up to date his profile. It’ll also facilitate keeping all the records of students, such
as their id, name, mailing address, phone number, DOB etc. So all the information about an student
will be available in a few seconds. Overall, it’ll make Student Information Management an
easier job for the administrator and the student of any organization. The main purpose of this SRS
document is to illustrate the requirements of the project Student information System and is intended
to help any organization to maintain and manage its student’s personal data. Without a student
information System, managing and maintaining the details of the student is a tedious job for any
organization. Student Information system will store all the details of the students including
their background information, educational qualifications, personal details and all the information
related to their resume.
The purpose of implementing the ‘Student Database Management System’ is for the ease of
maintaining student-related data on an institution, our system does serve this purpose and also is a
means of communication between the students/parents and teachers during times when physical
contact is not possible or when it is necessary to convey an important message quickly, due to this
system a lot of paperwork, maintenance, space, time are all reduced for the purpose of handling large
student data.

Submitted By-
Name: RAJEEB LOCHAN JENA
Reg.no: 2205102066

5
 ACKNOWLEDGEMENT

I am indebted to my revered supervisor Snigdha Dwivedy, Polosoft Technologies Pvt. Ltd,

Bhubaneswar whose continuous inspiration and encouragement has helped me to face all hurdles
in the course of my research and made me successful in giving a shape to this research work.

I would like to thank Prof (Dr.) Manas Ranjan Kabat, honorable Principal of our College to provide
me an opportunity to carry out an industrial training and gain real time industrial experience.

I am sincerely tankful to Dr. Suvendra Kumar Jayasingh , HOD, Department of Computer Science
& Engineering for his valuable suggestions and continuous inspiration.

I am grateful to all the faculty members of the Department of Computer Science & Engineering,
IMIT, Cuttack for their able guidance and motivation.

I would like to take this opportunity to thank all who have directly or indirectly contributed to this
research work in terms of their time, effort and good wishes.

RAJEEB LOCHAN JENA

Registration No. -2205102066

6
 CONTENT

 Acknowledgement i
 Preface ii
 List of Tables iii
 List of Figures iv

CHAPTER I INTRODUCTION
1.1 Purpose
1.2 SCOPE
1.3 Definitions, Acronyms and Abbreviations
1.4 TECHNOLOGIE
1.5 SOVERVIEW

CHAPTER II OVERALL DESCRIPTION

2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Constraints

CHAPTER III DESIGN & REQUIREMENTS

3.1 Functional Requirements
3.1.1 Data Flow Diagram
3.1.2 Class Diagram
3.1.3 Use Case Diagram
3.1.4 Sequence Diagram
3.1.5 Entity Relationship Diagram
3.1.6 Data Dictionary
3.2 External Interface Requirements
3.2.1 Lifecycle Model
3.3.1 System Architecture
3.3.2 Hardware Requirements
3.3.3 Software Requirements

7
CHAPTER IV TECHNICAL OVERVIEW
4.1 APACHE
4.2 XAMPP

4.3 Product Functions

CHAPTER V CODING AND DESCRIPTION

5.1 Web Based Application Code
5.2 Functional Testing
5.3 unit Testing Framework
5.5 Compatibility Testing
5.6 Using Cross-Browser Testing Tool
5.7 Load Testing
5.8 Using Apache JMeter

CHAPTER VI SAFETY PURPOSE

CHAPTER VII SNAPSHOTS OF THE PROJECT

CHAPTER VIII Conclusion & future scope

8.0
Features of “STUDENT MANAGEMT SYSTEM”

8.1 Benefits Accrued from “STUDENT

MANAGEMT SYSTEM”
8.2 REFERENCE

8
C

CHAPTER 1
INTRODUCTION

1. SOFTWARE REQUIREMENTS
SPECIFICATION
1.1 Purpose:
The objective of Student information System is to allow the administrator of
any organization to edit and find out the personal details of a student and allows
the student to keep up to date his profile .It’ll also facilitate keeping all the
records of students, such as their id, name, mailing address, phone number,
DOB etc. So all the information about an student will be available in a few
seconds.
Overall, it’ll make Student Information Management an easier job for
the administrator and the student of any organization.
The main purpose of this SRS document is to illustrate the requirements of the
project Student information System and is intended to help any organization
to maintain and manage its student’s personal data.
1.2 Scope :
Without a Student information System, managing and maintaining the
details of the student is a tedious job for any organization.
Student Information system will store all the details of the students including
their background information, educational qualifications, personal details and
all the information related to their resume .
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: Suppose there are hundreds of students and from
this we have to search a particular student and we know the name of the student
.In manual system it is a tedious task though we know the name of the student,
but using this module we can easily search the student by specifying the name
of the student in the search

criteria. Thus this module will help the administrator in searching the student with
various criteria easily.

9
Registration Module and Account Management: This module will help the student get
registered from anywhere if internet is present .This module will really simplify the task of
on paper registration. Also after successful registration the user can update information and
change their password as and when required.
User Management: This module will help the administrator in enabling/disabling a
user account and updating user information as required.
Purpose of project is to maintain details of the students such as storing information about:
Student id
Student password
Student name
Student DOB
Student mailing address
Gender
Registration date
Student status
Contact no
Qualific
ation
City
Resume
Image

1.3 Definitions, Acronyms and Abbreviations :

Personal details: Details of student such as user id, phone
number, address, image, resume, e-mail address etc.

• Contact details: Details of contact associated with the student.

• SRS: System requirement Specification
• WWW: World Wide Web
• Administrator: A Login Id representing the user is an administrator &
can access all the records details

10
1.4 Technologies :
• PHP.
• MYSQL
• JAVASCRIPT
• HTML
• CSS
1.5 Overview:
The rest of this SRS is organized as follows:
Section 2 gives an overall description of the software. It gives what level of
proficiency is expected of the user, some general constraints while making the
software.
Section 3 gives specific requirements which the software is expected to deliver.
Some performance requirements and constraints are also given and deal with
other Non-Functional Requirements.
Section 4 deals with External Interface Requirements like Hardware
and Software Interface.
CHAPTER:-2 OVERALL DESCRIPTION
2.1 Product Perspective :

The website Student Information System is aimed towards recording a

considerable number of student records and needs online assistance for
managing records of students. Website should be user-friendly, ‘quick to learn’
and reliable website for the above purpose.
Student Information System is intended to be a stand-alone product and
should not depend on the availability of other website. The system will also
have an administrator who has full-fledged rights with regards to performing
all actions related to control and management of the website.

2.2 Product Functions :

There are two different users who will be using this product:
Administrator who can view and edit the details of
any students.
Students who can view their details as well as they can
edit their details.
11
 The features that are available to the Administrator are:
An Administrator can login into the system and perform
any of the available operations.
Can enable/disable student.
Can edit student information to the database.
Can make search for a specific student.
Can access all the details of the student.
The features that are available to the student are:
Student can login into the system and can perform any of
the available options.
Can view his/her personal details.
Can edit his/her personal details Can upload
his/her resume.
Can upload his/her image.
2.3 User Classes and Characteristics:
There are mainly two kinds of users for the product.
The users include:
Administrator
Student
2.4 Operating Environment:
The product can run on any browser.
2.5 Constraints:
Every user must be comfortable using computer.
All operations are in English so user must have basic
knowledge of English.
2.6 USE CASE MODEL:

12
 Use Case Model
1. Administrator: Responsible for managing student records.
• Login into the website
• Update student details
• Search student details
• Display student details
• Enable/Disable student
2. Student: Has the access rights to view and edit their personal details.

• Login into the website

• Display student details
• Edit their details
• Upload their images
• Upload their resumes
2.7 Assumptions & dependencies

13
• Administrator is created in the system already.
• Roles and tasks are predefined.

Specific Requirements :

3.1 Use Case Reports

1. Administrator: Responsible for managing student
details. Use-case: Login into the website
Goal in context: Gain access to the website

Brief Description: This use case is used when the administrator wants to
access the website to enable/disable/update the personal details of the
student. Preconditions: The Administrator must be logged onto the
website in order for this use case to begin.
Basic Flow:
The Website prompts the administrator for the user name and password.
The Administrator enters the user name and password.
The Website verifies the password and sets the user’s authorization.
The Administrator is given access to the Website to perform his
tasks. Alternative Flow:
The administrator enters invalid username and password then
he will not be allowed to enter the website.
Post conditions: The website state is unchanged by this use case.

14
 Use Case Report- Login into the
website Use Case: Display student details

Goal in context: View the details of a student

Brief Description: This use case is used when the administrator wants to
view the personal details of the students already existing in the database
on the screen.
Preconditions:
The Administrator must be logged into the system in order for this use
case to begin
The details of the student must pre-exist in the database.
The student id must be entered correctly.
Basic Flow:
The Administrator logs onto the System.
The Administrator search the student from following keys:-
o Student id o First/last
name o Registration
date o status

The System prompts for the student detail from one of the above keys.
The student details are displayed on the screen.
Alternative Flow:
Student Not Found
If in the Display a student sub-flows, a student with the specified id
number does not exist, The system displays an error message.
The Administrator can then enter a different id number or cancel the
operation, at which point the use case ends.
Post conditions:
The student details are displayed on the screen already existing in the
system.

15
 The state of the system remains unchanged.
Use Case : Edit student details
Goal in context: Edit the details of a student.
Brief Description: This use case is used when the administrator wants
to edit the personal details of the himself/herself already existing in the
database. Preconditions:

The Administrator must be logged into the system in order for this
use case to begin.
The details of the student must pre-exist in the database
Basic Flow:
The Administrator logs onto the System.
The Administrator can edit following keys: -
o First/last name
o Gender o DOB
o Contact no o Qualification o
City o Email1 o
o Email2

16
 o o Address
o o Description
The Website updates the database according to edited details.
The student details are edited in the database.
Alternative Flow:
There is no alternative flow of this use case diagram.
Post conditions:
The student details get updated in the database.

Use Case Report- Edit student detail into the website

2. Student:
Use Case : student registration
Goal in context: Registration of a student

Brief Description: This use case is used when the student register
himself/herself in the database online.
Preconditions:
The Student must accessed the website in order for this use case to begin.
The user id must be unique and entered correctly.
Basic Flow:
The Student enters into the website.
The student fill his/her details from the following keys:-
o Student id o
password
17
 o First/last
name o Status o
Gender o DOB
o Contact no o
Qualification o
City o Email1 o
Email2 o

o Address o
Description o Resume
o Image
The System details are added to the database.
The student details are displayed on the screen.
Alternative Flow:
User ID not unique: if the user id entered is not unique then it will show an error
message.
Post conditions:
The student get registered on the website and to login into that particular the
administrator must enable it.

Use Case Report- Register student on website

18
Use-case: Login into the website
Goal in context: Gain access to the website
Brief Description: This use case is used when the student wants to
access the website
Preconditions: The Administrator must enabled the particular student
onto the website in order for this use case to begin.
Basic Flow:
The website prompts the student for the user name and password.
The Student enters the user name and password.
The website verifies the password and sets the user’s authorization.
The Student is given access to the website to perform his
tasks. Alternative Flow:
The Student enters invalid username and password then he will
not be allowed to enter the website.
Post conditions: The website state is unchanged by this use case.

Use Case Report- Login into the system

Use Case : Edit student details
Goal in context: Edit the details of a student
Brief Description: This use case is used when the student wants to edit
the personal details of the himself/herself already existing in the
database. Preconditions:
The Student must be logged into the system in order for this use
case to begin.
The details of the student must pre-exist in the database
The student must be enabled by administrator.

19
 Basic Flow:
The Student logs onto the System.
The Student can edit following keys:-
o First/last name
o Gender o DOB
o Contact no o
Qualification o
City o Email1 o
Email2 o Address
o Description
The Website updates the database according to edited details.
The student details are edited in the database.
Alternative Flow:
There is no alternative flow of this use case diagram.
Post conditions:
The student details get updated in the database.

Use Case Report- Edit Student Details Into Database

20
3.2 Functional Requirements :
The Administrator will be given more powers (enable/disable/ update)
than other users.
It will be ensured that the information entered is of the correct format.
For example name cannot contain numbers. In case if incorrect form
of information is added, the user will be asked to fill the information
again.
The system can be accessed anytime.
3.3 Non- Functional Requirement :
3.2.1. Performance Requirements:

The proposed system that we are going to develop will be used as the Chief
performance system for providing help to the organization in managing
the whole database of the student studying in the organization.
Therefore, it is expected
that the database would perform functionally all the requirements that are
specified.
3.2.2. Safety Requirements:
The database may get crashed at any certain time due to virus or
operating system failure. Therefore, it is required to take the database
backup.
3.2.3. Security Requirements:

We are going to develop a secured database. There are different

categories of users namely Administrator, Student who will be viewing
either all or some specific information form the database.
Depending upon the category of user the access rights are decided. It
means if the user is an administrator, then he can be able to modify the
data, append etc. All other users only have the rights to retrieve the
information about database.

3.4 Conclusion:
This SRS has given all the details of the application need to be built.
21
 CHAPTER 3
DESIGN PHASE

1. Introduction

1.1) Scope and purpose

The purpose of the design phase is to develop a clear understanding of what the developer
wants people to gain from his/her project. As you the developer work on the project, the
test for every design decision should be
"Does this feature fulfill the ultimate purpose of the project?"
A purpose statement affects the design process by explaining what the developer
wants the project to do, rather than describing the project itself.
The Design Document will verify that the current design meets all of the explicit
requirements contained in the system model as well as the implicit requirements desired
by the customer.

1.2) Overall System Design Objectives

The overall system design objective is to provide an efficient, modular design that will
reduce the system’s complexity, facilitate change and result in an easy implementation.
This will be accomplished by designing strongly cohesion system with minimal
coupling. In addition, this document will provide interface design models that are
consistent user friendly and will provide straight forward transition through the various
system functions.

1.3) Structure of Design Document

System Architecture Design – The System architecture section has detailed
diagram of the system, server and client architecture.
Data Design – The data Design include an ERD as well as Database design.
Functional Design Description – This section has the functional partitioning from the
SRS, and goes into great detail to describe each function

22
2. System Architecture Design

2.1) System Architecture

The SIMS is a system which contain major part which include: student Detail,
Student image and resume.
The user selects one of the available options as an input to the system. According to
the input by the user the system acts and the rest of the functions are performed
accordingly. The administrator can operate on any st udent details. But the normal
student or users can only access their details of all the functionalities.

3. Data Design
3.1) Entity Relationship Diagram:

23
24
 Entity Relationship Diagram

DATA DIRECTORY

Entity Relationship Diagram-

25
26
 Functional Design Description
Data Flow Diagram :

4.2 Decision Tree :

27
Conclusion
Hence we can conclude that the design phase of the SIMS give us the
information of all the processes used in the project and their relation.
Student_Registration_handler.php
<?php include 'Connect.php'; $flag = "success";
function rollbackData(){ mysql_query("
ROLLBACK "); global $flag; $flag =
"error"; if(mysql_error() != null){
die(mysql_error());
}
$student_id = $_POST['st_id'];
$student_pass = $_POST['st_pass'];
$first_name = $_POST['first_name'];
$last_name = $_POST['last_name'];
$gender = $_POST['gender'];
$contact_no = $_POST['contact_no'];
$qualification= $_POST['qualification'];
$city = $_POST['city'];
$email1 = $_POST['email1'];

28
 $email2 = $_POST['email2'];
$address = $_POST['address'];
$description = $_POST['description'];
$resumename = "";
$imagename = "";
$dobdate = date("Y-m-d",strtotime($_POST['dob']));
/*
This block is used to check whether the student_id already exits
in database.

29
 Chapter 4
TECHNICAL OVERVIEW
The technology selected for implementing Student Information Management System is
PHP/MYSQL. Apache is used as the HTTP server .The development was done in a
‘windows’ environment using adobe Dreamweaver CS5.

PHP
PHP is a general-purpose scripting language that is especially suited to server side web
development where PHP generally runs on a web server code is embedded into the HTML
source document. Any PHP code in a requested file is executed by the PHP runtime,
usually to create dynamic web page content. It can also be used for command- line
scripting and client-side GUI applications. PHP can be deployed on many web servers
and operating systems, and can be used with many relational database
management systems (RDBMS). It is available free of charge, and the PHP Group
provides the complete source code for users to build, customize and extend for their own
use.

MySQL
MySQL is a relational database management system (RDBMS) [1] that runs as a server
providing multi-user access to a number of databases. MySQL is a popular choice of
database for use in web applications and is an open source product. The process of
setting up a MySQL database varies from host to host, however we will end up with a
database name, a user name and a password. Before using our database, we must create
a table. A table is a section of the database for storing related information. In a table we
will set up the different fields which will be used in that table. Creating a table in
phpMyAdmin is simple, we just type the name, select the number of fields and click the
‘go’ button. we will then be taken to a setup screen where you must create the
fields for the database. Another way of creating databases and tables in phpMyAdmin
is by executing.

30
 TECHNICAL OVERVIEW Chapter 31

Apache
The Apache HTTP Server is a web server software notable for playing a key role in the
initial growth of the World Wide Web. In 2009 it became the first web server software
to surpass the 100 million web site milestone. Apache is developed and maintained by
an open community of developers under the auspices of the Apache Software
Foundation. Since April 1996 Apache has been the most popular HTTP server software
in use. As of November 2010 Apache served over 59.36% of all websites and over
66.56% of the first one million busiest websites.

XAMPP
XAMPP is a small and light Apache distribution containing the most common web
development technologies in a single package. Its contents, small size, and portability
make it the ideal tool for students developing and testing applications in PHP
and MySQL. XAMPP is available as a free download in two specific packages: full and
lite. While the full package download provides a wide array of development tools,
XAMPP Lite contains the necessary technologies that meet the Ontario Skills
Competition standards. The light version is a small package containing Apache HTTP
Server, PHP, MySQL, phpMyAdmin, OpenSSL, and SQLite.

Obtaining and Installing XAMPP

As previously mentioned, XAMPP is a free package available for download and use for
various web development tasks. All XAMPP packages and add-ons are distributed
through the Apache Friends website at the address: http://www.apachefriends.org/. Once
on the website, navigate and find the Windows version of XAMPP and download the
self-extracting ZIP archive. After downloading the archive, run and extract its contents
into the root path of a hard disk or USB drive. For example, the extract path for a local
Windows installation would simply be C:\. If extracted properly we will notice a new
xampp directory in the root of your installation disk. In order to test that everything has
been installed correctly, first start the Apache HTTP Server by navigating to the xampp
directory and clicking on the apache_start.bat batch file.
Next we will test if the server is running correctly by opening an internet browser and
typing http://localhost/ into the address bar. If configured correctly, we will be presented
with a screen similar to that of the one below.

31
 SOME BASIC CODE

XAMPP splash screen.

In order to stop all Apache processes we do not close the running terminal application,
but instead run another batch file in the xampp lite directory called apache_stop.bat.

Creating a Database and Inserting Data

Now that we have run and tested Apache and PHP, the next step is running MySQL and
creating a database and table which will hold information to be used by our website. In
order to start MySQL, navigate to the xampp directory and run the mysql_start.bat batch
file. The XAMPP package contains an application called phpMyAdmin which allows
developers to administer and maintain MySQL databases. We will be using
phpMyAdmin to create a database and table, and enter test data.

Before testing phpMyAdmin, make sure that both Apache and MySQL are running by
opening their respective batch files: apache_start.bat and mysql_start.bat. Along with
Apache and MySQL running in the background, we type http://localhost/phpMyAdmin/
into our web browser. If successful we will be presented with a phpMyAdmin start page
similar to the one shown below.

32
 SOME BASIC CODE

phpMyAdmin start page

The first step with phpMyAdmin running is creating a new database. We create a new
database by directly executing SQL statements as shown below. The successful
execution of the SQL query creates a database ‘student’ with two tables in it.
The tables are admin login and student information.We also inserted values in the
admin table.

33
 SOME BASIC CODE

Creation of database in MySQL using phpMyAdmin

Thus we have learned to create a database in MYSQL by executing sql statements. After
creating the database and tables we are now ready to use them in our website “Student
Information Management System” .

34
 SOME BASIC CODE

<?php

session_start();

error_reporting(0);

include('includes/dbconnection.php');

?>

<!doctype html>

<html>

<head>

<title>Student Management System || Home Page</title>

<script type="application/x-javascript"> addEventListener("load", function() { setTimeout(hideURLbar, 0);

}, false); function hideURLbar(){ window.scrollTo(0,1); } </script>

<!--bootstrap-->

<link href="css/bootstrap.css" rel="stylesheet" type="text/css" media="all">

<!--coustom css-->

<link href="css/style.css" rel="stylesheet" type="text/css"/>

<!--script-->

<script src="js/jquery-1.11.0.min.js"></script>

<!-- js -->

<script src="js/bootstrap.js"></script>

<!-- /js -->

<!--fonts-->

<link
href='//fonts.googleapis.com/css?family=Open+Sans:300,300italic,400italic,400,600,600italic,700,700italic,
800,800italic' rel='stylesheet' type='text/css'>

<!--/fonts-->

<!--hover-girds-->

<link rel="stylesheet" type="text/css" href="css/default.css" />

35
 SOME BASIC CODE

<link rel="stylesheet" type="text/css" href="css/component.css" />

<script src="js/modernizr.custom.js"></script>

<!--/hover-grids-->

<script type="text/javascript" src="js/move-top.js"></script>

<script type="text/javascript" src="js/easing.js"></script>

<!--script-->

<script type="text/javascript">

jQuery(document).ready(function($) {

$(".scroll").click(function(event){

event.preventDefault();

$('html,body').animate({scrollTop:$(this.hash).offset().top},900);

});

});

</script>

<!--/script-->

</head>

<body>

<?php include_once('includes/header.php');?>

<div class="banner">

<div class="container">

<script src="js/responsiveslides.min.js"></script>

<script>

$(function () {

$("#slider").responsiveSlides({

auto: true,

nav: true,

speed: 500,

36
 SOME BASIC CODE

namespace: "callbacks",

pager: true,

});

});

</script>

<div class="slider">

<div class="callbacks_container">

<ul class="rslides" id="slider">

<li>

<h3>Student Management System</h3>

<p>Registered Students can Login Here</p>

<div class="readmore">

<a href="user/login.php">Student Login<i class="glyphicon glyphicon-menu-right"> </i></a>

</div>

</li>

</ul>

</div>

</div>

</div>

</div>

<div class="welcome">

<div class="container">

<?php

$sql="SELECT * from tblpage where PageType='aboutus'";

$query = $dbh -> prepare($sql);

37
 SOME BASIC CODE

$query->execute();

$results=$query->fetchAll(PDO::FETCH_OBJ);

$cnt=1;

if($query->rowCount() > 0)

foreach($results as $row)

{ ?>

<h2><?php echo htmlentities($row->PageTitle);?></h2>

<p><?php echo ($row->PageDescription);?></p><?php $cnt=$cnt+1;}} ?>

</div>

</div>

<!--/welcome-->

<!--testmonials-->

<div class="testimonials">

<div class="container">

<div class="testimonial-nfo">

<h3>Public Notices</h3>

<marquee style="height:350px;" direction ="up" onmouseover="this.stop();"

onmouseout="this.start();">

<?php

$sql="SELECT * from tblpublicnotice";

$query = $dbh -> prepare($sql);

$query->execute();

$results=$query->fetchAll(PDO::FETCH_OBJ);

38
 SOME BASIC CODE

$cnt=1;

if($query->rowCount() > 0)

foreach($results as $row)

{ ?>

<a href="view-public-notice.php?viewid=<?php echo htmlentities ($row->ID);?>" target="_blank"

style="color:#fff;">

<?php echo htmlentities($row->NoticeTitle);?>(<?php echo htmlentities($row-

>CreationDate);?>)</a>

<hr /><br />

<?php $cnt=$cnt+1;}} ?>

</marquee></div>

</div>

</div>

<!--\testmonials-->

<!--specfication-->

<!--/specfication-->

<?php include_once('includes/footer.php');?>

<!--/copy-rights-->

</body>

</html>

39
 Chapter 5
DESCRIPTION
Student Information Management System can be used by education institutes
to maintain the records of students easily. Achieving this objective is difficult using a
manual system as the information is scattered, can be redundant and collecting relevant
information may be very time consuming. All these problems are solved using this
project

The directory structure of the project is as follows:

Description of root directory contents

40
Images Directory : This directory contains the images uploaded by the students during
registration process. Supported formats are the .jpg and .gif files.
Resume Directory : This Directory Contains resumes of students uploaded during registration
process of students. Files in this folder can be of .doc,.txt or .pdf format.
Admin_Edit_Student_Info.php : Admin page for editing information of a student. The
administrator can change details of a student in this page. Though facility of changing the image and
resume are not yet provided but will be provided in future versions of the
project.Admin_Edit_Student_Info_Handler.php : Page handler for handling the
Admin_Edit_Student_Info.php file.It writes the edited values in the database on the server.

Admin_Header.php : Header file for pages accessible to administrator only.

Admin_Home.php : Home page for administrator after logging in process.
Admin_Login.php : Login page for administrator access. Shows appropriate message for wrong
username and/or password.
Admin_Login_handler.php : Page handler for Admin_Login.php page.It checks the values provided
with the values in the database.

Admin_Student_View_Info.php : Page to display student information to the administrator.

Connect.php : Page for database connectivity. It is used whenever database values are required on the
page.

DisplayAll.php : Page to display all registered students to the administrator. This facility is only
available to the administrator.

Enable_Disable_handler.php : Handler page for enabling/disabling of students account

facility. This functionality is only available to the administrator.

Footer.php : Footer file for all pages.

Header.php : Header file for login page and homepage of the site.
Index.php : Homepage of the website.

Logout.php : Logout handler page. It Destroys all session variables thus ending user session.

Search.php : Search page to search students. It can only be used by administrator. Students can be
searched using different fields such as user id, account status etc.

Search_Result.php : Page to display search results to the administrator.

Search_View_Result.php : Page to display student information for any selected search result.

Student_Edit.php : Page to edit student information. It can be accessed by students.

Student_Edit_Handler.php : Page handler for Student_Edit.php.

41
 Student_Header.php : Header file for student pages.

Student_Home.php : Home page for students after they log into their respective accounts.

Student_login.php : Login Page for student login. Appropriate message is displayed if the login is
unsuccessful.

Student_login_handler.php : Page handler for Student_Login.php. It checks the values

provided with that in the database.

Student_Registration.php : Student Registration page. The students enters various details here for
registration.
Student_Registration_handler.php : Page Handler for handling the file Student_registration.php.It
adds value to the student_information table thus creating a new user.

Student_Reset_Password.php : Page for resetting password. It can be used only by

students.Administrator password can be changed only by changing the values in the table directly.

Student_Reset_Password_Handler.php : Page handler for handling page

Student_Reset_Password. php.

Student_View.php : Page to display student profile with all the details of the student.

Style.css : Stylesheet for the whole site design.

Validation.js : JavaScript validations used for validation of form values. Various form
entries are validated at the client side using this file only.

Description of database tables

admin_login :

o user_id : Stores user id of administrator(s). o password : Stores password of the

administrator(s). o last_login_date : Stores the last login date of the administrator(s).
Student_information :

42
 o student_id : Stores user id of the student(s) o student_password : Stores
password of the student(s) o first_name : Stores first name of the student(s) o last_name
: Stores last name of the student(s) o registration_date : Stores the registration date of
the student(s). o gender : Stores the gender of the student(s). o date_of_birth : Stores the
date of birth of the student(s).
o student_status : Stores the current status of the student account(s).
o contact_no : Stores the contact number of the student(s). o qualification

: Stores student(s) qualification.

o city : Stores the city in which the student(s) lives. o email1 : Stores primary
email of the student(s). o email2 : Stores secondary email of the student(s). o address :
Stores the address of the student(s). o description : Stores description of the student(s).
o resume : Stores resume of students(s). o image : Stores image of the student(s). o
last_login_date : Strores last login date of the student(s).

Features
The Website provides following functionalities to the users :
Administrator :
Information o Enable/disable student accounts o Search students

Student : o Login/Logout o View profile o Edit profile o Change

password
o Register new profile

43
Structure

44
45
 Chapter 6
Safety Purpose
1.USE A RELIABLE STUDENT DATA MANAGEMENT SYSTEM
Before the advent of school management software, educational institutions used to store all
their student information in registers or excel sheets. There was no way to ensure the privacy
and security of the data. The introduction of a data management system made the storage of
data more efficient and more secure. But a large number of companies flooded the market and
claimed to provide the best software. When it came to efficacy and security, only a few deliver
the desired results.
Getting a sophisticated student data management system from a trustworthy and experienced
service provider is winning half the battle. To keep their student information safe, every
educational institution should invest in a reliable student data management system. The key
is to find a trustworthy and experienced service provider.

2.USE ROBUST AND SECURE PASSWORDS

After getting a reliable student management system, educational institutions need to use
strong and secured passwords to keep the data safe. The first step is to set a password with a
mix of alphabets (both upper and lower case), numbers, and symbols. After that,
provide the authorized staff members with the new password and ask them to change it at
regular intervals. If possible, use encryption and enable multiple levels of authentication
in the computer systems for further security.

3.BE PARTICULAR ABOUT PROVIDING THE ACCESS

Just as setting a strong password, defining who can and who can’t access the system is equally
critical to data security. After installing the system, handpick some trustworthy staff members
who can handle the data and manage the system. The goal is to minimize the users with access
to important student data and ensure privacy. Decide how much access each user needs to
perform their assigned tasks and restrict their access after a certain level.
3.4.3 Security-
The security of the system is maintained by providing a login interface to the user. Only
those who have the login is and password can enter the system.
User-Friendly as the system is very interactive and can be easily operated.
Maintainability and reliability if the system is kept very thoroughly as all the records kept in
the database have the backups and system can restore if there is power loss.

46
Depending upon the category of user the access rights are decided. It means if the user is an
adminstrator then he can be able to modify the data, append etc. All other users only have the
rights to retrieve the information about database.

3.4.4 Performance-
The proposed system that we are going to develop will be used as the Chief performance
system for providing help to the organization in managing the whole database of the student
studying in the organisation. Therefore, it is expected that the database would perform
functionally all the requirements that are specified.

3.4.5 Usability-
The Administrator will be given more powers (enable/disable/ update) than other
users. It will be ensured that the information entered is of the correct format.
For example:
name cannot contain numbers. In case if incorrect form of information is added, the
user will be asked to fill the information again.
The system can be accessed anytime.
4.OVERALL PRODUCT
SPECIFICATION-
4.1 Product Overview-
The website Student Information System is aimed towards recording a considerable number
of student records and needs online assistance for managing records of students. Website
should be user-friendly, ‘quick to learn’ and reliable website for the above purpose. Student
Information System is intended to be a stand-alone product and should not depend on the
availability of other website. The system will also have an administrator who has full-fledged
rights with regards to performing all actions related to control and management of the website.
4.2 Product Perspective-
The rest of this SRS is organized as follows:
Section 2 : gives an overall description of the software. It gives what level
of proficiency is expected of the user, some general constraints while
making the software. Section 3 : gives specific requirements which the
software is expected to deliver. Some performance requirements and
constraints are also given and deal with other Non-Functional
Requirements.
Section 4 : deals with External Interface Requirements like Hardware
and Software Interface.

47
 4.3 Product Functions-
There are two different users who will be using this product:
• Administrator who can view and edit the details of any students.
• Students who can view their details as well as they can edit their details.

The features that are available to the Administrator are:

• An Administrator can login into the system and perform any of the available operations.
• Can enable/disable student.
• Can edit student information to the database.
• Can make search for a specific student.
• Can access all the details of the student.

The features that are available to the student are:

• Student can login into the system and can perform any of the available options.
• Can view his/her personal details.
• Can edit his/her personal details
• Can upload his/her resume.
• Can upload his/her image.

User Classes and Characteristics :

There are mainly two kinds of users for the
product. The users include:
• Administrator
• Student

Operating Environment :
The product can run on any browser.

48
 Chapter 7
SNAPSHOTS OF THE PROJECT

This is the homepage/indexpage of the site.

This is the student login page.

49
 This is the registration page where students can register online

After successful registration the user account needs to be first enabled by the
administrator.The students can then login into their accounts with the id and password they
choose during registration.The above page shows student login page.

50
After logging in the student home page is opened as shown above.

The student can view their profile.The above page shows the user profile.The link to
the resume is shown if a resume was uploaded during registration otherwise its not
shown.

51
Students can edit their profiles by using the edit profile option on their
homepage.the above page is used for editing student information.

The students have the option to change their password.They need their old password
in order to change the password.

52
After successful operation a password change notification is displayed to the user.

The above page is the administrator login page. It requires the administrator
username and password.

53
This is the displayall page wherein the administrator can see all the registered
students.He can enable/disable their accounts as well as view/edit students information.

This page shows the change in account status.after successful change a message
is displayed to the administrator.

54
This is the search page and it provides search function to the administrator.here
we search for all the students with theirs accounts enabled.

This is the search result display page.the administrator can view profile of any of the
searched students from here.If there are no results then an appropriate message is
displayed.

55
 SCOPE OF PROJECT

The Student Information Management System(SIMS) can be enhanced to

include some other functionality like marks, attendance management.
Talent management of students based on their performance evaluation can be
added.
Social networking can also be added wherein students can interact with each
other.

Online class functionality can be added.

Can evolve as an online institution.
Functionality of chat and messages can be added.
Online exam functionality can be added.
Online resume builder functionality can also be added.

56
 CHAPTER: -8
CONCLUSION
Student information management system lead to a better organization structure since the
information management of the students is well structured and also lead to better as well as
efficient utilization of resources.

Student Information Management System can be used by education institutes to maintain the
records of students easily. Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting relevant information may be very time
consuming. All these problems are solved using this project

Our project Student Information Management System was developed by all three of us. We, a team
of three persons took a step by step approach in order to reach our goal. We applied the knowledge
we gained during our training period at EN Technologies Pvt. Ltd. and developed this project
“STUDENT INFORMATION MANAGEMENT SYSTEM”.
R PHP5 by WROX.
E
F • www.google.com.
E • www.wikipedia.com
R
E • www.w3schools.com
N
C • Informatics practices by Sumita Arora.
E • Head First PHP & MySQL by Lynn Beighley and
• PHP book Michael Morrison (O’Reilly)
By Vasvani
(TMH
publications)

• Beginning

• Orrison(O’Reilly)

57