Trwebhuvan University

Faculty of Humanities and Social Science

Student Management System

A PROJECT REPORT

Submitted to

Department of Computer Application

Sungava College

In partial fulfillment of the requirements for the Bachelor in Computer Application

Submitted by:

Name: Darshan Bhattarai

Reg.No. 6-2-1095-05-2020

September, 2023

Under the Supervision of

Bhakta Raj Tamang
 Trwebhuvan University

Faculty of Humanities and Social Science

Sungava College

Supervisor's Recommendation

I hereby recommend that this project prepared under my supervision by DARSHAN

BHATTARAI entitled "STUDENT MANAGEMENT SYSTEM" in partial fulfillment of
the requirements for the degree of Bachelor of Computer Application is recommended for
the final evaluation.

………………….

SIGNATURE

Bhakta Raj Tamang

SUPERVISOR

<<Academic Designation>>

Department of Computer Application, Sungava College

Khairahani-6, Chitwan

i
 Trwebhuvan University

Faculty of Humanities and Social Science

Sungava College

LETTER OF APPROVAL

This is to certify that this project prepared by DARSHAN BHATTARAI entitled

"STUDENT MANAGEMENT SYSTEM" in the partial fulfillment of the requirements
for the degree on Bachelor in Computer Application has been evaluated. in my opinion, it
is satisfactory in the scope and quality as a project for the required degree.

……………………….. ………………………..
Bhakta Raj Tamang Hari Prasad Sapkota
Supervisor HOD
Department of Computer Application, Department of Computer Application,
Sungava College, Sungava College,
Khairahani-6, Chitwan Khairahani-6, Chitwan

……………………… ………………………
Internal Examinar External Examinar

i
i
 ABSTRACT
The submitted project is centered around a Student Information Management System
(SMS) Website. This Website is designed to efficiently organize and manage essential
information pertaining to students, academic departments, and available Courses.
Acknowledging the significance of data management in the educational realm, this Website
acts as a comprehensive tool for handling all relevant information seamlessly.

SMS is a web-based application that caters to the needs of students, faculty, and
administrators within an academic community. It allows Users to access student lists,
browse through department information, and explore the catalog of available Courses.
Students can view their academic records, register for Courses, and track their progress.
Faculty members can access student details, manage Courses materials. Administrators can
oversee the overall operation of the academic institution, monitor departmental activities,
and manage Courses offerings.

In the development of this Website, state-of-the-art software development tools such as

HTML and CSS have been employed for the frontend, while PHP and MySQL have been
utilized as the backend tools. These widely recognized and reliable software development
tools ensure the creation of a robust, User-friendly, and scalable Web-based application that
meets the demands of today's dynamic educational landscape.

i
ii
 ACKNOWLEDGEMENTS
I are thankful to my respected project Guide Mr. Bhakta Raj Tamang for his persistence
help throughout completion of this project. His suggestions and guidance in every stage is
one of the major reasons of successful completion of my project. Without his proper
guidance my project would not have been accomplished on time.

I would like to express my sincere thankfulness to Mr. Hari Parsad Sapkota, BCA
Program Co-Ordinator and Campus Chief of Sungava College, for encouraging me to
develop this Website. During the pre-development stage, developing state and post
developing stage, he always remained the source of inspiration and encouragement for me
to complete this project in time.

A bit closer to my home, I would like to add my heartfelt appreciation for my parents for
their infinite kindness and patience throughout my academic career.

Many thanks to Sungava College, for providing me the great platform on the field of
computer education and generously providing the relevant resources. I am thankful to Mr.
Parkash Chettri and Mr. Sobaraj Poudel, for helping me in every aspect of the academic
years in Sungava. I am also thankful to Mr. Narayan Nepal, and all staff members of the
Sungava College for their kind support.

Finally, I would like to thank all of hidden concern bodies who helped me to meet my goal
on this time and future too.

Thank you!

………………………..

Darshan Bhattarai

(Reg.no.6-2-1095-05-2020)

i
v
Table of Contents
CHAPTER 1: INTRODUCTION .................................................................................... 1
Introduction................................................................................................................. 1
Problem Statement ...................................................................................................... 2
Objectives: .................................................................................................................. 2
Scopes and Limitations................................................................................................ 2
1.1.1 Scopes ............................................................................................................ 2
1.1.2 Limitations ..................................................................................................... 2
Report Organization .................................................................................................... 3
CHAPTER 2: LITERATURE REVIEW .......................................................................... 4
2.1 Literature Review .................................................................................................. 4
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN ...................................................... 6
3.1 System Analysis .................................................................................................... 6
3.1.1 Requirement Analysis ..................................................................................... 6
3.1.2 Feasibility Analysis ......................................................................................... 7
3.1.3 Data Modeling (E-R Diagram) ........................................................................ 9
3.1.4 Process Modeling (DFD) ...............................................................................10
3.2 System Design ...................................................................................................... 11
3.2.1 Architectural Design ...................................................................................... 11
3.2.2 Database Schema Design ...............................................................................12
3.2.3 User Interface (UI) Design .............................................................................12
3.2.5 Use Case Diagram .........................................................................................13
CHAPTER 4: IMPLEMENTATION AND TESTING ....................................................14
4.1 Implementation ....................................................................................................14
4.1.1 Tools made ....................................................................................................15
4.1.2 Implementation Details of Modules ...............................................................16
4.2 Testing ..................................................................................................................18
4.2.1 Test Cases for Unit Testing ............................................................................18
4.2.2 Test Cases for System Testing ........................................................................19
CHAPTER 5: CONCLUSION AND FUTURE RECOMMENDATION .........................19
Outcome: ...................................................................................................................19
Conclusion .................................................................................................................19

v
 Future Recommendations ...........................................................................................20
APPENDIX A ................................................................................................................20
APPENDIX B ................................................................................................................23
REFERENCES ..............................................................................................................27

v
i
List of Figures:
Figure 1: E-R Diagram of SMS ............................................................................... 8
Figure 2: Level 0 and 1DFD of SMS ....................................................................... 8
Figure 3: Architectural Design of SMS ....................................................................11
Figure 4: Schema Diagram of SMS ..........................................................................12
Figure 5: User Interface of SMS ...............................................................................12
Figure 6: Physical DFD of SMS ...............................................................................13
Figure 7: use Case Diagram of SMS ........................................................................14
Figure 8: Agile Method Life Cycle .........................................................................16
Figure 9: Admin Module of Implementation ...........................................................18
Figure 10: User Module of Implementation ...............................................................19
Figure 11: Screenshot 1 .............................................................................................. 23
Figure 12: Screenshot 2 ...............................................................................................23
Figure 13: Screenshot 3 ...............................................................................................24
Figure 14: Screenshot 4 ................................................................................................24
Figure 15: Screenshot 5 ................................................................................................25

List of Abbreviations:

HTML: HyperText Markup Language

PHP: HyperText Preprocessor

XAMPP: X (cross platform), Apache, MySQL, PHP, Perl

SQL: Structured Query Language

CSS: Cascading Style Sheet

UI: User Interface

v
ii
SDLC: System Development Life Cycle

i
i
 CHAPTER 1: INTRODUCTION

Introduction
In today's educational landscape, managing student information, departmental details, and
Courses listings can present significant challenges. To address these complexities, my team
has developed a User-friendly Student Information Management System (SMS) that aims
to simplify and enhance the academic administrative experience. This platform is
reticulately designed to cater to the needs of both students and faculty, streamlining the
process of handling student data, departmental information, and Courses offerings, while
also providing essential functionalities for adding, reading, updating, and deleting records.

For students, the SIMS offers a straightforward interface for accessing their academic
profiles, viewing department information, and browsing available Courses. This empowers
students to register for classes, track their academic progress, and make informed decisions
about their educational Journey. By leveraging the platform's features, students can
conveniently manage their academic pursuits, ensuring a seamless experience throughout
their time at the institution.

On the other hand, the SIMS also benefits academic departments and faculty by providing
them with a tool for managing student records, departmental process, and Courses
offerings. The platform's search and update functionalities enable faculty to efficiently
maintain student records and Courses details. This streamlines administrative processes,
saving valuable time and effort, while ensuring the accuracy and relevance of academic
data.

The SIMS also prioritizes data security and reliability, ensuring that the confidentiality of
student and departmental information is upheld. Regular updates and improvements keep
the platform aligned with the evolving needs of academic institutions, providing an optimal
experience for all Users.

In conclusion, my Student Information Management System is a cutting-edge solution to

the complexities of academic administration. It emperies students to manage their
educational Journey with ease and equips faculty with a comprehensive tool for efficient
record keeping and Courses management. With its User-friendly interface and commitment
to excellence, the SIMS revolutionizes the academic administrative experience, ensuring

1
that student information, departmental records, and Courses listings are effectively and
securely managed.

Problem Statement
• Inadequate Data Security and Confidentiality,

• Manual and Time-Consuming Administrative Processes

• Lack of Real-Time Access and Updates.

Objectives:
• To provide a secure and confidential environment for storing and managing student
information,
• to streamline and automate administrative tasks related to student data management,
departmental record-keeping, and Courses management,

• to offer real-time access to accurate and up-to-date academic information for

students, faculty, and administrators.

Scopes and Limitations

1.1.1 Scopes
• It caters to the needs of both public and private institutions, offering a versatile
solution for academic administration.
• In the era of online education and e-learning, SIMS can be adapted to work
seamlessly,

• It can be customized to align with different education systems,

• SMS can further enhance its accessibility and mobility for students, faculty, and
administrators.

1.1.2 Limitations

• the reliance on a stable internet connection

• it may hinder their ability to access and mee SMS effectively.

2
Report Organization
This report is organized in five chapters. These chapters deal with important aspects of the
SDLC. Each of the chapters is divided into Headings and Subheadings. Chapter 1
introduces this project, its objectives and scopes. The background study and literature
review are explained in Chapter 2. Chapter 3 broadly deals with the requirements, analysis
and design. Chapter 4 includes the implementation and testing of the system. Chapter 5
deals with the conclusion and recommendations of the system. At the end of the report, the
references made the glossary along with appendices have been included.

3
 CHAPTER 2: LITERATURE REVIEW

2.1 Literature Review

The evolution of Student Information Management Systems can be traced back to the late
20th century, with the increasing demand for efficient management of academic data. Jmet
as Student Information System s transformed the job market in the early 1990s, SIMS
started to emerge as a crucial component of educational technology. These systems aimed
to address the challenges posed by traditional paper-based administrative processes.

For instance, in the late 1980s, MIT's Project Athena introduced an early version of a
student information system that allowed students to access their academic records
electronically. This innovation marked the beginning of a shift toward digital student
information management. Over time, various commercial SIMS solutions emerged,
catering to different educational levels and specific needs.

Today, institutions such as K-12 schools, colleges, and universities benefit from SIMS in
diverse ways. These systems enable the automation of tasks like enrollment, grading, and
attendance tracking. They offer educators and administrators the ability to access real-time
data, leading to informed decision-making and improved student outcomes.

PowerSchool: PowerSchool is a widely recognized SIMS made by K-12 schools and

districts worldwide. It offers features for managing student records, attendance, grades,
and communications with parents. PowerSchool has empowered educators and
administrators to make data-driven decisions, improving educational outcomes for
students.

Banner by Ellucian: Banner is a comprehensive SIMS tailored for higher education

institutions. It includes modules for student records, financial aid, Courses management,
and more. Thomians of colleges and universities globally rely on Banner to manage their
administrative tasks effectively.

4
Campman Solutions by Oracle: Oracle's Campman Solutions is another prominent SIMS
made by higher education institutions. It provides tools for student admissions,
registration, financial aid, and academic advising. Universities like Stanford and Yale
utilize Campman Solutions to enhance their academic operations.

However, despite the advantages, SIMS have faced challenges, including data security and
creolization for varying education systems. Some institutions have struggled with the high
costs associated with implementing and maintaining these systems. Additionally, ensuring
User-friendliness and adaptability to changing educational environments remain ongoing
concerns.

In conclusion, Student Information Management Systems have transformed the education

landscape, much like Student Information System s have revolutionized the job market.
Real-world examples such as Polar School, Banner, and campus Solutions in educational
institutions. While these systems have come a long way since their inception, they
continue to evolve to meet the ever-changing needs of educational institutions and
students.

5
 CHAPTER 3: SYSTEM ANALYSIS AND DESIGN

3.1 System Analysis

This Student Information Management System (SIMS) has been reticulately designed to
address the specific needs of educational institutions by facilitating the efficient
management of student information, departmental records, and Courses listings. The
development process began with a comprehensive analysis of the system requirements,
which Ire subsequently categorized into functional and non-functional requirements. My
team conducted in-depth analyses, leveraging the expertise of team members to ensure that
the system's features and capabilities align seamlessly with the academic environment.

The Functional and non-functional requirements that Ire found from the development
process are described below:

3.1.1 Requirement Analysis

Various things are required for the development of the site. The requirements Ire gathered
by me and I discussed with my teacher, supervisor and other friends too in order to find the
requirements for the Website. The requirements Ire then categorized into functional and
non-functional requirements by me. The categories of the requirements are shown below:

Functional Requirements:
The requirements that my system required Ire the functional requirements for the system.
These Ire such requirements that Ire necessary for the system to be complete and without
these requirements being fulfilled, the SMS System would not have worked.
The functional requirements found Ire:

1. Admin Login
2. Add, Edit, Delete, Student
3. Add, Edit, Delete department
4. Add, Edit, Delete Courses
5. User Management

6
Non-Functional Requirements
There are some for the requirements that Ire needed for the system to be scalable but not
those without which the system won't run. Such Non-Functional requirements found and
are listed as:

1. Performance
2. Security
3. Scalability
4. Motability
5. Availability, etc.

3.1.2 Feasibility Analysis

After I have studied about the requirements and I have prioritized the requirements, I then
moved to find whether the system that I are planning to develop is feasible or not. It is one
of the important phases in the development of any system. The feasibility study Process Int
through various stages where I looked whether the system is feasible in all different
important aspects or not. I performed the analysis of the following topics:

1. Technical Feasibility
Technical feasibility study is done by me in order to identify whether my system
can be developed by the technology I have or not. For this first I gathered the
technological tools that Ire required to develop the system. The major tools that Ire
required for this project Ire the software's and the hardware's for the design and
development of the software. I first gathered the software required such as the code
editor, host and the database management software, software design tools, etc. I
found that all the software that I needed Ire available easily and I Ire Ill known about
them which made it easy for me to operate them making the software easy to build.
There was not a much greater requirement of the hardware tools for the
development of the system. I needed a laptop that can handle the software easily
and I had it.
Since all the hardware and the software tools that Ire required Ire easily available
with me, it was technically feasible to develop this project.

7
2. Operational Feasibility
The main aim of the development of this Website was to make sure that the Website
becomes easy to operate and I can manage all the operations easily. The people who
are supposed to operate this site should be able to understand basic English
Language. The admin should be able to work on the computer having basic
computer operation capacity. On my study, I found that all this can be done easily
making this project operationally feasible. I talk with many people also and I found
that they Ire able to operate the system.

3. Economic Feasibility
The development of this project does not require much cost. The host was localhost
so I don't need to pay for the domain and hosting. The software that was required
for this project Ire available free of cost and some paid software also I got for free
being students. The cost for the hardware was also not much as I had computers
with me and it was not necessary to upgrade or purchase new specially for this
project.
With all of these, I concluded that the project I'm working on is feasible economically
too.
4. Schedule Feasibility
The most important thing for the development of any system is to know whether
the system can be made in time or not. I was given time of 12 weeks for the
development of the system and that was enough time for me. To know this, I have
to choose which methos of system development would be better for me to develop
the system. With my analysis I came to the completion that Agile Method of
software development was the better way of making the system as it made me easy
to develop the system within the given time frame. For the better management of
the time I have, I made a Gantt Chart that included the steps for the development of
the software and the time I needed to complete each stage.
The Gantt Chart that I created for my system to develop is as given below:

8
 Table 1 Gantt Chart
Tasks W W W W W W W W W W W W
1 2 3 4 5 6 7 8 9 10 11 12
Planning

Requirement
Analysis
Design

Coding

Testing and
Feedback
Documentation

3.1.3 Data Modeling (E-R Diagram)

The E-R Diagram shows the relation between various entities. The E-R Diagram of SMS is
as shown in the figure below:

Figure 1: E-R Diagram of SMS

9
3.1.4 Process Modeling (DFD)
Data Flow Diagram shows the flow of Process how something will happen on the system.
In my system, I have shown the data flow diagram of level 0, 1 and 2. The following are
the data Flow Diagram of the SMS System.

Figure 2: Level 0 and 1DFD of SMS

10
3.2 System Design
I have made various tools and technologies for the system design of my Student Information
System, SMS. I made Draw.io in order to design the diagrams that I have made and I have
made the schemas from the localhost's page. I have added all the diagrams that I have made
in this report.

System Design was done mainly meeting the design Tools like Draw.io. this was the best
tool for the design of the various diagrams for any System. The different designs include:

1. Architectural Design
2. Database Schema Design
3. User Interface Design
4. Physical DFD
5. Mee Case Diagram Design

All the above-mentioned diagrams and designs are given below:

3.2.1 Architectural Design

Figure 5: Architectural Design of SMS

11
3.2.2 Database Schema Design

Figure 6: Schema Diagram of SMS

3.2.3 User Interface (UI) Design

The meet interface of the Student Information System was made meeting the various tools
like HTML and CSS. The initial design was prepared by using the UI design tools like
Figma. Figma is a software tool that allows you to design the User interface of the
applications. The User interfaces of the Student Information System system are given in
the appendix A at the end of this documentation. The other images of variome pages are
also included in the appendix of the documentation.

Figure 7: User Interface of SMS

12
3.2.5 Use Case Diagram

Figure 9: Use Case Diagram of SMS

13
 CHAPTER 4: IMPLEMENTATION AND TESTING

4.1 Implementation
Implementing is the main phase of the development of the system. I have made the Agile
methodology for the development of this project. The Agile method was chosen to be the
method for the development of this process and I have made other software tools for the
development.

In the context of developing a Student Information System, the Agile method is a highly
effective approach for managing the software development process. Agile is a set of
principles and values that prioritize flexibility, collaboration, and satisfaction. It is Ill-suited
for projects with evolving requirements and allows for frequent feedback and continue
improvement. Unlike traditional waterfall methodologies, the Agile model embraces
change throughout the development process and frequent iterations to deliver functional
increments of the product. By fostering adaptability and centricity, the Agile model teams
to respond quickly to feedback and deliver high-quality software that aligns closely with
expectations.

Some of the core principles include:

• Satisfy the student through early and frequent information of software.

• Face-to-face communication is the most effective and efficient.
• Change can occur at any time in development.
• Simplicity is essential.

The tools that are made for the development of this project are descrwebed below in short:

Figure 10: Agile Method Life Cycle

14
4.1.1 Tools made
Following are the software made for the development of the project:

a. HTML and CSS Framework

HTML and CSS frameworks are pre-designed sets of code and styles that facilitate
the process of building Websites. They provide a foundation for structuring and
styling the pages, enabling developers to create responsive and visually appealing
sites more efficiently. Frameworks like Bootstrap, Foundation, and offer a
collection of remember components, grids, and typography styles. They promote
consistency across projects and reduce the need for writing repetitive code. With
these frameworks, developers can force on customizing and fine-tuning designs
rather than starting from scratch, making them valuable tools in modern
development.

b. PHP

PHP (Hypertext Preprocessor) is a server-side scripting language primarily made

for the development. It is a significant portion of the internet, enabling dynamic
content generation and interaction with databases. PHP is embedded within HTML
code and executed on the server, generating dynamic the pages that can be delivered
to Users. Its versatility allows developers to create various applications, from
simple contact forms to complex content management systems. PHP's extensive
documentation, large community, and broad hosting support make it a popular
choice for the developers seeking a reliable and powerful tool for building dynamic
Websites and the applications.

c. XAMPP Server
XAMPP is a widely made cross-platform software package that provides a local
development environment for the developers. The name stands for "X" (cross
platform), "Apache" (the server), "MySQL" (database management system), "PHP"
(server-side scripting language), and "Perl" (programming language). It also
includes other components like phpMyAdmin and FileZilla for database
management and FTP (File Transfer Protocol) support, respectively. XAMPP
enables developers to run and test Websites and the applications on their computers

15
 without the need for a live the server. This local testing environment is valuable for
debugging, development, and learning purposes before deploying the code to a live
server.

d. JAVASCRIPT

JavaScript is a versatile and essential programming language for the development.

As a client-side scripting language, it runs in the browsers and enables interactivity
and dynamic content on Websites. JavaScript allows developers to manipulate
HTML and CSS, handle events, and create responsive User interfaces. With the rise
of frameworks and lwebraries like React, Angular, and Vue.js, JavaScript has
evolved into a full-fledged ecosystem for building complex single-page
applications (SPAs). Additionally, Node.js enables developers to mee JavaScript on
the server-side, expanding its capabilities to build scalable the applications.
JavaScript's ubiquity and flexwebility make it a fundamental tool for modern the
developers.

4.1.2 Implementation Details of Modules

This project consists of two modules for implementation.

1. Admin Module
This module is accessweble by admins only. After entering validate credentials
admin will be able to enter the admin dashboard. Inside it, admin can add, view,
edit, and delete the student information according to their need. However, it
manages the overall software.

16
 Figure 11: Admin Module of Implementation

2. User Module
This module is accessweble by all the Users where in my software, the users and
the admin are same. In this module, User can resister student according to their
Courses and department and login to the system. They can view the student list and
can manage them.

Figure 12: User Module of Implementation

17
4.2 Testing
Cycles of implementation Ire performed, followed by testing and integration by developing
the modules derived in the architectural design based upon their importance to the system.
various sets of tests Ire run to perform unit and system testing

4.2.1 Test Cases for Unit Testing

Unit testing was done by testing the admin module and User module separately. Several
test cases Ire run to perform unit testing. Both modules survived the test and hence unit
testing was successful.

Table 2: Test Cases and Result

S. N Test case Input data Expected outcome Actual
result

1. Login page Correct Username & User can login successfully User
password logged in

2. Login page Incorrect Username User cannot login and an alert

message comes saying Alert
& valid password message
appeared

18
 3. Add student, Invalid Form An error message should appear Error
department, saying that the data is invalid. Message
Details
courses is shown.

4.2.2 Test Cases for System Testing

The System testing was performed separately in admin and User module separately. The
testing involved some valid and invalid data to be given in the system. Both modules
survived the test and hence system testing was successful. Some test cases and result of User
modules are given:

Table 3: Test Cases and Result for System Testing

S.No. Task Process Expected Result
Outcome
1 User Login Made those Successful Login Redirected to
credentials to login (with validation) login page after
to the Website. successful login.

2. View, edit, View the Student Student should be Student list can be
delete, update that have register shown with their shown with their
and create for the admission courses and department and
student list department courses.

CHAPTER 5: CONCLUSION AND FUTURE

RECOMMENDATION

Outcome:
The “SMS” after its completion will provide an outcome for all the Users of the system.
Outcome for system admin will be an interface that allows Users to see their list according
to their registration number, courses and department.

Conclusion
In conclusion, this system will reduce the amount of manual data entry and give greater
efficiency. A Student Information System can provide great convenience to both teacher
19
and their student. It allows student to choose their department along with courses. With the
right approach, a Student Information System Website can help to increase efficiency and
smoothness.

Future Recommendations
In the future, my Student Information System (SMS) will allow the both student and teacher
to find their list according to reg.no. The teacher will also be recommended the courses that
are related to their interest and capacity. The courses and the department will have the
separate page that will allow the college to search the student according to their reg.no.

APPENDIX A

Figure 13: Screenshot 1

20
Figure 14: Screenshot 2

Figure 15: Screenshot 3

21
Figure 16: Screenshot 4

Figure 17: Screenshot 5

22
 APPENDIX B

Index.php

<?php
session_start();
// check if the admin is already logged in
if(isset($_SESSION["adminname"]))
{
header("location: dashboard.php");
exit;
}
require_once "config/dbconnect.php";

$adminname = $password = "";

$err = "";

23
// if request method is post
if ($_SERVER['REQUEST_METHOD'] == "POST"){
if(empty(trim($_POST['admin_name'])) || empty(trim($_POST['password'])))
{
$err = "Please enter Admin Name and Password";
echo "<script>alert('$err');</script>";
}
else{
$adminname = trim($_POST['admin_name']);
$password = trim($_POST['password']);
}

if(empty($err))
{
$sql = "SELECT admin_name ,admin_password FROM admin_detail WHERE
admin_name = ?";
$stmt = mysqli_prepare($conn, $sql);
$param_admin_name = $adminname;
mysqli_stmt_bind_param($stmt, "s", $param_admin_name);

// Try to execute this statement

if(mysqli_stmt_execute($stmt)){
mysqli_stmt_store_result($stmt);
if(mysqli_stmt_num_rows($stmt) == 1)
{
mysqli_stmt_bind_result($stmt, $adminname, $hashed_password);
if(mysqli_stmt_fetch($stmt))
{

24
 if(password_verify($password, $hashed_password))
{
// this means the password is corrct. Allow User to login
// die("admin login");
$_SESSION["adminname"] = $adminname;
$_SESSION["logged_in"] = true;

//Redirect User to Ilcome page

header("location: dashboard.php");

}
else{
$err = "Admin Name and Password did not match.";
echo "<script>alert('$err');</script>";
}
}
}
else{
$err = "This admin is not registered..";
echo "<script>alert('$err');</script>";
}
}
}
}
?>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatweble" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="lstyles.css">
25
 <link href="https://fonts.googleapis.com/css2?family=Noto+Serif&display=swap"
rel="stylesheet">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/lwebs/font-
aIsome/6.3.0/css/all.min.css">
<script
src="https://ajax.googleapis.com/ajax/lwebs/jquery/1.8.3/jquery.min.js"></script>

<title>Sungava-Admin Login</title>
</head>
<body>
<div class="wrapper-right">

<div class="title">
<h1>Ilcome Back,</h1>
<p>Sign In to ymy account</p>
</div>
<form action="" method="post">
<div class="form-card">
<span class="label">Admin Name</span>
<div class="input-box">
<input type="text" id="adminname" name = "admin_name"
placeholder="Enter Admin Name">
<ion-icon name="person-outline"></ion-icon>
</div>
</div>
<div class="form-card">
<span class="label">Password</span>
<div class="input-box">
<input type="password" name="password" id="password"
placeholder="Enter Admin Password">
<ion-icon name="lock-closed-outline"></ion-icon>
</div>

26
 </div>
<input type="submit" value="Login" class="login-btn">
</form>
</div>
</body>
<script type="module"
src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.esm.js"></script>
<script nomodule
src="https://unpkg.com/[email protected]/dist/ionicons/ionicons.js"></script>
</html>

REFERENCES

[1] WikiMedia, "Student_Website," 5 September 2023. [Online]. Available:

https://en.wikipedia.org/wiki/Student_Website.

[2] W. S. Ltd, "sdlc-software-development-life-cycle," White Smyce Ltd, 2023.

[Online]. Available: https://www.mend.io/blog/sdlc-software-development-
lifecycle/. [Accessed 30 September 2023].

27
28