A

PROJECT REPORT
ON

“Student Result Management System”

In the fulfillment of the Requirement for the Degree of

Master of Computer Application (M.C.A.)

Submitted By
Vishal Bangale

Guided By
“Prof. Karishma Chaudhari”

To

G. H. Raisoni Institute of Engineering and Management, Jalgaon

Affiliated To

Kavayitri Bahinabai Chaudhari, North Maharashtra University,

Jalgaon

2024-2025

1
G. H. Raisoni College of Engineering and Management, Jalgaon

Department of Computer Applications

CERTIFICATE

This is to certified that,

Mr./Ms. .

Examination Seat No. a student of MCA

Semester : has satisfactorily performed the
project in the course of

during the academic year 2024-25.

Date : / /

Project Guide Head of Dept.

Examined By-

Examiner I Examiner

2
 ACKNOWLEDGEMENT
A successful project is the result of a good team-work which consists of not
only the partners who put in their long and hard work but also those who guided
them. Indeed, a true saying.

I would like to thank “Eclerx Services. Ltd, Pune” for giving me

an opportunity to work with them and for providing me all the requisite support.

I would like to thanks to Hon. “Dr. Preeti Agrawal” and Hon. HOD “Mrs.
Kalyani Neve” and our Project guide “Prof. Karishma chaudhari” all my college
Faculty members for providing me with valuable support and guiding me throughout
my college days.

I would like to thank my family and friends for being so supportive and
generous to me throughout my learning days.

Thanks and Regards,

“Vishal K. Bangale”

3
 DECLARATION

I,Vishal Kishor Bangale,hereby declare that the project report titled "Student
Result Management System " submitted as a partial fulfillment of the requirements for
the MCA degree, is a result of my original work and has not been submitted in part or
in full for any other degree or diploma.

I confirm that all the information and data presented in this report are authentic
and accurate to the best of my knowledge. Any external sources used in the report have
been duly cited and acknowledged.

I declare that the project was undertaken in accordance with the guidelines and
regulations set forth by the academic institution. The methodologies, techniques, and
tools employed during the development of the Secondment Process Approval system
have been appropriately referenced.

I take full responsibility for the contents of this report and any errors or
omissions it may contain. I understand that any act of plagiarism or academic
dishonesty is a serious offense and may result in severe consequences.

Furthermore, I declare that all the contributions made by individuals,

organizations, or resources that have aided me in the completion of this project have
been duly acknowledged in the acknowledgments section of this report.

I affirm that I have gained valuable knowledge and skills through this project,
and I am ready to defend and discuss the contents and findings presented in this report,
if required.

Visahl K. Bangale
Student of MCA SEM IV
GHRCEM, Jalgaon

4
 Apprenticeship Offer cum Appointment Letter
Date: Jan 13,2025

Candidate Name: Mr. Vishal Bangale

Candidate ID: 4640447 Address: S/O Kishore Sahebrao Bangale,Balad Road Badhgaon,, Shiv
Colony, Bhadhgaon, Jalgaon-424105, Maharshtra, India

Dear Vishal,

Congratulations!!!

We are extremely pleased to extend a warm welcome to you from the eClerx family, under the
Apprenticeship program. Your designation under the Digital Vertical would be an Analyst.Your functional
title will be "Analyst". We wish you a successful and professionally enriching experience with us.

Please find attached the additional terms and conditions under the Program which is to be treated as an
integral part of your Apprenticeship contract (hereinafter referred to as "Contract"). Please return a duly
signed duplicate copy of this letter for our records. Your HR Business Partner will soon reach out to you for
an introduction. Should you have any queries or concerns, they will be glad to assist you. Once again, we
welcome you to eClerx. We look forward to a long, fruitful, happy, and exciting association with you .

Regards

Offered By: Sagar Shetty

Designation: Program Manager– Human Resources
Date: Jan 13,2025

Dear Vishal,

We are pleased to appoint you as Analyst under the Apprenticeship program. Your training with us will
commence on "Jan 14,2025" and will continue until "Jun 13,2025".

Apart from the other policies binding upon you during your tenure with the company, the general terms and
conditions under the Program are as follows:

1. Work Location

1.1. Your initial work location will be Pune. Though you have been engaged for a specific position
and location, the Company reserves the right to transfer you, with reasonable notice, to any other
location, department, establishment, or branch of the Company / group / affiliates as the Company
may deem fit including new locations to be set up in future. You shall be bound by the policies, rules
and regulations of the office at the location you are posted in at any given point in time.
 INDEX

Chapter Sr. No Topics Page No

1 Introduction 8
1.1 Key Features 7
2 Need 9
2.1 Efficiency 9
2.2 Customization 9
3 Objectives 10
3.1 Make Grading Easier 10
3.2 Keep Student Data Safe 10
4 Scope Of Project 11
4.1 Recording Grades 11
4.2 Access Control 11
5 Technology Proposed for Project 12
5.1 Software Requirement 12
5.2 Hardware Requirement 12
6 Feasibility Study 13
6.1 Recognition of need 13
7 Case Tools 14
7.1 Technical Feasibility 14
8 Data Flow Diagram 15
9 Entity Relationship Diagram 17
10 Testing Tools 20
11 Onscreen Views 22
12 Limitation 30
13 Conclusion 31
14 User Manual 32
15 Reference 33

7
 1. INTRODUCATION

In the realm of educational institutions, managing and

tracking student results is an essential yet often challenging task. As
academic environments become increasingly complex and data-
driven, the need for efficient, accurate, and user-friendly systems to
manage student results has never been greater. Introducing the
Student Result Management System (SRMS) - a comprehensive
solution designed to streamline the process of recording, analyzing,
and communicating student academic performance.

The SRMS is a web-based application developed to cater to

the specific needs of educational institutions, ranging from schools to
universities. Its primary objective is to simplify the often cumbersome
and time-consuming tasks associated with result management,
allowing educators to focus more on enhancing teaching quality and
student learning outcomes.

Key Features:

 User-friendly Interface: The SRMS boasts an intuitive user

interface, ensuring ease of use for administrators, teachers, and
students alike. With its simple navigation and clean design, users
can quickly access relevant information and perform necessary
tasks without extensive training.

 Centralized Data Management: Gone are the days of scattered

spreadsheets and paper-based records. The SRMS centralizes all
student-related data, including examination results, attendance
records, and grading criteria, within a secure digital platform.
This centralized approach facilitates efficient data retrieval,
analysis, and reporting, leading to informed decision-making by
educators and administrators.

 Customizable Grading System: Recognizing the diverse

assessment methods employed across different educational
 contexts, the SRMS offers customizable grading systems.
Whether institutions follow a traditional letter-grade system or a
competency-based approach, the SRMS can adapt to
accommodate various grading schemes, ensuring flexibility and
alignment with institutional policies.

 Real-time Result Updates: Timely feedback is crucial for both

students and educators. The SRMS enables real-time result
updates, allowing students to access their grades promptly and
providing teachers with instant insights into student performance.
This instantaneous feedback loop fosters transparency,
accountability, and continuous improvement in the learning
process.
 2. NEED

Needs:
The need for a Student Result Management System (SRMS) arises from
various challenges and requirements within educational institutions:

 Efficiency: It saves time and effort by automating tasks like recording

grades and generating reports, freeing up educators to focus more on
teaching.

 Accuracy: By digitizing records, it reduces errors that can occur with

manual data entry, ensuring that student grades are recorded accurately.

 Transparency: It provides easy access to grades for students, parents, and

teachers, fostering transparency and accountability in the assessment
process.

 Customization: It can be tailored to suit the grading systems and reporting

needs of different institutions, making it adaptable and flexible.

 Insights: It helps educators analyze student performance trends and

identify areas where additional support may be needed, allowing for
targeted interventions to improve learning outcomes.

 Communication: It facilitates communication between teachers, students,

and parents by allowing for the sharing of feedback and progress reports in
a timely manner.

 Compliance and Security: It ensures that student data is securely stored

and managed in accordance with privacy regulations, protecting sensitive
information from unauthorized access or loss.
 3. OBJECTIVES

Objectives of project:

The main goals of a Student Result Management System (SRMS) in

simple terms are:

 Make Grading Easier: To simplify the process of recording and managing

student grades, saving time for teachers and staff.

 Ensure Grades are Correct: To reduce mistakes in grading by using

digital records instead of manual paperwork.

 Keep Everyone Informed: To let students, parents, and teachers easily

access grades and feedback, fostering transparency and accountability.

 Adapt to Different Systems: To work with various grading methods used

by different schools, being flexible to their needs.

 Help Teachers Understand Student Performance: To provide tools for

educators to analyze student data, helping them see trends and areas where
students might need extra support.

 Improve Communication: To enable quick and easy communication

between teachers, students, and parents about grades and progress.

 Keep Student Data Safe: To ensure that student information is kept secure
and private, following rules and regulations for data protection.

In essence, an SRMS aims to simplify grading, ensure accuracy, keep

everyone informed, adapt to different systems, help teachers understand
performance, improve communication, and keep student data safe.
 4. SCOPE OF PROJECT

The scope of a Student Result Management System (SRMS) project

refers to what the system will cover and what it aims to achieve. In simple
terms, the scope includes:

 Recording Grades: The system will allow teachers to enter and store
student grades for various assignments, exams, and activities.

 Managing Student Information: It will keep track of basic student

details such as names, IDs, and classes, ensuring accurate records.

 Generating Reports: The system will be able to produce reports

summarizing student performance, both for individual students and
classes as a whole.

 Access Control: It will ensure that only authorized users, such as

teachers and administrators, can view and modify student data.

 User Interface: The system will have an easy-to-use interface for

teachers to input grades, students to view their results, and administrators
to manage the system.

 Security: The system will prioritize keeping student data safe from
unauthorized access or tampering.

 Support and Maintenance: The project scope may include provisions

for ongoing support and maintenance to ensure the system continues to
function smoothly after implementation.
5. TECHNOLOGY PROPOSED FOR PROJECT

HARDWARE AND SOFTWARE REQUIREMENT

A major element in building system is selection of compatible

hardware & software. Hardware selection they begin with requirements analysis
following by a request for proposal, evaluation & validation, post installation
review.

While selecting the software various criteria is considered such as

reliability (gives consistent results), functionality (function to standards),
capacity (satisfies volume requirements), flexibility (adapts to changing needs),
usability (user friendly), security (to prevent unauthorized access), performance
(capacity to deliver as expected), serviceability (good documentation), minimal
cost (affordable for intended application).

• Software Requirement:
1. Operating System Windows 7,8,10,11

2. PHP v5.6, 7.4,8.2.0

3. MySQL

4. XAMPP v3.2.3

• Hardware Requirement:
1. I3 Processor

2. Minimum 2GB RAM.

3. Minimum 40 GB HDD.

4. Input Devices: Keyboard, Mouse.

 6. FEASIBILITY STUDY

At the time of the development we have gone through the following phases:

Recognition of need (Requirement specification):

It refers to the organization’s needs, requirements and expectations from
the project to be developed. After recognizing the organization’s need, it has been
taken in writing and then a rough idea of the system/project has been given to the
firm.

1. Feasibility Study:
It is always essential to evaluate the various aspects before we develop the
project. Evaluation should always justify the cost and benefits ratio. Economic,
social and technical feasibility of project is analyzed.

2. Data Collection:
Here comes an important aspect of project development i.e. data collection. For
this to accomplish, we observe registers, bills, invoices and order forms at
client’s firm.

3. Data Normalization:
Normalization means allowing only a single value in a table’s row and column
intersection. For this, entities are identified from the data collected and
normalized tables with appropriate relationship and minimized redundancy are
designed.

4. System Design:
This step includes drawing of different diagrams such as DFD and ERD. It
includes database design, form design etc.

5. Coding:
It is the most critical stage among all the stages of development. It has taken
approximately seven days to complete. It involves giving functioning to data
entry forms with the help of action, validation, calculations and linking of
different data entry forms.

6. Testing:
It involves testing of the working of the project.

7. Implementation:
This involves deployment of project to client side.
 7. CASE TOOLS
It is always essential to evaluate the various aspects before we develop a system.
Evaluation should always justify the cost and benefits ratio. If it is found that
benefits are less as compare to the cost of project, then it is better to avoid going
in for computerization.
The key consideration involved in the Feasibility analysis is:
1. Technical Feasibility.
2. Economical Feasibility.
3. Social Feasibility.

1. Technical Feasibility:
For this project technical feasibility should be studied in two aspects i.e.
Hardware feasibility and software feasibility. The system should be easy to
update i.e. if the user wants to made some changes in the system then it should
be easy for him to change without disturbing the initial system. It should be
develop in such a way that it will easy to operate.
It should be menu driven and provide help features and give message on each
option so it should be easy to even novice to operate the package. Few hours
training is sufficient to train the operator.

2. Economical feasibility:
Cost benefit analysis gives justification for the computerization. In this the
benefits and savings that are expected are comparing with costs. If benefits
overweigh cost then only the decision is made to design and implement the
system. In our case, computerization results reduction of cost, reduction of staff
and reduction and of non-reusable stationary. The computer stationary will
replace various types of bills and registers. However the overall effect on the
operating cost is that we get substantial reduction in monthly running cost. Cost
will reduce also in terms of reduction in expenses for space and computers
required.

3. Social Feasibility:
Operating with records in both situations i.e. in manual system and
computerized system is quite different. Manual system is always disliked because
of the complications and other hustle involved in maintaining the records.
Computerization will be welcomed because of the simplicity in the data entry and
fastest and easy way of getting outputs. After computerization it will become the
job of single operator with no risk involved in posting and report generation.
Speed of the operation will also increase substantially and hence reporting service
to patient will be faster. Hence all welcomes computerization.
 Data Flow Diagram (DFD)

 Data flow diagram is graphical tool which is used to describe and analyze
the movement of data through a system. They focus on the data flowing
into the system, between processes and in & out of data stores.
 DFD is a graphical technique that detects information flow and
transformation that are applied as data move from input and output.
 DFD is a central tool and the basis from which other components are
developed.
 DFD provides mechanism for a final modeling as well as information flow
modeling.
 DFD has very simple notation which are easily understood by the users &
those who involved in the system.

Symbol used for DFD

Symbol Meaning

External Entity as source

Destination.

Process or Function.

Indicates the direction of data

flow

File Storage i.e. data is

Stored for use by one or
more.
 Data Flow Diagram

Check Result Student

For Student Classes

Dashboard Subject
Creation
Student Result
Management
System
Class Admin
Change

Password

Enter Your Student

Roll Result Admission
ID+++++++++
++++++++++
++++++++++
++++++++++
++
 Entity Relationship Diagram

An ER-Diagram can express the overall logical structure of a database

graphically. The Entity Relationship Diagram enable a software engineer to fully
specify the data objects that are input from a system, the attributes that define the
properties of these objects and the relationship between the objects.

o The ER model is one of the several semantic data models; the

semantic aspect of the model lies in the attempt to represent meaning
of the data.

o The ER model is extremely useful in mapping the meaning and

interaction of real world enterprise into a conceptual schema.

o It is notable point that concept of ERD is totally different from DFD.

The ER-Diagram is used to describe the logical organization of data.

There are following four type of relationships diagram between entities given as
follows:

1. One to One
2. One to Many
3. Many to One
4. Many to Many
 Symbol used for ERD

Symbol Meaning

Entity

Attribute

Relationship

Links
 Entity Relationship Diagram
Start

Check Result Admin Login

Enter Class Username Password

Your ID

Dash
RMD Display board

Create
Student Class

Forgot Logout
Password

Class name Class name Section

in Numeric
Current New Confirm
Subject Password Password Password
Creation

Add Sub
Combination

Subject Subject
Name Code
Student
Admission

Full Name Roll ID Email ID Class DOB Gender

Declare
Result

Class Subject
Student Name
 8. TESTING TOOLS

Testing is important from the point of view of accurate functioning of the

project. There are many testing measures and tools available to test a project.
Basic tools used to test this project are:

1. Black Box Testing.

2.White Box Testing

3. GUI Testing

1. Black Box Testing:

It is a method of software testing that tests the functionality of an
application as opposed to its internal structures or workings. Specific knowledge
of the application’s code/internal structure and programming language in general
is not required. The tester is only aware of what the software is supposed to do,
but not how i.e. when he enters a certain input, he gets certain output; without
being aware of how the output was produced. Tests cases are build around
specifications and requirements, i.e., what the application is supposed to do. It
uses external descriptions of the software, including specifications, requirements
and designs to derive test cases. These test designer select valid and invalid inputs
and determine the correct output. There is knowledge of the test object’s internal
structure.
This method of test can be applied to all levels of software testing: Unit,
Integration, System and Acceptance. It typically comprises most if not all testing
at higher levels, but can also dominate unit testing as well.

The advantages of this type of testing include:

 The test is unbiased because the designer and the tester are independent of
each other.
 The tester does not need knowledge of any specific programming
languages.
 The test is done from the point of view of the user, not designer.

The disadvantages of this type of testing include:

 The case can be redundant if the software designer has already run a test
case.
 The test cases are difficult to design.
 2. White Box Testing:
White box testing is a method of testing software that tests internal
structures or workings of an application, as opposed to its functionality. In white-
box testing an internal perspective of the system, as well as programming skills,
are required and used to design the test cases. The tester chooses input to exercise
paths through the code and determine the appropriate outputs. While white-box
testing can be applied at the unit, integration and system levels of the software
testing process, it is usually done at unit level. It can test paths within a unit, paths
between units during integration, and between subsystems during a system level
test. Though this method of test design can uncover many errors or problems, it
might not detect unimplemented parts of the specification or missing
requirements.

White-Box test design techniques include:

 Control flow Testing
 Data flow Testing
 Branch Testing
 Path Testing
For a complete software examination, both white box and black box tests are
required.

3. Graphical User Interface Testing:

It is the process of testing a product’s graphical user interface to ensure it meets
its written specifications. This is normally done through the use of a variety of
test cases. It checks only the user friendliness. The creation of the user interface
is less time consuming for the user but more complex for the programmer. It must
be tested for its sole purpose.

This test must be carried out to ensure:

 Windows open properly.
 All data contents are properly addressable.
 All the graphical elements are available and displayed.
Multiple or incorrect mouse click do not produce side effects
9. Onscreen Views

Login Page

Dashboard Page
 Dashboard Page

Create Student Class

 Manage Class

Subject Creation
 Manage Subject

Add Subject Combination

Manage Subjects Combination

Student Admission
Manage Students

Declare Result
 Manage Students

Admin Change Password

Check Result

Display Result
 10. LIMITATION

Here are the limitations of a Student Result Management System (SRMS)

in simple terms:

 Technical Glitches: Sometimes, the system might have technical

problems like crashing or running slowly, disrupting access to student
data.

 Initial Costs: Setting up the system can be expensive, including the cost
of software, hardware, and training, which may be a challenge for schools
with limited budgets.

 Training Needed: Teachers and staff may need training to use the
system effectively, and some might resist or find it difficult to adapt to
the new technology.

 Security Concerns: Storing student data digitally raises concerns about

keeping it safe from unauthorized access or cyber attacks.

 Integration Challenges: Integrating the SRMS with other school

systems, like attendance or learning management, may be complex and
time-consuming.

 Risk of Data Loss: Despite backups, there's always a risk of losing data
due to technical failures or human error.

 Accessibility: Ensuring all students, including those with disabilities or

limited internet access, can use the system equally may require additional
measures.
 11. CONCLUSION

The Student Result Management System project aims to

revolutionize the way educational institutions manage and analyze
student performance data. By leveraging technology to automate
processes, enhance transparency, and provide actionable insights, the
SRMS will empower educators, students, and parents to collaborate
effectively in supporting academic excellence and student success.

The project provides the user friendly interface for the admin
to manage the data and generate reports. The project allows the admin
to add new student, enter their exam scores, and generate reports based
on various criteria.

Overall, the Student Result Management System project is an

efficient and effective way to analyze data and generate in insights for
better decision-making in educational institutions.
 12. USER MANUAL

USER REQUIREMENTS:
Every user interacts with the system with some needs and requirement such as:-
1. Basic knowledge of computer should be required.
2. Comprehensive information accessing and retrieving so as to provide
valuable report and figures.
3. Data security and priority is not to be ignored.
4. At the time of generating the reports, where the corresponding reports are to
be set in the computerized system.
5. Every user must know the function of each Master entry, Transaction entry
and Reports.
6. The format, field within a format, data types, what type of data is to be
entered, what is the maximum size of each entry module. The user must know
each thing.
7. In short, operating environment about the computerized “Bags Shop” must
be familiar to the user.
8. Every Text Box should be filled with Data .If data is not available put at list
‘.’(DOT) for character, as well as for numeric data’0’ (ZERO) should be
placed.
 13. REFERENCES

Books:
1. S.K. Jain
2.U. Joshi, and B. K. Sharma
3.Attendance Management System
4.Masters Project Report

Websites:
1. https://www.researchgate.net/
2. www.w3schools.com
3. https://codeastro.com/
4. https://www.mysql.com/
5.https://www.php.net/