Use Case Diagram for the Amazon Locker Service

Let’s build the use case diagram of the Amazon Locker System and understand the relationship between its main actors and functions. First, we’ll define the different elements of our system, followed by the complete use case diagram.

System

Our system is the Amazon Locker system. It manages automated package deliveries and returns via secure locker locations.

Actors

Now, we’ll define the main actors of our Amazon Locker system.

Primary actors

• Customer: This is an Amazon customer who ordered a package delivered to the Amazon Locker. The customer is responsible for selecting and booking a locker location for their order delivery. This actor can enter the code at the locker to retrieve their product, request a return, and drop off the package at the locker.

• Delivery person: This actor can also enter the code and add the product to the locker so the “Customer” can pick it up. This actor can also pick up a returned package from the locker. The delivery person uses unique, one-time codes for each delivery or return.

Use cases

This section defines locker use cases. We have listed them according to their respective interactions with a particular actor.

Note: Some use cases will occur multiple times because they are shared among different actors in the system.

Customer

• Select locker location: Choose a preferred location for package delivery or product return.

• Pick up package: Retrieve the delivered package from the locker after unlocking it.

• Remove package: Collect a package from the locker after delivery or for return.

• Add package: Use the provided access code to place a return package inside the locker.

• Submit return request: Start the process to return a purchased product through a locker.

• Receive delivery notification: You will be notified when a package has been delivered to the assigned locker, including locker details and access code.

• Receive return notification: Get notified with instructions and code for returning a product via a locker.

• Receive overdue notification: Get notified if the package was not picked up before the deadline.

Delivery person

• Deliver package: Place a customer’s package inside the assigned locker for pickup.

• Remove package: Retrieve returned items from the locker for processing or transport.

• Receive return notification: Get alerted about packages that have been returned and are ready for pickup.

System

• Issue locker: Assign a suitable locker to a package based on size and availability.

• Generate code: Create a unique access code for locker entry.

• Validate code: Check if the entered code is correct and valid for locker access.

• Find locker: Locate the correct locker corresponding to the access code.

• Lock/unlock locker door: Control the mechanism to secure or open the locker door.

• Send delivery notification: Inform the customer that their package has been delivered and provide locker details and code.

• Send return notification: Notify the delivery person about returned products that require pickup.

• Send overdue notification: Alert the customer when a package hasn’t been collected within the specified time frame.

Relationships

This section describes the relationships between and among actors and their use cases.

Associations

The table below shows the association relationship between actors and their use cases.