COMSATS University Islamabad

Abbottabad, Pakistan

SCHOOL TRANSPORT SERVICE

By

Hassaan Ahmad CIIT/FA19-BCS-033/ATD

Usman Naeem CIIT/ FA19-BCS-016/ATD
Laiba Binte Zarshaid CIIT/ FA19-BCS-143/ATD

Supervisor
Dr. Rab Nawaz Jadoon

Bachelor of Science in Computer Science (2019-2023)

The candidate confirms that the work submitted is their own and appropriate
credit has been given where reference has been made to the work of others.
 COMSATS University Islamabad, Pakistan

SCHOOL TRANSPORT SERVICE

A project presented to
COMSATS Institute of Information Technology, Islamabad

In partial fulfillment
of the requirement for the degree of

Bachelor of Science in Computer Science (2019-2023)

By

Hassaan Ahmad CIIT/FA19-BCS-033/ATD

Usman Naeem CIIT/ FA19-BCS-016/ATD
Laiba Binte Zarshaid CIIT/ FA19-BCS-143/ATD

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

Hassaan Ahmad Usman Naeem Laiba Binte Zarshaid

--------------------- --------------------- ---------------------------

ii
 CERTIFICATE OF APPROVAL

It is to certify that the final year project of BS (CS) School Transport Service was developed
by Hassaan Ahmad (CIIT/FA19-BCS-033), Usman Naeem (CIIT/FA19-BCS-016) and
Laiba Binte Zarshaid (CIIT/FA19-BCS/143) under the supervision of DR. RAB NAWAZ
JADOON that in his opinion; it is fully adequate, in scope and quality for the degree of
Bachelor of Science in Computer Sciences.

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

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

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

iii
 EXECUTIVE SUMMARY

The School Transport Service project is a mobile application designed to simplify the
management of school transportation for parents, students, and schools. The application offers
a user-friendly interface and a range of features tailored to enhance convenience, safety, and
communication.
Parents can easily schedule and manage their child's school transportation using the mobile
application. The features include real-time tracking of the school vehicle, notification
management for updates and alerts, and driver and vehicle selection for added control and
peace of mind.
Developed using the React Native framework, the application ensures compatibility across
both iOS and Android platforms. The integration of Google Maps API enables accurate
location tracking and efficient route optimization, ensuring timely and safe transportation for
students.
The School Transport Service project offers significant benefits to Parents and Drivers. Parents
can easily manage their child's transportation, ensuring their safety and reducing the
administrative burden and Drivers can easily connect with schools, efficiently manage their
schedules and seats availability.
Future work for the project includes integrating payment systems to facilitate seamless
transactions, expanding multilingual support for broader accessibility, and implementing
advanced features such as analytics to optimize transportation operations.
In conclusion, the School Transport Service project provides a user-friendly and efficient
solution for managing school transportation. With its features focused on convenience, safety,
and communication between drivers and schools, the project aims to enhance the overall
transportation experience for parents, ensuring a reliable and streamlined process

iv
 ACKNOWLEDGEMENT

We express our utmost gratitude to Almighty Allah, from whom we have been granted a
modest portion of His boundless knowledge, enabling us to successfully accomplish this
challenging task.
Our sincere appreciation goes to our esteemed project supervisor, Dr. Rab Nawaz Jadoon,
whose personal supervision, valuable guidance, and unwavering support have been
instrumental in the completion of this project. Without their expertise and encouragement, the
successful outcome would have been uncertain.
Furthermore, we extend our heartfelt thanks to our parents and family, whose constant
encouragement and instilled values of honesty and hard work have been a driving force behind
our endeavors. Their unwavering belief in us has been a constant source of inspiration
throughout this journey.
We acknowledge the blessings and guidance that have come our way, making this project
possible, and we remain committed to applying the knowledge and experience gained for future
endeavors.

Hassaan Ahmad Usman Naeem Laiba Binte Zarshaid

--------------------- --------------------- ---------------------------

v
 ABBREVIATIONS
SRS Software Require Specification

PC Personal Computer
STS School Transport Service
APP Application
API Application programming interface

vi
 TABLE OF CONTENTS

1. Introduction ...................................................................................................................... 1
1.1. Brief ............................................................................................................................. 1
1.2. Relevance to Course Modules ..................................................................................... 1
1.3. Project Background ..................................................................................................... 1
1.4. Literature Review ........................................................................................................ 2
1.5. Analysis from Literature Review ................................................................................ 2
1.6. Methodology and Software Lifecycle for This Project ............................................... 2
1.6.1. Rationale behind Selected Methodology ............................................................. 3
2. Problem Definition ........................................................................................................... 4
2.1. Problem Statement ...................................................................................................... 4
2.2. Deliverables and Development Requirements ............................................................ 4
3. Requirement Analysis ...................................................................................................... 5
3.1. Use Cases Diagram(s) ................................................................................................. 5
3.2. Functional Requirements............................................................................................. 6
3.3. Non-Functional Requirements .................................................................................... 6
4. Design and Architecture .................................................................................................. 7
4.1. System Architecture .................................................................................................... 7
4.2. Data Representation .................................................................................................... 8
4.3. ER Diagram ................................................................................................................. 9
4.4. Class Diagram ........................................................................................................... 10
4.5. Sequence Diagram for Add School ........................................................................... 10
4.6. Update Vehicle Deatails ............................................................................................ 11
4.7. Update Driver Deatails .............................................................................................. 11
4.8. Feedback.................................................................................................................... 12
4.9. Connection Request................................................................................................... 12
4.10. Update parent details ................................................................................................. 13
4.11. Update payment method............................................................................................ 13
4.12. System Sequence Diagram ........................................................................................ 14
4.13. Design Models........................................................................................................... 14
5. Implementation ............................................................................................................... 16
5.1. Algorithm .................................................................................................................. 16
5.2. External APIs ............................................................................................................ 16
5.3. APIs ........................................................................................................................... 16
5.4. User Interface ............................................................................................................ 17

vii
6. Testing and Evaluation .................................................................................................. 45
6.1. Manual Testing .......................................................................................................... 45
6.1.1. System Testing ................................................................................................... 46
6.1.2. Unit Testing ....................................................................................................... 46
6.1.1. Login and Signup Unit Testcase ........................................................................ 47
6.1.1. Edit Profile Unit Testcase .................................................................................. 47
6.1.1. System Testing ................................................................................................... 48
6.1.3. Functional Testing ............................................................................................. 48
6.1.4. Integration Testing ............................................................................................. 48
6.2. Automated Testing: ................................................................................................... 49
6.2.1. Tools used: ................................................................................................................ 49
7. Conclusion and Future Work ........................................................................................ 51
7.1. Conclusion ............................................................................................................................... 51
7.2. Future Work .......................................................................................................................... 51
8. References........................................................................................................................ 52

viii
 LIST OF FIGURES

Fig 3.1 Use Case Diagram ......................................................................................................... 5

Fig 4.1: ER Diagram .................................................................................................................. 8
Fig 4.2: Class Diagram .............................................................................................................. 9
Fig 4.3: Sequence Diagram for Add School ............................................................................ 10
Fig 4.4: Update Vehicle Deatails ............................................................................................. 10
Fig 4.5: Update Driver Deatails ............................................................................................... 11
Fig 4.6: Feedback ..................................................................................................................... 11
Fig 4.7: Connection Request .................................................................................................... 12
Fig 4.8: Update parent details .................................................................................................. 12
Fig 4.9: Update payment method ............................................................................................. 13
Fig 4.10: System Sequence Diagram ....................................................................................... 13
Fig 5.1: Signup Screen ............................................................................................................. 17
Fig 5.2: Purpose Selection Screen ........................................................................................... 18
Fig 5.3: SignIn Screen.............................................................................................................. 19
Fig 5.4: Send OTP Screen ........................................................................................................ 20
Fig 5.5: OTP Screen ................................................................................................................. 21
Fig 5.6: Home Screen .............................................................................................................. 22
Fig 5.7: Notification Screen ..................................................................................................... 23
Fig 5.8: Edit Profile Screen ...................................................................................................... 24
Fig 5.9: Vehicle Screen ............................................................................................................ 25
Fig 5.10: Live Location Screen ................................................................................................ 26
Fig 5.11: Subscription Screen ................................................................................................. 27
Fig 5.12: Availabe School Screen ............................................................................................ 28
Fig 5.13: Vehicle Details Screen ............................................................................................. 29
Fig 5.14: Driver Profile Screen ................................................................................................ 30
Fig 5.15: School Details Screen .............................................................................................. 31
Fig 5.16: Signup Screen ........................................................................................................... 32
Fig 5.17: Purpose Selection Screen ......................................................................................... 33
Fig 5.18: SignIn Screen............................................................................................................ 34
Fig 5.19: Send OTP Screen ...................................................................................................... 35
Fig 5.20: OTP Screen ............................................................................................................... 36
Fig 5.21: Home Screen ............................................................................................................ 37
Fig 5.22: Notification Screen ................................................................................................... 38
Fig 5.23: Edit Profile Screen .................................................................................................... 39
Fig 5.24: School Details Screen ............................................................................................... 40
Fig 5.25: Live Location Screen ................................................................................................ 41
Fig 5.26: Subscription Screen ................................................................................................. 42
Fig 5.27: Availabe School Screen ............................................................................................ 43

ix
 LIST OF TABLES

Table 3.1: Functional Requirements .......................................................................................... 6

Table 3.2: Non Functional Requerments ................................................................................... 6
Table 5.1: APIs ........................................................................................................................ 16
Table 6.1: Login and Signup Unit Testcase ............................................................................. 45
Table 6.2: Edit Profile Unit Testcase ....................................................................................... 45
Table 6.3: Request Unit Testcase............................................................................................. 46
Table 6.4: Login Functional Testcase ...................................................................................... 46
Table 6.5: Request Functional Testcase................................................................................... 46
Table 6.6 : Integration Testcase ............................................................................................... 47
Table 6.7: Tools Used .............................................................................................................. 48

x
1. Introduction
The School Transport Service Mobile App aims to simplify the way parents and students
manage school transportation. It offers a user-friendly interface to book rides, track the
vehicle's location, select vehicles and drivers based on ratings, and set a budget. The app is
cross-platform and helps parents avoid physically searching for transportation. It ensures the
safety of students and offers real-time updates. The School Transport Service Mobile App is a
groundbreaking solution that addresses the transportation needs of parents and students.

1.1. Brief
We have developed a School Transport Service Mobile App specifically catering to
the needs of parents and schools. This app offers real-time location tracking, budget-
friendly travel options, and the ability to choose preferred vehicles and drivers based on
ratings. Using Agile methodology and React Native, we built a cross-platform app for iOS
and Android. We utilized PostgreSQL for data management and Google Maps API for
location tracking, ensuring a convenient and reliable transportation service. Through user
discussions and rigorous testing, we have designed a user-friendly interface and ensured
optimal functionality.

1.2. Relevance to Course Modules

 Software Engineering Concepts: The project incorporates software engineering
principles and methodologies, such as the Agile methodology, which emphasizes
iterative development and continuous improvement based on user feedback. This
ensures the app's functionality, usability, and maintainability through software
development lifecycles.
 Database Systems: The app utilizes a backend platform, PostgreSQL, for storing and
managing user data. Database design principles and concepts learned in the Database
Systems course are applied to ensure efficient data management and retrieval.
 Mobile Application Development: The project involves the development of a mobile
application using React Native, a popular cross-platform framework. The concepts and
techniques learned in the Mobile Application Development course are applied to create
a user-friendly and platform-independent mobile app.
 Web Development: Although the focus is on mobile app development, the project
also involves web development aspects, such as integrating APIs like Google Maps
API for location tracking. The knowledge and skills acquired in Web Development
courses contribute to designing responsive and interactive web Admin Dashboard.
1.3. Project Background
The School Transport mobile application facilitates communication between parent
and transport providers. It enables real-time tracking, notifications, and communication for
parents and students. The app enhances student safety with features like GPS tracking and

1
emergency notifications. It improves convenience, efficiency, and collaboration in the
school transport service.

1.4. Literature Review

School transportation services play a crucial role in students' academic performance
and attendance. The use of technology, particularly mobile apps, has emerged as a solution
to address challenges in school transportation. Research shows that transportation issues can
negatively impact academic outcomes. Mobile apps offer real-time tracking, notifications,
and direct communication between parents and transport providers. Existing apps like Safe
Stop and Zonar provide features such as tracking, delay notifications, and driver behavior
monitoring. Designing effective apps requires user-friendly interfaces, real-time updates,
and integration with existing systems. Implementing mobile apps for school transportation
services can enhance safety, accessibility, and reliability, leading to improved educational
experiences for students.

1.5. Analysis from Literature Review

The literature review highlights the critical role of transportation in ensuring that
students can attend school and participate in educational programs. The use of technology,
including mobile apps, has the potential to enhance transportation services for school
children and address challenges such as safety, accessibility, and reliability. By reviewing
existing research and trends, we can identify areas where our project can make a significant
contribution to the field of school transportation services.

1.6. Methodology and Software Lifecycle for This Project

The School Transport Service Project follows an Agile development methodology and
a systematic Software Development Lifecycle (SDLC) to ensure the successful delivery of
the mobile application. Requirements gathering is the initial phase, followed by system
design, development, testing, and deployment. The Agile methodology allows for flexibility
and continuous improvement through iterative sprints, regular meetings, and feedback from
stakeholders. The application is built using the React Native framework, ensuring cross-
platform compatibility. Rigorous testing is conducted throughout the development process,
including unit testing, functional testing, and user acceptance testing. Deployment to
production servers or app stores is followed by maintenance and updates based on user
feedback. Collaboration tools and software tools such as project management software,
version control systems, PostgreSQL for data management, Figma for wireframing and
designing the final UI, focusing on creating an intuitive and user-friendly experience and
Google Maps API for location tracking are utilized. This approach ensures the delivery of a
high-quality and reliable mobile application that meets the needs of parents, students, and
school administrators, streamlining the school transportation process.

2
 1.6.1. Rationale behind Selected Methodology
We selected Agile methodology for the development of the School Transport
Service Mobile App for several reasons:
 Flexibility: Agile methodology is highly flexible and allows for changes to be made
throughout the development process, making it easier to adapt to changing
requirements or priorities.
 Faster delivery: Agile methodology enables faster delivery of working software by
dividing the project into smaller sprints, allowing for continuous delivery of working
software at regular intervals.
 Continuous improvement: Agile methodology allows for continuous improvement
through constant feedback from stakeholders, enabling the team to make changes
and improvements based on user feedback.
 Collaboration: Agile methodology emphasizes collaboration and teamwork, which
helps to ensure that all team members are working together towards a common goal
and that everyone is aware of what is happening at all times.
 Component-based approach: It is a software development methodology that
focuses on building the app's features and functionality as modular and reusable
components. Each component can be developed separately and can be combined
with other components to create the final app as we created in School Transport
Service. This approach allows for more efficient development, as the components
can be reused in different parts of the app, reducing the need for redundant code. It
also enables faster development and easier maintenance, as changes made to a
component will automatically reflect in all the parts of the app where that component
is used.

3
2. Problem Definition
Parents need a more efficient and transparent way to ensure safe school transportation for
their children. The School Transport Service app aims to provide this solution.

2.1. Problem Statement

Many parents and guardians face difficulty in ensuring the safe and timely transportation
of their children to and from school. Traditional methods of arranging transportation, such as
physical searching, can be time-consuming and inefficient. Additionally, there is often a lack
of transparency and accountability in the transportation process, leaving parents unsure of their
children's safety and well-being during transit. The School Transport Service mobile app aims
to address these issues by providing a convenient, efficient, and transparent platform for parents
and guardians to arrange transportation for their children to and from school.

2.2. Deliverables and Development Requirements

Deliverables:
 User requirements: This document describes the functional and non-functional
requirements of the app, as well as the user personas and use cases.
 Technical design: This document outlines the technical architecture of the app,
including the database design, API design, and system integration.
 Prototype: This is a working prototype of the app that showcases the app's basic
functionality and design.
 Test plan: This document outlines the testing approach for the app, including
functional testing, user acceptance testing, and regression testing.
 User manuals and documentation: These documents provide guidance on how to
use the app and address common issues that users may face.
Development requirements:
 Platform: The app should be compatible with both iOS and Android devices, and
the development team should have the necessary expertise to develop for both
platforms.
 Front-end development: The app should have a user-friendly and intuitive interface
that is easy to navigate.
 Back-end development: The app should have a robust and scalable back-end
system that can handle a large volume of users and data.
 GPS tracking: The app should be equipped with GPS tracking features that enable
real-time tracking of the school transport vehicle.
 Payment gateway: The app should provide a secure and reliable payment gateway
to enable parents to pay for the school transport service.

Overall, the deliverables and development requirements for the school transport service app
project include project plan, user requirements, technical design, prototype, test plan, user
manuals and documentation, as well as the platform, front-end and back-end development,
GPS tracking, payment gateway, and integration with existing systems.

4
3. Requirement Analysis
The following parts of Software Requirements Specification (SRS) report should be
included in this chapter.
3.1. Use Cases Diagram(s)

Figure 3.1: Use Case

5
3.2. Functional Requirements

Table 3.1: Functional Requirements

No. Requirement Description

Allow parents and students to register and create their accounts. Collect basic
FR-01 User Registration
information such as name, contact details, and student ID.

Provide real-time tracking of the school bus or van using GPS technology. Allow
FR-02 Vehicle Tracking
parents and students to track the location of the vehicle.

Provide a feature to identify the driver of the school transport vehicle to ensure safety
FR-03 Driver Identification
and accountability.

Allow parents and students to book seats for school transport vehicles. Manage seat
FR-04 Seat Booking
availability and assign seats based on user preferences and availability.

Ensure the security of user's personal information and implement measures to prevent
FR-05 Security
unauthorized access to the app.

Provide a secure payment gateway for parents to make payments for the school
FR-06 Payment
transport service through the app.
Design the app with accessibility in mind, ensuring it meets the needs of users with
disabilities. Implement features such as screen reader compatibility, adjustable font
sizes, color contrast, and intuitive navigation to comply with accessibility standards.
FR-07 Accessibility
Utilize universally recognizable icons and visual cues on the interface to aid
understanding, particularly for drivers with limited literacy skills. Ensure compliance
with WCAG 2.1 guidelines to provide an inclusive user experience for all users.

3.3. Non-Functional Requirements

Table 3.2: Non-Functional Requerments

No. Requirement Description

The system should provide fast and responsive performance, ensuring quick loading times
NFR-01 Performance
and minimal latency.
The user interface should be intuitive and user-friendly, allowing users to navigate and
NFR-02 Usability
interact with the app easily.
The system should be reliable and available for use at all times, with minimal downtime and
NFR-03 Reliability
system failures.
The app should be scalable to accommodate a growing user base and handle increasing data
NFR-04 Scalability
and traffic loads.

6
4. Design and Architecture
4.1. System Architecture
It is a software development methodology that focuses on building the app's features
and functionality as modular and reusable components. Each component can be developed
separately and can be combined with other components to create the final app. This
approach allows for more efficient development, as the components can be reused in
different parts of the app, reducing the need for redundant code. It also enables faster
development and easier maintenance, as changes made to a component will automatically
reflect in all the parts of the app where that component is used. The component-based
approach is a software development methodology that focuses on building the app's
features and functionality as modular and reusable components. Each component can be
developed separately and can be combined with other components to create the final app.
This approach allows for more efficient development, as the components can be reused in
different parts of the app, reducing the need for redundant code. It also enables faster
development and easier maintenance, as changes made to a component will automatically
reflect in all the parts of the app where that component is used. In addition, the component-
based approach helps to ensure better scalability and flexibility, as new components can
be added or removed from the app as needed, without affecting the rest of the codebase.

7
4.2. Data Representation
4.2.1. ER Diagram

Figure 4.1: ER Diagram

8
4.3.1. Class Diagram

Figure 4.2: Class Diagram

9
4.3.2. Sequence Diagram

Figure 4.3: Sequence Diagram

for Add School

Figure 4.4: Sequence Diagram

for update vehicle

10
Figure 4.5: Sequence Diagram
for update driver details

Figure 4.6: Sequence Diagram

for feedback review

11
 Figure 4.7: Sequence Diagram
for connection request

Figure 4.8: Sequence Diagram for

update parent details

12
Figure 4.9: Sequence Diagram for
update Payment Method

13
4.3.3. System Sequence Diagram

Figure 11: System Sequence

Diagram for Register account

Figure 4.10: System Sequence

Diagram

14
4.2.5. Design Models
The design methodology is one of the most fundamental components of the model.
Software design methodology offers a methodical and logical way to move forward with the
design process as well as a set of rules for making decisions. Here the design methodology
followed is component-based where each feature of the app is developed as a separate and
reusable component. The app is built using React Native, a cross-platform framework that
enables development for both iOS and Android platforms simultaneously. The app is divided
into three main layers: presentation, business logic, and data storage. The presentation layer
handles the user interface, while the business logic layer contains the app's core functionality,
and the data storage layer stores and manages user data.

15
5. Implementation
In our implementation, key algorithms power the School Transport Service app. These
include real-time tracking, notification management, driver selection, booking, rating, and
school search algorithms. We also integrate external APIs to enhance app functionality.

5.1. Algorithm
 Real-time Tracking Algorithm: This algorithm is responsible for tracking the
location of school vehicles in real-time. It utilizes the Global Positioning System
(GPS) data from the vehicles and updates the location information on the user
interface.
 Notification Management Algorithm: This algorithm handles the sending and
receiving of notifications related to pick-up and drop-off times, delays, and schedule
changes. It communicates with the server to fetch and send notifications to the
respective users.
 Driver Selection Algorithm: This algorithm assists parents in selecting a suitable
driver based on ratings and feedback from other users. It retrieves driver information
and ratings from the database and presents them to the user for selection.
 Booking Algorithm: This algorithm allows parents to book transportation services for
their children. It checks for available vehicles, validates the requested dates and times,
and assigns the booking to the selected vehicle and driver.
 Rating Algorithm: This algorithm calculates and displays the rating of schools based
on feedback from parents and students. It aggregates the ratings and reviews received
for each school and calculates the average rating.
 School Search Algorithm: This algorithm enables parents to search for schools based
on specific criteria such as location, name, or rating. It retrieves school information
from the database and filters the results based on the search criteria.

5.2. External APIs

Table 5.1: APIs
List down the
Purpose of
Name of API Description of API function/class name in
usage
which it is used

Twilio Used for sending OTP Authentication Authentication

Google maps Used for live location

Live Tracking Location
API tracking

16
5.3. User Interface
Parents App

Figure 5.1: Signup Screen

17
Figure 5.2: Purpose Selection
Screen

18
Figure 5.3: SignIn Screen

19
Figure 5.4: Send OTP Screen

20
Figure 5.5: OTP Screen

21
Figure 5.6: Home Screen

22
Figure 5.7: Notification Screen

23
Figure 5.8: Edit Profile Screen

24
Figure 5.9: Vehicle List Screen

25
Figure 5.10: Live Location Screen

26
Figure 5.11: Subscription Screen

27
Figure 5.12: Available School Screen

28
Figure 5.13: Vehicle Details Screen

29
Figure 5.14: Driver Profile Screen

30
Figure 5.15: School Details Screen

31
 Driver App

Figure 5.18: SignIn Screen

32
Figure 5.19: Send OTP Screen

33
Figure 5.19: OTP Screen

34
Figure 5.20: Home Screen

35
Figure 5.21: Notification Screen

36
Figure 5.22: Edit Profile Screen

37
Figure 5.23: School Details Screen

38
Figure 5.24: Live Location Screen

39
Figure 5.11: Subscription Screen

40
Figure 5.12: Available School Screen

41
Figure 5.21: Notification Screen

42
Figure 5.22: Edit Profile Screen

43
6. Testing and Evaluation
Testing encompasses manual evaluations, unit, functional, and integration testing to
ensure the School Transport Service functions reliably and meets user expectations.
6.1. Manual Testing
Manual testing is a critical phase in software development where the software is
meticulously evaluated by human testers to identify potential errors or inconsistencies. It
enables a comprehensive understanding of the software's functionalities and user
experience, making it an indispensable part of ensuring software quality.
6.1.1. System Testing
Once the School Transport Service system has been successfully developed,
comprehensive testing is performed to ensure its proper functioning and adherence
to the defined requirements. System testing helps identify any hidden errors or issues
that may impact the user experience. It involves various types of testing, including
unit testing, functional testing, and integration testing. All testing activities must be
completed before the system is deployed for users to ensure a reliable and robust
transportation solution for schools.
During system testing for the School Transport Service, the following activities
are carried out:
1. Unit Testing: Individual components and functionalities of the system, such as
user registration, notification management, and location tracking, were
thoroughly tested to ensure they work correctly and meet the expected
functionality.
2. Functional Testing: The entire system is tested to ensure it performs according
to the defined functional requirements. This included validating features such as
user authentication, real-time tracking, notification delivery, and data
management.
3. Integration Testing: Different modules and components of the system were
tested together to ensure smooth communication and integration between them.
This verifies that the system as a whole function correctly and maintains data
consistency across various components.
By conducting thorough system testing, the School Transport Service ensures that
the developed system meets the requirements, functions as intended, and provides a
reliable and user-friendly solution for managing school transportation. The testing
phase is crucial in identifying and resolving any issues or defects, ensuring a high-
quality and dependable transportation service for schools and their stakeholders.
6.1.2. Unit Testing
Once the system has been successfully developed. We perform unit testing
where individual components of a software are tested to verify their correct
operation. This approach ensures the reliability of each unit, or function, and aids
in the early detection of errors within the code.

44
 Unit Testing 1: Login and signup as Driver and parent.
Testing Objective: To ensure the login and signup is working correctly

Table 6.1: Login and Signup Unit Testcase

No. Test Case/Test Script Attribute and Value Expected Result Result
Phone No:
Successful login, user redirected
1 Login as Parent user 923400190311, Password: Pass
to the Home Screen
12345678
Phone No:
Successful login, user redirected
2 Login as Driver user 923400190311, Password: Pass
to the Home Screen
12345678
Phone No:
Login with incorrect Error message displayed:
3 923400540311, Password: Fail
password "Incorrect password"
12378
4 Signup as a new user Phone No: 923400190311 Send OTP on phone number Pass
Successful authentication of
Receive OTP and
5 OTP: 123456 OTP user redirected to the Home Pass
authenticate
Screen

 Unit Testing 2: Edit Modules

Testing Objective: To ensure the Edit Modules are working properly.

Table 6.2: Edit Profile Unit Testcase

Test Case/Test
No. Attribute and Value Expected Result Result
Script
Name:hassaan, Phone
Edit profile with valid no:0333333333, Success message displayed:
1 Pass
changes Address:Atd,CNIC:0000- "Profile updated successfully"
0000000-0,etc
Edit profile with invalid
CNIC:00000-0000-00, License Error message displayed:
2 cnic and license no Fail
No,etc "Invalid format"
format
Edit vehicle details with Vehicle ID: 12345, Capacity: Success message displayed:
3 Pass
valid changes 30, Vehicle Type: Van "Vehicle details updated"

45
 Unit Testing 3: Subscription request, Notification and Live tracking Modules.
Testing Objective: To ensure the Subscription request, Notification and Live tracking Modules
are working properly.

Table 6.3: Request Unit Testcase

No. Test Case/Test Script Attribute and Value Expected Result Result
Driver Name: username, Seat
Send seat request Notification sent to the driver
1 Request From: school details, Pass
notification to the driver for the seat request approval
address with seats required
Verify seat request Parent Name: name, Seat Request Notification received from the
2 Pass
notification from the driver details: message driver for the seat request
Real-time location of the
3 Live tracking of vehicle Subscribed Driver: Name Pass
vehicle displayed on the map
Subscription cancellation Success message displayed:
6 Subscription Type: Premium Pass
Request "Subscription cancelled"

6.1.3. Functional Testing

 Functional Testing 1: Login with different roles as shown in Table 5.4

Objective: To ensure the login and signup is for different roles move to the accurate screens

Table 6.4: Login Functional Testcase

Test Case/Test
No. Attribute and Value Expected Result Result
Script
Phone No: 923400190311, Successful login, user redirected
1 Login as Parent user Pass
Password: 12345678 to the Home Screen
Phone No: 923400190311, Successful login, user redirected
2 Login as Driver user Pass
Password: 12345678 to the Home Screen
Login with incorrect Phone No: 923400540311, Error message displayed:
3 Fail
password Password: 12378 "Incorrect password"

 Functional Testing 2: Subscription request and Live tracking Modules

Objective: To ensure that the Subscription request and Live tracking functionality is
working accurate

Table 6.5: Request Functional Testcase

No. Test Case/Test Script Attribute and Value Expected Result Result
Driver Name: username, Seat
Send seat request Notification sent to the driver
1 Request From: school details, Pass
notification to the driver for the seat request approval
address with seats required
Verify seat request Parent Name: name, Seat Notification received from the
2 Pass
notification from the driver Request details: message driver for the seat request
Real-time location of the
3 Live tracking of vehicle Subscribed Driver: Name Pass
vehicle displayed on the map

46
 6.1.4. Integration Testing
Table 6.6 : Integration Testcase
No. Test Case/Test Script Attribute and Value Expected Result Result
Successful registration using the
Phone Number Registration Phone Number:
1 phone number and successful Pass
and OTP Confirmation Test 1234567890
OTP confirmation
Phone Number: Successful login using the phone
Phone Number Login and
2 1234567890, OTP: number and successful Pass
OTP Verification Test
123456 verification of the OTP
Phone Number:
Phone Number Login with Error message displayed:
3 1234567890, OTP: Fail
Invalid OTP Test "Invalid OTP"
654321
Phone Number:
Phone Number Login with Error message displayed:
4 1234567890, OTP: Fail
Expired OTP Test "Expired OTP"
987654
Phone Number Login with Phone Number:
Error message displayed: "Phone
5 Unregistered Phone Number 9876543210, OTP: Fail
number not registered"
Test 123456
Signup with Existing Phone Phone Number: Error message displayed: "Phone
6 Fail
Number Test 1234567890 number already registered"
Signup with Invalid Phone Phone Number: Error message displayed:
7 Fail
Number Test 9876543210 "Invalid phone number"
Signup with Valid Phone Phone Number:
Error message displayed:
8 Number and Invalid OTP 9876543210, OTP: Fail
"Invalid OTP"
Test 654321
Name: Hassaan, Successful update of the user's
Edit Profile and Phone
9 Phone Number: profile information, including Pass
Number Update Test
1234567890 the phone number
Edit Vehicle Details and Vehicle ID: 12345, Successful edit of vehicle details
10 Pass
Seat Request Requested Seat: 5 and seat request integration
Find Vehicle and Live School ID: 98765, Successful search for the vehicle
11 Pass
Tracking Vehicle ID: 12345 and tracking its live location
Subscription cancellation Subscription Type: Success message displayed:
12 Pass
Request Premium "Subscription cancelled"
Successful approval of seat
13 Approve Seat Request Request ID: 54321 request and integration with Pass
notification system
Successful notification sent for
Seat Request Notification Request ID: 54321,
14 the seat request and integration Pass
and Live Tracking Driver ID:3321
with live tracking of the vehicle
Driver Name:
username, Seat
Send seat request Notification sent to the driver for
15 Request From: school Pass
notification to the driver the seat request approval
details, address with
seats required
Parent Name: name,
Verify seat request Notification received from the
16 Seat Request details: Pass
notification from the driver driver for the seat request
message
Subscribed Driver: Real-time location of the vehicle
17 Live tracking of vehicle Pass
Name displayed on the map

47
 6.2. Automated Testing:
Automated testing involves the use of scripts and testing tools to perform software
tests more quickly and consistently, enhancing efficiency and reducing the need for
repetitive manual work.

6.2.1.Tools used:
Table 6.7: Tools Used
Tool Name Tool Description Applied on [list of related tests Results
cases / FR / NFR]
Appium Open-source framework for automated Test cases related to UI and user Successfully validated UI
mobile app testing interactions interactions and user flows
XCUITest Apple's testing framework for iOS app IOS-specific test cases, FR and Ensured accurate
testing NFR functionality on iOS devices

48
7. Conclusion and Future Work

7.1. Conclusion
In conclusion, the School Transport Service Mobile App is an innovative and
transformative solution that addresses the complexities and challenges of school
transportation management. By leveraging the power of technology, this app offers a
seamless and user-friendly experience for parents and students. With features such as ride
booking, parents can conveniently schedule transportation for their children with just a
few taps on their mobile devices. Real-time tracking functionality provides parents with
peace of mind as they can monitor the exact location of the school vehicle, ensuring the
safety and security of their children throughout the journey. The app goes beyond basic
functionality by allowing parents to select vehicles and drivers based on ratings, enabling
them to make informed decisions about their child's transportation. Additionally, the
option to set a budget empowers parents to choose travel options that align with their
financial preferences. Throughout the development process, Agile methodology was
employed, ensuring continuous improvement and responsiveness to user feedback. The
utilization of React Native facilitated the creation of a cross-platform app, making it
accessible to a wider user base on both iOS and Android devices. The integration of
Google Maps API enhanced the app's tracking capabilities, providing accurate and up-to-
date location information. In conclusion, the School Transport Service Mobile App
revolutionizes the way parents and students manage school transportation. It streamlines
the process, enhances convenience, and prioritizes the safety of students. By simplifying
the booking process, offering real-time tracking, providing vehicle and driver selection,
and accommodating budget preferences, the app truly transforms the school
transportation experience for all stakeholders involved.

7.2. Future Work

Future work for the School Transport Service Mobile App includes the following
areas of improvement and expansion:
 Enhanced Features: Continuously enhancing the app's features and functionality
based on user feedback and emerging technologies. This could include adding
additional services such as automated attendance tracking, route optimization,
integration with school calendars, and communication features between parents,
drivers, and school administrators.
 Integration with Payment Systems: Integrating the app with secure and
convenient payment systems to enable seamless and cashless transactions for ride
bookings. This could involve integrating with popular payment gateways or
developing an in-app payment solution.
 Expansion to More Schools: Expanding the reach of the app by partnering with
more schools and educational institutions. This would involve establishing
collaborations with schools, implementing the app's services in new geographical

49
 locations, and onboarding additional vehicles and drivers to accommodate the
increased demand.
 Data Analytics and Reporting: Implementing robust data analytics capabilities
to gather insights on usage patterns, transportation trends, and performance
metrics. This data can be leveraged to optimize operations, improve service
quality, and make data-driven decisions for future enhancements.
 Integration with School Management Systems: Integrating the app with existing
school management systems to streamline data exchange and information flow
between the transportation service and the school administration. This integration
would ensure seamless coordination and efficient communication between various
stakeholders involved in managing school transportation.
 Multilingual Support: Adding multilingual support to the app to cater to users
from diverse linguistic backgrounds. This would enhance accessibility and
usability for parents and students who prefer to interact with the app in their native
language.
 User Experience Refinements: Continuously improving the user experience by
refining the app's interface, optimizing performance, and implementing intuitive
user workflows. This includes conducting user testing, gathering feedback, and
iteratively enhancing the app's design to ensure a seamless and enjoyable user
experience.

These future endeavors will enable the School Transport Service Mobile App to evolve and
adapt to the changing needs of parents and Drivers further enhancing its value and effectiveness
in managing school transportation efficiently.

50
8. References
1. National Center for Education Statistics (NCES). (2018). The Condition of Education
2018: Strategies for Improving School Attendance and Truancy.
Retrieved from https://nces.ed.gov/programs/coe/indicator_cga.asp
2. Title: School Transport Safety Guidelines
Website: www.schooltransportsafetyguidelines.com
3. Safe Stop. (n.d.). School Bus Tracking and Parent Communication.
Retrieved from https://www.safestopapp.com/
4. Zonar Systems. (n.d.). School Bus Tracking and Fleet Management.
Retrieved from https://www.zonarsystems.com/solutions/school-transportation/
5. Google Maps Platform. (n.d.). Mapping Platform for Web and Mobile.
Retrieved from https://cloud.google.com/maps-platform

51