Parcel Delivery System Report

Prepared by

Mahir Muzahid

[email protected]
Table Of Contents
Project Description .......................................................................................................................................................3
Project Overview ............................................................................................................................................................ 3
Project Scenario ............................................................................................................................................................. 3
Sender Scenario .....................................................................................................................................................3
Courier Scenario.....................................................................................................................................................3
Recipient Scenario..................................................................................................................................................3
Naming Conventions and Definitions ............................................................................................................................. 4
Definitions and key business terms ........................................................................................................................4
Data Dictionary. .....................................................................................................................................................4
Software Dependency ............................................................................................................................................5
Requirements ................................................................................................................................................................6
Use Case Diagrams .................................................................................................................................................6
Individual Functional Requirments .........................................................................................................................7
User Journey .................................................................................................................................................................9
Sender Journey ......................................................................................................................................................9
Delivery Man Journey ............................................................................................................................................9
Receiver Journey ....................................................................................................................................................9
Payment ........................................................................................................................................................................9
PROJECT DESCRIPTION
PROJECT OVERVIEW
This parcel delivery software will offer a user-centric solution for individuals to send and receive parcels conveniently.
Through three interconnected microservices, users can initiate shipments, track parcels, and customize delivery
preferences. The software prioritizes user convenience, transparency, and efficiency, providing a seamless and
satisfying experience for reliable and convenient parcel delivery.

PROJECT SCENARIO

SENDER SCENARIO
A sender accesses the software platform through a user-friendly website or mobile application. They enter the
pickup and delivery addresses, along with parcel details and any special instructions. The sender can choose delivery
preferences such as specific time slots or leaving the parcel at a drop point. Once the details are submitted, the
sender receives a unique tracking number to monitor the progress of the delivery.

COURIER SCENARIO
Upon receiving the pickup request, a courier assigned to the delivery receives real-time notifications through a
dedicated mobile application. The courier views the pickup and delivery addresses, along with any specific
instructions from the sender. They utilize the application's navigation feature to reach the pickup location, collect
the parcel, and proceed to the recipient's address. The courier updates the delivery status in real-time using the
mobile application.

RECIPIENT SCENARIO
The recipient receives a notification about the impending parcel delivery, including the estimated delivery time and
the courier's details. They can track the parcel using the provided tracking number through the software's website
or mobile application. The recipient can provide delivery preferences, such as leaving the parcel with a neighbor or
rescheduling the delivery for a more convenient time. Upon successful delivery, the recipient receives confirmation
and can provide feedback or rate the service.
NAMING CONVENTIONS AND DEFINITIONS

DEFINITIONS AND KEY BUSINESS TERMS

Client: Partner Individuals who have the rights to utilize the parcel delivery software.

1. Sender: Individuals who send parcels using the software.

2. Receiver: Individuals who receive parcels using the software.

Delivery Man: Individuals who deliver parcels using the software.

Admin: The system administrator overseeing the operations of the parcel delivery software.

Vouchers: Incentives or discounts provided to customers based on specific conditions or terms of the parcel delivery
service.

Customer Data: Comprehensive information about the customers using the software. Clients have authorized access
to customer data.

System Data: Overall data related to the software and its functionality. Only the authorized system administrators
can access and utilize system data.

DATA DICTIONARY .
Sender Service: Microservice dedicated to handling sender-specific functionality in the parcel delivery software.

Courier Service: Microservice focused on courier management and logistics within the software.

Recipient Service: Microservice responsible for managing recipient-specific operations in the software.

Unit Testing: Testing methodology employed to verify the reliability and functionality of the backend APIs and
frontend user experience.

JWT Authorization: Authorization package utilizing JSON Web Tokens for secure authentication and access control.

Dependency Injection: Software design pattern implemented in the parcel delivery software to manage software
component dependencies efficiently.
SOFTWARE DEPENDENCY
Azure Web Service: SQL Database and other services will be used from the Azure web service.

Validations: Information validation with .net.

Swagger: API documentation tool.

Language: C#, JavaScript.

Markup Language: HTML, CSS

Query Language: MYSQL.

Website Framework: Blazor

Mobile App Framework: .Net MAUI

REQUIREMENTS

USE CASE DIAGRAMS

INDIVIDUAL FUNCTIONAL REQUIRMENTS
Client
Requirements# 1 Requirements Type: Backend

Title Login And Signup

Rationale With authentication and role based

Requirements# 2 Requirements Type: Backend

Title Request Parcel

Rationale Client can request parcel

Requirements# 3 Requirements Type: Backend

Title Reject Parcel

Rationale Receiver can reject parcel

*This feature may not be developed for employer

Requirements# 4 Requirements Type: Backend

Title Limited Area of Service

Rationale Admin can limit the area of service

 Requirements# 5 Requirements Type: Backend

Title Online Payment

Rationale Client can pay online

Requirements# 6 Requirements Type: Backend

Title Tacking Parcel

Rationale Client can track parcel

Requirements# 7 Requirements Type: Backend

Title Drop Point

Rationale Client can drop parcel on a Drop Point

Delivery Man
Requirements# 8 Requirements Type: Backend

Title Accept / Reject Delivery

Rationale Deliver man can accept or reject parcel delivery

Requirements# 9 Requirements Type: Backend

Title View Location

Rationale Deliver man can see client location

USER JOURNEY

SENDER JOURNEY
User will go the website -> Sign up with required information -> Create Parcel -> Select Payment Option -> Will get
a tracking number.

DELIVERY MAN JOURNEY

Delivery man will get notification about new delivery -> Go to pick up location -> Confirm the parcel handover ->
Deliver the parcel -> Confirm the delivery.

RECEIVER JOURNEY
Receiver will get notification that a parcel has onboard on this number -> Will get the tracking number -> Will Get
the parcel -> Complete the payment (if necessary)

PAYMENT

LANDING PAGE 15,000 Taka

CLIENT DASHBOARD 45, 000 Taka

CLIENT APP (ANDROID) 80,000 Taka

DELIVERY MAN APP (ANDROID) 45,000 Taka

ADMIN DASHBOARD 30,000 Taka

TOTAL 215,000 Taka