College Management System

By

Abdul Sammi Bhutta 2017-GCUF-058156

Sajal Murtaza 2017-GCUF-058185

Saif-ur-Rehman 2017-GCUF-058181

BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

GOVERNMENT COLLEGE UNIVERSITY, FAISALABAD

i
 College Management System

BY
Abdul Sammi Bhutta
2017-GCUF-058156
Sajal Murtaza
2017-GCUF-058185
Saif-ur-Rehman
2017-GCUF-058181

Project submitted by the fulfillment of the

requirement for the degree of

BACHELOR OF
COMPUTER SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

GOVERNMENT COLLEGE UNIVERSITY FAISALABAD

ii
 DECLARATION
We hereby declare that this project, neither whole nor as a part has been copied out from
any source. We have developed this project and accompanied report entirely on the basis of our
personal efforts. If any part of this project is proved to be copied out from any source. We will
stand by all the consequences. No Portion of the work presented has been submitted of any
application for any other degree of this or any other university or institute.

Signature of the Student

Name: Abdul Sammi Bhutta
Registration: 2017-GCUF-058156

Signature of the Student

Name: Sajal Murtaza
Registration: 2017-GCUF-058185

Signature of the Student

Name: Saif-ur-Rehman
Registration: 2017-GCUF-058181

iii
 PROJECT COMPLETION REPORT

Title of the project: CMS: College Management System

Project ID: ……………………

Student Name: Abdul Sammi Bhutta
Student Name: Sajal Murtaza
Student Name: Saif-ur-Rehman

Session: 2017-2021
Program: BS Computer Science

It is to certify that the title & proposal submitted by the students are clear and according
to project scope. It is further certifying that the project of the students may kindly be
process for external examiner/ viva voice.

Project Coordinator

Chairman

Department of Computer Science

Government College University Faisalabad

iv
CERTIFICATE BY THE PROJECT SUPERVISOR
This is to certify that the final year project of BS(CS) CMS(College Management
System) was developed by Sajal Murtaza, Abdul Sammi Bhutta AND Saif-ur-
Rehman supervised by Mr. Hafiz Moeez Amin and that in his opinion it is fully
adequate, for the degree of BS Computer Science.

Internal Examiner

Name:

Signature:

External Examiner

Name:

Signature:

Chairman:

Department Of Computer Science

Government College University Faisalabad

v
 ACKNOWLEDGMENT

We would like to express our gratitude to our adviser Mr. …………………

for his guidance and support, and his continuous enthusiasm and encouragement
throughout the project. We are also very thankful and extend our thanks to the
Heads and staff members of the department of CS & IT for their cooperation by
sharing the load and for giving time to work on this project.

Finally, thanks to the supervisor, who have helped and give us many suggestions,
supports and corrections during the project

6
Table of Contents
CHAPTER - 1 ..................................................................................................................................... 8

INTRODUCTION .............................................................................................................................. 8

1.1 Introduction .............................................................................................................................. 9

1.2 Background ............................................................................................................................... 9

1.3 Motivation ............................................................................................................................... 10

1.4 Objective ................................................................................................................................. 10

CHAPTER - 2 ................................................................................................................................... 12

SOFTWARE REQUIREMENTS AND SPECIFICATIONS ....................................................... 12

2.1 Project Introduction............................................................................................................... 13

2.2 Purpose of document .............................................................................................................. 13

2.3 Project Scope .......................................................................................................................... 13

2.4 Functional Requirements ...................................................................................................... 13

2.4.1 Admin: .................................................................................................................................. 14

2.4.2 Teacher: ............................................................................................................................... 14

2.4.3 Student: ................................................................................................................................ 14

2.5 Non Functional Requirement ................................................................................................ 14

2.5.1 Performance of Project .......................................................................................................... 15

2.5.2 Security ................................................................................................................................. 15

2.5.3 Safety: ................................................................................................................................... 15

2.5.4 Reliability: ............................................................................................................................. 16

2.5.5 Availability:........................................................................................................................... 16

2.5.6 Compatibility:........................................................................................................................ 16

2.5.7 Audience: .............................................................................................................................. 16

2.5.8 Detail Work: .......................................................................................................................... 16

2.6 TOOLS AND TECHNIQUES: ............................................................................................. 17

1
 2.6.1 BACK END: - ...................................................................................................................... 17

2.6.1.1 LARAVEL MVC: .............................................................................................................. 17

2.6.1.2 DATABASE: ..................................................................................................................... 17

2.6.1.3 My SQL:............................................................................................................................. 18

Working: ........................................................................................................................................ 18

2.6.1.4 VISUAL STUDIO CODE: ................................................................................................. 18

2.6.2 FRONT END: - .................................................................................................................... 18

2.6.2.1 HTML: ............................................................................................................................... 18

2.6.2.2 CSS:.................................................................................................................................... 19

2.6.2.3 BOOTSTRAP: ................................................................................................................... 19

2.6.2.4 BLADE TEMPLATE:........................................................................................................ 19

2.6.2.5 JQUERY: ........................................................................................................................... 19

2.6.2.6 JAVASCRIPT: ................................................................................................................... 20

CHAPTER-3 ..................................................................................................................................... 22

SOFTWARE ARCHITECTURE/DESIGN ................................................................................... 22

3.1 METHODOLOGY: ............................................................................................................... 23

3.2 User Management: ................................................................................................................. 23

3.2.1 User list: ................................................................................................................................ 24

3.2.2 User settings: ......................................................................................................................... 24

3.2.3 Easy to register: ..................................................................................................................... 24

3.2.4 Forgot password .................................................................................................................... 24

3.2.5 Search members: ................................................................................................................... 24

3.2.6 Update password: .................................................................................................................. 24

3.2.7 Access of profile: .................................................................................................................. 24

3.3 Role Management: ................................................................................................................. 25

Explanation: ................................................................................................................................... 25

3.3.1 Student Profile: ...................................................................................................................... 25

2
3.3.2 Administrative rights: ............................................................................................................ 25

3.4 Assumption ............................................................................................................................. 26

3.5 Use Case .................................................................................................................................. 26

3.6 Role Management................................................................................................................... 26

Explanation: ................................................................................................................................... 26

3.6.1 Admin: .................................................................................................................................. 28

Explanation: ................................................................................................................................... 28

3.6.2 Student: ................................................................................................................................ 29

Explanation: ................................................................................................................................... 98

3.6.3 Teacher: ................................................................................................................................. 98

Explanation: ................................................................................................................................... 99

4.1 Implementation: ................................................................................................................... 101

4.2 Database Tables: .................................................................................................................. 101

4.2.1 User Login:.......................................................................................................................... 101

Explaination: ................................................................................................................................ 101

4.2.2 Admin Login ....................................................................................................................... 102

4.2.3 Class-Section: ...................................................................................................................... 102

4.2.4 Class-Teachers: ................................................................................................................... 103

4.2.5 Student: ............................................................................................................................... 104

4.2.6 Student Attendance: ............................................................................................................ 105

4.2.7 Student Fee: ......................................................................................................................... 105

2.4.8 Student Fee Detail: .............................................................................................................. 106

2.4.9 Student Result: .................................................................................................................... 107

2.4.10 Subject: .............................................................................................................................. 107

2.4.11 Teacher Attendance: .......................................................................................................... 108

2.4.12 Teacher: ............................................................................................................................. 108

2.5 ER Diagram .......................................................................................................................... 111

3
Chapter – 5...................................................................................................................................... 113

Conclusions ..................................................................................................................................... 113

5.1 CONCLUSION: ................................................................................................................... 114

5.2 COMPLETING PROCESS: ............................................................................................... 114

5.3 Cost and Quality: ................................................................................................................. 114

5.4 Future Work: ........................................................................................................................ 115

5.4.1 Current scope: ..................................................................................................................... 115

5.4.2 Future Scope:....................................................................................................................... 115

CHAPTER-6 ................................................................................................................................... 117

USER MANUAL ............................................................................................................................ 117

6.1 SCREENSHOTS .................................................................................................................. 118

6.1.1 Home page: ......................................................................................................................... 118

6.1.2 About: .................................................................................................................................. 118

6.1.3 Courses: ............................................................................................................................... 119

6.1.4 Gallery: ................................................................................................................................ 119

6.1.5 Contact us: ........................................................................................................................... 119

6.1.6 Admin Login Page: ............................................................................................................. 120

6.1.7 Admin Dashboard: .............................................................................................................. 120

6.1.8 Course List: ......................................................................................................................... 121

6.1.9 Add Course:......................................................................................................................... 121

6.1.10 Class & Section List: ......................................................................................................... 122

6.1.11 Add Class & Section: ........................................................................................................ 122

6.1.12 Student List: ...................................................................................................................... 123

6.1.13 Student Attendance: .......................................................................................................... 123

6.1.14 Student Fee List:................................................................................................................ 124

6.1.15 Add Student Fee: ............................................................................................................... 124

6.1.16 Add New Student: ............................................................................................................. 125

4
 6.1.17 Teacher List: ...................................................................................................................... 125

6.1.18 Class Teacher List: ............................................................................................................ 126

6.1.19 Add Class Teacher: ........................................................................................................... 126

6.1.20 Teacher Attendance List:................................................................................................... 127

6.1.21 Mark Teacher Attendance: ................................................................................................ 128

6.1.22 Add New Teacher: ............................................................................................................ 129

6.1.23 Student Result: .................................................................................................................. 129

6.1.24 Add Student Result: .......................................................................................................... 130

6.1.25 Teacher Login Page:.......................................................................................................... 130

6.1.26 Teacher Dashboard:........................................................................................................... 131

6.1.27 Class Attendance List: ....................................................................................................... 131

6.1.28 Mark Class Attendance: .................................................................................................... 132

6.1.29 Teacher Attendance List:................................................................................................... 132

6.1.30 Student Result: .................................................................................................................. 133

6.1.31 Student Login Page: .......................................................................................................... 133

6.1.32 Student Dashboard: ........................................................................................................... 134

6.1.33 Student Attendance List: ................................................................................................... 134

6.1.34 Fee Voucher List: .............................................................................................................. 135

6.1.35 Student Result: .................................................................................................................. 135

Chapter – 7...................................................................................................................................... 136

Data Visualization .......................................................................................................................... 136

7.1 Software Testing:.................................................................................................................. 137

7.2 White Box Testing: ............................................................................................................... 137

7.3 Black box Testing: ................................................................................................................ 138

7.4 Unit Testing: ......................................................................................................................... 138

7.5 Integration Testing:.............................................................................................................. 139

7.6 System Testing: ..................................................................................................................... 139

5
7.8 Test scenario: ........................................................................................................................ 139

7.8.1 Login Test Scenario: ........................................................................................................... 139

6
Table of Figures

Figure 1:Architecture .................................................................................................................................. 23

Figure 2 Admin ........................................................................................................................................... 28
Figure 3 Student .......................................................................................................................................... 98
Figure 4 Teacher ......................................................................................................................................... 99
Figure 5 ER Diagram 1 ............................................................................................................................. 111
Figure 6 ER Diagram 2 ............................................................................................................................. 112
Figure 7 Iterative Waterfall Model ........................................................................................................... 114
Figure 8 Home Page.................................................................................................................................. 118
Figure 9 About .......................................................................................................................................... 118
Figure 10 Courses ..................................................................................................................................... 119
Figure 11 Gallery ...................................................................................................................................... 119
Figure 12 Contact Us ................................................................................................................................ 119
Figure 13 Admin Login Page:................................................................................................................... 120
Figure 14 Admin Dashboard:.................................................................................................................... 120
Figure 15 Course List: .............................................................................................................................. 121
Figure 16 Add Course: .............................................................................................................................. 121
Figure 17 Class & Section List: ................................................................................................................ 122
Figure 18 Add Class & Section: ............................................................................................................... 122
Figure 19 Student List:.............................................................................................................................. 123
Figure 20 Student Attendance:.................................................................................................................. 123
Figure 21 Student Fee List: ....................................................................................................................... 124
Figure 22 Add Student Fee: ...................................................................................................................... 124
Figure 23 Add New Student: .................................................................................................................... 125
Figure 24 Teacher List: ............................................................................................................................. 125
Figure 25 Class Teacher List: ................................................................................................................... 126
Figure 26 Add Class Teacher:................................................................................................................... 126
Figure 27 Teacher Attendance List: .......................................................................................................... 127
Figure 28 Mark Teacher Attendance: ....................................................................................................... 128
Figure 29 Add New Teacher: .................................................................................................................... 129
Figure 30 Student Result:.......................................................................................................................... 129
Figure 31 Add Student Result: .................................................................................................................. 130
Figure 32 Teacher Login Page: ................................................................................................................. 130
Figure 33 Teacher Dashboard: .................................................................................................................. 131
Figure 34 Class Attendance List: .............................................................................................................. 131
Figure 35 Mark Class Attendance:............................................................................................................ 132
Figure 36 Teacher Attendance List: .......................................................................................................... 132
Figure 37 Student Result:.......................................................................................................................... 133
Figure 38 Student Login Page:.................................................................................................................. 133
Figure 39 Student Dashboard: .................................................................................................................. 134
Figure 40 Student Attendance List: .......................................................................................................... 134
Figure 41 Fee Voucher List: ..................................................................................................................... 135
Figure 42 Student Result:.......................................................................................................................... 135

7
CHAPTER - 1

INTRODUCTION

8
1.1 Introduction
We have developed College Management System. It can handle a student's information
such as course, class section, attendance, result and fee information. It can also handle teacher’s
information. Manual systems require a lot of time, manpower, and other resources. Almost all of
the work is done on a computer here. As a result, the consistency is preserved. It's pretty simple
to keep a backup. It can be completed in a matter of minutes. Administrator and user access
options are available in our system. The administrator's responsibility is to insert updates and
oversee the entire process. When a user enters the system,

This system was created for the handling of student and instructor issues in the
educational system. The majority of educational establishments are not digital. The old manual
management method was inefficient and prone to numerous minor and significant errors. This is
the first step in transforming the old method of educational administration into a completely
automated one.

We supply this system to educational institutes to meet their management needs and to
assist them in replacing their existing management system with a more efficient and user-
friendly management system. It will improve their system and make it more efficient to manage.
The fundamental reason for the necessity for a College Management System is to make it easier
to supervise the college. The system aids in the exploration of all activities taking on within the
campus. It can manage information on students, Teachers, courses, and fee.

1.2 Background
The web site was a Web IT buzzword in the late 1990s. Many companies tried to find a
site after the emergence of the Web browser in the late 1990s. The online gateway has gotten
special attention because it is the first step for many users when they open their browser. A link
page is referred to as a portal when it provides information from a range of sources in an
integrated manner.

9
 Prior to the advent of the web portal era, organisations relied on a manual mechanism to
register students and send information to faculty members. It had been a long and exhausting
procedure. Manual testing of the student enrolment system is time-consuming and inefficient,
causing delays in the enrollment process. It's a waste of everyone's time and effort. Because of
the long wait throughout the registration process, it was a waste of people's time and effort. Such
reports may be misplaced or lost as a result of data collection processes. The College
Management System was launched after thinking about these issues. There may be resources on
the student site. Search engine optimization, email, news, and information are all services
provided by these companies. In other words, it encourages students to have easy access to
information and materials. Members of the faculty can supply all essential information and
resources for their students through the portal, and students' information can be found on the
website. The amount of content and style on the College’s website do not fulfill student
expectations or modern needs.

In order to meet student expectations, institutions are spending millions of dollars to

construct and remodel websites that claim students are insufficient and lack basic functions. To
date, this research has looked into the elements that influence student admittance to college
websites. To satisfy students' expectations, we created a simple, efficient, and portal system that
eliminates confusion by separating student, teacher, and administrator portals.

1.3 Motivation
We were inspired by the fact that it was a simultaneous scenario project. It has never
been used in a low-level educational setting. When it is implemented in the educational system,
it becomes bug-free and simple to use, allowing it to be implementsed in other local institutes.
We shall advocate for a growing mindset rather than a fixed one. We receive recognition from
the school system, which has a significant impact on our long-term aims. The first step in
automating the local institutes will be this.

1.4 Objective
1. The old system is being replaced with a contemporary computerized system.

10
2. To keep educational institutions' management systems in good shape.
3. A method of management that is quick and requires little time.
4. It is simple to move from the top to the bottom and from the bottom to the top.
5. Providing a single location for students to access all information.
7. Students, instructors, and administrative personnel should benefit from the suggested system.

11
 CHAPTER - 2

SOFTWARE REQUIREMENTS AND SPECIFICATIONS

12
2.1 Project Introduction

Every firm relies heavily on effective communication. According to the report, In today's
globe, the world is progressing toward technology, but most low-level institutes are still stuck in
the past. For many years, the handbook has been in use, and institutes that use the portal system
are experiencing issues such as a drab look and a dearth of information. It is a challenge for us to
groom our low-level educational institute system by delivering an effective system that is full of
basic facts.

We supply this College Management System to educational institutes to meet their

management needs and to assist them in replacing their existing management system with a more
efficient and user-friendly management system.

2.2 Purpose of document

The documentation's goal is to make the College Management functional and non-
functional requirements understandable to end users (Students, Teachers, and Administrators).
Every student, teacher, and administrator has their own account, which contains all of their
information. Any student can see his or her academic record.

2.3 Project Scope

The project scope is broad since it is a high-level project; if low-level institutes stay
manual and hazy, their students will be unable to compete in the technological world. This will
make it easier for them to communicate with their students. It will almost entirely satisfy the
organization's and students' expectations.

2.4 Functional Requirements

The term "functional requirements" refers to a list of services that the software must
provide. It's a term that refers to a software system or its components. The following are the
functional requirements for our software.

13
2.4.1 Admin:

1. The expert will generate a user ID and password, which will be assigned to the students
and teachers by the administrator.

2. Oversee all of the modules (Admin, Teacher, Student).

3. The administrator has complete control over all legal and unlawful actions on the
platform.

4. Any difficulty will be reported by the student to the administration office, who will then
rectify the issue at the portal.

2.4.2 Teacher:

The teacher will be able to complete several duties after logging in.

1. When students enter the classroom, the teachers will record their attendance on the portal.

2. Teachers can view and print their profile.

3. Teachers can download the result of students which is uploaded by the admin.

4. Teachers can view and print their attendance.

2.4.3 Student:

1. Updates uploaded by administrators can be viewed by students on the site.

2. Students can view and print their profile.

3. Students can examine information about their dues such as fee.

4. Students can get their results and also print their fee voucher.

5. Students can download the result that are available in PDF format.

2.5 Non Functional Requirement

14
2.5.1 Performance of Project

The technology is suitable for quick responses. This project will be completed entirely
online. In approximately 2-3 seconds, the user must be able to sign in and receive responses to
their queries. Maintain all records regarding students and teachers in the institute. The project
involves retrieving information via an internet-based portal.

2.5.2 Security

1. All passwords that are generated or approved must be encrypted and kept in a database.

2. Each of the generated IDs must be unique.

3. Each module has its own account, complete with its own ID and password.

4. The user has limited access, which is granted by the administrator.

5. No one can access the user's personal information through the portal unless they are an
authentic individual.

2.5.3 Safety:

1. If the system administrator discovers a security issue, the system should be able to be
shut down.

2. Admin can quickly disable all connections to the server in order to preserve previously
saved documents.

3. The system crash does not damage the entire database; other modules can recover it.

4. In order for the document to be produced, the system must be able to recover from past
damage and proceed.

5. The system should notify the administrator if the system is malfunctioning.

15
2.5.4 Reliability:

Participants in current research have proven that portals, like other methods of spreading
knowledge to other students at their colleges, have the advantage of being always open and
accessible. The portal is the finest way to learn new information about what is going on campus,
according to the students. Our project has the capability of continuously sharing information over
the portal for hours.

2.5.5 Availability:

It is dependent on the system's reliability and ability to function properly. Except for
scheduled maintenance tasks, the CMS Portal will be online, up and running 24 hours a day,
seven days a week throughout the year. If the system is reliable and functions properly, the
system will be available at all times. Because our system is dependable, it will be accessible
every time a user logs in.

2.5.6 Compatibility:

A good digital platform can boost engagement, boost institutional legitimacy, and boost
user satisfaction. You can do all of that and more with College Management System Mobiles,
tablets, and desktops are all part of a unified platform that is interoperable with every device
environment. It is cross-platform and cross-environment compatible. It will be a secure platform
with multi-factor authentication. Our system can work with any type of Windows plate. Any web
browser will be supported.

2.5.7 Audience:

Our target audience for the system will be the institute's students, teachers, and
administrator. As a result, the paper is critical to their understanding of the system. They will be
able to operate the system with ease.

2.5.8 Detail Work:

Different modules can be used to describe College Management System. Each of these
modules has a distinct purpose. Three basic modules are in action here, each doing its job. The

16
administrator module is the first. Who will have the authority to add users (Teachers, Students).

The second module is the teacher module, which provides them with their own profile.
On a daily basis, mark attendance on the attendance form. Results should be uploaded to the site.

The third module is the student module. The student module allows them to access their
profile have been assigned to them. Student can view his or her dues, such as fee. They can also
access the portal to obtain a result. The attendance record of a student can be viewed by them.
Students who have not paid all of their dues might be added on the late fee list by the admin.

2.6 TOOLS AND TECHNIQUES:

2.6.1 BACK END: -

2.6.1.1 LARAVEL MVC:

Laravel is an open-source PHP web framework created by Taylor Otwell. It is intended

for the development of web applications that follow the model–view–controller (MVC)
architectural pattern. MVC (Model-View-Controller) is a design pattern that divides an
application into three logical components: model, viewing, and control. The database, user, and
data processing components' back and back limits are provided by MVC. The separation of
software before and after it improves software development and partition maintenance.

MVC stands for Concept View Controller. It is a three-part application architecture

model. Model (data), view (user interface), and controller are all included (input handling
processes). The MVC model or "pattern" is widely used to improve modern user methods. Basic
components for creating desktop and mobile applications, as well as web applications. It works
well with an object-oriented program because different models, views, and controllers can be
treated as objects and reused within the application.

2.6.1.2 DATABASE:

A database, in particular, is an electronic programme that allows data to be easily

accessed, controlled, and manipulated and it has been updated. In other terms, a database is a
system that allows a company to store, manage, and retrieve data. A data management system is

17
used to manage modern data (DBMS).

2.6.1.3 My SQL:

My SQL is a relational database management system that is free and open-source

(RDBMS). "My" is the name of co-founder Michael Widenius's daughter, and "SQL" is the
abbreviation for Structured Query Language. Data warehousing, e-commerce, and logging
applications are just a few of the uses for the application. However, the most popular application
of My SQL is as a web database.

Working:

• My SQL generates a database to store and manipulate data, with each table's relationship
defined.
• Clients can submit requests to My SQL by inputting specified SQL statements.
• The requested information will be returned by the server application and displayed on the
clients' side.

2.6.1.4 VISUAL STUDIO CODE:

Visual Studio Code is a lightweight code editor that includes features for debugging, task
execution, and version management. It seeks to give developers only the tools they need for a
rapid code-build-debug cycle, leaving more involved workflows to full-featured IDEs like Visual
Studio IDE.

2.6.2 FRONT END: -

2.6.2.1 HTML:

HTML (Hyper Text Markup Language) is the most extensively used language for
creating web pages links to other websites. HTML is a markup language that specifies text tags
that tell a web browser how to alter the display. HTML was created with the intention of
specifying the structure of texts such as titles, categories, lists, and other elements in order to
improve the sharing of scientific data among researchers.

18
2.6.2.2 CSS:

CSS is an acronyms for Cascading Style Sheets. CSS specifies how HTML elements
should appear on a screen, in print, or in other media. It saves a lot of time and allows you to
control the creation of several web pages at the same time. CSS files are used to store external
styles.

2.6.2.3 BOOTSTRAP:

Bootstrap is a framework for creating websites (pre-end-frame) Bootstrap is a free and

open source CSS framework for developing responsive websites for the first time. For typing
formats, forms, buttons, navigation, and other links, it includes a CSS and (optional) JavaScript
template. Bootstrap is a robust ultimate framework for developing modern websites and online
apps. It's a free and easy-to-use library, but it comes with a lot of HTML and CSS templates for
UI connecting components like buttons and forms. JavaScript extensions are also supported by
Bootstrap.

2.6.2.4 BLADE TEMPLATE:

In the Laravel framework, the Blade is a powerful templating engine. The blade
templating engine has its own structure, which includes conditionals and loops. To make a blade
template, simply create a view file and save it.

Blade templates are usually kept in the resources/views directory in PHP. The main
benefit of using the blade template engine is that it allows you to construct a master template that
can be expanded by adding additional individual pages.

2.6.2.5 JQUERY:

For speedier website construction, J Query is a small and fast JavaScript library that may
be used to ease event management, HTML transcript, Ajax interaction, and pictures. J query
makes it easier to write HTML client. The JavaScript library's J question is simple: "write less,
do more." The goal of j query is to make using JavaScript on your website easier. J query tackles
a number of typical activities that might otherwise necessitate numerous lines of JavaScript code
and replaces them with what you would term a single line of code.

19
2.6.2.6 JAVASCRIPT:

The signature language for clients is commonly JavaScript. This indicates that the
JavaScript code is embedded in the HTML document. When a user requests an HTML page that
contains JavaScript, the script is transmitted to the browser, which then has to deal with it.
JavaScript is a popular programming language that may be used to add automation, pictures, and
connections to Web pages. JavaScript is used by web developers for everything from simple
activities to complicated Web pages that operate like desktop software.

20
21
 CHAPTER-3

SOFTWARE ARCHITECTURE/DESIGN

22
3.1 METHODOLOGY:

We developed our system using the software development life cycle. In the development
of our system, we use the waterfall model. The waterfall model is a model of SDLC (Software
Development Life Cycle) which is a combination of two process models incremental and
iterative. CMS is developed on the basis of iterative process model of the waterfall model which
allows the user to feedback paths from every phase to its preceding phases.

ADMIN/TEACHER/
STUDENT

ADMIN TEACHER STUDENT

ADD ADD ADD

ROLES ROLES ROLES
Manage and Teachers can Student can
update the view their view their DATABASE
record of profile and profile,
students and attendance and attendance and
teachers. can also mark fee details.
the student’s
attendance.

Figure 1:Architecture

3.2 User Management:

23
 3.2.1 User list:

1. ADMIN

2. TEACHER

3. STUDENT

On the website's homepage, there is a list of registered users.

3.2.2 User settings:

The admin can change personal information, such as their name, date of birth,
country, city, profile photo, and bio.

3.2.3 Easy to register:

The admin can quickly and easily register by filling out the relevant information
on a simple page.

3.2.4 Forgot password

If the user forgets his password, then he approach to administrator office to reset
his password.

3.2.5 Search members:

A user can look for a specific category, country, level, or keyword like name.

3.2.6 Update password:

The admin can update the password of users.

3.2.7 Access of profile:

Your system only lets you manage your user profile and doesn't let you access all
of the functions.

24
3.3 Role Management:

In the software development process, the project management role is the first. The project
manager does not perform "real work." The project management function is intended to assist in
ensuring that the software development process runs smoothly. The project manager's job is to
promote, motivate, and priorities the process in conjunction with the development manager's job.

Due to the evolution of project management as a function, the role of project

management is perhaps the most well defined role within the software development process.

In this project, three jobs are defined.

1. Administrator

2. Teachers

3. Students

Explanation:

Everyone has their own individual dashboard and role. We demonstrated in our web app
that when a person log in, he may see his profile. When it comes to the administrator, he has the
authority to register or not register a user. Others may not be able to take use of this type of
service. After allowing the administrator, a user can register and see the document according to
their designation. If an unauthorized user wants to view a restricted page, he can go to the
dashboard that we have specified in our programme, thus there is no way for an unauthorized
user to update the software.

3.3.1 Student Profile:

We can quickly find out the student's description. Picture of the student, information
about bios of the student are all included in the student profile. Administrators can utilise the
information to track a student's interests and personality traits, as well as to notify him/her.
Administrators usually have full access to all profile data.

3.3.2 Administrative rights:

25
 A college registration form is a document that is used to enroll new students at a college.
With our Student Registration Forms, where admin can quickly gather contact information, and
supporting documents online to cut out manual paperwork, save time, and organize your records.
User will be adding by the allowance of administrative person. Administrator have a power to
create, delete, and change items.

An administrator is a local account or a local security group on a computer who has

complete and unlimited access to create, delete, and edit files. This is in contrast to other types of
user accounts that have only been granted specific permissions and levels of access. An
administrator account is used to make system-wide changes to the computer, such as:

• On the system, creating or removing user accounts.

• Creating passwords for other computer users' accounts.

• Changing others' account names, pictures and passwords.

3.4 Assumption

➢ The coding should be flawless.

➢ To access their accounts and take action, users must have the necessary usernames and
passwords.

➢ The application should be user-friendly, making it simple for the user to use.

➢ Every user's accurate information must be saved in a database that the website can access.

3.5 Use Case

This is an example of how to use an action list or an event list. The activities of this
software are depicted in this diagram.

3.6 Role Management

Explanation:

26
 Due to the evolution of project management as a function, the role of project
management is perhaps the most well defined within the software development process.

In this project, three jobs are defined.

1. Admin

2. Teachers

3. Students

27
3.6.1 Admin:

Figure 2 Admin
Explanation:

The system is managed by the administrator. The person in charge of all actions is the
administrator. Some of the most typical repair activities are available in the maintenance
component. When you click on a link to add a word, it will be added to that category right away.
System updates are included in the update phase. Finding faults or difficulties and reporting them
to the expert is part of reporting.

The following are some of the administratively controlled activities:

1. System maintenance.

2. System updating.

3. System reporting.

28
3.6.2 Student:

29
 Figure 3 Student
Explanation:

The dashboard is the portal's main page, which students will see after logging in. The student dashboard is
an online tool that allows students to see how they are progressing in their studies. Many features are available on
the dashboard, including:

1. Details about the fee can be found here.

2. View the attendance list.

3. View the result.

3.6.3 Teacher:
98
 Figure 4 Teacher
Explanation:

Teachers log in to their portal by entering their user name and password on the log in page. After logging
in, the teacher is taken to the dashboard. Different features of a teacher's dashboard include:

1. Download the result that is uploaded by the admin.

2. Manage student attendance.

3. View their own profile and attendance.

99
 Chapter – 4

IMPLEMENTATION

100
4.1 Implementation:

This is the phase in which the system was recognised the technology outlined in the design phase served as
the foundation for the system's development one of the objectives in this phase was to plan.

As we mentioned at the start of the previous chapter about the modules in this system, we'll go over them
one by one, starting the programme one at a time, to show how each phase is completed. We'll look at the network
rating, which will define how many computers a client will utilise, as well as software updates and anunique
requirement that will lead to the creation of a client/network server.

Every company will be assigned to a single server network. This allows for the separation of the number of
file services, the maintenance of rigorous network environment control, workflow, and storage teams, as well as
easy management and network server configuration installation.

The following variables must be taken into account in order for the project to be successful.

1. Design the launch programme by incorporating low-cost elements.

2. Registration data management over the internet.

3. Continue to upgrade and improve the infrastructure and systems that have been put in place.

4. Network types that have been used.

4.2 Database Tables:

4.2.1 User Login:

Id User-Role Username Password

1 Teacher Arslan Manaarsal
2 Student Sajal Sajalmrur
3 Student Zainab iqra2233
4 Student Akarma akarma11
5 Student Fahad fahad456

Explaination:

101
 The login database is shown in this diagram. The CMS(College Management System) database is created
with MySQL. The table consist of User id, User role, User name and Password. The user id is the login page's
primary key. The data used for login is stored in a table on the login page. The table's data type properties are as
follows:

1. The data type of the user id is int.

2. The data type for username is nvarchar.

3. Password have nvarchar data type.

4.2.2 Admin Login

Id Name Email Password

1 Super Admin admin@admin.com Password

The database table for admin is shown in the diagram above. There is only one admin in the system. Admin
database contains admin Id, admin name, admin email, and admin password. The primary key in the admin
database table is admin id. Attributes in admin tables have the following data types:

1. The data type of the admin id is int.

2. The data type of admin name is nvarchar.

3. The data type of admin email is nvarchar.

4. The data type of password is nvarchar.

4.2.3 Class-Section:

Id Class title Section name Subject Id Seats

4 11th A 5 5
5 12th A 6 5
6 11th B 7 5
7 12th B 8 5
8 11th C 9 5

The class section database is shown in this diagram. Class section database contains id, class title, section
name, subject id and seats. The primary key in the class section database table is id. The foreign key in the class
102
section is subject id. Attributes in class section tables have the following data type.

1. The data type of class section id is int.

2. The data type of the class title is nvarchar in the class section database table.

3. The data type of the section name is nvarchar in the class section database table.

4. The data type of the subject id is int in the class section database table.

5. The data type of the seats is int in the class section database table.

4.2.4 Class-Teachers:

Id Teacher Id Class Section Id

4 5 8
5 6 6
6 7 10
7 8 11
8 10 7

The database table for class teacher is shown in the diagram above. Class teacher database contains id,
teacher id and class section id. The primary key in the class teacher database table is id. The foreign key in the class
teacher database table are teacher id, class section id. Attributes in class teacher table have the following data type.

1. The data type of class teacher id is int.

2. The data type of teacher id, class section id is int.

103
4.2.5 Student:

User name Student roll no Student name Student f name Student CNIC

Sajal 11th-2021-001 SajalMurtaza GhulamMurtaza 3630298783359

Iqra 11th-2021-002 Iqra Sultan Sultan Ahmad 3630289885586

Ramsha 11th-2021-003 Ramsha Sajjad Muhammad Sajjad 3630268046728

Sana 11th-2021-003 Sana Khan Arbaz Khan 3630265432789

Akarma 11th-2021-004 Akarma Haider Khalid Shamshad 3630276429875

Student_email DOB Gender Address Password

Sajalmurtaza@gmail.com 1999-03-06 Female Afzal City Sajalmur
Iqrasultan@gmail.com 1999-09-02 Female Multan Iqra1234
ramshasajjad@gmail.com 1998-08-04 Female Multan Ramsha231
sanakhan@gnail.com 1999-07-16 Female Multan Sana2233
akarmahaider@gmail.co 1997-09-19 Male Multan Akarma11
m

The database table for student is shown in the diagram above. Student database contains id, username,
student roll no, student name, student father name, student CNIC, student email, DOB, gender, address and
password. The primary key in the student table is id. Attributes in student table have the following data type.

1. The data type of student id is int.

2. The data type of the username is varchar.

3. The data type of the student roll no is varchar.

4. The data type of the student name is varchar.

5. The data type of the student father name is varchar.

6. The data type of the student CNIC is varchar.

7. The data type of the student email is varchar.

104
 8. The data type of the student DOB(date of birth) is date .

9. The data type of the gender is varchar.

10. The data type of the address is varchar.

11. The data type of the password is varchar.

4.2.6 Student Attendance:

Id Student Class Section Attendance Attendance

Date
4 8 5 2021-08-21 Present
5 9 5 2021-08-21 Present
6 10 5 2021-08-21 Present
7 11 5 2021-08-21 Absent
8 12 5 2021-08-21 Present

The database table for student is shown in the diagram above.. The student attendance database table
contains id, student, class section, attendance and attendance date. The primary key in the student table is id. The
foreign key in the student database table are student and class section. Attributes in student attendance table have
the following data type

1. The data type of student attendance id is int.

2. The data type of student is int.

3. The data type of class section is int.

4. The data type of attendance is varchar.

5. The data type of attendance date varchar.

4.2.7 Student Fee:

Id Student Studen Fee Paid Fee Remaining Invoice

Fee Number
3 3 36000 3000 33000 #101
4 4 36000 6000 30000 #102

105
5 5 36000 5000 31000 #103
6 6 36000 7000 29000 #104
7 7 36000 7000 29000 #105

The database table for student fee is shown in the diagram above. The student fee database table contains id,
student, student fee, paid fee, remaining fee, invoice number. The primary key in the student fee table is id. The
foreign key in the student database table is student. Attributes in student fee table have the following data type.

1. The data type of student fee id is int.

2. The data type of student is int.

3. The data type of student fee is varchar.

4. The data type of paid fee is varchar.

5. The data type of remaining fee is varchar.

6. The data type of invoice number is varchar.

2.4.8 Student Fee Detail:

Id Student Fee Invoice Fee of month Paid Is Paid

fee Amount Number date
25 3 2750 #101-0 2021-08-01 Nill 0
26 3 2750 #101-1 2021-09-01 Nill 0
27 3 2750 #101-2 2021-10-01 Nill 0
28 4 2750 #101-0 2021-08-01 Nill 0
29 4 2750 #101-1 2021-09-01 Nill 0

The database table for student fee detail is shown in the diagram above. The student fee detail database
table contains id, student fee, fee amount, invoice number, fee of month, paid date, is paid. The primary key in the
student fee detail table is id. The foreign key in the student database table is student fee. Attributes in student fee
detail table have the following data type.

1. The data type of student fee detail id is int.

2. The data type of student fee is int.

3. The data type of fee amount is varchar.

106
 4. The data type of invoice number is varchar.

5. The data type of fee of month is varchar.

6. The data type of paid date is varchar.

7. The data type of is paid is varchar.

2.4.9 Student Result:

Id Class-Section Result-Title Result

2 4 Annual Result/1629534397 BS Computer
Science
3 4 Mid Term results/1630312236CamScanner
4 4 Annual results/1630313180BS-CS-179.pdf

The database table for student result is shown in the diagram above. The student result database table
contains id, class section, result title. result. The primary key in the student result table is id. The foreign key in the
student result table is class section. Attributes in student result table have the following data type.

1. The data type of student result id is int.

2. The data type of class section is int.

3. The data type of result title is varchar.

4. The data type of result is varchar.

2.4.10 Subject:

Id Course Title Subjects Practical Subjects

5 F.S.C (Pre-Engineering)-Ⅰ Physics/Chemistry/Math Physics/Chemistry
6 F.S.C (Pre-Engineering)-Ⅱ Physics/Chemistry/Math Physics/Chemistry
7 F.S.C (Pre-Medical)-Ⅰ Physics/Chemistry/Bio Physics/Chemistry/Bio
8 F.S.C (Pre-Medical)-ⅠI Physics/Chemistry/Bio Physics/Chemistry/Bio
9 ICS-I Physics/Math/Computer Physics/Computer

The database table for subject is shown in the diagram above. The student subject database table contains
id, course title, subjects, Practical subjects. The primary key in the subject table is id. Attributes in subject table
have the following data type.
107
 1. The data type of subject id is int.

2. The data type of course title is varchar.

3. The data type of subjects is varchar.

4. The data type of practical subjects is varchar.

2.4.11 Teacher Attendance:

Id Teacher Attendance date Attendance

15 12 2021-08-21 Present
16 11 2021-08-21 Absent
17 10 2021-08-21 Present
18 9 2021-08-21 Present
19 8 2021-08-21 Present

The database table for Teacher attendance is shown in the diagram above. The Teacher attendance database
table contains id, teacher, attendance date, attendance. The primary key in the teacher attendance is id. The foreign
key in the teacher attendance is teacher. Attributes in teacher attendance table have the following data type.

1. The data type of teacher attendance id is int.

2. The data type of teacher is int.

3. The data type of attendance date is varchar.

4. The data type of attendance is

2.4.12 Teacher:

Id Teacher Id User-Name Password Teacher-Name Teacher-Father-Name

5 169 Arslam monaarsal ArslanIftikhar Iftikhar
6 179 Faheem Faheem34 Faheem Khan Bashir Ahmed
7 189 Hammad Hammad21 Hammad Khan Lal Muhammad
8 199 Hassnain Hassnain9 Hassnain Bhatti Aziz Bhatti

Teacher- Teacher Is-Class- Teacher CNIC Teacher=DOB

Qualification Phone teacher
108
MPhil Computer 0313-8992200 Yes 3630299724467 1990-08-02
Science
MPhil Biology 0313-6078606 Yes 3630265432319 1987-01-12
MPhil English 03138654209 Yes 3630255885539 1980-11-24
MPhil Urdu 03048982678 Yes 3630257688569 1990-12-01

Teacher-Email Teacher- Teacher - Teacher- Teacher-

Address Religion Designation Gender
itsmeiftikhar@gmail.com MDA Chowk Islam Permanent Male
Faheemkhan@gmail.com MDA Chowk Islam Permanent Male
Hammadkhan@gmail.com Wapda Town Islam Senior Male
Hasnainbhatti@gmail.com Kashmir Islam Visitor Male
Chowk

The database table for Teacher is shown in the diagram above. The Teacher database table contains id,
teacher id, user name, password, teacher name, teacher father name, teacher qualification, teacher phone, is class
teacher, teacher CNIC, teacher = DOB, teacher email, teacher address, teacher religion, teacher designation,
teacher gender. The primary key in the teacher table is id. Attributes in teacher table have the following data type.

1. The data type of id is int.

2. The data type of teacher id is varchar.

3. The data type of username is varchar.

4. The data type of password is varchar.

5. The data type of teacher name is varchar.

6. The data type of teacher father name is varchar.

7. The data type of teacher qualification is varchar.

8. The data type of teacher phone is varchar.

9. The data type of is class teacher varchar.

10. The data type of teacher CNIC is varchar.

109
11. The data type of teacher DOB is varchar.

12. The data type of teacher email is varchar.

13. The data type of teacher address is varchar.

14. The data type of teacher religion is varchar.

15. The data type of teacher designation is varchar.

16. The data type of teacher gender varchar.

110
2.5 ER Diagram

Figure 5 ER Diagram 1

111
Figure 6 ER Diagram 2

112
Chapter – 5

Conclusions

113
5.1 CONCLUSION:

1. We offer this technology to educational institutions in order to meet their internal communication needs.

2. In educational institutions, a good management system is essential.

3. With little time available, a quick management method is used.

4. Easy transitions from the top to the bottom and from the bottom to the top are possible.

5. Provide pupils with a single location where they may access all information.

6. This system is useful for Teachers, Students, and Administrator.

7. Easy access and resolution of all issues involving Students or teachers.

5.2 COMPLETING PROCESS:

We chose this project since similar concepts are popular these days. We chose this concept since we are
eager to produce something in this subject and are becoming increasingly interested. On their portal, students can
find out everything they need to know about themselves. The process is designed to be a comprehensive
description of all managerial and operational tasks carried out by a college.

Figure 7 Iterative Waterfall Model

5.3 Cost and Quality:
114
 1. Our programme includes numerous capabilities, including the ability to add students, teachers.

2. The portal project is free of charge, thanks to the hard work that went into developing the tools.

3. It is not very expensive department users can log in and utilise it for free.

4. This software is superior to other software in terms of quality since it provides excellent security.

5.4 Future Work:

5.4.1 Current scope:

Our current scope is as follows:

1. Using an computerized system, make the education system more efficient.

2. It also eliminates the drawbacks of the manual system.

3. It clears the air of ambiguity and uncertainty.

4. It delivers clear and relevant information that is simple to utilize.

5. Organizing all of the necessary elements for a successful college separation.

6. Many colleges have adopted this unique technology-based approach as part of their division Administrative.

5.4.2 Future Scope:

We'll improve the software's reliability by doing the following:

1. Instead of specific features, we shall introduce more diverse ones.

2. Using sophisticated technologies, we can make it more advanced.

3. Users most recent views or requirements will be used to update this system.

4. We will create software that is completely user-friendly.

5. Because this tool is free, it can be used by any college.

6. After deployment to production, support and maintenance.

115
116
 CHAPTER-6

USER MANUAL

117
6.1 SCREENSHOTS

6.1.1 Home page:

Figure 8 Home Page

6.1.2 About:

Figure 9 About

118
6.1.3 Courses:

Figure 10 Courses
6.1.4 Gallery:

Figure 11 Gallery
6.1.5 Contact us:

Figure 12 Contact Us

119
6.1.6 Admin Login Page:

Figure 13 Admin Login Page:

6.1.7 Admin Dashboard:

Figure 14 Admin Dashboard:

120
6.1.8 Course List:

Figure 15 Course List:

6.1.9 Add Course:

Figure 16 Add Course:

121
6.1.10 Class & Section List:

Figure 17 Class & Section List:

6.1.11 Add Class & Section:

Figure 18 Add Class & Section:

122
6.1.12 Student List:

Figure 19 Student List:

6.1.13 Student Attendance:

Figure 20 Student Attendance:

123
6.1.14 Student Fee List:

Figure 21 Student Fee List:

6.1.15 Add Student Fee:

Figure 22 Add Student Fee:

124
6.1.16 Add New Student:

Figure 23 Add New Student:

6.1.17 Teacher List:

Figure 24 Teacher List:

125
6.1.18 Class Teacher List:

Figure 25 Class Teacher List:

6.1.19 Add Class Teacher:

Figure 26 Add Class Teacher:

126
6.1.20 Teacher Attendance List:

Figure 27 Teacher Attendance List:

127
6.1.21 Mark Teacher Attendance:

Figure 28 Mark Teacher Attendance:

128
6.1.22 Add New Teacher:

Figure 29 Add New Teacher:

6.1.23 Student Result:

Figure 30 Student Result:

129
6.1.24 Add Student Result:

Figure 31 Add Student Result:

6.1.25 Teacher Login Page:

Figure 32 Teacher Login Page:

130
6.1.26 Teacher Dashboard:

Figure 33 Teacher Dashboard:

6.1.27 Class Attendance List:

Figure 34 Class Attendance List:

131
6.1.28 Mark Class Attendance:

Figure 35 Mark Class Attendance:

6.1.29 Teacher Attendance List:

Figure 36 Teacher Attendance List:

132
6.1.30 Student Result:

Figure 37 Student Result:

6.1.31 Student Login Page:

Figure 38 Student Login Page:

133
6.1.32 Student Dashboard:

Figure 39 Student Dashboard:

6.1.33 Student Attendance List:

Figure 40 Student Attendance List:

134
6.1.34 Fee Voucher List:

Figure 41 Fee Voucher List:

6.1.35 Student Result:

Figure 42 Student Result:

135
 Chapter – 7

Data Visualization

136
7.1 Software Testing:

It gathers all of the pieces in a dedicated testing area, where they are examined for bugs, pests, and
interactions. The process of testing software products is known as software testing. Effective software testing will
result in higher-quality software products, happier users, lower repair costs, more accurate results, and more
dependable results. Ineffective testing, on the other hand, will result in low-quality items, dissatisfied users,
growing storage costs, and unreliable and direct outcomes. Testing is the most common method of quality control
in software development. Its primary purpose is to discover software flaws. It's an extremely expensive process,
costing one-third to one-half of the average development project. Testing is the process of creating a programme
(or a component of a programme) with the goal of discovering errors; nevertheless, testing cannot verify the
absence of faults, but it can indicate that errors do exist.

"Errors can be found in even the most thoroughly tested software."

This was not the purpose of the programme developers, who should have created the software with the goal
of generating it error-free. Software testing is becoming more critical in the early stages of the software
development life cycle, with the goal of detecting mistakes before they get deeply established in systems. The
earlier in the software's life cycle the first problems are discovered and corrected, the lower the cost of correcting
them. The most dangerous faults are those that go undetected during testing and so continue once the system is
turned on.

Testing requires the detection of faults in software by developers. It's quite tough for a software developer
to spot flaws in his work. A good test is one that has a high chance of uncovering an undiscovered flaw. A
successful test case uncovers an inaccuracy that was previously undetectable. This means that the test will look for
problems created not just during the coding process, but also in preceding stages. The goal of the test is to find the
required flaws, construct the systems, and encrypt them.

7.2 White Box Testing:

The white box test is a form of software testing in which the tester is aware of the system internal structure
and implementation. The tester chooses the input for which the methods in the code will be applied, and then
determines the proper results. Information about the system and how it is used is critical. From the end to the
preceding amount, this is done and checked for each field entry (Database). It is completed at the planning stage.
There are necessary improvements made to ensure that the modules in the system perform efficiently in terms of
the expected module departure.
137
 All of the choices were thoroughly examined. The White Box exam is more user-friendly and focuses on
the system's details. This method is named after the software system's resemblance to a white / visible box in the
eyes of the tester; within which one can clearly see.

7.3 Black box Testing:

Black Box Testing is a type of software testing in which the functionalities of software applications are
tested without knowledge of the internal code structure, implementation details, or internal routes. Black Box
Testing is a type of software testing that focuses on the input and output of software applications and is totally
driven by software requirements and specifications. Behavioral testing is another name for it.

The following categories of errors are targeted by this method:

1. Jobs that are invalid or missing

2. Data structure errors or external access to data
3. Errors in behaviour or performance

7.4 Unit Testing:

Unit testing is a type of software testing that examines specific software units or components. The goal is to
make sure that each software unit works as intended. The smallest component that may be tested in any software is
the unit. One or a few inputs are frequently present, with one being the most common. The module is
independently tested and is usually done at the same time as the module coding in our team. The goal is to discover
encoding issues by using various parts of the module code. We test each table field and it works well according to
unit intelligence testing.

138
7.5 Integration Testing:

Individual modules are integrated and tested as a team during integration testing, which is a type of
software testing. The goal of this test level is to find communication issues between integrated units. It's utilised in
Integration testing to help with test drivers and test tubes. Modules are gradually incorporated into subsurface
systems, and finally the complete system is integrated. Integration testing focuses on testing the links between our
project elements in order to uncover design problems.

7.6 System Testing:

System testing is a type of testing that verifies that a software product is complete and integrated. The
system test's goal is to determine the system's final state. Software is frequently only one component of a larger
computer-based application. The programme is finished once it has been compiled. The system is reviewed based
on its requirement to see if all of the requirements have been met and if the system is performing as expected.

7.8 Test scenario:

7.8.1 Login Test Scenario:

Expected
Scenario Username Password Results
Outcome
Redirect to
Login Null Password Same
login
Redirect to
Ambiguous Null Same
login
Redirect to
Null Ambiguous Same
login
Redirect to
Correct Ambiguous Same
login

139
 Redirect to
Ambiguous Correct Same
login
Redirect to
Correct Correct Same
Dashboard

Table: Test Case Login

140