DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

FACULTY OF ENGINEERING & TECHNOLOGY,

RAMA UNIVERSITY, KANPUR UTTAR PRADESH

Certificate of Approval

This is to certify that Suraj Chakrawarti (1410104017) and Pinki Kumari Soni
(1410104012) of the final year B. Tech (CSE) have successfully completed the
major project “University Online System”.

Under the able guidance of Ms. Preeti Raj Verma toward the fully fulfillment of the
Bachelor degree course in Computer Science in Rama University (Faculty of
Engineering & Technology), Kanpur.

Internal Examiner External Examiner

Head of Department
Dr. Hari Om Sharan

i
 Candidate Declaration

I hereby certify that the work which is being presented in the report, entitled
"University Online System", in the partial fulfillment of the requirement for the
award of the degree of Bachelor in Technology and submitted to the institution is
an authentic record of our own work carried out during the period Feb, 2018 to
Apr, 2018 under the supervision of Ms. Preeti Raj Verma.

The matter presented in this report has not been submitted elsewhere for the
award of any degree and diploma from any Institutions.

Date: Signature of
Candidate

1. Suraj Chakrawarti
2. Pinki Kumari Soni

This is to certify that the above statement made by the candidate is correct to the
best of our knowledge.

Date: Signature of Project

Guide

ii
 Acknowledgements

The extensive endeavor that accompanies the successful completion of any task
would not be complete without the expression of gratitude to the people who
made it possible. We express our sincere thanks to our project guide Ms. Preeti
Raj Verma Ma’am. She was always patient and willing to help. We thank her for
all his encouragement, inspiring guidance, valuable advises and suggestions
throughout our project work.

We would like to express our sincere gratitude towards Dr. Hari Om Sharan Sir
(Head of CS Department) and Mr. Sarvesh Patel Sir for his kind support and
suggestions given in every step.

We extend our whole-hearted thanks to all the staff of in Computer Science &
Engineering Department for providing all facilities, valuable suggestions and
constant supervision for the completion of the project.

Last but not the least, we would like to acknowledge to all the ongoing support of
our parents and our family members, whose patience and encouragement during
these long days and night have been paramount in making of this project a
reality.

iii
 Abstract

A University Online System is designed to help colleges and university for

management of student information related to his marks, attendance, subject,
department, and also sending notice to student through Admin, HOD, Faculty.
Extensive information is available at your fingertips through this system.

There are custom search capabilities to aid in finding student information, Faculty
information with related to subject assign and also getting information about the
HOD of the Department with User ID (Roll No). This can make the system easier
to navigate and to use maximizing the effectiveness of the other resources.
Security of the system provides the keeping of personal data in a form that can
easily accessed and analyzed in a consistent way.

Our work useful for easy user interface. We will provide more ease for managing
the information online than manually documents. Our work is useful for saving
valuable time and reduces the huge paper work.

iv
 Table of Contents
1. Introduction ......................................................................................... 1
1.1. Objective........................................................................................................................... 1
1.2. User of The System ........................................................................................................... 1
1.3. Benefits............................................................................................................................. 1
1.4. Scope ................................................................................................................................ 2
1.5. Module Descriptions ........................................................................................................ 3
1.5.1. Login Portal ............................................................................................................. 3
1.5.2. Admin or Dean ....................................................................................................... 3
1.5.3. HOD ......................................................................................................................... 3
1.5.4. Faculty ..................................................................................................................... 3
1.5.5. Students .................................................................................................................. 3

2. Requirement Analysis ....................................................................... 4

2.1. Feasibility Study ................................................................................................................ 4
2.1.1 Operational Feasibility........................................................................................... 4
2.1.2 Technical Feasibility .............................................................................................. 4
2.1.3 Economic Feasibility.............................................................................................. 4
2.2. Technical Specification ..................................................................................................... 5
2.2.1. Software Requirement .......................................................................................... 5
2.2.2. Hardware Requirement ......................................................................................... 5
2.3. Technology Description .................................................................................................... 5
2.3.1. PHP .......................................................................................................................... 5
2.3.2. MySQL ..................................................................................................................... 6
2.3.3. HTML ....................................................................................................................... 6
2.3.4. CSS .......................................................................................................................... 6
2.3.5. APACHE.................................................................................................................. 6
2.3.6. XAMPP .................................................................................................................... 7
2.3.7. Obtaining & Installing XAMPP ............................................................................. 7

3. Process Design Methodology ......................................................... 9

3.1. SDLC Methodology ........................................................................................................... 9
3.2. Iterative Model ............................................................................................................... 10
3.3. DFD - Data Flow Diagram ............................................................................................... 11
3.1.1. DFD of The System ............................................................................................. 12
3.1.2. Zero Level User’s DFD ....................................................................................... 13
3.1.3. 1st Level User’s DFD ........................................................................................... 14

v
 3.1.4. 2nd Level User’s DFD........................................................................................... 15

4. Project Flow Diagram ...................................................................... 16

4.1. Flow Chart of System ...................................................................................................... 16

5. Project Description .......................................................................... 18

5.1. Description & Structure of Database Tables .................................................................. 18
5.1.1. Database Structure of “project” ......................................................................... 18
5.1.2. Table Structure of “auth” ..................................................................................... 18
5.1.3. Table Structure of “profile” .................................................................................. 19
5.1.4. Table Structure of “attend” ................................................................................. 19
5.1.5. Table Structure of “department” ........................................................................ 20
5.1.6. Table Structure of “Student Semester” ............................................................. 20
5.2. Snapshots ....................................................................................................................... 21
5.2.1. Login Portal ........................................................................................................... 21
5.2.2. Admin Dashboard ................................................................................................ 21
5.2.3. HOD Dashboard................................................................................................... 22
5.2.4. FACULTY Dashboard ......................................................................................... 22
5.2.5. Take Attendance .................................................................................................. 23
5.2.6. View Attendance .................................................................................................. 23
5.2.7. View Details of Faculty ........................................................................................ 24
5.2.8. Student Details ..................................................................................................... 24
5.2.9. Marks Report ........................................................................................................ 25
5.2.10. Promote Students in Next Semester ............................................................ 25
5.2.11. Notice ................................................................................................................. 26

6. Testing ................................................................................................ 27
6.1. Software Testing Strategies ............................................................................................ 27
6.1.1. Unit Testing ........................................................................................................... 27
6.1.2. Integration Testing ............................................................................................... 28
6.1.3. Validation Testing ................................................................................................ 28
6.1.4. System Testing..................................................................................................... 28

7. Source Code ..................................................................................... 29

7.1. Authentication ................................................................................................................ 29
7.2. Encryption ...................................................................................................................... 30
7.3. Reset Password............................................................................................................... 30
7.4. Connection ..................................................................................................................... 30
7.5. Ajax Query ...................................................................................................................... 31

vi
8. Conclusion ........................................................................................ 32
9. Bibliography ...................................................................................... 34

vii
 1. Introduction
A University Online System is software which is helpful for Students as well
as the school authorities. In the current system all the activities are done
manually. It is very time consuming and costly. Our University Online System
deals with the various activities related to the Students. In the Software we can
register as a user and user has four types, Student, Faculty, HOD, Admin or
Dean. Admin has the power to add or modify HOD. HOD has the power to add
or modify Faculty. Faculty has the power to add or modify Students, upload
Manage Attendance, Test Marks, etc. A student can register as user and can
add edit own profile. Faculty, HOD, Admin/Dean can see test marks,
attendance, Student application, etc.

1.1. Objective

It provides a common platform to connect Admin, HOD, Faculty and

Students online. The registered Faculty can create Notice, Attendance,
Test Marks and Students can see details of test marks, attendance &
notice.

1.2. User of The System

a) Dean or Admin
b) HOD
c) Faculty
d) Student

1.3. Benefits

a) The main benefits of university online system a user can get all information
related to his or her department, either the information is related to his HOD,
Faculty, and Students and also get notice information without wasting time
just only using this System.

b) This project is based on PHP which is a popular technology with user

friendly and it can interact with many different database languages including

1
 MySQL. Both PHP and MySQL are compatible with an Apache server
which is also free to license.

c) Using this system student does not have the problem to wait for the
attendance percentage list they can see they attendance whenever they
want to see and can calculated their percentage own.

d) The system make work easier for everyone whether HOD, Faculty and
Students because HOD also don’t need to wait for the attendance report
and marks report, HOD can see everything online.

e) This system also show notice online with sender and receiver information.
We can say that this system can save time resource and also update
information consistence with security.

f) You do not have to install anything on your computer. This system is an

online university system. That means you use it in your favorite browser.

g) It's easy to work on University Online System software on your first login
without any instructions all you need is the basic knowledge of working a
computer.

1.4. Scope

a) University online system is use in any kind of educational institution -

universities, colleges, any institute or center which needs to manage
Students, Faculty and many more information related to their department in
the colleges, universities and institute. Online University is the ultimate
solution for user to manage their data.

b) University online system can be used by the user who want to maintain their
whole department work online without wasting time and not interested to do
paper work which is sometime become very difficult to maintain.

2
 c) It provides a friendly user interaction which proves to be better when
compared to the existing system.

1.5. Module Descriptions

In university online system we can divide project in sub parts called modules.

1.5.1. Login Portal

i. Login: Fill forms with correct data.

ii. Forget: If forget password, then enter Aadhar card no as a password
and reset your password.

1.5.2. Admin or Dean

i. Can create notice alerts.

ii. Can access student’s details (Like test marks, attendance report etc.).
iii. Can send notice to HOD, Faculty and Students.

1.5.3. HOD

i. Can communicate with Faculty and Students.

ii. Can access Student’s details.
iii. Can create notice alert.

1.5.4. Faculty

i. Can add mid marks, attendance, class notes etc.

ii. Can access Student’s details.

1.5.5. Students

i. Can view attendance subject wise, test marks, Notice etc.

ii. Can create application for Faculty, HOD and Dean.

3
 2. Requirement Analysis
2.1. Feasibility Study
Feasibility study is conducted once the problem is clearly understood. Feasibility
study is a high-level capsule version of the entire analysis and design process. The
objective is to determine quickly at a minimum expense how to solve a problem.
The purpose of feasibility is not to solve the problem but to determine if the problem
is worth solving.

The system has been tested for feasibility in the following points.
a) Operation feasibility
b) Technical feasibility
c) Economic feasibility

2.1.1 Operational Feasibility

Proposed project is beneficial only if they can be turned into “University online
system” that will meet the treatment requirements. Simply stated, this test of
feasibility asks. If the system will work when it is developed and installed.

2.1.2 Technical Feasibility

It involves studying the system for checking that whether it will be technically
feasible to develop and implement the system.
The proposed project is technical feasible due to –
a) The database has the capacity to hold the data required to use the new
system as well as to satisfy all the condition, which is used in this project.
b) The technology on which project is going designed (PHP & MySQL using
XAMPP, Bootstrap, HTML, CSS and AJAX) is easily available in market.
c) System has capability to enhance its working as desired in feature.
d) This system provide reliability, ease of access and data security features.

2.1.3 Economic Feasibility

A system that can be developed technically and that will be used if installed must
still be a good investment for system. Study involves seeing whether it is feasible

4
to do the changes in the system or build a new one, as per the outcome of
preliminary investigation. The algorithm efficiency will improve by the proposed
project. Organization will also complete their task timely because they find
response for University Online System. Since it is holds the Technical feasibility,
Economical feasibility, and operational feasibility so proposed project is feasible.

2.2. Technical Specification

2.2.1. Software Requirement

a) Operating System: Any Operating System (Like Window, Mac etc.).
b) Tools: XAMPP, Text Editor (Like Notepad++, Sublime etc.)
c) Programming Language:
 Front End: HTML, CSS & Bootstrap.
 Back End: PHP, MySQL & Ajax.

2.2.2. Hardware Requirement

a) Processor: Pentium or Above.
b) Storage: 1 GB.
c) RAM: 512 MB.

2.3. Technology Description

2.3.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 system 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.

5
2.3.2. MySQL
MySQL is a Relational Database Management System (RDBMS) 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.3.3. HTML

HTML stands for Hypertext Markup Language, and it is the most widely used
language to write Web Pages.

a) Hypertext refers to the way in which Web pages (HTML documents) are
linked together. Thus, the link available on a webpage are called Hypertext.

b) As its name suggests, HTML is a Markup Language which means you use
HTML to simply "markup" a text document with tags that tell a Web browser
how to structure it to display.

2.3.4. CSS

a) CSS is a stylesheet language that describes the presentation of an HTML

(or XML) document.
b) CSS describes how elements must be rendered on screen, on paper, or in
other media.

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

6
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.3.6. 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 developer, developing and testing applications
in PHP and MySQL. XAMPP is available as a free.

2.3.7. Obtaining & Installing XAMPP

As previously mentioned, XAMPP is a free package available for download and
use for various web development tasks. All XAMPP packages and add-ons are
distributed through the Apache Friends website at the address:
http://www.apachefriends.org/. Once on the website, navigate and find the
Windows version of XAMPP and download the self-extracting ZIP archive. After
downloading the archive, run and extract its contents into the root path of a hard
disk or USB drive. For example, the extract path for a local Windows installation
would simply be C:\. If extracted properly we will notice a new XAMPP directory in
the root of your installation disk. In order to test that everything has been installed

Fig. No. – 2.3.7.a: XAMPP Control Panel

7
correctly, first start the Apache HTTP Server by navigating to the XAMPP directory
and clicking on the apache_start.bat batch file. Next, we will test if the server is
running correctly by opening an internet browser and typing http://localhost/ into
the
address bar. If configured correctly, we will be presented with a screen similar to
that of the one below.

8
 3. Process Design Methodology
Design is the first step in the development phase for any techniques and
techniques and principles for the purpose of defining a device, a process or
system in sufficient to permit its physical realization. Once the software
requirements have been analyzed and specified the software design involves
three technical activates- design, coding, implementation and testing that are
required to build and verify the software. Design activities are of main
importance in this phase, because in this activity, decision ultimately affecting the
success of the software implementation and its ease of maintenance are made.
These decisions have the final bearing upon reliability and maintainability of the
system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system. Design the place where quality
is fostered in development. Software design is a process through which
requirements are translated into a representation of software.
Software design is conducted in two steps. Preliminary design is concerned with
the transformation of requirements into data.

3.1. SDLC Methodology

This document plays a vital role in the development of life cycle (SDLC) as it
describes the complete requirement of the system. It means for use by developers
and will be the basic during testing phase. Any changes made to the requirements
in the future will have to go through formal change approval process.

Fig. 3.1.a: Steps of SDLC

9
3.2. Iterative Model

This model leads the software development process in iterations. It projects the
process of development in cyclic manner repeating every step after every cycle of
SDLC process.

Fig. 3.2.a: Iterative Model

The software is first developed on very small scale and all the steps are followed
which taken into consideration. Then, on every next iteration, more features and
modules are designed, coded, tested and added to the software. Every cycle
produces a software, which is complete in itself and has more features and
capabilities than that of the previous one.
After each iteration, the management team can do work on risk management and
prepare for the next iteration. Because a cycle includes small portion of whole
software process, it is easier to manage the development process but it consumes
more resources.

10
3.3. DFD - Data Flow Diagram
Dataflow diagrams represent the flow of the through a system. A DFD is
composed of:

a) Data movement shown by tagged arrows.

b) Transformation of process of data shown by named bubbles.
c) Sources and destination of data represented by named rectangles.
d) Static storage or data at rest denoted by an open rectangle that is named.

The DFD is intended to represent information flow but it is not a flow chart and it
is not intended to indicate decision-making, flow of control, loops and other
procedural aspects of the system. DFD is a useful graphical tool and is applied at
the earlier stages of requirements analysis. It may be further refined at preliminary
design states and is used as mechanism for creating a top level structural design
for software.

a) The DFD drawn first at a preliminary level is further expanded into greater
details
b) The context diagram is decomposed and represented with multiple
bubbles.
c) Each of these bubbles may be decomposed further and documented as
more detailed DFD’s.

11
3.1.1. DFD of The System

This is DFD of the university online system, it is connected with four modules
Admin, HOD, Faculty and Students. By combining we make a complete University
Online System.

Fig. No. – 3.1.1.a: DFD of The System

12
3.1.2. Zero Level User’s DFD

This is DFD of zero level of user’s where user send request for login then login
process check in to database that user is authenticated or not if authenticated then
database give replay that user is authenticated and user get login otherwise it will
move to forget password and user id process.

13
3.1.3. 1st Level User’s DFD

This is first level DFD of user where user’s after getting login they perform their
task like add HOD, add Faculty, add subject, take attendance give mark, assign
subject to Faculty, add department forward notice. View details of HOD and
Faculty. Database store add HOD data, add marks data, add Faculty data, take
attendance data, add subject data and also notice data.

Fig. No. – 3.1.3.a: 1st Level DFD

14
3.1.4. 2nd Level User’s DFD

This is second level of DFD of user where user can remove department, remove
notice, remove HOD, remove FACULTY and can view marks, view subject, view
attendance. If user want to remove department then user have to be send
department code to database to remove department. If user want to remove
notice then user have to send notice id to database to remove notice. If user
want to view attendance then send data of student to display data of attendance.

Fig. No. – 3.1.4.a: 2nd Level of DFD

15
 4. Project Flow Diagram
Diagram that a given problem. Process operation are represented in these boxes,
and arrows connecting them represent flow of control.

4.1. Flow Chart of System

Fig. No. – 4.1.a: Flow Chart

16
There are following steps:
Step 1
Start the system and enter user id and password check for validation to database
that user is authenticated if yes then move to next step. If no then move to again
start program or system.

Step 2
Enter to dashboard of user’s (Admin, HOD, Faculty and Students) and check
their task according to their access id.

Step 3
After checking task users perform their task like Admin can add HOD, add
department, and send notice, view attendance, view marks, view Student and
Faculty details. So, every user performs their task like Admin.

Step 4
End of process or stop.

17
 5. Project Description

5.1. Description & Structure of Database Tables

5.1.1. Database Structure of “project”

This is snapshots of database with database name “project” having all table with
tables name as shown in snapshots.

Fig. No. - 5.1.1.a: Structure of Project Database

5.1.2. Table Structure of “auth”

This is authentication table to store password and user id with access id of the
users. This table have Sr no, user id, name, password. (Pass).

Fig. No. - 5.1.2.a: Table Structure of “auth”

18
5.1.3. Table Structure of “profile”

This is profile table where user data is added with Aadhar no for first time when
user add by Admin or HOD.

Fig. No. – 5.1.3.a: Table Structure of “profile”

5.1.4. Table Structure of “attend”

This table of Attendance, where attendance store in database with the help of
subject code Faculty id, Students id, date, semester etc.

Fig. No. – 5.1.4.a: Table Structure of “attend”

19
5.1.5. Table Structure of “department”

Department table it stores department name with department code and course.

Fig. No. – 5.1.5.a: Table Structure of “department”

5.1.6. Table Structure of “Student Semester”

This table of student semester store semester of student with the help of student
id, department code & course

Fig. No. – 5.1.6.a: Table Structure of “Student Semester”

20
5.2. Snapshots

5.2.1. Login Portal

This is Login portal where ADMIN, HOD, FACULTY & STUDENTS can login
and move to their dashboard. In this portal user enter USER ID AND
PASSWORD, after done SIGN IN it will be access by id which have given to the
Admin, HOD, Faculty and Students.

Fig. No. – 5.2.a: Login Portal

5.2.2. Admin Dashboard

Fig. No. – 5.2.2.a: Admin Dashboard

21
This is Admin dashboard where Admin can add HOD and see details, add
department, remove department, view attendance, marks, Faculty & Students
details and also forward notice to whom Admin want to forward.

5.2.3. HOD Dashboard

Fig. No. – 5.2.3.a: HOD Dashboard

This is HOD dashboard where HOD perform their task, like add FACULTY, view
attendance and marks, forward notice. Assign subject to FACULTY, with semester
wise. See student details.

5.2.4. FACULTY Dashboard

Fig. No. – 5.2.4.a: Faculty Dashboard

22
This is Faculty dashboard where Faculty can perform their takes like take
attendance view attendance give marks and view marks. View Students details.

5.2.5. Take Attendance

Fig. No. – 5.2.5.a: Take Attendance

5.2.6. View Attendance

Fig. No. – 5.2.6: View Attendance

This is student portal where attendance report of particular logged like above fig.

23
5.2.7. View Details of Faculty

Here Faculty details view by department wise or subject wise.

Fig. No. – 5.2.7: Details of Faculty

5.2.8. Student Details

Students details view by Admin, HOD & Faculty, Students search by department,
semester or session.

Fig. No. – 5.2.8: Students Details

24
5.2.9. Marks Report

Fig. No. – 5.2.9: Marks Report

5.2.10. Promote Students in Next Semester

Only HOD can promote Students in next semester.

Fig. No. – 5.2.10: Promote Student in Next Semester

25
5.2.11. Notice

Fig. No. – 5.2.11: Notice

26
 6. Testing

It is the process of testing the functionality and functionality and correctness of

software by running it. Process of executing a program with the intent of finding an
error. A good test case is one that has a high probability of finding an as yet
undiscovered error. A successful test is one that uncovers an as yet undiscovered
error. Software testing is usually performed for one of two reasons.
a) Reliability
b) Defect detection

6.1. Software Testing Strategies

A strategy for software testing will begin in the following order:
a) Unit testing
b) Integration testing
c) Validation testing
d) System testing

6.1.1. Unit Testing

It concentrates on each unit of the software as implemented in source code and is
a white box oriented. Using the component level design description as a guide,
important control paths are tested to uncover errors within the boundary of the
module in the unit testing. The step can be conducted in parallel for multiple
components.

a) Black Box Testing

Applies to software systems or modules, tests functionality in terms of input and
outputs at interfaces. Test reveals if the software function is fully operational with
reference to requirements specification.

b) White Box Testing

i. Knowing the internal working i.e., to test if all internal operations are
performed according to program structures and data structures.
ii. To test if all internal components have been adequately exercised.

27
6.1.2. Integration Testing
Here focus is on design and construction of the software architecture. Integration
testing is a systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors associated with interfacing. The
objective is to take unit tested components and build a program structure that been
dictated by design.

6.1.3. Validation Testing

In this, requirements established as part of software requirements analysis are
validated against the software that has been constructed i.e., validation succeeds
when software functions in a manner that can reasonably that can have expected
by the customer.

6.1.4. System Testing

System testing of software or hardware is testing conducted on a completed,
integrated system to evaluate the system’s compliance with its specified
requirements. System testing falls within scope of black testing, and as such,
should require no knowledge of the inner design of the code or logic.
The following examples are different types of testing that should be considered
during system testing.
a) Graphical user interface testing
b) Usability testing
c) Software performance testing
d) Compatibility testing
e) Exception handling
f) Load testing
g) Volume testing

28
 7. Source Code
7.1. Authentication

<?php
session_start();
if(isset($_POST['login'])){
$id=$_SESSION['id']=$_POST['uid'];
$pass=$_POST['password'];
$aadh=mysqli_query($conn, "select aadhar, department from profile where id='$id'; ");
$row=mysqli_fetch_assoc($aadh);
if($pass==$aadhard){
$_SESSION["pid"]=$id;
header("Location:index.php?g=r"); }
else{
$check="select name, pass, access from auth where user_id = '$id'; ";
$result=mysqli_query($conn, $check);
$rows_num=mysqli_num_rows($result);
$row=mysqli_fetch_assoc($result);
$user=$row["name"];
$_SESSION['user']=$user;
$pass2=$row["pass"];
$valid_pass=my_simple_crypt( $pass2, 'd' );
$access=$row["access"];
if($rows_num==0){
header("Location:index.php?status=inc"); }
else{
if($pass==$valid_pass){
if($access==1){
header("Location:admin/");
$_SESSION["access"]=$access; }
elseif ($access==2) {
header("Location:hod/");
$_SESSION["access"]=$access; }
elseif ($access==3) {
header("Location:faculty/");
$_SESSION["access"]=$access; }
elseif ($access==4) {
header("Location:student/");
$_SESSION["access"]=$access; }
else{
header("Location:index.php?status=inc");
}}
else{
header("Location:index.php?status=warn");
} }}}
else{
header("Location:index.php?status=lg");
}

?>

29
7.2. Encryption

<?php
function my_simple_crypt( $string, $action = 'e' ) {
$output = false;
$enc_method = "AES-256-CBC";
$k = hash( 'sha256', $secret_key );
$i = substr( hash( 'sha256', $secret_iv ), 0, 32 );

if( $action == 'e' ) {

$output = base64_encode( openssl_encrypt( $string, $enc_method, $k, 0, $i ) ); }
else if( $action == 'd' ){
$output = openssl_decrypt( base64_decode( $string ), $enc_method, $k, 0, $i ); }
return $output; }
?>

7.3. Reset Password

<?php
if(isset($_SESSION["pid"])){
if(isset($_POST["change"])){
$pid=$_SESSION["pid"];
$newpass=my_simple_crypt( $_POST["pass"], 'e' );
if ($conn->query("UPDATE auth SET pass='$newpass' WHERE user_id='$pid';") === TRUE) {
header("Location:index.php?status=ps");
session_destroy(); }
else{
$pmsg="Something Problems Occur, You Can Try After Some Time.";
$pmsgClass="alert-danger"; } }
else{ } }
else{
session_destroy();
header("Location:index.php?g=l"); }
?>

7.4. Connection

<?php
$conn=mysqli_connect("localhost", "root", ".akd.dio@ihf’skflk@", "project");
if (!$conn){
die('Could not connect: ' . mysqli_error());
}
?>

30
7.5. Ajax Query

<?php
if(isset($_REQUEST['id'])){

// Prepare a select statement

$sql = "SELECT * FROM auth WHERE name LIKE ?";
if($stmt = mysqli_prepare($link, $sql)){

// Bind variables to the prepared statement as parameters

mysqli_stmt_bind_param($stmt, "s", $param_term);

// Set parameters
$param_term = $_REQUEST['id'] . '%';

// Attempt to execute the prepared statement

if(mysqli_stmt_execute($stmt)){
$result = mysqli_stmt_get_result($stmt);

// Check number of rows in the result set

if(mysqli_num_rows($result) > 0){

// Fetch result rows as an associative array

while($row = mysqli_fetch_array($result, MYSQLI_ASSOC)){
echo "<p>" . $row["user_id"] . "</p>"; } }
else{ } }
}
}
elseif(isset($_REQUEST['sub_code'])){
$sql = "SELECT * FROM subject WHERE subject_name LIKE ?";

if($stmt = mysqli_prepare($link, $sql)){

mysqli_stmt_bind_param($stmt, "s", $param_term);
$param_term = $_REQUEST['sub_code'] . '%';
if(mysqli_stmt_execute($stmt)){
$result = mysqli_stmt_get_result($stmt);
if(mysqli_num_rows($result) > 0){
while($row = mysqli_fetch_array($result, MYSQLI_ASSOC)){
echo "<p>" . $row["subject_code"] . "</p>";
} }
else{ }
else{
echo "ERROR: Could not able to execute $sql. " . mysqli_error($link);
} }

// Close statement
mysqli_stmt_close($stmt);
}
?>

31
 8. Conclusion

In University online system we have shown Admin, HOD, Faculty and Student
Dashboard with login portal and access by the id of every authorization. Notice
is used to forward notice as according to user need or want to send notice. By
this system, we can maintain all details of every department online in a secure
manner. Details of HOD, Faculty and Student details can be view by an
authorized user (Admin) of the system.

Previously users have to wait for information in order to get the documents
acknowledged by the concerned officials whereas the currently developed
system offers an efficient way to perform these operations. The users can
access the login portal online either from a computer or a smartphone and fill
the necessary information and submit it for further approval. This web
application provides us with ease of access, user-friendliness, and
transparency. On the other hand, from organizations viewpoint, it helps in
maintaining transparency, data consistency, data accessibility and easy
maintenance.

Implementation of the proposed system will reduce the workload of all those
involved as the data can be now managed with proper authentication and
authorizations instead of being hard copied and accessible to everyone. This
system will largely save the precious time of Admin, HOD, and Faculty instead
of explicitly signing every document; they just have to acknowledge entries
online with the click of a mouse.

All the technologies i.e. PHP, Apache, and MySQL used for current system
design are open source and hence freely available for download. PHP provides
a strong platform for creating the visual front-end of the web application and
PHP combined with HTML provides a very flexible development environment.
For the purpose of fulfilling Web Server requirements XAMPP was used, which
is again Open Source and is supported across multiple platforms. For constant
testing, analysis and execution needs, Firefox and Google Chrome web-
browsers were used. With a combination of all these technologies, we were

32
able to create a web application environment that is efficient and consistent
enough.

The primary objective of our research and development was to automate

student and department information online procedure. It has been achieved
successfully and the system is tested to be working efficiently. Students and
departments information is entered during the semester, the system verifies the
data entered and maintain data with security and authorization.

Online application of the whole system helps easy access to the system
anywhere. The physical presence of the user is not required. The time taken
for process completion is now largely reduced. After login and enter the
information either which is related to Student, Faculty, HOD, Admin, notice and
any department the database is automatically updated at the end of process
completion removing the hassle for department officials who had to enter the
data manually. As the database is managed through MySQL, data duplication
is eliminated and thereby reducing chances of error. Also, data can now be
easily retrieved, edited and printed whenever required. Authentication based
access proves to be more secure than the manual system. Database access
is authorized and cannot be viewed or edited by unauthorized personnel. So,
this automated and computerized system is safe, fast and user-friendly.

33
 9. Bibliography
There had been a lot of influences while making this project “University Online
System”.

a) https://www.google.com
b) http://www.php.net
c) https://www.w3school
d) https://www.apachefriends.org

34