Car Driving School Management System

Undertaken By:
MUHAMMAD ASIM RIAZ
REG. NO. CIIT/FA20-BSE-001/VEHARI

HARIS ALI
REG. NO. CIIT/FA20-BSE-065/VEHARI

Supervised By:
UMER RASHEED

DEPARTMENT OF COMPUTER SCIENCES

COMSATS UNIVESITY ISLAMABAD, VEHARI CAMPUS

VEHARI – PAKISTAN (SESSION 2020-2024)

 DECLARATION
We hereby declare that this software, neither whole nor as a part has been copied out from
any source. It is further declared that we have developed this software 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 or found to be reproduction of some other. We will stand by the
consequences. No Portion of the work presented has been submitted of any application for
any other degree or qualification of this or any other university or institute of learning.

Asim Riaz Haris Ali

--------------------------- ---------------------------
 CERTIFICATE OF APPROVAL
It is to certify that the final year project of BS (CS) “Project title” was developed by
ASIM RIAZ (CIIT/FA20-BSE-001/VHR) and HARIS ALI
(CIIT/FA20-BSE-065/VHR) under the supervision of “UMER RASHID”and that in
(their/his/her) opinion; it is fully adequate, in scope and quality for the degree of Bachelors
of Science in Computer Sciences.

---------------------------------------
Supervisor

---------------------------------------
External Examiner

---------------------------------------
Head of Department
(Department of Computer Science)
 Executive Summary

In public places, there is often a need for monitoring people and different activities going on,
which can be referred later for many reasons including security. Appointing humans for this
task involves many problems such as increased employee hiring, accuracy problem, trust, no
proof for later use, and also the fact that a human can remember things till a certain time
limit. Talking about the current security system, they use dumb still cameras with a
continuous recording facility ir-respective of the fact that any event may happen or not.
Moreover they are usually pointing at a specific user defined locations so more than one
cameras are required to cover the entire region.

To prevent all these problems from prevailing, the CSCS is developed. It is a surveillance
system, which provides solution to many of these problems. It is a stand-alone application
which doesn‟t require any computer to operate. It monitors different situations using a
camera which is able to rotate intelligently based on sensor messages and captures the scene
in the form of video or photos later reference as well.

Customizable Surveillance Control System (CSCS) is a surveillance system that can be

assigned a sensor type as in our case a heat sensor is used, it works accordingly, rotates the
camera upon event detection and perform user defined actions like capturing video and
stores them, for the future use.
 Acknowledgement
All praise is to Almighty Allah who bestowed upon us a minute portion of His boundless
knowledge by virtue of which we were able to accomplish this challenging task.

We are greatly indebted to our project supervisor “Dr. Majid Iqbal Khan” and our Co-
Supervisor “Mr. Mukhtar Azeem”. Without their personal supervision, advice and valuable
guidance, completion of this project would have been doubtful. We are deeply indebted to
them for their encouragement and continual help during this work.

And we are also thankful to our parents and family who have been a constant source of
encouragement for us and brought us the values of honesty & hard work.

Asim Riaz Haris Ali

--------------------------- ---------------------------
 Abbreviations
SRS Software Require Specification

PC Personal Computer
 Table of Contents

1. INTRODUCTION ..............................................................................................................................................1
1.1 SYSTEM INTRODUCTION ......................................................................................................................................1
1.2 BACKGROUND OF THE SYSTEM ............................................................................................................................1
1.3 OBJECTIVES OF THE SYSTEM................................................................................................................................1
1.4 SIGNIFICANCE OF THE SYSTEM ............................................................................................................................2
2. OVERALL DESCRIPTION .............................................................................................................................2
2.1 PRODUCT SCOPE ..................................................................................................................................................2
2.2 PRODUCT DESCRIPTION .......................................................................................................................................2
2.3 PRODUCT FUNCTIONALITY ..................................................................................................................................2
2.4 USERS AND CHARACTERISTICS ............................................................................................................................3
2.5 OPERATING ENVIRONMENT .................................................................................................................................3
2.6 SPECIFIC REQUIREMENTS.....................................................................................................................................4
2.7 BEHAVIOUR REQUIREMENTS............................................................................................................................6
2.8 EXTERNAL INTERFACE REQUIREMENTS ...........................................................................................................7
2.9 NON-FUNCTIONAL REQUIREMENTS ..................................................................................................................9
2.10 SAFETY AND SECURITY REQUIREMENTS ................................................................................................... 10
2.11 SOFTWARE QUALITY ATTRIBUTES ................................................................................................................. 11
3 DESIGN DESCRIPTION ................................................................................................................................ 13
3.1 COMPOSITE VIEWPOINT .................................................................................................................................... 13
3.2 LOGICAL VIEWPOINT ..................................................................................................................................... 14
3.3 INFORMATION VIEWPOINT ............................................................................................................................. 15
3.4 INTERACTION VIEWPOINT .............................................................................................................................. 16
3.5 STATE DYNAMICS VIEWPOINT ....................................................................................................................... 19
3.6 ALGORITHM VIEWPOINT ................................................................................................................................ 20
4 DEVELOPMENT AND TOOLS .................................................................................................................... 21
4.2 INTRODUCTION: ............................................................................................................................................. 21
4.3 DEVELOPMENT PLAN: .................................................................................................................................... 21
4.4 DEVELOPMENT TOOLS ................................................................................................................................... 21
4.5 CONCLUSION AND FUTURE WORK/EXTENSIONS ............................................................................................ 22
5 QUALITY ASSURANCE ................................................................................................................................ 22
5.2 INTRODUCTION .............................................................................................................................................. 22
5.3 TRACEABILITY MATRIX ................................................................................................................................. 23
5.4 TEST PLAN ..................................................................................................................................................... 23
6 USER MANUAL .............................................................................................................................................. 26
6.2 INTRODUCTION .............................................................................................................................................. 26
6.3 HARDWARE/SOFTWARE REQUIREMENTS FOR THE SYSTEM............................................................................ 26
6.4 INSTALLATION GUIDE FOR APPLICATION ....................................................................................................... 26
6.5 OPERATING MANUAL ..................................................................................................................................... 27
 Page 1

1. Introduction

1.1 System Introduction

Online Car Driving School Management System is designed to help driving schools manage themselves
through using efficient management and replacing old manual systems with a digital platform. In addition to
managing the payment process, among other tasks like application tracking, it serves to address the emerging
need for driver training through the most efficient means by restructuring its operations to enhance
automation. It works as a main system that enables the users and administrators to work closely through
improving their interaction with them and at the same time the LMS is characterized by a simple design of
the interface used by the administrator for the proper running of the system and also in training of the users.

1.2 Background of the System

At the present time, there are very few software programs that are specially designed to be used by driving
schools, and this puts the owners of such schools in a very precarious position because they have no choice
other than to rely on manual operations most of which are not full-proof and do not possess all the full
features needed for efficient functioning. Car driving school is what this carrier is designed with, a complete
solution that is at par with the need above. Car driving school enhances procedures of application
management, payment and user communication since it tackles all requirements in a single system instead of
systematic segments as other systems. There is also a feature that facilitates the administration to navigate
with comfort while making it simpler to have an initial overview through a dashboard so that ways, it is
inclined towards user friendly. The assertion was made in light of the implementation of user-oriented design
and the rectification of existing errors.

1.3 Objectives of the System

The objectives of this system are:
To change analogue into digital forms so as to increase efficiency and accuracy in documentation.
• Package Management: admin communications & updates.
• Application Processing: Track & update statuses while user application administration.
• Payment Management: Precisely document & oversee payments made by different users.
• Subscription Management: Control time slots, user subscriptions, modifications, and removals.
• Content Management: Revise ‘Contact Us’ & ‘About Us’ sections
• User Search: Allow rapid look up of users using their registration numbers
• Reporting: Provide detailed summaries about applications received including payments made or
pending among others such details per month/year etcetera
• Profile management: recover, update, modify passwords.
• User Features : Contact details, package details , subscription options
• User Profile Management : Password recovery , profile updates and changes
 Page 2

1.4 Significance of the System

The car driving school management system streamlines information management, user experience, and
manual processes, ensuring transparency, responsiveness, financial integrity, and adaptability to technology,
setting a precedent for best practices in the sector.

2. Overall Description

2.1 Product Scope

The car driving school improves interaction between administrators and users by making it easy for them to
communicate. Within its system there are automated functions like package handling, application processing,
payment tracking, subscriptions among others. In addition to being able to handle subscriptions, process
applications, update material track payments manage packages reporting tools can also be used by
administrators. However, this does not replace more generic systems such as learning management or ERP
systems because they are designed specifically for use in driving schools.

2.2 Product Description

Perspective of the product:
The Online Car Driving School Management System integrates digital technologies for improved operations.
It consists of two modules: admin and user. The admin manages packages, processes applications, payments,
subscriptions, queries, content search reporting, and profiles. The user module handles registration, training
status tracking, and profile management. Data is processed by the admin module, ensuring smooth
communication and data accessibility.

2.3 Product Functionality

At the present time, there are very few software programs that are specially designed to be used by driving
schools, and this puts the owners of such schools in a very precarious position because they have no choice
other than to rely on manual operations most of which are not full-proof and do not possess all the full
features needed for efficient functioning. Car driving school is what this carrier is designed with, a complete
solution that is at par with the need above. Car driving school enhances procedures of application
management, payment and user communication since it tackles all requirements in a single system instead of
systematic segments as other systems. There is also a feature that facilitates the administration to navigate
with comfort while making it simpler to have an initial overview through a dashboard so that ways, it is
inclined towards user friendly. The assertion was made in light of the implementation of user-oriented
design and the rectification of existing errors.
 Page 3

2.4 Users and Characteristics

There are two main types of users that exist within the Online Car Driving School Management System
(CDSMS): administrators and subscribers. The load generated by each user group is often dissimilar since
the groups differ in the functions they perform in the system.

Administrators:
Characteristics:
• Competent professionals who oversee overall operations at a driving school
• Digital literacy skills
• Organizational skills

Subscribers:
Characteristics:
• Different levels of technical ability ranging from beginners to advanced users
• Individuals in need of driving education
• Various educational backgrounds & age brackets

Instructors:
Characteristics:
• Certified experts who have trained in driving safety and skills
• Directly communicate with students during training.
• Monitor learner progress then give guidance plus feedback.

2.5 Operating Environment

The Online Car Driving School Management System (CDSMS) has the normal graphical WEB BASED
interface that is user friendly and can be run From Any Device. The following are components of the
operational environment: The following are components of the operational environment:

Minimum Platform Requirements:

Hardware:
• Smart personal computers including desktops, tablets and laptops
• At least 4gb ram required.

Operating System:
Windows, macOS and Linux

Web Browsers:
Microsoft Edge, Mozilla Firefox, Google Chrome and Safari

Server Requirements:
• Web server with PHP
• MySQL database
• Software Components:
• PHP for web programming language
• MySQL for data storage.
• HTML, CSS & JavaScript for user interface and interactivity.
 Page 4

Internet Connectivity:
• Stable internet connection is necessary to access the system.

2.6 Specific Requirements

Functional Requirements
The Online Car Driving School Management System (CDSMS) should meet the following functional
requirements:The Online Car Driving School Management System (CDSMS) should meet the following
functional requirements:

1.User Registration and Authentication:

• Allow users to create accounts by providing valid login credentials.
• Verify user identity in order to allow access to system features.

Managing Courses:
• Enable administrators to create, update or delete driving courses.
• Provide specifics about the course such as duration, cost and number of available slots.

Processing Applications:
• Provide a form for users to apply for a driving course.
• Enable administrators to review and either approve or disapprove applications.

Processing Payments:
• Integrate payment gateways so that customers can securely pay for their courses.
• Keep track of payment status and update user accounts accordingly.

Handling Inquiries:
• Create a forum where users can ask questions about timetables, courses etc.
• Make sure that such queries are responded by an administrator as soon as possible.

User Subscription Management:

• Allow users to enroll and control their driving course subscription.
• Enable admins to view and manage user subscriptions made.

Content Management:
• Allow admins to edit the text on system pages like "Contact Us" and "About Us."

Reporting and Analytics:

• Create reports about application usage, application status, payment information etc.
• Provide admins with analytics to track system performance.

User Profile Management:

• Enable users to change their preferences or personal information.
• Enable administrators to manage permissions and user profiles.

Instructor Management:
• Allow administrators to edit, delete, add instructor profiles.
 Page 5
• Assign teachers to specific schedules and courses

Training Application Management:

• Allow users to sign up for driving instruction;
• Allow administrators check training applications submitted; approve/deny them as appropriate

Communication Features:
• It should allow users to freely message or @ mention fellow staff members
• Ensure that instructions relating to school activities and changes in the class or timetable are
communicated to students through teachers.
 Page 6

2.7 Behaviour Requirements

USE CASE DIAGRAM:

Figure 1: Use Case

 Page 7

2.8 External Interface Requirements

User Interfaces

Figure2: login

Figure 3: Home
 Page 8
1. Admin Dashboard:
Upon logging in, administrators are greeted with a dashboard that provides an overview of key metrics such
as total subscribers, users, and enquiries.

Figure 4: Dashboard

Figure 5: Enrollment
 Page 9

Figure 6: Packages

2.9 Non-functional Requirements

Performance Requirements
1. Response Time:
Normal load intended here refers to the average or typical rate of incoming user requests such as enquiring or
changing status of an application and it should take less than 3 seconds to process this requests.The operation
to fetch both package and user details should take no more than 5 seconds to provide a smooth customer
experience.

2. Concurrent User Handling:

The system’s basic performance requirements should support at least 100 concurrent users without a severely
low response to response times.At times of concurrent user engagement, the system must be able to
gracefully grow to handle greater user simultaneous interactions without degenerating to the Zone of
Response Times.

3. Database Query Performance:

Recent and frequently acceussed application and payment management queries in any database should be
cached to provide faster access and update.Simple queries can take as long as a few minutes depending on
the complexity of the search and to ensure that the data processing is under 5 seconds for more complex
searches.

4. Scalability:
he system architecture should be flexible so that it can support some growth in the user base as well as the
amount of data generated.Extra space should complement the process without compromising its efficiency as
the system expands.
 Page 10
5. Fault Tolerance:
This means that in the event of server or database failure, the system must be congruent with ways and
means that will enhance minimum down time.Records must remain accurate and consistent at all times even
when there is a mainframe system failure or when system backups are being done.

6. Security Overhead:
As for the secure data transfer via the SSL encryption, it is not expected that the necessary overhead will
cause very large response time in the app.The system should make a compromise between security steps and
speed so the user doesn’t experience a slow and restrictive feel with all of the security measures in place.

7. Data Backup and Recovery:

Backup operations should be automated and take up as little resource as possible so that they should ideally
not slow down the system.If any database recovery is needed, it should be as fast as possible to limit the lost
time during which the services may not become available to users.

8. Logging and Auditing:

The profiling and logging activities should be performed at the required levels and should not undue impact
the system response by capturing the events such as the user actions and other events that are occurring in the
system.Audit trails and logs should be managed so as not to bring efficiency concerns to implementations.

These performance requirements are necessary for guaranteeing that the conception and development of the
Online Car Driving School Management System will produce a high-quality system that can effectively
respond to users’ queries and administrators’ changes without overburdening or crashing frequently. The
defined requirements and response times as well as the actions for making the system scalable help to
achieve an effective and optimized performance depending on the situation.

2.10 Safety and Security Requirements

Safety Requirements:
Data Integrity:
Again, there is the need to retain data security for users’ record especially when dealing with payment
information to avoid loss or damage.

Backup and Recovery:

Therefore, the system data should be backed up automatically in a regularly based manner so that there will
be no loss of information in cases like system crashes or data corruptions.

Security Requirements:
User Authentication:
Only those who shave the proper authentication and privileges are allowed into the system.
Password regulation: The password complexity is one of the general rules established to improve the
organization’s security.

Encryption:
Any users must be required to use HTTPS in order to protect details from any hackers and or any third
parties eavesdroppers. This includes user passwords, client details and payments, identity of users, messages
between the client and server among others.

Role-based access control (RBAC):

Depending on the classification of a user of the social media site being an admin or a normal user, then some
of the operations can only be completed by this particular user. Users should only be permitted to some level
 Page 11
of usage while the whole services and features within the system should only allow its adaptation by the
system administrators.

User Privacy:
In this case, the software has to meet the legal requirements of protection of individuals personal identifiable
information (PII) by safely handling it, as well as offering strict guide lines related to such matters.

2.11 Software Quality Attributes

Reliability:
Availability:
The system must have 99% uptime during business hours so that administrators and users can always get in
when they need it.

Usability:
User Interface Consistency:
The UI throughout the whole application should look same which will make it easier for both users and
admins alike to navigate through different sections without having any problems whatsoever.

Ease of Navigation
Easy-to-use navigation structure of the system should allow users easily move between various features of
this complex application without facing difficulties at any point in time while using it .

Accessibility:
The system has to support accessibility standards in order to accommodate impaired individuals who may
want use it; for example, screen readers & keyboard navigation among others.

Maintainability:
Modularity:
Different parts/components/modules within the system should be designed in such a way that they can be
developed and maintained independently of each other without causing any negative impact on other
modules when one module is changed.

Documentation:
There should be comprehensive documentation available for both code as well as usage of entire system thus
making it easy to support/maintain/modify/extend in future times when required.

Performance Efficiency:
1. Scalability:
Horizontal scalability is recommended so that the system can handle more users and data. Scaling should not
lead to performance degradation.

2. Resource Utilization:
Optimization is needed with regards to how server resources are utilized by different parts of this application
in order to prevent bottlenecks from occurring due to inefficient use of these resources.

Security:
1. Regular Security Audits:
The risks arising from these threats should then be addressed appropriately, and this can only be done if
frequent security audits are conducted.
The observation gathered from a given audit should serve as a resource for strengthening the security
measures within the system.
 Page 12

2. Data Encryption:
Laptops’ files and databases should use encryption techniques compliant with industry norms during transfer
or when info is stored, if it is sensitive info.

3. User Authentication Strength:

Passwords must also be kept securely through defensible hashing methods, these methods have been adopted
and approved by the relevant authorities. A few more ways of improvement in the user security could be the
use of various forms of authentications for instance two factor.

Interoperability:
1. Compatibility with Modern Browsers:
Browser versions recommended include those that are modern and widely used; it is essential to guarantee
that it runs cohesively with this application for all the platforms supported by those browsers.

Testability:
1. Automated Testing:
Automated testing may also assist in easy regression testing such that new releases do not interfere with
functionality accidentally but at the same time, everything is tested to check that it functions efficiently
immediately after release cycle.

2. User Acceptance Testing (UAT):

It is recommended that stakeholders should have a natural feel to the place where they would be undertaking
their user-acceptance testing (UAT) to ensure that their needs have been fully met by the system being
developed.
 Page 13

3 Design Description

3.1 Composite Viewpoint

In the composite viewpoint, we'll use a **Package Diagram (Logical)** to represent the major design
constituents and modular assembly of the Online Car Driving School Management System.

Figure 7: Composite Diagram

 Page 14

3.2 Logical Viewpoint

In the logical viewpoint, we'll use a Class Diagram to represent the existing and designed types, their
implementations as classes and interfaces, and their structural static relationships in the Online Car Driving
School Management System.

Figure 8: Class Diagram

 Page 15

3.3 Information Viewpoint

Entity Relationship Diagram (ERD)

In the information viewpoint, we'll use an **Entity Relationship Diagram (ERD)** to represent the
persistent data content and relationships within the Online Car Driving School Management System.

Figure 9: ER Diagram
 Page 16

3.4 Interaction Viewpoint

Sequence Diagrams

Let's illustrate the interaction between objects for two key use cases in the Online Car Driving School
Management System: User Application Submission and Admin Application Review.

Use Case 1: User Application Submission

Figure 10: Sequence Diagram (User Application)

 Page 17
Use Case 2: Admin Application Review

Figure 11: Sequence Diagram (Admin Application)

 Page 18

Figure 12: Sequence Diagram

 Page 19

3.5 State Dynamics Viewpoint

UML State Machine Diagram
Let's represent the state dynamics of the Online Car Driving School Management System using a UML State
Machine Diagram. We'll focus on the Application State Transitions for a better understanding of the
application lifecycle.

Figure 13: Sequence Diagram

 Page 20

3.6 Algorithm Viewpoint

Pseudo Code

Within this algorithmic view point, we shall give pseudo codes snippets for some key operations in the
Online Car Driving School Management System. We will concentrate on updating application status process
as well as user authentication management.

Updating Application Status:

// Application Management Module
function updateApplicationStatus(applicationID, newStatus):
// Retrieve application details from the database
application = DatabaseConnector.fetchApplicationDetails(applicationID)
// Check if the application exists
if application is not null:
// Update the application status
application.setStatus(newStatus)
// Save the updated application details in database
DatabaseConnector.updateApplication(application)

// Return success status

return "Application status updated successfully"
else:
// Return error status if application does not exist
return "Error: Application not found"

User Authentication:
// Security Manager Module
function authenticateUser(username, password):
// Retrieve user details from the database
user = DatabaseConnector.fetchUserDetails(username)
// Check if the user exists and password matches
if user is not null and user.getPassword() == hashFunction(password):
// Return success status
return "Authentication successful"
else:
// Return error status if authentication fails
return "Error: Authentication failed"
 Page 21

4 DEVELOPMENT AND TOOLS

4.2 Introduction:
This chapter gives an outline of the development plan for Online Car Driving School Management
System, which consists of team members, activities during development and tools used.

Team Members:

1. Asim Riaz
2. Haris Ali

4.3 Development Plan:

The idea of creating a product was generated by Asim Riaz and his friend Haris Ali. Enumerated in the
development plan are requirement gathering and analysis, design, implementation, testing, and
deployment among others. In order to achieve balance as far as time is concerned all members have
been booked to perform various tasks as per their capacities. Below is a simplified breakdown
structure of the development plan:Below is a simplified breakdown structure of the development plan:
Table 1: Plan
Activity Start Date End Date Assigned To
Requirements Gathering 2024-05-01 2024-05-07 Asim Riaz
Design 2024-05-08 2024-05-14 Haris Ali
Implementation 2024-05-15 2024-06-15 Asim & Haris
Testing 2024-06-16 2024-06-30 Asim & Haris
Deployment 2024-07-01 2024-07-07 Asim & Haris

This plan outlines the timeline and responsibilities for each phase of the project, ensuring a systematic
approach to development.

4.4 Development Tools

During the development process of the Managers Dashboard System, the following tools were utilized:

Integrated Development Environment (IDE):

Visual Studio Code: For coding, modifying, checking and testing the program and also for the use of version
control systems.

Frontend Development:
HTML5: Tags used to designate the content elements and layout of the website and its individual web pages.
CSS3: As for enhancing the look of the pages, let us mention Cascading Style Sheets.
JavaScript: Programming language for adding ‘activities’ and ‘behaviors’ into web pages; for creating
interactive web applications.

Backend Development:
PHP: Programming language that used on web server side to create dynamical web applications.
 Page 22
Laravel: PHP framework which is useful to develop complex web applications with better security and
performance.

Database Management:
MySQL: It has also a relational database management system for storing and managing the application data.

Version Control:
Git: Source code management system to implement changes in the file base and various developers.
GitHub: Online repository hosting service used to manage and share version of software source codes.

Other Tools:
Composer: PHP tool that can manage project dependencies and libraries for the user.
npm (Node Package Manager): Local caching of Node. js packages and modules.
Postman: Highly flexible API development and testing tool that is used in the development of designing and
testing of APIs as well as in documenting the APIs.

All these instruments were used in the development of the Managers Dashboard System and in the overall
process of its implementation.

4.5 Conclusion and Future Work/Extensions

In summary, the Online Car Driving School Management System was created with an aim of
streamlining processes involved in driving schools through automation thereby improving efficiency by
minimizing manual data processing. There could be several enhancements made for next work or
extensions so as to further enhance the system like;

As for future work and extensions, several enhancements can be considered to further improve the
system. These include:

• Mobile Application Development

• Integration with Payment Gateways
• Advanced Reporting and Analytics
• Expanded Features for Driving Instructors

5 QUALITY ASSURANCE

5.2 Introduction
This chapter describes quality assurance phase for Online (CDSMS) including test types, test approach
and test plan. It highlights user satisfaction as the utmost priority and employs efficient testing processes.
 Page 23
A requirement traceability matrix links test cases to functional requirements which allow presentation of
findings by means of test cases.

5.3 Traceability Matrix

Table 2: Traceability Matrix
Test Case ID Functional Requirement
TC001 Admin can manage packages
TC002 Admin can view application details
TC003 Admin can update application status
TC004 Admin can update payments
TC005 Admin can manage subscribed users
TC006 Admin can read new enquiries
TC007 Admin can manage about us and contact us pages
TC008 Admin can search users by registration number
TC009 Admin can view application and payment details in specific periods
TC010 Admin can update profile and change password
TC011 Admin can view total number of subscribers/users
TC012 Admin can view total number of enquiries received
TC013 User can subscribe with a driving school
TC014 User can view driving school services
TC015 User can put enquiries
TC016 User can view recent packages offered by a driving school
TC017 User can view details of driving school
TC018 User can contact a driving school
TC019 User must register for training
TC020 User can apply for training for self or family member
TC021 Registered users are welcomed on the welcome page
TC022 Registered users can update their profile
TC023 Registered users can change password
TC024 Registered users can recover password

This traceability matrix maps each test case to its corresponding functional requirement, ensuring
comprehensive test coverage and alignment with user expectations.

5.4 Test Plan

 Page 24
Table 3: Test Case for Admin Management - Manage Packages
Date Test
Test of Application Expected Actual Role
Test ID Name Test Name Description Input Output Output (Actor) Test Verified By
Admin
accesses the
Online Car Manage
Driving Packages New New
School page and Click on package package
Manage 2024- Management adds a new "Manage added added Team
TC001 Packages 05-01 System package. Packages" successfully successfully Admin Member/Supervisor
Admin
accesses the
Manage
Online Car Packages
Driving page and Package Package
School updates an Click on details details
Manage 2024- Management existing "Manage updated updated Team
TC002 Packages 05-01 System package. Packages" successfully successfully Admin Member/Supervisor
Admin
accesses the
Manage
Online Car Packages
Driving page and
School deletes an Click on Package Package
Manage 2024- Management existing "Manage deleted deleted Team
TC003 Packages 05-01 System package. Packages" successfully successfully Admin Member/Supervisor

Table 4: Test Case for Admin Management - View Application Details

Date Test
Test of Application Expected Actual Role
ID Test Name Test Name Description Input Output Output (Actor) Test Verified By
View 2024- Online Car Admin Click on Application Application Team
TC004 Application 05-02 Driving accesses "View details details Admin Member/Supervisor
 Page 25

Date Test
Test of Application Expected Actual Role
ID Test Name Test Name Description Input Output Output (Actor) Test Verified By
Details School the View Application displayed displayed
Management Application Details"
System Details
page to
view
details of
an
application.
Admin
searches
Online Car for an Enter
Driving application registration
View School by number Application Application
Application 2024- Management registration and click details details Team
TC005 Details 05-02 System number. "Search" displayed displayed Admin Member/Supervisor
 Page 26

6 USER MANUAL

6.2 Introduction
This provides detailed instructions on how consumers can use Online Car Driving School Management
System effectively. It gives a comprehensive guide on how the system can be used, its features accessed
as well as carrying various activities through it. Users are given step by step instructions coupled with
tips to enhance their application experience.

6.3 Hardware/Software Requirements for the System

Software Requirements:

• Operating System: Windows 10 or later, macOS, Linux

• Web Browser: Google Chrome, Mozilla Firefox, Safari, Microsoft Edge
• Server Environment: Apache or Nginx
• Database Management System: MySQL 5.7 or later
• PHP: Version 7.4 or later
• Development Tools: IDE (Integrated Development Environment) such as Visual Studio Code,
Sublime Text, or PhpStorm

Hardware Requirements:

• Processor: Intel Core i3 or equivalent

• RAM: 4GB or higher
• Storage: At least 100MB of free disk space
• Network: Internet connection for accessing online features and updates

6.4 Installation guide for Application

1. Download Application Files:
• Visit the official website of the Online Car Driving School Management System.
• Navigate to the "Downloads" section.
• Click on the link to download the application files.

2. Extract Files:
• Once the download is complete, locate the downloaded zip file.
• Right-click on the file and select "Extract All" to extract the contents.
• Choose a destination folder for extraction and click "Extract".

3. Set Up Server Environment:

• Ensure that you have a server environment set up with Apache or Nginx installed.
• Configure the server to support PHP and MySQL.

4. Database Setup:
• Create a new MySQL database for the application.
• Import the provided SQL file into the database to set up the required tables and data.
 Page 27

1. Configuration:
• Navigate to the extracted application folder.
• Locate the configuration file (e.g., config.php) and open it using a text editor.
• Update the database connection settings with the appropriate credentials.

6. Upload Files to Server:

• Transfer all the extracted application files to the root directory of your web server.
• Ensure that the files are placed in the correct directory structure.

7. Access the Application:

• Open your web browser and enter the URL of your application (e.g., http://localhost/online-
car-driving-system).
• You should see the login page of the application.

8. Login and Test:

• Use the default admin credentials (if provided) or register as a new admin user.
• Once logged in, navigate through the application and test its various functionalities to ensure
everything is working correctly.

6.5 Operating Manual

1. Dashboard:
• Upon logging in, you will be directed to the dashboard, which provides an overview of key metrics
such as total subscribers, total enquiries received, etc.
• The dashboard also contains quick links to important sections of the application.

2. Admin Management:
• Navigate to the "Admin Management" section to manage admin users.
• Here, you can add new admin users, view existing users, update their details, or delete them if
necessary.

3. Package Management:
• Access the "Package Management" section to manage driving packages offered by the driving
school.
• You can add new packages, update existing ones, or delete them as needed.

4. Application Management:
• In the "Application Management" section, you can view and manage user applications for training.
• Update the status of applications, view application details, and manage payments.

5. Enquiry Management:
• Manage user enquiries in the "Enquiry Management" section.
• View new enquiries, mark them as read, and respond to user queries.

6. User Management:
• Admins can manage user accounts in the "User Management" section.
• View registered users, update their profiles, and manage passwords.

7. Profile Settings:
• Update your admin profile settings in the "Profile Settings" section.
• Change your password and update personal information as needed.
 Page 28

8. Logout:
• Finally, ensure to log out of the application once you have finished using it to maintain
• security.

Follow these guidelines to effectively operate the Online Car Driving School Management System and make
the most out of its features.