STUDENT

RESULT
MANAGEMENT
SYSTEM
 PROJECT REPORT
ON
“STUDENT RESULT MANAGEMENT
SYSTEM”
Submitted in partial fulfillment for the

Award of degree of

Bachelor of Technology in Computer Science & Engineering

Submitted by:-
Kamna Gupta

GU15R0111

Submitted to:-
Head of Department Project Guide

Dr. Mazhar Afzal Mr. Arif Ali Wani

 CERTIFICATE

Certified that this is a bonafide record of the project work titled

STUDENT RESULT MANAGEMENT SYSTEM

Done by

KAMNA GUPTA
of VII semester Computer Science & Engineering in the year 2018 in partial fulfillment
of the requirements for the award of Degree of Bachelor of Technology in Computer
Science & Engineering from The Glocal University ,Mirzapur Pole ,Saharanpur.

Head of Department Project Guide

Dr. Mazhar Afzal Mr. Arif Ali Wani
 ACKNOWLEDGEMENT

We take this occasion to thank God, almighty for blessing us with his grace

and taking our endeavor to a successful culmination. We extend our sincere and

heartfelt thanks to our esteemed guide, Mr. Arif Ali Wani, for providing us with

the right guidance and advice at the crucial junctures and for showing me the

right way. We extend our sincere thanks to our respected Head of the

Department Dr. Mazhar Afzal, for allowing us to use the facilities available. We

would like to thank the other faculty members also, at this occasion. Last but not

the least, we would like to thank our friends and family for the support and

encouragement they have given us during the course of our work.

HOD Signature Project Guide Signature

------------------------- -------------------------------
 TABLE OF CONTENTS
1. Introduction

1.1. Purpose

1.2. Key features

2. Software and Hardware Specifications

2.1. Software requirements

2.2. Hardware requirements

3. Literature survey

3.1. Introduction

3.2. Software evolution

4. Software requirements Analysis

4.1. Scope

4.1.1. Existing system with limitations

4.1.2. Proposed system features

4.2. Administrator module

4.3. Student module

5. Use case model

6. Snapshots

7. Conclusion

7.1. Future enhancements

 7.2. References

1. INTRODUCTION

An individual report card of each student has to be displayed and printed at a keystroke
according to any selected format. An important aid for teachers and students to judge their
performance. Merit list printing by totals for a class by individual subject marks for a class.
Student performance in a particular subject or all the subjects must be expressed.
Performance of teachers of various classes can be easily compared.

1.1 Purpose

The system displays the list of all issues that are open, closed, in progress. If the user can get
registered by clicking on the logon button and provide the required information as specified.
Each time the registered customer come on to the site he can makes use of the user name and
the password that is allocated to him.

1.2 Key features

 Admin panel to add entries in every database

 Student entry to get the results
 Class can be added
 Results can be managed
 Admin can block the user
 Report card can be generated in pdf format.
2. SOFTWARE AND HARDWARE SPECIFICATIONS

2.1 Software requirements

Language Used : PHP

Database : My SQL

User Interface Design : HTML, AJAX, JQUERY, JAVASCRIPT

Web Browser : Mozilla, Google Chrome, IE8,OPERA

Software : XAMPP Server

2.2 Hardware requirements

Processor : Standard processor with a speed of 1.6 GHz or more

RAM : 256 MB RAM or more

Hard Disk : 20 GB or more

Monitor : Standard color monitor

Keyboard : Standard keyboard

Mouse : Standard mouse

3.LITERATURE SURVEY

3.1 Introduction
PHP is currently one of the most popular programming languages, widely used in both the open

source community and in industry to build large web-focused applications and application

frameworks. [1] Eshkevar, Dos Santos, Cordy, & Antoniol also add that PHP is by far the most

popular WEB scripting language, accounting for more than 80% of existing websites. However,

Scripting languages such as PHP have been criticized as inadequate for supporting maintenance

of largescale software projects. [2] Kyriakakis & Chatzigeorgiou attempt to provide insight into

the way that PHP applications evolved over time. They examined several aspects of their history

including the amount of unused code, the removal of functions, the use of libraries, the stability

of their interfaces, the migration to object-orientation and the evolution of complexity. This

evolution is brought about because a web application (Build in PHP) evolve, new versions of

programs, interactions and functionalities are added and existing ones are removed or modified.

Web applications require configuration and programming attention to assure security,

confidentiality, and trustiness of the published in for28 http://www.i-jes.org Paper—Evolution of

PHP Applications: A Systematic Literature Review mation. During evolution of Web software,

from one version to the next one, security flaws may be introduced, corrected, or ignored. [3]

This paper also takes into consideration that PHP is dynamically typed, which means that

variables take on the type of the objects that they are assigned, and may change type as execution
proceeds. While some type changes are likely not harmful, others involving function calls and

global variables may be more difficult to understand and the source of many bugs.

3.2 Software Evolution

Software evolution deals with the process by which programs are modified and adapted to their

changing environment. The aim of Lehman’s research was to formulate a scientific theory of

software evolution. As any sound theory, it was meant to be based on empirical results and

aimed at finding invariant properties to be observed on entire classes of software development

projects. [5] Software evolution is also a crucial ingredient of so-called agile software

development processes, of which extreme programming (XP) is probably the most famous

proponent. In brief, agile software development is a lightweight iterative and incremental

(evolutionary) approach to software development that is performed in a highly collaborative

manner and explicitly accommodates the changing needs of its stakeholders, even late in the

development cycle, because this offers a considerable competitive advantage for the customer. In

many ways, agile methods constitute a return to iterative and incremental development as

practiced early in the history of software development, before the widespread use of the waterfall

model. [6] Mens & Demeyer go on to say, today software evolution has become a very active

and well-respected field of research in software engineering, and the terms software evolution

and software maintenance are often used as synonyms. For example, the international ISO/IEC

14764 standard for software maintenance, acknowledges the importance of pre-delivery aspects

of maintenance such as planning.

4. SOFTWARE REQUIREMENTS ANALYSIS

Requirement analysis for web applications encompasses three major tasks: formulation,
requirements gathering and analysis modeling. During formulation, the basic motivation and
goals for the web application are identified, and the categories of users are defined. In the
requirements gathering phase, the content and functional requirements are listed and interaction
scenarios written from end-user’s point-of-view are developed. This intent is to establish a basic
understanding of why the web application is built, who will use it, and what problems it will
solve for its users.

4.1 Scope

4.1.1 Existing System with Limitations

 It is time consuming process as the user has to type the dbase commands. He has to
remember all the commands which are difficult.
 It is limited to a single system.
 A user who wants only to have some information has to contact the administrator every
time.

4.1.2 Proposed System Features

 User friendliness is provided in the application with various controls.

 The system makes the overall project management much easier and flexible.

 It can be accessed over the internet.

 Vast amount of data can be stored.

  There is no risk of data mismanagement at any level while the project development is
under process.

 Relationship between the administrator, owner/developer and subcontractor can be

maintained very easily.

 It provides high level of security using different protocols like https etc.

The Student Result Processing consists of 3 users or modules, they are:

 Administrator

 Student

4.2 Administrator Module

The functionalities of Administrator are

1. The Administrator should Login into the system with unique his/her username and
password.

2. If the username and password is valid then he can gain the access to the system.

3. Admin views student Personal details.

4. Admin updates student Personal details.
5. Admin views his/her own Personal details.
6. Admin updates his/her Personal details.
7. Admin views details of students.
8. Admin updates details of students
9. Admin views Results of students.
10. Admin updates Results of students.
11. Admin views Schedules.
12. Admin updates Schedules.
13. Admin sends emails to students once marks have been entered.
The Administrator can do the following actions

1. Login

2. Admin Actions

1. Views personal details

2. updates details

3. views reports

4. updates results of students

3. Logout

4. Change password

4.3 Student Module

The functionalities of Student are

1. Student views Results.

2. Student views Schedules

The Student can do the following actions:

1. Login

2. Student Actions

1. views results

2. View Schedules
 2. Log out

5. USE CASE MODEL

Admin use case

Add/remove
student

View student
information

Update student
information
Student use case

View results

Search results

Download
report
6.Snapshots

Admin Dashboard
Admin can manage all the information and details of the students and the results. There are
various panels for admin to manage the system accordingly.
Registered users will be displayed like this. Only the admin can view this. And, admin can
add/remove students as per requirements.
Admin can manage subjects like this. Admin has the right to manage, add or remove any subject
from the database.

The subject code and creation date will also be displayed.

Admin can manage classes like this. Admin has the right to manage, add or remove any class
from the database as well as from the result management system.

The class name, section and creation date will also be displayed.
Admin can create student class like this. Admin has the right to manage, add or remove any class
from the database as well as from the result management system.

The class name, section and creation date will also be created by the administrator.
Admin can create subject like this. Admin has the right to manage, add or remove any subject
from the database as well as from the result management system.

The subject name, subject code will also be created by the administrator.
Admin can create subject with combination like this. Admin has the right to manage, add or
remove any subject from the database as well as from the result management system.

The subject name, and class will also be created by the administrator. It can also be managed
separately.
Admin can admit students in Student Result Management System like this. Admin has the right
to manage, add or remove any student from the database as well as from the result management
system.

The details of the student will be added by the administrator.

Admin can declare results like this. Admin has the right to manage, add or remove any result
from the database as well as from the result management system.

The result of a particular student along with the class and student name and subjects will be
added by the administrator.
Admin can view results like this. Admin has the right to manage, add or remove any result from
the database as well as from the result management system.

The result of a particular student along with the class and student name and subjects will be
added by the administrator.
7.CONCLUSION
From a proper analysis of positive points and constraints on the component, it can be safely
concluded that the product is a highly efficient GUI based component. This application is
working properly and meeting to all user requirements. This component can be easily plugged in
many other systems.

7.1 FUTURE ENHANCEMENTS

Now the developed System is a web based system, it gives all the student details. In the future
the results can be directly printed, and this functionality can be made available to the user. This
can also be enhanced by giving the user more services such as aggregate calculation etc.,

7.2REFERENCES

- phptpoint.com

-www.google.com

-www.freelancer.in