On the Spot Courier Services

Assignment of Use Cases in On the Spot System

In the On the Spot system, package pickup and delivery are closely integrated with route schedules. However, recall the RMO system, where there is a Sales subsystem, an Order fulfillment subsystem, a Customer account subsystem, and a Marketing subsystem. You could conceive of the On the Spot system as also consisting of four subsystems:

• Customer account subsystem (like customer account)
• Pickup request subsystem (like sales)
• Package delivery subsystem (like order fulfillment)
• Routing and scheduling subsystem

Assuming that on the Spot's system developer approached this new system from this point of view and that the developer also decided to use an adaptive, iterative approach, answer these questions:

Review and Assignment of Use Cases

This approach allows for modular development and maintenance, where each subsystem can be developed and improved iteratively, adapting to changing requirements without affecting other subsystems.

As per the given information, let's assign the use cases to the corresponding subsystems in the On the Spot system:

Customer account subsystem (similar to customer account):

• Create an account
• Update account information
• View account details
• Make payment

Pickup request subsystem (similar to sales):

• Place a pickup request
• Cancel a pickup request
• Modify a pickup request

Package delivery subsystem (similar to order fulfillment):

• Deliver a package
• Track package status
• Update package status

Routing and scheduling subsystem:

• Generate route schedules
• Optimize routes
• Assign packages to routes

Assigning the use cases to these subsystems aligns with the concept of dividing the On the Spot system into four subsystems, just like in the RMO system. It strengthens the original premise of having separate subsystems for different functional areas and ensures a clear separation of responsibilities within the system.