Final Report On
Student Information System
Submitted to
Department of Computer Science and Engineering
Nepal Engineering College
In Partial Fulfillment of the
Requirements for the Degree of B.E. in Computer
By
Jeshik Phuyal (018-311)
Laxmi Chalise (018-317)
Bipana Tripathi (018-349)
Supervised By: Asst. Prof. Bishwadeep Mainaly
Date: 07/13/2023
ABSTRACT
The idea of developing a student information system is to improve communication
between teacher and parents. The student management system can be used by
teachers, parents, and students. It aids in the tracking of a student’s development
so that the optimal decisions for the student’s learning path may be made. The
most important of which is to centralize the data administration and accessibility.
Teachers will be able to input, maintain, and access student data more simply.
Parents and guardians have a better understanding of how their children perform
in class. This project mainly explains the various actions related to student details.
This project shows some ease in adding, editing and deleting the student details. It
also provides a less time-consuming process for viewing, adding, editing and
deleting the marks of the student. Our project includes: student registration,
subject allocation, semester wise selection examination marks entry, displaying
semester result, student details.
Keywords: [Student management system, student information system.]
i
ACKNOWLEDGEMENT
We would like to extend our gratitude towards Department of Computer
Engineering, Nepal Engineering College and Pokhara University for providing a
platform, opportunity to undertake an exclusive Major project. We would like to
thank all the members in Department of Computer Engineering and Project
Coordinator Bishwadeep Mainaly along with all the teachers for providing help in
the every step during the development of the project. Furthermore, we would like
to give special thanks to our friends for providing knowledge, support, help and
encouragement in accomplishing the task that are needed for the development of
our Major project.
ii
Table of Contents
ABSTRACT .............................................................................................................. i
ACKNOWLEDGEMENT .......................................................................................ii
Chapter 1: Introduction ............................................................................................ 1
1.1
Background ............................................................................................... 1
1.2
Problem Statement .................................................................................... 2
1.3
Objective ................................................................................................... 2
1.4
AIMS ......................................................................................................... 3
1.5
Scope ......................................................................................................... 3
1.6
Application ................................................................................................ 3
1.7
Feasibility .................................................................................................. 4
Chapter 2: Literature Review ................................................................................... 5
Chapter 3: System Design ........................................................................................ 7
3.1 Methodology ...................................................................................................... 7
3.1.1 Client Server Architecture ........................................................................... 7
3.1.2 Software Development Life Cycle .............................................................. 8
3.2 Modules and their description .......................................................................... 10
3.3 DFD Diagram: .............................................................................................. 12
3.4 Use Case Diagram: ....................................................................................... 13
3.5 ER-Diagram: .................................................................................................... 14
3.6 Experimental Tools and Setup ......................................................................... 16
3.6.1 php ............................................................................................................. 16
3.6.2 HTML &CSS ............................................................................................ 16
3.6.3 XAMMP .................................................................................................... 17
3.6.4 Visual Paradigm Community Edition ....................................................... 17
3.6.5 Visual studio code ..................................................................................... 17
3.6.6 MySQL ...................................................................................................... 17
Chapter 4: Implementation and discussion ............................................................ 18
4.1 Task implemented: ........................................................................................... 18
4.2 Testing: ............................................................................................................ 19
iii
4.2.1 Unit Testing .................................................................................................. 19
Module-1: login .................................................................................................. 20
Module-2: add new student ................................................................................ 21
Module-3: add attendance .................................................................................. 22
4.2.2 System Testing: ......................................................................................... 23
4.3 Output Obtained ............................................................................................... 25
Chapter 5: Analysis and evaluation ....................................................................... 26
5.1 Analysis of output obtained ............................................................................. 26
5.2 Evaluation of project ........................................................................................ 27
Chapter 6: Conclusion and future works ............................................................... 27
6.1 Future work ...................................................................................................... 28
REFERENCES ...................................................................................................... 28
Appendices ............................................................................................................. 30
iv
List of figures
Figure 1 DFD Diagram……………………………………………….9
Figure 2 Use Case Diagram……………………………………….....10
Figure 3 Flow Diagram……………………………………………...11
Figure 4 ER Diagram………………………………………………..12
v
ABBREVATIONS
Word
Abbreviation
CSS
Cascading Style Sheet
SIS
Student Information System
SRS
System requirement Specification
HTML
Hyper Text Markup Language
PHP
Hypertext Preprocessor
QA
Quality Assurance
VS
Visual Studio
ER
Entity Relationship
DFD
Data Flow Diagram
vi
vii
Chapter 1: Introduction
1.1 Background
The "Student Information System" has been developed to override the problems
prevailing in the practicing manual system. Student information system is
software which is helpful for students as well as the parents as well as the college
authorities. In the current system all the activities are done manually. It is very
time consuming and costly. Our Student Information System deals with the
various activities related to the students.
This software is supported to eliminate and in some-cases reduce the hardships
faced by this existing system. Moreover, this system is designed for the particular
need of the company to carry out operations in a smooth and effective manner. In
the software, we can register as a user and user has of three types: student, teacher
and parents.
Administrator has the power to add new user and can edit and delete a user. A
student can register as user and can add edit and delete his/her profile. The
administrator can add edit and delete marks for the student. All the allowed users
can see the marks. 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/website based on the same concept.
1
1.2 Problem Statement
The existing student information system has many problems in relation to
registrations and database management, since it is a file-based system. The
following are problems of the existing system. The common issue faced by
student management in educational institutions is the data loss, manual monitoring
of students performance and etc. These activities create loads of tasks to be done
by the educators and school administrators. Their records were also prone to
losses due to a lack of security.
There are still a lot of problems to be discussed but we only highlighted the major
ones. Data collection is not accurate and based on timely manner. Duplication of
data occurs when data input into the system. It is difficult to add, replace, delete
and edit the required information. Checking the validity of input data is difficult
since information is not collected timely and accurately, the output is not precise
and on time. Processing the input data in order to get an output takes much time
because of the manual system (like grade point calculation takes time). Due to this
student do not see their grade report on time. It is difficult to check whether the
output data is valid or not. The data stored takes more rooms. Difficult in order to
add some additional requirements to the existing system’s stored data (i.e.it is not
flexible).
1.3 Objective
The main objective of the Student Management System is to:
•
To retrieve the students and instructors information.
•
To show detail report about exam and attendance.
•
To maintain well organized schedules.
•
Student Data Maintenance.
•
To make student and parents see exam grades online.
2
1.4 AIMS
The aim of this project is develop a quality standalone management system for
resolving problems in the current paper base system and to make a proper
combination between class staff and students/instructors using information
technology.
The proposed system has the following significance:
•
Avoid manual problems
•
Centralized database management.
•
Easy operations for user of the system.
1.5 Scope
Without 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 scope of the project includes the following:
•
Integration of all records of classes.
•
Manage the information of attendance.
•
Shows the information of teacher and students.
1.6 Application
The main purpose using Student Information System Project is
•
Co-ordinate scheduling and communication between different faculties
regarding student.
•
Information tracking for both parent and administrative staff.
•
Applicable in any educational institute for student management.
3
1.7 Feasibility
Feasibility is the determination of whether or not a system or a project is worth
doing. The feasibility of this proposed project shows that this project workable,
meets user requirements, does effective use of resources and is very cost effective.
This project is highly applicable and feasible because:

Time and man power can effectively utilized.

It can be used anytime anywhere as it is a web-based application.

Users can get their services in easy possible way.

This project makes better use of available resources.

This project is technically feasible with the help of available technology.

It has a better working environment with the admin and other users.
The project requires a complete web application that can be used to manage
student details. This is a web app, so that it can be viewed easily. All the
technologies that are used to develop the system are open-sourced, such as PHP,
xampp, bootstrap and so on.
4
Chapter 2: Literature Review
A. Toward a Student Information System for Sebha University
This paper [1] basically focuses on providing a simple interface for the easy
collation and maintenance of all manner of student information. The creation and
management of accurate, up-to- date information regarding students’ academic
careers is critical students and for the faculties and administration of Sebha
University in Libya and for any other educational institution. A student
information system deals with all kinds of data from enrollment to graduation,
including program of study, attendance record, payment of fees and examination
results to name but a few. All these data need to be made available through an
online interface.
B. A Study of Student Information Management Software
This paper [2] focuses on providing information to support the operation,
management and decision-making functions of enterprises or organizations. In the
face of huge amount of information, it is required to possess the student
information management system to improve the efficiency of student
management. Through this system, the standardized management, scientific
statistics and fast query of student information can be realized, and thus the
workload of management can be reduced. In this paper, a typical student
information management system will be established to realize the systematization,
standardization and automation of student information relationship.
C. Web Based Student Information System
This paper [3] focuses on simple interface for maintenance of student information.
The creation and management of accurate, up-to- date information regarding a
student’s academic career is critically important in the university as well as
colleges. Student information system deals with all kind of student details,
academic related reports, college details, course details, curriculum, batch details,
placement details and other resource related details too. It tracks all the details of a
5
student which can be used for all reporting purpose, tracking of attendance,
progress in the course, completed semesters, years. Different reports and Queries
can be generated based on vast options related to students, batch, course, faculty,
exams, semesters, certifications and even for the entire college.
Proposed system (student information system) feature:
 Easy to use i.e. user friendly
 Updatable and less time consuming.
 Less manpower required
 Advance search system.
 Admin with different accessibility.
 Messaging feature.
Limitations of the existing system:
 Existing solutions are slow in the terms of performance,
 Less user friendly
 Lots of paper work and also wastage of paper.
 Problem in delivering service.
 Time consuming.
6
Chapter 3: System Design
3.1 Methodology
3.1.1 Client Server Architecture
The client-server architecture refers to a system that hosts, delivers, and manages
most of the resources and services that the client requests. In this model, all
requests and services are delivered over a network, and it is also referred to as the
networking computing model or client server network.
Client-server architecture, alternatively called a client-server model, is a network
application that breaks down tasks and workloads between clients and servers that
reside on the same system or are linked by a computer network.
Client-server architecture typically features multiple users’ workstations, PCs, or
other devices, connected to a central server via an Internet connection or other
network. The client sends a request for data, and the server accepts and
accommodates the request, sending the data packets back to the user who needs
them.
Figure 1: Client Server Architecture
7
3.1.2 Software Development Life Cycle
The SDLC model is a simplified methodology for understanding the business
objectives of any systems and designing an appropriate solution that covers the
business objectives. There are many versions of life cycle, each with their own
strengths and weakness. An auditor must understand how each of these methods
affects risk. The software development life cycle is a project management
technique that divides complex projects into smaller, more easily managed
segments or phrases. Segmenting projects allows managers verify the successful
completion of project phases before allocating resources to subsequent phases.
The software development life cycle is the entire process of formal, logical steps
taken to develop a software product. SDLC refers to methodology for developing
software. It provides a consistent framework of tasks and deliverables needed to
develop systems. The SDLC methodology may be concerned to include only those
activities appropriate for particular project, whether the system is automated or
annual, whether it is a new system or an enhancement to existing systems. The
SDLC methodology tracks a project from an idea developed by the user, through a
feasibility study, system analysis, design, programming, testing, implementation
and post implementation analysis. Documentation developed during the project
development is used in future when the system is reassessed for its contribution,
modification or deletion. Software development projects typically include
initiation,
planning,
design,
development,
testing,
implementation
and
maintenance phases. However, the phases may be divided differently depending
on the organization involved. Some popular models of SDLC include the waterfall
model, the spiral model and he incremental build model.
The different stages of Software Development Life Cycle are as follows:

Initial Phase

Planning Phase

Design Phase.

Development Phase.

Testing Phase.
8

Documentation Phase.

Implementation Phase.

Maintenance Phase.
Figure 2: Incremental Model
This system is based in incremental model of software development life cycle.
The requirements are gathered first for initiating this project. Analysis is made for
different stages and modules for making a proper functionality of the system.
After making analysis the next phase of designing is implemented as front end for
making a proper user interface and easy in handling the system. As a designing of
one 12 module is completed, coding phase is started to make the system functional
and testing phase is implemented for proper working of a system and is finally
deployed for operation and maintenance. After one module is completed than
9
another module is initiated during development of this project which fulfills the
incremental model of SDLC.
The design of the student information management system includes the design of
the home page which provides the way for all the students, staff and other user to
access the system. Every user of the system has a unique username and password.
The home page mainly contains a login form through which a new user can
register, or an existing user can login to the system by entering the username and
password. The system maintains records of students, the courses and modules on
which they are registered and the outcome of their studies. The application is
distributed application because the data is stored centrally by the registration
database administer that accessed by academic staff and administrators across the
employees. Students also access the system to view their results.
3.2 Modules and their description
There are four users i.e. admin, student, teacher and parent. The accessibilities of
the respected user in different modules are given below:
•
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.
•
User Management:
This module will help the administrator in enabling/disabling a user
account and updating user information as required.
10
•
Delete items module:
This module allows the deletion of any item by the admin only.
•
View result module:
This module can be accessed by any user and allows to view student result
on website
•
View attendance module:
This module can be accessed by any user and allows to view student
attendance on website.
•
Create event module:
This module can be accessed by admin and allows to create different
events and helps in management.
System design is one of the most important stages in web development, as it
creates the baseline for what is to be created and what is its scope. System design
for software is similar to the architecture design for a building. This system will
be completely web-based application and will be developed using html, css,
bootstrap, php, and MySQL.
The purpose of project is to maintain details of the students such as storing
information about:
 Student CRN.
 Student name.
 Student password.
 Student DOB.

Student mailing address.
 Gender
 Contact no.
 Address.
 Image
11
In the current system we need to keep a number of records related to the student
and want to enter the details of the student and the marks manually. In this system
only, the teacher or the authority views the mark of the student and they want to
enter the details of the student. This is time consuming and has much cost.
3.3 DFD Diagram:
12
3.4 Use Case Diagram:
figure3:Use Case Diagram
13
3.5 ER-Diagram:
: ER Diagram
14
Administrator:
•
Login into the website
•
Update student details
•
Search student details.
•
Display student details
•
Enable/Disable student
•
Add events and routine.
•
Add subject, grades.
Student:
•
Login into the website.
•
View attendance
•
View results.
•
Events and routine.
•
Upload their images.
•
Edit their details.
•
Have the access rights to view and edit their personal details.
Teacher:
•
Login into the website.
•
View attendance
•
View results.
•
Events and routine.
•
Upload their images.
•
Do attendance
•
Add and view student marks.
Parent:
•
Login into the website.
•
View children attendance
15
•
View children results.
•
Events and routine.
•
Upload their images.
•
Edit their profile.
•
View payment details.
3.6 Experimental Tools and Setup
Following tools are used for developing our project:
DESCRIPTION
TYPE
Operating System
Windows 10
Language
HTML5, CSS3, PHP, Bootstrap
Database
XAMPP
IDE
Visual Studio Code
3.6.1 php
PHP is a general purpose scripting language especially suited to web
development. PHP is mainly used in the process of web development as primary
scripting language. It is one of the basic and fundamental scripting language in
web development sector. PHP code is usually processed on a web server by a PHP
interpreter implemented as a module, a daemon or as a Common Gateway
Interface (CGI) executable.
3.6.2 HTML &CSS
These technologies are used to build the system. PHP and HTML are used to build
the interface of the system and build the functionality of the system. CSS is used
to define styles of the system.HTML is used for making fundamental web page
where the style is given by css for attractive web page. Bootstrap is also used in
the developing process of the website.
16
3.6.3 XAMMP
XAMPP is a free and open-source cross-platform web server solution stack
package. This software is used to connect to Apache and MySQL.
3.6.4 Visual Paradigm Community Edition
Visual Paradigm Community Edition is a UML CASE Tool. This software is used
to draw the use case diagram and activity diagram.
3.6.5 Visual studio code
Visual Studio Code is a code editor redefined and optimized for building and
debugging modern web and cloud applications. Visual Studio Code, also
commonly referred to as VS Code, is a source-code editor made by Microsoft for
Windows, Linux and macOS. Features include support for debugging, syntax
highlighting, intelligent code completion, snippets, code refactoring, and
embedded Git. VS code comes with built-in support for JavaScript, TypeScript
and Node.js and has a rich ecosystem of extensions for other languages such as
C++, C#, JavaScript, python. VS code contains the extension with some code
snippets provide better experience while coding.
3.6.6 MySQL
MySQL is an open-source relational database management system (RDBMS). Its
name is a combination of "My", the name of co-founder Michael Widenius's
daughter, and "SQL", the abbreviation for Structured Query Language. A
relational database organizes data into one or more data tables in which data may
be related to each other; these relations help structure the data. SQL is a language
programmers use to create, modify and extract data from the relational database,
as well as control user access to the database. In addition to relational databases
and SQL, an RDBMS like MySQL works with an operating system to implement
a relational database in a computer's storage system, manages users, allows for
network access and facilitates testing database integrity and creation of backups.
17
Chapter 4: Implementation and discussion
This chapter will now discuss the tasks that we have implemented till now, the
technology stack we used, the complications that we faced till now, and the tasks
that will be implemented from now on.
Implementation is the stage in the project where the theoretical design is turned
into a working system and is giving confidence on the new system for the users
that it will work efficiently and effectively. It involves careful planning,
investigation of the current system and its constraints on implementation, design
of methods to achieve the changeover, an evaluation of change over methods.
Apart from planning, major task of preparing the implementation are education
and training of users. The implementation process begins with preparing a plan for
the implementation of the system. According to this plan, the activities are to be
carried out, discussions made regarding the equipment and resources and the
additional equipment has to be acquired to implement the new system. In network
backup system no additional resources are needed. Implementation is the final and
the most important phase. The most critical stage in achieving a successful new
system is giving the users confidence that the new system will work and be
effective. The system can be implemented only after through testing is done and if
it is found to be working according to the specification.
4.1 Task implemented:
Firstly, home page of the website was created using html and css. Then the html
file was converted into php file and certainly we can state that the website was
created using php and mysql. Different plugins such as sass for css, bootstrap, owl
carousel are used. The work was followed by creating login page connecting to
database. At the login page website provides features for verified users only in
order to provide a better platform for user friendly experience. With the check of
database, it redirects to the home page of the website. Some lacking sites were
discussed with the supervisor and senior personnel regarding the database
connection that included backend as well as frontend of the developing site. The
18
project starts with the concept of providing proper student information in effective
manner.
Also, admin panel has been created where the authorized admin can login through
the system. After, the successful login by admin they can:
i.
Add/delete admin.
ii.
Add/delete student, teacher and parents.
iii.
Update student information.
iv.
Assign role to admin.
v.
Manage the overall website.
4.2 Testing:
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way
to check the functionality of components, sub-assemblies, assemblies and/or a
finished product. It is the process of exercising system with the intent of ensuring
that the system meets its requirements and user expectations and does not fail in
an unacceptable manner. The testing strategies chosen for this are unit testing and
system testing. Each test type addresses a specific testing requirement.
4.2.1 Unit Testing
In unit testing, each module of the application is tested separately and
individually without the interference of the other modules. Unit testing is done
manually to find bugs and to test the functionality of the application.
19
Module-1: login
Test
Test
Pre-
Steps
Test Data
Case Objective Condition
Expected
Post-
Actual
Pass
Result
Condition Result
/Fail
Admin
Pass
ID
TC-
Verify
Admin
001
admin
should be valid
login with registered
Enter
Email-id:
admin System
@gmail.com
username Password: 12345
displays
should be Expected
admin
kept
username
with valid and
and
email and password
until
password
password.
logout.
TC-
Verify
Student
002
student
should be valid
login with provided
Enter
As
homepage logged in
Email-id:
System
Student
nikita@gmail.com
displays
should be Expected
student
kept
username
Password: 12345
valid
with valid and
username
email and password
until
and
password.
logout.
As
Pass
homepage logged in
password
TC-
Verify
Teacher
003
teacher
should be valid
login with provided
Enter
Email-id:
System
Teacher
dinesh@gmail.com
displays
should be Expected
teacher
kept
username
Password: 12345
valid
with valid and
username
email and password
until
and
password.
logout.
As
Pass
homepage logged in
password
TC-
Verify
Parent
004
parent
should be valid
login with provided
Enter
Email-id:
System
Parent
ram@gmail.com
displays
should be Expected
parent
kept
username
Password: 12345
valid
with valid and
username
email and password
until
and
password.
logout.
password
20
homepage logged in
As
Pass
TC-
Verify
User
is Enter
Email-id:
Display
005
user login not
valid
with
registered
username Password: user1234
invalid
with valid and
login
username
email and password
failed.
and
password.
newuser@gmail.com error
message
Redirect
to
As
Pass
login Expected
page.
password
Table 1: Login Module Testing
Module-2: add new student
Test
Test
Pre-
Steps
Test Data
Case Objective Conditio
ID
Expected
Post-
Actual
Pass
Result
Conditio
Result
/Fail
pass
n
n
TC-
Add new
Admin
Enter
Crn:311, full
Display
Select
As
001
student
mustbe
valid
name: jeshik
grade and
grade and
expected
logged
CRN, full
phuyal, name with
subject
subject to
in.
name,
initials:jp,
adding
add new
address
address:mulpani,
page.
student.
,gender,
DOB,
photo,
contacts,email of
both
student
and
guardian.
Contacts:9840177
407,
email:jeshik@gma
il.com, gname:jay
phuyal, name with
initials:jayp,
address:mulpani,
Contacts:9841365
516,
email:jay@gmail.
com, gender: male
and photo
21
TC-
Add
Admin
Enter
email:
Invalid
Red edges
As
002
invalid
must be
invalid e-
jeshik@lgdail.com
email
around
expected
email in
logged in
mail id .
address
email
new
label and
student.
could not
Pass
add
student
TC-
Add
Admin
Enter
Contacts :
Invalid
Red edges
As
003
invalid
must be
invalid
9812314341414
phone
around
expected
phone no.
logged in
phone no.
format.
phone
in new
label and
student.
could not
Pass
add
student
Table 2: add new student
Module-3: add attendance
Test
Test
Case Objective
Pre-
Steps
Test Data
Condition
Expected
Post-
Actual
Pass
Result
Condition
Result
/Fail
Your
Attendance As
ID
TC-
Verify
Teacher
001
attendance must
Click
on CRN : 311
be attendance.
information is
logged in
has
and
updated.
student
must
Pass
taken Expected
been and
teacher
remains in
be
same page
valid.
for another
attendance.
TC-
Add
Teacher
Click
002
previously
must
updated
logged in
on CRN: 311
be attendance.
Your
Attendance As
information is not done Expected
has already and
attendance and
been
22
teacher
Pass
again.
student
must
updated
be
remains in
same page
valid.
for another
attendance.
TC-
Verify
Teacher
003
invalid
must
Click
on CRN: 340
be attendance.
Attendance As
is not done Expected
attendance logged in
and
and
teacher
student
remains in
mustn’t be
same page
valid.
for another
attendance.
Table 3: add attendance
4.2.2 System Testing:
System testing, also referred to as system-level tests or system-integration testing,
is the process in which a quality assurance (QA) team evaluates how the various
components of an application interact together in the full, integrated system or
23
Pass
application. In this testing we checked if the functional requirement of the system
were met or not. This testing is done after the completion of unit testing. Once this
is done, the system as a whole was tested to ensure that the system is functioning
correctly and efficiently. This test is very helpful to determine the problems and
bugs that have been escaped during the unit testing. If any problems are found,
then they are eliminated during this testing.
Test
Test Objective
Case
Test
Test Data
Expected
Actual
Result
Output
Valid
Successful
Successful
provided
username
Login
Login
username
and
and
password
Steps
Remarks
ID
TC-
Verify
001
of Admin
Login Enter
No Error
password
TC-
Verify
002
student
add click on Enter details Successfully
add
Successful
of student
added
display
Valid
Successfully
Successfully
updated
updated
Subject
Subject
added
added
No Error
student
TC-
Delete/Modify
Remove
003
student
or modify information
No Error
student
details
TC-
Verify subject
004
Enter
Grade: 018
grade and
subject.
No Error
Subject:
O&M
TC-
Verify
005
teacher
add click on Enter details Successfully
add
of student
student
24
added
Successful
display
No Error
TC-
Verify Search
006
Enter all Enter valid Successful
Display
student
student
student
name
Search
or
No Error
details
CRN no.
TC-
Verify
Click on Enter CRN Successful
Your
007
attendance
add
information
TC008
Verify result
no.
attendance
attendanc
has
e
updated
Click on Select exam Successful
Display
exam and type
results
No Error
been
No Error
select
grade
Table 4: System Testing
4.3 Output Obtained
With the help of different websites and references, the project is expected to be
completed. By login into the web page different tasks such as attendance history,
subject routing, event information, student details, result history can be obtained.
Parents and teachers can have a conversation via message to find the information
about the student. Student can evaluate their progress report and attendance.
Different events and schedules are easily access-able and are managed by admin.
25
Chapter 5: Analysis and evaluation
5.1 Analysis of output obtained
The obtained output is most probably the same as expected output in proposal.
26
5.2 Evaluation of project
Evaluation is a systematic method for collecting, analyzing, and using information
to answer questions about projects particularly about their effectiveness and
efficiency. These steps are repeated to ensure that processes followed in the
project are evaluated and improved on a periodic basis.
i.
Plan: Plan and establish the process related objectives and determine the
processes that are required to deliver a high-quality end product.
ii.
Do: Development and testing of processes and also "do" changes in the
processes.
iii.
Check: Monitoring of processes, modify the processes, and check whether
it meets the predetermined objectives
iv.
Act: Implement actions that are necessary to achieve improvements in the
processes
The project is still under development till this date. And some features could be
added to the system to make it more practical. During the course of the time while
developing the system, the analysis was performed at the early phase where the
output was expected. But while developing the system, with lot of study and
research, a lot of modification and changes were made which made the system
output slightly deviated by the expressions.
Chapter 6: Conclusion and future works
The student management system is a powerful tool that can revolutionize the way
educational institutions manage student-related administrative tasks. By
automating processes, improving communication, and providing real-time access
to critical information, an SMS can greatly enhance the efficiency and
effectiveness of educational institutions. However, it is important to carefully
27
consider the challenges and plan for proper implementation and ongoing support
to ensure the successful integration of an SMS into an educational institution's
infrastructure.
Student information systems make faculty jobs more accessible by giving them an
easy place to find and sort information. This system allows teachers and student
managers to follow with their student engagement. Our project is only a humble
venture to satisfy the needs in an institution. This project shall prove to be a
powerful package in satisfying all the requirements of the organization.
This system saves the time of the student and of the administrator. It includes
processes like registration of the student's details, assigning the department based
on their course, and maintenance of the record. This system reduces the cost and
workforce required for this job.
6.1 Future work
The following section discusses the work that will be implemented with future
release of website:
1. Releasing in live server: This project could be fruitful if it could be run in live
server
REFERENCES
[1] AlmahdiAlshareef, Ahmed Alkilany "Toward a Student Information System
for Sebha University, Libya",Fifth international conference on Innovative
Computing Technology (INTECH 2015)-p 34-39.
[2] Prabhu T Kannan, Srividya K Bansal,"Unimate: A Student Information
System",2013 International Conference on Advances in Computing,
Communications and Informatics (ICACCI)-p-1251-1256.
28
[3] S.R.Bharamagoudar, Geeta R.B, S.G.Totad, “Web service api for student
information and course management systems”International Journal of Advanced
Research in Computer and Communication Engineering Vol. June 2013.
29
Appendices
•
Admin module:
Responsible for managing student records, login into the website, update
student details, search student details, display student details.
•
Student module:
Students are the users and they can view their attendance history, grade
marks, can have a conversation with teachers via msg.
•
Teacher module:
Teachers are also the users and they can do student attendance, upgrade
grade marks, can have a conversation with students via msg.
•
Parents module:
Parents are responsible to view their children academics result and
attendance history, can look payment history.
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44