STUDENT INFORMATION

MANAGEMENT SYSTEM
A Project Report
Submitted in partial fulfillment of the
Requirements for the award of the Degree of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY)

By

Sayyed Huda Muhammad Ali

Under the esteemed guidance of

Prof. Siddhi Malpekar
Designation

DEPARTMENT OF COMPUTER SCIENCE

J. K. COLLEGE OF SCIENCE AND COMMERCE
(Affiliated to University of Mumbai)
NAVI MUMBAI, 400701
MAHARASHTRA
2021
J. K. COLLEGE OF SCIENCE AND COMMERCE
(Affiliated to University of Mumbai)
NAVI MUMBAI-MAHARASHTRA-400701
 DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE

This is to certify that the project entitled, "STUDENT INFORMATION MANAGEMENT

SYSTEM", is bonfire work of SAYYED HUDA MUHAMMAD ALI bearing Seat.No: ( )
submitted in partial fulfillment of the requirements for the award of the degree of BACHELOR
OF SCIENCE in INFORMATION TECHNOLOGY from the University of Mumbai.

Internal Guide Coordinator

External Examiner

Date: College Seal

 Abstract

This project “Student Information Management System” provides us a simple interface

for maintenance of student information. It can be used by educational institutes or colleges
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.

Throughout the project the focus has been on presenting information in an easy and
intelligible manner. The project is very useful for those who want to know about Student
Information Management Systems and want to develop software’s/websites based on the
same concept.

The project provides facilities like online registration and profile creation of students thus
reducing paperwork and automating the record generation process in an educational
institution.
 ACKNOWLEDGEMENT

The presented project, as a part of the curriculum, was a first-of-its-kind experience for
me. I had looked upon this project not merely as a syllabus to be completed but as an aim to know,
study, develop and experience the commercial software technologies.
I would like to thank and appreciate the support of a few, who served a helping hand
physically, mentally, and intellectually in the course of this project. Foremost regards to my guide,
I would thank Mrs.Siddhi who made available the facilities required for the project work. I am
pleased to be able to say that, in an acceptable manner, I have achieved my goals and goals to
make this project a result. I also wish to mention the unsaid support of my parents who, as always
helped me in every possible way to make this work of mine, a success. The contribution made by
my friends and mates directly or indirectly was indispensable, and will always be remembered.
This opportunity has given me valuable experience in software development.

Thanking You,
 DECLARATION

I hereby declare that the project entitled, “STUDENT INFORMATION

MANAGEMENT SYSTEM” done at the J. K. COLLEGE OF SCIENCE AND
COMMERCE, has not been in any case duplicated to submit to any other university for the award
of any degree. To the best of my knowledge other than me, no one has submitted to any other
university.
The project is done in partial fulfillment of the requirements for the award of the degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as a V
semester project as part of our curriculum.

Name and Signature of the Student

 TABLE OF CONTENTS

TABLE OF CONTENTS 6
Introduction 8
1.1 Background 8
1.2 Problem Statement 8
1.3 Objectives 8
1.4 Scope 9
1.5 Expected outcome
1.5 Organization of report 9
Survey Of Technologies 11
2.1 Technology Used 11
2.1.1 PHP 11
2.1.2 MYSQL 12
2.1.3 APACHE 14
2.1.4 XAMPP
Requirements and Analysis 15
3.1 Requirement Analysis 16
3.1.1 Functional Requirements: 16
3.1.2 Non-Functional Requirements: 16
3.2 Hardware & Software Requirements 17
3.2.1 Hardware Requirements 17
3.2.2 Software Requirements 17
1
7
1
7
System Design 19
4.1 Module Division 19
4.2 Data Dictionary 20
4.3 Flow Chart 22

Overall Description 23
5.1 Product Perspective 23
 5.2 Product Functions 23
5.3 User Classes and Characteristics 24
5.4 Operating Environment 25
5.5 Constraint 26
5.6 Use Case Model 27

System Architecture Design 28

6.1 System Architecture Design 28

6.2 Data Design 29
6.3 Functional Design Description 30

Conclusion and Future Work 31

7. CONCLUSION 32
7.1 Significance of the System 33
7.2 Limitations of the system 34
7.3 Future scope of the project 35

References
 Introduction

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.

1.1 Background
In earlier manage, collection and storing student record is the most difficult tasks. Hence
with the help of this management system, it becomes very easy to collect, search, manage and to
store the student records

1.2 Problem Statement

There are several obstacles that I came to know about while trying to develop this
application.

1.3 Objectives
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.

1.4 Scope
Without a Student information System, managing and maintaining the details of the
student in 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
1.5 Expected Outcome
A management system that helps to take information for User which can be easily
access or maintain by the Admin.

1.6 Achievements
Through this project, I enlarged my knowledge of how to understand the real-world
problem and to come up with a digital clarification to the people. Also, I have been educated to
integrate various things into my project.

We learned how to write a project SRS.

We gain a lot of information about the software and technology available in this field.
We learned about java.
We learned about developing U.I.
It’s more reliable and improves productivity.
We learn about how to use MySQL for the backend.
Build or create graphics-based UI design.

1.7 Organization of report

Chapter 1: Introduction:
Chapter 1 includes several parts and is as follows:
Background: An explanation of the development context and its association with the work
already done in the field.
Objectives: Comprehensive declaration of the goals and aims of the plan.
Purpose: Project theme description that answers questions about why this project is
implemented.
Scope: An ephemeral summary of the methodology, hypotheses, and limits.
Achievements: Explain what knowledge the student achieved after the accomplishment of the
work.
Organization of report: Summing up the permanent parts of the project description, in fact,
gives the reader an overview of what will come in the project report.

Chapter 2: Survey of Technologies:

This chapter contains all the details of the technology that I have used as a backend and
frontend for building the project. It also embraces the details of the Android Studio I have used
for completing this project. This section also contains the details of why I have chosen a
particular technology for backend and frontend. I am using Android Studio as a Front End and
Firebase is used as a backend. I am developing the chat application System with the support of
the Android Studio.

Chapter 3: Requirements and Analysis:

This chapter defines what problem you are experiencing and how your project will
overcome the problem that is occurring in society. Listing the necessities of the project.
Preparation and forecasting for the project so that the project should complete on period and
doesn't go on a critical path. Give the list of software along with hardware components require
by the project and explain key points about it.

Chapter 4: System Design:

This chapter describes features and procedures researched in aspect, including modules,
modules description and other documentation which is appropriate for the project.

Chapter 5: Overall Description:

This chapter contain the overall description of project.

Chapter 6: System Architecture Design:

This chapter describes the features including system architecture design, data design,
Data flow, Functional Design Description.

Chapter 7: Conclusion and Future Work

It contains the Conclusion of the project and the Feature which can be added to the
project.
 Survey of Technologies

2.1 Technology Used:

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

2.1.1 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. PHP 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.

2.1.2 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 simple SQL statements. We
have used this method in order to create our database and tables.

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

2.1.4 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.
 Requirements and Analysis

3.1 Requirement Analysis

Requirement specification means to analyze and gather the needed requirements to
complete the project.

3.1.1 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.1.2 Non-Functional Requirements:

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.2 Hardware & Software Requirements

3.2.1 Hardware Requirements

➢ CPU: Intel Pentium IV processor or equivalent or higher
➢ Memory: 512 MB Ram or Higher
➢ 20 GB HDD or Higher
➢ Network Connectivity

3.2.2 Software Requirements

➢ Front End: HTML and JavaScript
➢ Back End: MySQL
➢ Web Designing language: PHP
➢ OS: Windows 10 64-bit and above versions.
 SYSTEM DESIGN

4.1 Module Division:

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

 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

 Qualification

 City

 Resume

 Image
 OVERALL DESCRIPTION

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

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

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

5.3 User Classes and Characteristics:

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

5.4 Operating Environment:

 The product can run on any browser.

5.5 Constraints:
 Every user must be comfortable using computer.
 All operations are in English so user must have basic knowledge of English.
5.6 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

5.7 Assumptions & dependencies

• Administrator is created in the system already.

• Roles and tasks are predefined.

 System Architecture Design

6.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 student details. But the normal student or users can only access
their details of all the functionalities.
6.2 Data Design

6.2.1 Entity Relationship Diagram:

Entity Relationship Diagram

6.3 Functional Design Description

6.3.1 Data Flow Diagram:

6.3.2 Decision Tree:

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.
 Conclusion and Future Work

7.1 CONCLUSION
This classified Application for Chatting will make it easier for people to send and receive
messages which will save the user from paying the money for each message. To use this
application the user needs to register on this application else they will not be able to send and
receive messages to the application. By submitting general information like name, phone
number, and images they can register on this application. After completing registration they will
be able to login into an application and to use other features which only registered members can
use.
Benefits of application:
● Easy to use.
● Users can chat online.
● Users can send and receive messages without paying any cost.

7.1.1 Significance of the System:

Registration of the user: The user or anyone can do registration just by filling up some
information name, contact number, and Images and other specified details

7.2 Limitations of the system

● If the software is not affordable to educational institute then it became a financial
burden.
● If the software does have enough features to fulfill the requirements.

7.3 Future scope of the project

● This management system can be implemented in different educational institutes.
● It provides security and privacy.
● It also helps to enhance the user interaction.
● The data can be handled easily.
● Administrative processes becomes easier.

References

1) https://stackoverflow.com/
2) https://firebase.google.com/
3) https://square.github.io/picasso/
4) https://youtube.com/
5) https://github.com/hbb20/CountryCodePickerProject/
6) https://www.geeksforgeeks.org/android-studio-tutorial/
7) https://www.tutorialspoint.com/android/android_studio.htm