Finalsprint

Group 3
TrackTrek
Software Design Document
Names:
Andres Cortes
Sophie Le
Sohail Bangi
Joel Biju
Tri Ngo
Nadia Trigoso
Date: (08/15/2024)
TABLE OF CONTENTS
1.0......INTRODUCTION……………………………................................................................................... 3
1.1......Purpose………………………………................................................................................................ 3
1.2......Scope….……………………………………………………………………….................................. 3
1.3......Available alternatives………….......................................................................................................... 3
1.4......Competitors and novel in our approach …........................................................................................ 3
1.5......Overview……………………….......................................................................................................... 3
2.0......SYSTEM OVERVIEW........................................................................................................................ 3
3.0.......SYSTEM ARCHITECTURE............................................................................................................ 4
3.1.......Architectural Design…..................................................................................................................... 4
3.2.......Class Diagram…………................................................................................................................... 4
3.3.......Activity Diagram………................................................................................................................... 5
2
1.0 INTRODUCTION
1.1 Purpose
This software design document describes the architecture and system design of our
delivery courier tracking website that is for servicing a delivery company (admin)
and their clients (customers).
1.2 Scope
In the business end, they are able to fulfill orders, manage drivers and warehouse,
driver metrics (hours, miles, compliance, etc), track driver’s performances. In the
customer end, they are able to place and manage orders, register and subscribe to
receive notifications, provide customer feedback, and track down their orders. Both
the company and customer will be receiving notifications about the orders. With
the increase in delivery services, it is important to keep track of the numerous
parameters that come with the job both for the client and the admins.
1.3 Available alternatives

Quickbooks, in person shopping
1.4 Competitors and novel in our approach
Some competitors are Quickbooks and H&R block. What is novel in our approach
is that we offer flexible delivery time windows to accommodate busy schedules.
1.5 Overview
This document goes over the design of the system. Included in this document are
both the class diagram and activity diagram. Both of these show how the system
will work for users.
2.0 SYSTEM OVERVIEW
This system was built with a combination of web-programming languages. HTML, CSS,
and Java/PHP were used for the frontend of the project. For the backend, we have database
interfaces using Django and GPS API. An interesting aspect of this project is the
integrated system that offers dashboards for both the customer to track their package and
the delivery company to provide updates and ensure on-time delivery. We have both a
client and admin login where the client could track packages and the admin could keep
track of their service. In the business end, it helps keep track of mileage, workers. In the
customer end, it helps the customers track package location and on-time delivery.
3
3.0 SYSTEM ARCHITECTURE
3.1 Architectural Design

The program consists of seven different modules, and they are mainly independent
in their implementation. However, they rely on the data structure of their login
credentials. The user ID of both the customer and admin are essential for the user
to be able to interact with our program. If the user is a customer, they have access
to placing an order and choosing the type of delivery they would like. If the user is
an admin, they are able to edit the customer’s orders and begin the shipment
processes.
3.2 Class Diagram
3.3 Activity Diagram
4

Finalsprint

Uploaded by

Copyright:

Available Formats

Finalsprint

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Finalsprint

Uploaded by

Copyright:

Available Formats

Group 3

1.4......Competitors and novel in our approach …........................................................................................ 3

1.3 Available alternatives

1.4 Competitors and novel in our approach

2.0 SYSTEM OVERVIEW

3.0 SYSTEM ARCHITECTURE

3.1 Architectural Design

3.2 Class Diagram

3.3 Activity Diagram

You might also like