American International University – Bangladesh

Spring 2020-21

Introduction to Database
Section – B

Course Teacher:
Juena Ahmed Noshin

Project Name:
Parcel Delivery Management System
Group Members
SL No. Name ID
01 WASEK-AL-AZAD, MD 19-39381-1
02 SAHA, TAPU 19-40152-1
03 OHI, SABIHA KHAIR 20-41905-1
04 ANZOOM, TANVIR 20-41920-1
05 FARDOUS, RIJOAN 20-41943-1
 Page |1

Contents

Introduction ............................................................................................... 2
Scenario Description ................................................................................. 3
ER Diagram ............................................................................................... 4
Normalization ............................................................................................ 5
Normalization Steps: ........................................................................ 5
Temporary Tables: ......................................................................... 11
Final Tables: ................................................................................... 12
Schema Diagram ..................................................................................... 13
Table Creation ......................................................................................... 14
Sequence: ........................................................................................ 17
Data Insertion .......................................................................................... 18
Query Writing .......................................................................................... 23
Subquery ......................................................................................... 23
Joining ............................................................................................ 24
View ............................................................................................... 24
Relational Algebra ................................................................................... 26
Conclusion ............................................................................................... 27

Parcel Delivery Management System Introduction to Database [B]

 Page |2

Introduction

Nowadays, parcel delivery is a common scenario in our country. If we can

manage the whole data of a parcel delivery company into a database, it
would be very much easy to do work. So, Parcel Delivery Management
System is a SQL-based data management system for a parcel delivery
company. The main focus of the company is to make proper and
fast/speed up delivery of a parcel to appropriate customer reducing human
efforts and errors caused by traditional system. It earns customer
satisfaction through accurate delivery and hassle-free computerized
billing system.

Parcel Delivery Management System Introduction to Database [B]

 Page |3

Scenario Description

In a parcel delivery management system, a customer can place many

orders. One order is placed by one customer. A customer id number
identifies a customer. The system also stores the name, address, email,
and phone number of each customer. There may be multiple phone
numbers. A customer address is composed of apartment no, street name,
city and postal. An order number identifies an order. The system also
stores the date of that order.
Each order may contain many products. A product must have exactly one
order. Each product is identified by product number. The system also
stores the name, price and quantity for each product.
There may have multiple orders for one payment. But for one order there
is only one payment. Each payment is identified by payment id number.
For each payment, the system also stores the total price.
A customer can pay multiple payments. But a payment is paid by a
customer. The system stores the payment date for each payment. Payment
is collected by delivery man. A delivery man can collect many payments
but one payment is collected by one delivery man.
A delivery man delivers the products to the customer. A delivery man can
deliver many products. One product is delivered by one delivery man. A
customer can receive many products. But a product is received by only
one customer.

Parcel Delivery Management System Introduction to Database [B]

 Page |4

ER Diagram

Parcel Delivery Management System Introduction to Database [B]

 Page |5

Normalization

Normalization Steps:

Place Branch
UNF
place (OrderID, OrderDate, CustID, CustName, CustEmail, CustPhone,
ApartmentNo, PostalCode, StreetName, City)
1NF
CustPhone is a multi-valued attribute.
1. OrderID, OrderDate, CustID, CustName, CustEmail, CustPhone,
ApartmentNo, PostalCode, StreetName, City
2NF
1. OrderID, OrderDate
2. CustID, CustName, CustEmail, CustPhone, ApartmentNo,
PostalCode, StreetName, City
3NF
1. OrderID, OrderDate
2. CustID, CustName, CustEmail, CustPhone
3. ApartmentNo, PostalCode, StreetName, City
Table Creation
1. OrderID, OrderDate, CustID
2. CustID, CustName, CustEmail, CustPhone, AddressID
3. AddressID, ApartmentNo, PostalCode, StreetName, City

Parcel Delivery Management System Introduction to Database [B]

 Page |6

Contain Branch
UNF
contain (OrderID, OrderDate, ProductID, ProductName, ProductPrice,
Quantity, DeliveryDate)
1NF
There is no multivalued attribute. Relation already in 1NF.
1. OrderID, OrderDate, ProductID, ProductName, ProductPrice,
Quantity, DeliveryDate
2NF
1. OrderID, OrderDate
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate
3NF
There is no transitive dependency. Relation already in 3NF.
1. OrderID, OrderDate
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate
Table Creation
1. OrderID, OrderDate
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
OrderID

Pay Branch
UNF
pay (PaymentID, TotalPrice, PaymentDate, CustID, CustName,
CustEmail, CustPhone, ApartmentNo, PostalCode, StreetName, City)

Parcel Delivery Management System Introduction to Database [B]

 Page |7

1NF
CustPhone is a multi-valued attribute.
1. PaymentID, TotalPrice, PaymentDate, CustID, CustName,
CustEmail, CustPhone, ApartmentNo, PostalCode, StreetName,
City
2NF
1. PaymentID, TotalPrice, PaymentDate
2. CustID, CustName, CustEmail, CustPhone, ApartmentNo,
PostalCode, StreetName, City
3NF
1. PaymentID, PaymentDate, TotalPrice
2. CustID, CustName, CustEmail, CustPhone
3. ApartmentNo, PostalCode, StreetName, City
Table Creation
1. PaymentID, PaymentDate, TotalPrice, CustID
2. CustID, CustName, CustEmail, CustPhone, AddressID
3. AddressID, ApartmentNo, PostalCode, StreetName, City

Receive Branch
UNF
receive (ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
CustID, CustName, CustEmail, CustPhone, ApartmentNo, PostalCode,
StreetName, City)

Parcel Delivery Management System Introduction to Database [B]

 Page |8

1NF
CustPhone is a multi-valued attribute.
1. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
CustID, CustName, CustEmail, CustPhone, ApartmentNo,
PostalCode, StreetName, City
2NF
1. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate
2. CustID, CustName, CustEmail, CustPhone, ApartmentNo,
PostalCode, StreetName, City
3NF
1. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate
2. CustID, CustName, CustEmail, CustPhone
3. ApartmentNo, PostalCode, StreetName, City
Table Creation
1. ProductID, DeliveryDate, ProductName, ProductPrice, Quantity,
CustID
2. CustID, CustName, CustEmail, CustPhone, AddressID
3. AddressID, ApartmentNo, PostalCode, StreetName, City

Has Branch
UNF
has (PaymentID, TotalPrice, PaymentDate, OrderID, OrderDate)

Parcel Delivery Management System Introduction to Database [B]

 Page |9

1NF
There is no multi-valued attribute. Relation already in 1NF.
1. PaymentID, TotalPrice, PaymentDate, OrderID, OrderDate
2NF
1. PaymentID, TotalPrice, PaymentDate
2. OrderID, OrderDate
3NF
There is no transitive dependency. Relation already in 3NF.
1. PaymentID, TotalPrice, PaymentDate
2. OrderID, OrderDate

Table Creation
1. PaymentID, TotalPrice, PaymentDate
2. OrderID, OrderDate, PaymentID

Collect Branch
UNF
collect (PaymentID, TotalPrice, PaymentDate, DmID, DmName,
DmSalary, DmPhone)
1NF
DmPhone is a multi-valued attribute.
1. PaymentID, TotalPrice, PaymentDate, DmID, DmName,
DmSalary, DmPhone

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 10

2NF
1. PaymentID, TotalPrice, PaymentDate
2. DmID, DmName, DmSalary, DmPhone
3NF
There is no transitive dependency. Relation already in 3NF.
1. PaymentID, TotalPrice, PaymentDate
2. DmID, DmName, DmSalary, DmPhone

Table Creation
1. PaymentID, TotalPrice, PaymentDate, DmID
2. DmID, DmName, DmSalary, DmPhone

Deliver Branch
UNF
deliver (DmID, DmName, DmSalary, DmPhone, ProductID,
ProductName, ProductPrice, Quantity, DeliveryDate)
1NF
DmPhone is a multi-valued attribute.
1. DmID, DmName, DmSalary, DmPhone, ProductID, ProductName,
ProductPrice, Quantity, DeliveryDate
2NF
1. DmID, DmName, DmSalary, DmPhone
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate
3NF

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 11

There is no transitive dependency. Relation already in 3NF.

1. DmID, DmName, DmSalary, DmPhone
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate

Table Creation
1. DmID, DmName, DmSalary, DmPhone
2. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
DmID

Temporary Tables:

1. OrderID, OrderDate, CustID

2. CustID, CustName, CustEmail, CustPhone, AddressID
3. AddressID, ApartmentNo, PostalCode, StreetName, City
4. OrderID, OrderDate
5. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
OrderID
6. PaymentID, PaymentDate, TotalPrice, CustID
7. CustID, CustName, CustEmail, CustPhone, AddressID
8. AddressID, ApartmentNo, PostalCode, StreetName, City
9. ProductID, DeliveryDate, ProductName, ProductPrice, Quantity,
CustID

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 12

10. CustID, CustName, CustEmail, CustPhone, AddressID

11. AddressID, ApartmentNo, PostalCode, StreetName, City
12. PaymentID, TotalPrice, PaymentDate
13. OrderID, OrderDate, PaymentID
14. PaymentID, TotalPrice, PaymentDate, DmID
15. DmID, DmName, DmSalary, DmPhone
16. DmID, DmName, DmSalary, DmPhone
17. ProductID, ProductName, ProductPrice, Quantity,
DeliveryDate, DmID

Final Tables:

1. CustID, CustName, CustEmail, CustPhone1, CustPhone2,

AddressID
2. AddressID, ApartmentNo, PostalCode, StreetName, City
3. OrderID, OrderDate, CustID, PaymentID
4. ProductID, ProductName, ProductPrice, Quantity, DeliveryDate,
OrderID, CustID, DmID
5. PaymentID, PaymentDate, TotalPrice, CustID, DmID
6. DmID, DmName, DmSalary, DmPhone1, DmPhone2

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 13

Schema Diagram

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 14

Table Creation
Address Table:
CREATE TABLE Address
(AddressID NUMBER (5) CONSTRAINT PK_Address PRIMARY KEY,
ApartmentNo NUMBER (3),
StreetName VARCHAR2(20),
PostalCode NUMBER (4),
City VARCHAR2 (15));

Customer Table:
CREATE TABLE Customer
(CustID NUMBER (5) CONSTRAINT PK_Customer PRIMARY KEY,
CustName VARCHAR2(20),
CustEmail VARCHAR2(20),
CustPhone1 NUMBER (11),
CustPhone2 NUMBER (11),
AddressID NUMBER (5) CONSTRAINT FK_AddressID REFERENCES Address);

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 15

DelivaryMan Table:
CREATE TABLE DelivaryMan
(DmID NUMBER (5) CONSTRAINT PK_DelivaryMan PRIMARY KEY,
DmName VARCHAR2(20),
DmSalary NUMBER (7,2),
DmPhone1 NUMBER (11),
DmPhone2 NUMBER (11));

Payment Table:
CREATE TABLE Payment
(PaymentID NUMBER (5) CONSTRAINT PK_PaymentID PRIMARY KEY,
PaymentDate DATE,
TotalPrice NUMBER (7,2),
CustID NUMBER (5) CONSTRAINT FK_CustID REFERENCES Customer,
DmID NUMBER (5) CONSTRAINT FK_DmID REFERENCES DelivaryMan);

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 16

Orders Table:
CREATE TABLE Orders
(OrderID NUMBER (5) CONSTRAINT PK_OrderID PRIMARY KEY,
OrderDate DATE,
CustID NUMBER (5) CONSTRAINT FK_CustID1 REFERENCES Customer,
PaymentID NUMBER (5) CONSTRAINT FK_PaymentID REFERENCES
Payment);

Product Table:
CREATE TABLE Product (ProductID NUMBER (5) CONSTRAINT PK_ProductID PRIMARY
KEY,
ProductName VARCHAR2(20),
ProductPrice NUMBER (7,2),
Quantity NUMBER (2),
DelivaryDate DATE,
CustID NUMBER (5) CONSTRAINT FK_CustID2 REFERENCES Customer,
DmID NUMBER (5) CONSTRAINT FK_DmID1 REFERENCES DelivaryMan,
OrderID NUMBER (5) CONSTRAINT FK_OrderID REFERENCES Orders);

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 17

Sequence:

1. CREATE SEQUENCE Customer_custNo

INCREMENT BY 5
START WITH 1110
MAXVALUE 5000
NOCACHE
NOCYCLE;

2. CREATE SEQUENCE Orders_orderID

INCREMENT BY 7
START WITH 2222
MAXVALUE 7777
NOCACHE
NOCYCLE;
3. CREATE SEQUENCE ProductID
INCREMENT BY 3
START WITH 103;

4. SELECT SEQUENCE_NAME, MIN_VALUE, MAX_VALUE, INCREMENT_BY,

LAST_NUMBER FROM USER_SEQUENCES;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 18

Data Insertion
Address Table:
1. INSERT INTO ADDRESS VALUES (222, 12, 'ABC', 1215, 'DHAKA');
2. INSERT INTO ADDRESS VALUES (333, 23, 'BCD', 1326, 'DHAKA');
3. INSERT INTO ADDRESS VALUES (444, 34, 'CDE', 1437, 'DHAKA');
4. INSERT INTO ADDRESS VALUES (555, 45, 'DEF', 1548, 'DHAKA');
5. INSERT INTO ADDRESS VALUES (666, 56, 'EFG', 1659, 'DHAKA');
SELECT * FROM ADDRESS;

Customer Table:
1. INSERT INTO CUSTOMER VALUES (Customer_custNo.NEXTVAL,
'Ohi', '[email protected]', 01720419051, 01920419051, 222);
2. INSERT INTO CUSTOMER (CustID, CustName, CustEmail, CustPhone1,
AddressID) VALUES (Customer_custNo.NEXTVAL, 'Rijoan',
'[email protected]', 1720419431, 333);
3. INSERT INTO CUSTOMER VALUES (Customer_custNo.NEXTVAL,
'Siam', '[email protected]', 20419201, 01920419201, 444);
4. INSERT INTO CUSTOMER (CustID, CustName, CustEmail, CustPhone2,
AddressID) VALUES (Customer_custNo.NEXTVAL, 'Wasek',
'[email protected]', 0171939811, 555);
5. INSERT INTO CUSTOMER VALUES (Customer_custNo.NEXTVAL,
'Tapu', '[email protected]', 01719401521, 01919401521, 666);
SELECT * FROM CUSTOMER;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 19

DelivaryMan Table:
1. INSERT INTO DELIVARYMAN VALUES (4040, 'Azad', 7000, null,
01719456812);
2. INSERT INTO DELIVARYMAN VALUES (5050, 'Fardous', 7500,
01645984125, null);
3. INSERT INTO DELIVARYMAN VALUES (6060, 'Sabiha', 9000,
01545896574, 01436578951);
4. INSERT INTO DELIVARYMAN VALUES (7070, 'Tanvir', 8500, null,
0139217586);
5. INSERT INTO DELIVARYMAN VALUES (8080, 'Saha', 8000,
01648217457, null);
SELECT * FROM DELIVARYMAN;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 20

Payment Table:

1. INSERT INTO PAYMENT VALUES (7035, to_date('08-10-2020','dd-mm-

yyyy'), 500, 1115, 5050);
2. INSERT INTO PAYMENT VALUES (7045, to_date('12-10-2020','dd-mm-
yyyy'), 1000, 1120, 6060);
3. INSERT INTO PAYMENT VALUES (7055, to_date('08-10-2020','dd-mm-
yyyy'), 700, 1115, 5050);
4. INSERT INTO PAYMENT VALUES (7065, to_date('15-09-2020','dd-mm-
yyyy'), 850', 1125, 4040);
5. INSERT INTO PAYMENT VALUES (7075, to_date('08-10-2020','dd-mm-
yyyy'), 670, 1135, 7070);
6. INSERT INTO PAYMENT VALUES (7085, to_date('12-10-2020','dd-mm-
yyyy'), 350, 1120, 6060);
7. INSERT INTO PAYMENT VALUES (7095, to_date('20-12-2020','dd-mm-
yyyy'), 420, 1130, 8080);
8. INSERT INTO PAYMENT VALUES (8000, to_date('08-10-2020','dd-mm-
yyyy'), 720, 1135, 7070);

SELECT * FROM PAYMENT;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 21

Orders Table:

1. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,

to_date('08-10-2020','dd-mm-yyyy'), 1115, 7035);
2. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('12-10-2020','dd-mm-yyyy'), 1120, 7045);
3. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('08-10-2020','dd-mm-yyyy'), 1115, 7055);
4. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('15-09-2020','dd-mm-yyyy'), 1125, 7065);
5. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('08-10-2020','dd-mm-yyyy'), 1135, 7075);
6. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('12-10-2020','dd-mm-yyyy'), 1120, 7085);
7. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('20-12-2020','dd-mm-yyyy'), 1130, 7095);
8. INSERT INTO ORDERS VALUES (Orders_orderID.NEXTVAL,
to_date('08-10-2020','dd-mm-yyyy'), 1135, 8000);

SELECT * FROM ORDERS;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 22

Product Table:

1. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Shirt', 500,

1, to_date('12-10-2020','dd-mm-yyyy'), 1115, 5050, 2222);
2. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Charger',
250, 4, to_date('16-10-2020','dd-mm-yyyy'), 1120, 6060, 2229);
3. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Pant', 700,
1, to_date('12-10-2020','dd-mm-yyyy'), 1115, 5050, 2236);
4. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Memory
Card', 670, 1, to_date('18-09-2020','dd-mm-yyyy'), 1125, 7070, 2243);
5. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Data Cable',
175, 2, to_date('12-10-2020','dd-mm-yyyy'), 1135, 6060, 2250);
6. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Calculator',
210, 2, to_date('16-10-2020','dd-mm-yyyy'), 1120, 8080, 2257);
7. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Watch', 720,
1, to_date('24-12-2020','dd-mm-yyyy'), 1130, 7070, 2264);
8. INSERT INTO PRODUCT VALUES (ProductID.NEXTVAL, 'Light', 850,
1, to_date('12-10-2020','dd-mm-yyyy'), 1135, 4040, 2271);

SELECT * FROM PRODUCT;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 23

Query Writing
Subquery:

1. Which products have higher price than a charger?

SELECT PRODUCTNAME AS P_NAME, PRODUCTPRICE AS PRICE
FROM PRODUCT WHERE PRODUCTPRICE > (SELECT PRODUCTPRICE
FROM PRODUCT WHERE PRODUCTNAME = 'Charger');

2. Display all the deliveryman’s information who has a lower salary than
Tanvir’s salary.
SELECT * FROM Delivaryman WHERE DmSalary < (SELECT DmSalary
FROM Delivaryman WHERE DmName = 'Tanvir');

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 24

Joining:

1. Display all the customers name whose products were delivered on 12 Oct
2020. Also show the product they ordered.
SELECT Customer.CustName, Product.ProductName FROM Customer,
Product WHERE Customer.CustID = Product.CustID AND
Product.DelivaryDate = '12-OCT-20';

2. Display all the deliveryman’s name and salary who delivered the products
which has product id greater than 110.

SELECT Delivaryman.DmName, Delivaryman.DmSalary,

Product.ProductID FROM Delivaryman, Product where Delivaryman.DmID
= Product.DmID AND Product.ProductID>110;

View:

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 25

1. Create a view called ProductView based on the ProductName, ProductPrice

and Quantity from the Product table.
CREATE VIEW ProductView AS SELECT ProductName, ProductPrice,
Quantity FROM Product;

SELECT * FROM ProductView;

2. Write a query to display all ProductName and ProductPrice where quantity

is greater than 1 from ProductView.
SELECT ProductName, ProductPrice From ProductView WHERE Quantity >
1;

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 26

Relational Algebra
1. Find the name of the customer whose customer id is 1125.
∏CustName (σ CustID =1125(Customer))

2. Find the price of the charger.

∏ProductPrice (σ ProductName = “Charger” (Product))

3. Find the apartment no, street name and postal code where
AddressID is equal to 555.
∏ApartmentNo, StreetName, PostalCode (σ AddressID = 555 (Address))

4. Find order ids which were ordered on 08-OCT-20.

∏OrderID (σ OrderDate = “08-OCT-20” (Orders))

5. Find the deliveryman’s name whose salary is less than 8500.

∏DmName (σ DmSalary < 8500 (Delivaryman))

Parcel Delivery Management System Introduction to Database [B]

 P a g e | 27

Conclusion
In this project, we have mainly created a sql-based parcel delivery
management system focusing on proper quick delivery to the appropriate
customer in an error-free manner to reduce all sorts of hassle that happen
in a traditional management system. The project queries run in ‘Oracle
10g’. Here, we have made seven relationship among all the entities with
cardinality. We have also normalized the project to organize data elements
properly.

Future Planning:
We have tried our level-best to make the parcel delivery management
system more convenient. Yet, it has some shortcomings that can be
improved through proper arrangements. A few of them are:

Real-time vehicle tracking: Real-time vehicle tracking data can be used

to verify driver deliveries and the amount of time spent at each location
which reduces the chance of intentional delays of delivery boys. The
shipment and delivery update can also be shown to the customers to earn
customer satisfaction.

Distributed database approach in place of centralized approach: A

centralized system is very unstable, since any problem that affects the
central server can generate chaos throughout the system. Besides, our
centralized system won't be able to handle larger amount of data properly
in near feature. So, we will have to create a distributed management
system which will be more stable by storing all the information of the
system in a large number of associate branches eradicating all sorts of
uncertainty. So, it is expected that, in future the system will be more
convenient and user friendly.

Parcel Delivery Management System Introduction to Database [B]