COMSATS University

Islamabad Sahiwal, Pakistan

Vehicle Wave
(Mobile Application)

By
Muhammad Bilal CIIT/ SP20-BSE-050 /SWL

Raima Fatima CIIT/ SP20-BSE-020/SWL

Shahzaib Zahid CIIT/ SP20-BSE-025 /SWL

Supervisor

Mr. Muhammad Umar

Bachelor of Science in Software Engineering (2020-2024)

The candidates confirm that the work submitted on their own and appropriate credit has
been given where reference has been made to the work of others.
 COMSATS University
Islamabad Sahiwal, Pakistan

Vehicle Wave (android)

(Mobile Application)

A Project Represented to
COMSATS University Islamabad, Sahiwal Campus

In partial fulfillment
the requirement of the degree of

Bachelor of Science in Software Engineering (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 the
report entirely based on our efforts. If any part of this project is proved to be copied from any
source or found to be the reproduction of some other. We will stand by the consequences. No
portion of the work presented has been submitted because of any application for any other
degree or qualification of this or any other university or institute of learning.

Muhammad Bilal Raima Fatima Shahzaib Zahid

 Certificate of approval
This is to certify that the final year project of BS(SE) “Vehicle Wave(android)” was
developed by Muhammad Bilal (CIIT/SP20-BSE-050/SWL), Raima Fatima(CIIT/SP20-
BSE-020/SWL) and Shahzaib Zahid (CIIT/SP20-BSE-025/SWL) under the supervision of
“Mr. Muhammad Umar” and that in his opinion; it is fully adequate, in scope and quality
for the degree of bachelors of science in computer science.

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

Supervisor

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

External Examiner

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

Head of Department

(Department of Computer Science)

 Executive summary
Vehicle Wave revolutionizes the industry by offering a comprehensive, user-friendly, and
efficient solution for managing auto shipments. This cutting-edge application optimizes every
stage of the shipment process, enhancing operational efficiency, real-time tracking, and
customer satisfaction. The functional requirements of the Auto Shipment Management
System are the cornerstone of its capabilities, defining the specific behaviors and functions
that the system must perform to meet user needs. These requirements encompass essential
features such as user authentication, shipment creation, real-time tracking, route optimization,
and communication tools. Users, including drivers, dispatchers, and customers, can interact
with the system through an intuitive interface, creating and managing shipments seamlessly.
The system ensures efficient route planning, utilizing advanced algorithms to optimize travel
routine time and fuel consumption.

The app's development will follow an incremental model, allowing for the implementation of
the features in stages. The development process will be guided by the functional requirements
of the app, user authentication, shipment creation, real-time tracking, route optimization, and
communication tools. Users, including drivers, dispatchers, and customers, can interact with
the system through an intuitive interface, creating and managing shipments seamlessly.

The app's testing and evaluation will involve unit, integration, and system testing to ensure
that all functionalities are working as intended. The app will also undergo user acceptance
testing to improve the app's usability.

The auto-shipment system revolutionizes the logistics landscape, offering a powerful,

efficient, and user-friendly platform. By seamlessly integrating route optimization, real-time
tracking, communication tools, and automated documentation, this application transforms
auto shipment management into a streamlined, transparent, and customer-centric process,
setting new benchmarks in the industry.
 Acknowledgment
All praise is to almighty Allah who bestowed upon us a minute portion of his boundless
knowledge by which we were able to accomplish this challenging task.

We are greatly indebted to our project supervisor “Mr. Muhammad Umar”. Without their
supervision, advice, and valuable guidance, the 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.

Muhammad Bilal Raima Fatima Shahzaib Zahid

 Abbreviations
OOP Object Oriented Programming

SDLC Software Development Life Cycle

iOS iPhone Operating System

API Application Programming Interface

GUI Graphical User Interface

Table of Contents
1 Introduction.......................................................................................................................1
1.1 Project Brief...................................................................................................................1
1.2 Relevance to the course module.....................................................................................2
1.3 Background....................................................................................................................2
1.4 Literature review...........................................................................................................2
1.4.1 Analysis review from literature review............................................................................................3

1.5 Methodology and software life cycle..............................................................................3

1.5.1 Design methodology........................................................................................................................3
1.5.2 The rationale behind the selected methodology...............................................................................4

2 Problem definition............................................................................................................6
2.1 Problem statement.........................................................................................................6
2.2 Deliverables and development requirements.................................................................6
2.2.1 Deliverables:....................................................................................................................................6
2.2.2 Development Requirements:...........................................................................................................6

2.3 Current system...............................................................................................................7

3 Requirement analysis.......................................................................................................8
3.1 Use case diagram............................................................................................................8
3.1.1 Use case 1 description.........................................................................................................................8

3.2 Use case 2.....................................................................................................................10

3.2.1 Use case 2 description...................................................................................................................10

3.3 Use case 3.....................................................................................................................12

3.3.1 Use case description 3...................................................................................................................12

3.4 Functional requirements..............................................................................................14

3.4.2 Shipment Management:................................................................................................................14
3.4.3 Customer Module..........................................................................................................................14
3.4.4 Price Generator..............................................................................................................................14
3.4.5 Admin Module...............................................................................................................................15

3.5 Non-functional requirements.......................................................................................15

3.5.1 Usability........................................................................................................................................15
3.5.2 Performance...................................................................................................................................16
3.5.3 Reliability......................................................................................................................................16
3.5.4 Compatibility.................................................................................................................................16
3.5.5 Availability....................................................................................................................................16
3.5.6 System requirements......................................................................................................................16
3.5.7 Hardware requirements..................................................................................................................16
3.5.8 Software requirement.....................................................................................................................16

4 Design and architecture..................................................................................................15

4.1 System architecture......................................................................................................15
4.2 Data representation......................................................................................................15
 4.2.1 Sequence diagram..........................................................................................................................15
4.2.2 Class diagram................................................................................................................................16
4.2.3 Process flow representation...........................................................................................................16

4.3 Design models...............................................................................................................18

4.3.1 Incremental model.........................................................................................................................18

5 Implementation...............................................................................................................19
5.1 Algorithm.....................................................................................................................19
5.1.1 User Authentication:......................................................................................................................19

5.2 External API's..............................................................................................................21

5.3 User interface...............................................................................................................22
5.4 Screen objects and actions.............................................................................................24
6 Testing and evaluation....................................................................................................24
6.1 Manual testing..............................................................................................................24
6.1.1 System testing................................................................................................................................24
6.1.2 Unit testing....................................................................................................................................25

6.2 Integration testing........................................................................................................27

6.3 Functional testing.........................................................................................................28
7 Conclusion and future work..........................................................................................29
7.1 Conclusion....................................................................................................................29
7.2 Future work.................................................................................................................29
References...............................................................................................................................31
List of Figures
FIGURE 1.1 INCREMENTAL MODAL.......................................................................................................................4
FIGURE 4.1 SEQUENCE DIAGRAM........................................................................................................................15
FIGURE 4.2 CLASS DIAGRAM...............................................................................................................................16
FIGURE 4.3 PROCESS FLOW.................................................................................................................................17
FIGURE 4.4 INCREMENTAL MODEL......................................................................................................................18
FIGURE 5.2 USER INTERFACE 2............................................................................................................................22
FIGURE 5.1 USER INTERFACE 1............................................................................................................................22
FIGURE 5.4 USER INTERFACE 3............................................................................................................................23
FIGURE 5.3 USER INTERFACE 3............................................................................................................................23
FIGURE 5.5 USER INTERFACE 5............................................................................................................................23

List of Tables
TABLE 1.1 COMPARABILITY CHART........................................................................................................................3
TABLE 5.1 EXTERNAL APIS...................................................................................................................................21
TABLE 6.1 MANUAL TESTING...............................................................................................................................24
TABLE 6.2 SYSTEM TESTING.................................................................................................................................24
TABLE 6.3 UNIT TESTING.....................................................................................................................................25
 Chapter 1
Introduction
1 Introduction
In today's fast-moving world, getting vehicles from one place to another efficiently is crucial
for businesses and individuals. Imagine a world where sending a car, a truckload of goods, or
even a single package could be as simple as a few taps on your smartphone. That's exactly
what the vehicle shipment system offers. It's like having a personal logistics manager in your
pocket, simplifying the way vehicles are transported.

With this user-friendly app, you can effortlessly create and manage shipments. Whether
you're a business sending out multiple vehicles or a customer needing a car transported, the
process is as easy as entering your details and destination. The app not only plans the best
routes for the vehicles but also allows you to track them in real-time. You can see exactly
where your shipment is, ensuring you're always in the know. Plus, communication between
drivers, dispatchers, and customers is seamless, reducing misunderstandings and ensuring
smooth operations.

In essence, this android application transforms the hassle of vehicle shipment into a hassle-
free experience. It's about simplifying logistics, saving time, and ensuring that your precious
cargo, whether it's a car, a truck, or any goods, reaches its destination swiftly and securely.
Welcome to the future of effortless transportation right at your fingertips.

1.1 Project Brief

Our vehicle shipment system is a user-friendly android application designed to simplify the
process of shipping vehicles efficiently and reliably. With a straightforward interface, the app
allows users to easily create, track, and manage vehicle shipments from their smartphones.

Users can quickly input shipment details, including vehicle type, destination, and preferred
delivery date. The app then automatically generates optimized routes, reducing delivery time
and costs. The application offers real-time tracking features, enabling users to monitor the
exact location of their shipments. This ensures transparency and allows for timely updates on
delivery progress. Our app promotes seamless communication between drivers, customers,
and dispatchers. Instant messaging and notifications keep everyone in the loop, reducing
misunderstandings and enhancing collaboration. In essence, our vehicle shipment
management system simplifies the complexities of vehicle shipping. It provides a hassle-free
way to create, track, and manage shipments, ensuring a smooth and efficient experience for
all users involved.

11
The primary aim is to streamline vehicle shipment operations. By integrating advanced route
optimization algorithms and real-time tracking, the system aims to reduce transit times,
minimize fuel consumption, and enhance overall operational efficiency.

The system aims to provide complete transparency in the shipment process. Real-time
tracking features empower users with precise location data, ensuring they are always aware of
the status and location of their vehicles. This transparency builds trust and confidence among
customers and stakeholders.

The system aims to facilitate seamless communication between drivers, dispatchers, and
customers. Instant messaging and automated notifications ensure that everyone involved is
well-informed about shipment updates, reducing communication gaps and enhancing
collaboration.

1.2 Relevance to the course module

The main purpose of the project is to provide ease and save time for people having android
phone with the help of the android application. So, it is related to the field of software
engineering. We have concepts of OOP, software engineering, SDLC, etc. in the
development of this android application.

1.3 Background
In a world where moving vehicles from one place to another is common, there's a need for a
simple and efficient way to manage these shipments. Traditional methods often involve
paperwork, phone calls, and guesswork about vehicle locations. To solve these challenges,
our auto shipment system android application was created. It's like a digital assistant for
shipping vehicles. This app uses smart technology to plan the best routes, track vehicles in
real-time, and keep everyone involved in the shipment process connected. By eliminating the
confusion and enhancing communication, this application makes vehicle shipments smoother,
faster, and much more reliable for everyone involved.

1.4 Literature review

We have studied systems that are precisely not like these, but some of the modules are
implemented in these apps:

 ShipItNow[1]
 QuickLoad Logistics[2]

12
1.4.1 Analysis review from literature review
Table 1.1 Comparability Chart

Application Name Weakness Proposed Project Solution

 Our application
integrates advanced
 ShipItNow lacks efficient
route optimization
route optimization, often
ShipItNow algorithms,
leading to longer delivery
ensuring the
times and increased fuel
quickest and most
costs.
cost-effective
routes for vehicle
shipments.

 Our application
automates the
documentation
 QuickLoad Logistics
process, eliminating
lacks automated
paperwork and
QuickLoad documentation
reducing the chance of
capabilities, relying
Logistics errors.
heavily on manual
paperwork for record-  It maintains digital
keeping. records of shipments,
 This manual process is ensuring accuracy and
prone to errors and can be compliance with
time-consuming for regulations, saving
administrative tasks. time for
administrative tasks
and enhancing overall
efficiency.

1.5 Methodology and software life cycle

1.5.1 Design methodology
We will use “Incremental design methodology”. In the incremental model, firstly all the
requirements are gathered. After gathering all the requirements and analysis we further move
to the next phase which is making the design of a project and then the implementation,
testing, and maintenance phases. As all the next phases of this model are dependent on the
previous phase.

In the software development process, the very first model that is published from other
engineering processes that cascade from one phase to another is known as the waterfall
model. This model is also known as the linear sequential model. In the waterfall model,

13
firstly all of the requirements are gathered. After gathering all the requirements and analysis
of all the requirements further move to the next phase which is making the design of a project
and then the implementation, testing, and maintenance phases. All the next phases of this
model are dependent on the previous phase. All the phases worked as a waterfall after one
another. We will use this methodology.

Figure 1.1 Incremental modal

1.5.2 The rationale behind the selected methodology

The incremental software development methodology is an iterative approach to software
development that involves breaking down a large project into smaller, more manageable
components or increments. Each increment is developed and tested independently, allowing
for feedback and improvement throughout the development process. This methodology is
ideal for projects that involve complex and evolving requirements, as it allows for flexibility
and adaptability to changing needs.
For the Vehicle Wave project, the incremental software development methodology was
selected for several reasons. Firstly, the project involves developing an application with
various modules, each with specific requirements and functionalities. By breaking down the
project into smaller increments, the development team can focus on one module at a time,
ensuring that each module is developed to the highest standard before moving on to the next
one.
Secondly, the incremental approach allows for regular feedback from stakeholders, including
users and project managers. This feedback can be incorporated into each increment, ensuring

14
that the final product meets the needs and expectations of users.
Finally, the incremental software development methodology allows for faster delivery and
deployment of the product. Each increment can be tested and released independently,
allowing for early delivery of working software and faster time-to-market.
Overall, the incremental software development methodology was selected for the Vehicle
Wave project due to its flexibility, adaptability, and ability to deliver a high-quality and
reliable product promptly.

15
 Chapter 2

Problem definition
2 Problem definition
2.1 Problem statement
The auto shipment industry faces numerous challenges that hinder its efficiency and customer
satisfaction. Existing processes are often plagued by inefficiencies in route planning, lack of
real-time tracking, ineffective communication between stakeholders, and cumbersome
paperwork for documentation. These issues lead to longer delivery times, increased
operational costs, customer dissatisfaction due to lack of transparency, and potential errors in
compliance-related paperwork. Additionally, the absence of a centralized and user-friendly
platform exacerbates these challenges, making it difficult for drivers, dispatchers, and
customers to collaborate seamlessly.

Considering these challenges, there is a pressing need for a sophisticated Auto Shipment
Android Application. This application must address the inefficiencies in route planning,
provide accurate real-time tracking, facilitate seamless communication, automate
documentation processes, and offer an intuitive interface for all users involved. By doing so,
it will not only optimize operational processes within the auto shipment industry but also
enhance transparency, communication, and overall customer experience. The development of
such an application is crucial to revolutionizing the auto shipment sector, ensuring timely
deliveries, reducing costs, and fostering trust and satisfaction among businesses and
consumers alike.

2.2 Deliverables and development requirements

2.2.1 Deliverables:
 Intuitive and easy-to-navigate design for drivers, dispatchers, and customers.
 User authentication and authorization system for secure access control.
 User manuals and documentation for end-users and administrators.
 Shipment creation and editing features.
 Route planning and optimization functionality.
 Database for storing shipment data, user profiles, and historical records.
 APIs for communication between the Android app and the backend.

2.2.2 Development Requirements:

1. The app should be developed for the android platform.

6
 2. The app should be user-friendly and intuitive, with a simple and clean interface design
that allows users to navigate easily between modules.
3. The app should include the following modules:
 Shipment management module to develop features for creating, editing, and
canceling shipments, allowing users to input essential details such as vehicle type,
destination, and delivery time.
 Implement a secure user authentication system for drivers, dispatchers, and
customers, ensuring data privacy and access control.
 Route optimization module to implement algorithms for efficient route planning,
considering factors like distance, and delivery time windows to optimize shipment
routes.
 Implement automated notifications and alerts to inform users about shipment
status changes and important updates.
 Price generation module ensures transparency and fairness in pricing, providing
both the business and customers with clear insights into the expenses involved in
vehicle shipments.
4. The app should allow users to customize their reminders, and notifications according
to their preferences.
5. The app should have a reliable and secure database that stores user data and app
settings.
6. The app should have a testing phase to identify and fix bugs, as well as optimize the
app's performance and speed.
7. The app should comply with the relevant privacy and security regulations and
standards.
8. The app should have regular updates to fix bugs, add new features, and improve the
app's overall performance and usability.

2.3 Current system

The current systems frequently lack the seamless integration of automated documentation and
dynamic pricing, leading to operational bottlenecks and customer dissatisfaction. Unlike
these systems, our solution offers advanced route optimization, precise real-time tracking,
seamless communication features, automated documentation, and transparent pricing. [3]

7
 Chapter 3

Requirement Analysis
3 Requirement analysis
3.1 Use case diagram
In this use case diagram, we are showing how a user can find the timetable. There are three
types of users: Customer, Admin, and Driver.

Figure 3.1 Use case of booking

3.1.1 Use case 1 description

The table below indicates a comprehensive use case template filled in with an example drawn
from use case 1
Table 3.1 Description for book shipment

Use Case ID CUIT-1

Use Case Name Book Shipment

Actors Customer

This use case enables the customer to create a new shipment booking.
Description Users can enter their address, vehicle details, and schedule a
shipment for transport.

8
Trigger User selects the "Book Shipment" option in the application.

Preconditions User is logged into their account.

Shipment is scheduled for pickup, and the user receives a

Post conditions
confirmation.

 User selects the "Book Shipment" option in the application.

 User enters their pickup and delivery addresses.

 User provides vehicle details (type, make, model, etc.).

 User selects preferred pickup date and time.

 User confirms the booking details.

Normal Flow
 System calculates the estimated cost of the shipment based on
entered information.

 User confirms the booking and makes the payment.

 System processes the payment, generates a confirmation, and

schedules the shipment for pickup.

 User can edit the entered information at any step before

confirming the booking.
 System displays an error message, allowing the user to update
Alternative Flows payment information or choose an alternative payment
method.
 System notifies the user of alternate available dates/times for
shipment scheduling.

 If the user enters an invalid pickup or delivery addresses, the

system displays an error message.
Exceptions
 If the user enters invalid vehicle details, the system prompts
for valid information.

Assumptions  User has a stable internet connection.

 User has valid and accurate address and vehicle details.
 Payment processing services are available and functional.
 System can accurately calculate shipment costs based on the

9
 provided details.

3.2 Use case 2

3.1 Use case of confirm delivery 1

3.2.1 'Use case 2 description

The table below indicates a comprehensive use case template filled in with an example drawn
from use case 2.
Table 3.2 Description for confirmation 1

Use Case ID CUIT-2

Use Case Name Confirm Delivery

Actors Driver

This use case represents the interactions of a driver within the appli.
Description The driver can log in, view assigned loads, update load statuses, view
load details, and confirm deliveries.

10
 The use case is triggered when the driver successfully logs into the
Trigger
mobile application.

 The driver must have a valid account and must be logged into
the application.
Pre condition
 There must be assigned loads in the system for the driver to
interact with.

 Load statuses are updated based on the driver's actions.

 Load details are confirmed and updated in the system.
Post conditions
 Confirmation notifications are sent to the users associated
with the shipments.

1. Login:
 Driver enters valid credentials.
 System authenticates the driver.
 System redirects the driver to the dashboard.
2. View Assigned Load:
 The driver navigates to the assigned loads section.
Normal Flow  The system displays a list of assigned shipments to the
driver.
3. Update Load Status:
 The driver selects a load from the list.
 The driver updates the load status.
 System records the status update.

If the driver enters invalid credentials during login:

Alternative Flows
System displays an error message, and the use case ends.

 If the driver loses internet connectivity during any interaction:

Exceptions
 System displays a message indicating a loss of connection.

Assumptions  Drivers have access to a stable internet connection during

interactions.
 Load assignments are made correctly and are available in the
system for the driver.

11
3.3 Use case 3

Figure 3.3 Use case for admin management 1

3.3.1 Use case description 3

The table below indicates a comprehensive use case template filled in with an example drawn
from use case 3.
Table 3.3 Description for admin 1

Use Case ID CUIT-3

Use Case Name Admin Management

Actors Admin

This use case represents the interactions of an Admin within the Auto
Shipment Management System. The admin can log in, manage
Description
customer accounts, manage shipments, view reports, and manage
driver information.

Trigger The use case is triggered when the admin successfully logs into the

12
 Auto Shipment Management System.

 The admin must have valid login credentials.

Preconditions  There must be existing customer accounts, shipments, and
driver profiles in the system.

 Customer and driver information is updated as per admin's

actions.
Post conditions
 Shipments and driver assignments are managed and updated
in the system.

1. Login:
 Admin enters valid credentials.
 System authenticates the Admin.
 System redirects the admin to the admin dashboard.
2. Manage Customer:
 Admin navigates to the customer management section.

Normal Flow  Admin can add, modify, or delete customer accounts.

 System updates customer information accordingly.
3. Manage Shipment:
 Admin navigates to the shipment management section.
 Admin can view, modify, or cancel existing
shipments.
 System updates shipment details based on Admin's
actions.

 If the Admin enters invalid credentials during login:

Alternative Flows
 System displays an error message, and the use case ends.

 If the system experiences a database connection failure during

any interaction:
Exceptions
 The system displays an error message indicating a technical
issue.

Admin has sufficient privileges to manage customer accounts,

Assumptions
shipments, and driver profiles.

3.4 Functional requirements

This system will have the following modules:
13
3.4.1 Login Module:

 Secure user login and authentication processes for drivers, dispatchers, and customers,
ensuring data privacy and access control.

 Users login the system by inserting their username and password

 They can reset their password.

 Users create their new account.

 They will be capable of changing their passwords.

3.4.2 Shipment Management:

 Shipment creation
 Editing
 Cancellation functionalities,
 Allowing users to input shipment details, modify existing shipments, and cancel
orders when necessary.

3.4.3 Customer Module

 This module is made for customers who want to transport their vehicles.
 This module will take the complete information from them.
 After this, it generates a price for them if the customer accepts the price, then it adds
his load to the shipment box.
 The shipment box will contain tracking, driver details and status of his load.
 The customer can also chat with the driver.
 Step-by-step shipment for a vehicle.

3.4.4 Price Generator

 The Price Generator module is a crucial component that calculates the cost of vehicle
shipments based on various factors such as distance, vehicle type, and transportation
options.
 Price Generator module considers the pickup and delivery locations, vehicle
specifications, and customer preferences to generate an accurate and competitive price
quote.

14
  By automating the price calculation process, the Price Generator module eliminates
the need for manual price negotiations and provides customers with instant, fair, and
reliable pricing information.

3.4.5 Admin Module

 The admin module enables administrators to manage user accounts, including creating
new accounts, modifying user information, and handling account-related issues. This
goal ensures proper user management and access control within the system.
 Order and Shipment Management: Administrators can monitor and manage the entire
lifecycle of vehicle shipments through the admin module.
 This includes tracking the status of orders, managing pickup and delivery schedules,
resolving any shipment-related issues, and generating reports for analysis and
decision-making.

3.4.6 Logout Module

 All users must use the logout to exit from the application.

3.5 Non-functional requirements

Non-functional requirements are the requirements that specify criteria that can be used to
judge the operation of a system. Those constraints under which the system will be operated
are called non-functional requirements. For example, language run time environment,
operating environment performance requirements, usability requirements, etc. These are all
those requirements that do not belong to functional requirements but affect the system
overall. We can say some extra conditions and requirements that are not included in the use
cases. These are usually called non-functional requirements; some of these are given below.

3.5.1 Usability
The app must have a simple and intuitive user interface that is easy to use for both the
customer and driver. It should also be visually appealing and customizable.

3.5.2 Performance
The app should be fast and responsive, with quick load times and minimal lag. It should also
be optimized for different screen sizes and device specifications.

15
3.5.3 Reliability
The app should be reliable, with minimal downtime and errors. It should be able to handle
many users simultaneously without crashing or slowing down.

3.5.4 Compatibility
The app should be compatible with the latest version of android and should work seamlessly
across different devices and operating systems.

3.5.5 Availability
This app will be readily available to all its users all the time.

3.5.6 System requirements

These requirements consist of the hardware and software components of a computer system
that are required to develop and install to use the software efficiently.

3.5.7 Hardware requirements

 Minimum 2 GB RAM to ensure seamless multitasking and application
responsiveness.
 Stable 3G, 4G, or Wi-Fi connection for data communication and real-time updates.

3.5.8 Software requirement

 The Internet is necessary to run this application.
 Pre-installed web browser for external links and web-based interactions within the
application.

16
 Chapter 4

Design and Architecture

4 Design and architecture
4.1 System architecture
We will discuss what the existing methodologies are and which one we have chosen for the
implementation of this project effectively, also we will discuss the advantages of the adopted
methodology.

4.2 Data representation

4.2.1 Sequence diagram
The sequence diagram is a visual representation of the interactions between the different
objects and components of the system. It shows the flow of messages between the objects and
how they collaborate to achieve specific tasks in the system. The sequence diagram captures
the dynamic behavior of the system and is useful in identifying potential issues and
optimizations in the system's design. [4]

Figure 4.2 Sequence diagram

15
4.2.2 Class diagram
The class diagram is a graphical representation of the system's classes, their attributes, and
the relationships between them. It depicts the static structure of the system and shows how
the different classes in the system are related to each other.

Figure 4.3 Class diagram

4.2.3 Process flow representation

The process begins when a customer creates a new shipment request using the mobile app.
The system then optimizes the route, ensuring the vehicle reaches its destination efficiently.
Simultaneously, the customer can track the shipment in real-time through the app. The driver,
guided by the optimized route, picks up the vehicle and proceeds to the destination. During
the journey, the system provides constant updates to both the customer and the dispatch team,
ensuring everyone is aware of the vehicle's progress. Once the vehicle reaches the
destination, the system generates digital paperwork and receipts, completing the transaction.

16
The entire process, from creating the request to successful delivery, is seamless and
transparent, enhancing efficiency and customer satisfaction.[5]

Figure 4.4 Process flow

17
4.3 Design models
4.3.1 Incremental model
The incremental model was used in the development of the Vehicle Wave android app. This
model allows for the development of the application in increments, with each increment
adding new functionality and features to the app. The model was chosen because it enables
the development team to quickly produce a working version of the app, which can be tested
and refined before the next increment is added.

Using the incremental model also allows for greater flexibility in the development process, as
changes can be made to the app as it is being developed, rather than waiting until the entire
app is completed. This helps to reduce the risk of errors and omissions in the final product, as
any issues can be identified and corrected early in the development process.

Overall, the use of the incremental model has helped to ensure that the Vehicle Wave android
app is developed efficiently, with a focus on producing a high-quality product that meets the
needs of its users.[6]

Figure 4.5 Incremental model

18
 Chapter 5

Implementation
5 Implementation
In this chapter, we’ll focus on the implementation of the “Vehicle Wave(android)” mobile
application. Where users can perform many activities on this mobile application.
The most important goal of this phase is to develop the application. The work in this phase
should be much more straightforward because of the work done in the planning and design
phases. This phase involves changing design specifications into executable programs. When
the design is there, developers can have an idea of the looks of the application. All that is
needed by developers is to put them in one place to understand.
 The Auto Shipment Management App is developed using Flutter, a robust and
versatile framework for building cross-platform applications. Flutter's single codebase
approach allows developers to write code once and deploy it on both Android and iOS
platforms, ensuring consistency in user experience across devices. Flutter's extensive
widget library provides a wide range of customizable UI components, enabling the
creation of visually appealing interfaces tailored to the specific needs of the auto
shipment management system.
 The database schema is carefully designed to optimize queries, ensuring quick
retrieval of information. Additionally, data normalization techniques are applied to
eliminate redundancy and improve data integrity. Indexing is utilized strategically to
speed up search operations and enhance overall database performance.

5.1 Algorithm
A general algorithm for Vehicle Wave is:

5.1.1 User Authentication:

 The user enters their login credentials to access the app.

 The app verifies the credentials against the database and grants access if they are
correct.
 If the credentials are incorrect, the user is prompted to re-enter them.

5.1.2 Sign Up Module:

 The user enters their credentials on the sign-up page, typically find fields to input
login credentials. These usually include:

1. Username: Enter your unique username.

19
 2. Email: Enter your email address associated with your account.

3. Password: Create a strong and secure password following the app's password
requirements (e.g., length, special characters, etc.).

4. Confirm Password: Re-enter the password to confirm accuracy.

5.1.3 Customer Module

 This module is made for customers who want to transport their vehicles.

 This module will take the complete information from them.

 After this, it generates a price for them if the customer accepts the price, then it adds
his load to the shipment box.

 The shipment box will contain tracking, driver details and status of his load.

 The customer can also chat with the driver.

 Step-by-step shipment for a vehicle.

5.1.4 Shipment Management:

 Shipment creation by user.

 Editing in any sort of filled information is entertained.

 Cancellation functionalities.

 Allowing users to input shipment details, modify existing shipments, and cancel
orders when necessary.

5.1.5 Price Generator

 The Price Generator module is a crucial component that calculates the cost of vehicle
shipments based on various factors such as distance, vehicle type, and transportation
options.

 Price Generator module considers the pickup and delivery locations, vehicle
specifications, and customer preferences to generate an accurate and competitive price
quote.

20
  By automating the price calculation process, the Price Generator module eliminates
the need for manual price negotiations and provides customers with instant, fair, and
reliable pricing information.

5.1.6 Admin Module

 The admin module enables administrators to manage user accounts, including creating
new accounts, modifying user information, and handling account-related issues. This
goal ensures proper user management and access control within the system.

 Shipment management administrators can monitor and manage the entire lifecycle of
vehicle shipments through the admin module.

 This includes tracking the status of orders, managing pickup and delivery schedules,
resolving any shipment-related issues, and generating reports for analysis and
decision-making.

5.2 External API's

Table 5.2 External APIs

Name of API Description of API Purpose of usage

Google Maps API Google Maps API provides Google Maps API is essential in
developers with a set of auto shipment management
powerful tools to integrate systems to enable users to
interactive maps, geolocation monitor the precise location of
services, and customized their shipments.
mapping features into their It optimizes routes, calculates
applications and enhancing user distances, and enhances overall
experience. logistics efficiency, ensuring
timely deliveries and improved
customer satisfaction.
Vehicle Data API The Vehicle Data API is a In auto shipment management
service that provides systems, Vehicle Data API is
comprehensive information crucial for gathering accurate
about vehicles, including make, details about the vehicles being
model, year, VIN (Vehicle shipped.

21
 Identification Number), fuel
efficiency, and maintenance
records.

5.3 User interface

The application's interface will be designed to be straightforward and intuitive, ensuring ease
of use for the user. The user will be able to navigate and utilize the application independently
without relying on external assistance. Some pages of the user interface are further explained
along with images below:

22
Figure 5.6 User interface 1 Figure 5.7 User interface 2

23
 Figure 5.8 User interface 3
Figure 5.9 User interface 3

Figure 5.10 User Interface 5

5.4 Screen objects and actions

In the Auto Shipment Android-based
application, the screen
objects and actions are meticulously designed
to ensure a seamless user experience. The
main screen features intuitive elements such
as buttons for the authentication, booking,
and price generation modules. When users
access the authentication module, they encounter input fields where they can specify their
personal information. Once entered correctly, the screen displays the dashboard of the
application. In the Booking module, users navigate through a booking page showcasing
24
various fields for pickup and delivery locations, vehicle details, and preferred dates and
times. Authentication actions, such as password verification ensure secure transactions.

For Example, in our application text fields are used for pickup Location that allow users to
enter the address from where the vehicle will be picked up. Delivery location enables users to
input the address where the vehicle will be delivered. Vehicle details provide space for users
to specify vehicle make, model, and other relevant information. Same as date and time
pickers are used to pick up dates that allow users to select the date for vehicle pickup.

Dropdown menus are used to select vehicle type users can select the type of vehicle being
shipped. Additional services provide options like expedited delivery or insurance, enhancing
user choices.

The overall design and layout of the app aim to provide a user-friendly and intuitive
experience for users, allowing them to easily navigate the app and access the
information they need.

25
 Chapter 6

Testing and Evaluation

6 Testing and evaluation
The testing and evaluation phase is a crucial component of the Vehicle Wave android project,
ensuring that the developed application meets the desired requirements and is reliable and
functional. This chapter outlines the various types of testing that will be conducted during the
project, including manual testing, system testing, unit testing, functional testing, and
integration testing.[7]

6.1 Manual testing

Manual testing is the process of verifying the functionality of the app manually by the testers.
This process is essential to ensure that the app meets the user requirements and performs as
expected. The following table shows the test cases and results for manual testing:

Table 6.3 Manual Testing

Test Cases Expected Result Actual Result Pass/Fail

App Installation Successful Successful Pass
App Launch Successful Successful Pass
User Login Successful Successful Pass
User Registration Successful Successful Pass
Search Routes Accurate Accurate Pass
Vehicle Details Accurate Accurate Pass
Add Vehicle Accurate Accurate Pass
Shipment Details Accurate Accurate Pass
Shipment Booking Successful Successful Pass
Payment Processing Successful Successful Pass
Error Handling Accurate Accurate Pass
App Performance and Response Smooth Smooth Pass
App Navigation Easy Easy Pass
App Usability and User
High High Pass
Friendliness

6.1.1 System testing

System testing is the process of verifying that the application functions as intended in the
overall system environment. The following table shows the test cases and results for system
testing:
Table 6.4 System testing

24
 Test Cases Expected Result Actual Result Pass/Fail

Compatibility with android

Compatible Compatible Pass
Version

Compatibility with Device Compatible Compatible Pass

Data Security Secure Secure Pass

Data Backup Reliable Reliable Pass

User Management Effective Effective Pass

Application Response Time Acceptable Acceptable Pass

Application Resource Usage Optimal Optimal Pass

6.1.2 Unit testing

Unit Testing 1: Signup a user

Testing objective: To ensure the user can sign up into the system properly.
Table 6.5 Unit testing

Test Actual
Input Expected Output Pass/Fail
Case Output

1 User will sign E-mail: Successfully Pass

up through Raimafatima95@gmail.com signup into the
username system.
Password: Raima1661
email and

25
 password
User will sign E-mail:
up through
MuhammadBilal786@gmail.com Successfully
2 username Pass
signup into the
email and Password: 1234mb
system.
password

Unit Testing 2: Login into the system.

Testing objective: To ensure the login form works properly.
Table 6.4 Unit testing of login

Actual
Test Case Input Expected Output Pass/Fail
Output

User will
login E-mail:
Successfully
through raimafatima6262@gmail.com login into the
email and
Password: raima@62 system.
1 password or Pass
direct to
Google.

Unit Testing 3: Booking with invalid Input.

Testing objective: To ensure that system shows an error message.
Table 6.5 Unit testing of booking 1

Actual
Test Case Input Expected Output Pass/Fail
Output

Valid pickup
and delivery App displays
Booking should fail due to
details, valid an error
invalid date/time, and an error
vehicle type, message
1 message should be displayed. Pass
but past indicating an
date/time for invalid pickup
pickup. date/time.
Booking fails.

2 Valid pickup Pass

Booking should fail due to an App displays
and delivery

26
 invalid vehicle type, and an an error
details,
error message should be message
invalid
vehicle type, displayed. indicating an
and invalid
preferred
vehicle type.
date/time.
Booking fails.

6.2 Integration testing

Integration testing is a critical phase in software development where individual components
or modules of a software application are combined and tested as a group to ensure they work
together seamlessly.
Table 6.6 Integration testing

Test Case name Signup a user

Test Case number 01

Description The user can sign up into the system with

enter his/her basic information like
username, email and valid password.

Testing technique used Manual testing, Interface Testing using

the black-box testing technique,
Condition Coverage testing.

Precondition Users should have valid email and

password for signup.

Input values Enter email

xyz@gmail.com
Enter password
12345

Valid inputs Enter email

xyz@gmail.com
Enter password
12345

27
  Users need to on their internet
Steps services.
 User must need valid username,
email and password on the
dashboard to click on the signup
button and enter his/her basic
information.
The status is signup successfully

Expected output Sign up successfully

Actual output Status changed.

Status Pass

6.3 Functional testing

Functional testing will be conducted to ensure that the application meets the functional
requirements specified in the project scope. The testing will cover all modules of the
application, including user module, pricing module, admin module, shipment management
module and authentication module. The test cases for functional testing are as follows:
Table 6.7 Functional Testing 1

Test
Test Description Expected Result
ID

Verify that the user can login into The user can login into the system.
F01
the system

Verify that the user can sign up into The user can correctly sign up into the
F02
the system. system.

F03 Verify that the user can reset the The user can reset the password.

28
 password.

Verify that the user can select pick User can select any valid address.
F04
up and drop off address.

Verify user can view past shipment User should be able to access and view their
F05
history. past shipment details.

Verify user receives notifications for User should receive timely notifications
F06
shipment status updates. about the status of their active shipments.

Verify the accuracy of the estimated The estimated cost displayed after entering
F07 shipment cost calculation. shipment details should match the calculated
cost based on distance and vehicle type.

Verify the functionality of adding User should be able to add and manage
F08 and managing multiple shipments multiple shipments concurrently without
simultaneously. any conflicts or data overlapping.

Verify the accuracy of the delivery The estimated delivery time provided to the
F09 time estimation. user should be accurate, considering factors
such as distance and delivery route.

29
 Verify the secure handling of User data should be encrypted and securely
sensitive user data, such as stored, and there should be no unauthorized
F10
passwords and payment access to sensitive information.
information.

Verify the functionality of the date User should be able to select any valid
and time selection during shipment future date and time for pickup, ensuring the
F11
booking. system accepts the chosen schedule
accurately.

Verify user can log out of the User should be successfully logged out,
F12
application. terminating the current session.

30
 Chapter 7

Conclusion and Future Work

7 Conclusion and future work
7.1 Conclusion
The auto shipment system is to simplify and streamline the process of shipping vehicles from
one place to another. By providing users with a user-friendly platform, the system aims to
enable effortless booking and efficient management of vehicle shipments. It serves businesses
and individuals by ensuring secure, timely, and convenient transportation of vehicles,
ultimately enhancing customer satisfaction, and optimizing the logistics involved in auto
shipments.

By automating tasks and providing a centralized platform, the system reduces manual efforts,
minimizes errors, and optimizes the logistics chain. It enables businesses to efficiently
manage their fleet, ensures timely deliveries, and enhances customer communication through
real-time tracking and notifications. Additionally, it promotes cost-effectiveness by
optimizing routes and resources, making the vehicle shipping industry more efficient and
reliable for both providers and customers.

In conclusion, the auto shipment android application is well-equipped to meet user

expectations and deliver a smooth, efficient, and secure experience in the realm of vehicle
logistics. The meticulous testing efforts have validated the application's functionality,
ensuring it is ready for deployment, contributing to a seamless user experience, and fulfilling
the needs of its users in the auto shipment domain.

7.2 Future work

We plan to add modules to this application in the future. These modules are:

 Driver Module
 Tracking Module
 Chat Module

These modules will enhance the functionality of the application, making it more user-friendly
and efficient. The Driver Module enhances system efficiency by providing a streamlined
interface for carriers. Drivers can receive job assignments, access optimized routes, and
update shipment statuses in real-time. The Tracking Module significantly improves system
efficiency by offering real-time visibility into shipment locations for both users and carriers.

29
The Chat Module enhances efficiency by enabling instant communication between users,
carriers, and customer support within the application.

Overall, adding these modules will provide a more comprehensive and complete user
experience, and we are excited to implement them soon.

30
References

[1] M. A. Quddus, W. Y. Ochieng, and R. B. Noland, “Current map-matching algorithms for

transport applications: State-of-the art and future research directions,” Transp. Res. Part
C Emerg. Technol., vol. 15, no. 5, pp. 312–328, 2007.
[2] C. Barnhart, N. Krishnan, D. Kim, and K. Ware, “Network design for express shipment
delivery,” Comput. Optim. Appl., vol. 21, pp. 239–262, 2002.
[3] A. Artiba and S. E. Elmaghraby, The planning and scheduling of production systems:
methodologies and applications. Springer Science & Business Media, 1996.
[4] T. Le-Anh and J. R. van der Meer, “Testing and classifying vehicle dispatching rules in
three real-world settings,” J. Oper. Manag., vol. 22, no. 4, pp. 369–386, 2004.
[5] H. Durrant-Whyte, D. Pagac, B. Rogers, M. Stevens, and G. Nelmes, “Field and service
applications-an autonomous straddle carrier for movement of shipping containers-from
research to operational autonomous systems,” IEEE Robot. Autom. Mag., vol. 14, no. 3,
pp. 14–23, 2007.
[6] F. Böse, J. Piotrowski, and B. Scholz‐Reiter, “Autonomously controlled storage
management in vehicle logistics–applications of RFID and mobile computing systems,”
Int. J. RF Technol. Res. Appl., vol. 1, no. 1, pp. 57–76, 2009.
[7] M. K. Alzaylaee, S. Y. Yerima, and S. Sezer, “DynaLog: An automated dynamic analysis
framework for characterizing android applications,” presented at the 2016 International
Conference On Cyber Security And Protection Of Digital Services (Cyber Security),
IEEE, 2016, pp. 1–8.

31