UC9::Manage Orders
Overview
Allows the user to view current (open) and previous orders and track order and delivery progress.
Document History
  1. Current Version1.2
  2. 1.1odlingsmee; 20 Sep 2009 ; Initial Revision
  3. 1.2odlingsmee; 31 Jan 2010 ; Added main an alternative flows
Properties
  • TriggerA user wishes to track or view an open order or they wish to view a historical order.
  • GoalTo review the order details and (if it is an open order) track the order progress.
  • Primary ActorBuyer
  • Primary ActorMerchant
  • Primary ActorService Support
  • Secondary ActorMerchant Ordering System
  • Pre-RequisitesThe user shall be [UC1] logged on.
  • Success OutcomeThe user will have been informed about the current status of appropriate orders current and historic.
  • Failure OutcomeThe user will have been informed about any technical exceptions in a way that is meaningful to them. They will have been reassured that the technical issue will not affect the delivery of their order.
  • Priority2
  • Complexity3
  • target release release-2
  • Packageorder
Basic Flow
  1. The user selects the option to review current and historic orders.
  2. The system searches for all orders [RQ31] than can be viewed by the user..
  3. For each open order the system will query the [RQ30] appropriate merchant-system(s) to get the latest order progress status.
  4. The system [RQ36] displays the list of all orders with [RQ35] open orders first, otherwise in reverse chronological order.
  5. The user reviews the list of orders.
  6. The use-case ends.
Alternative Flows
No current or historic orders

At step 4 of the Main flow when No orders found

  1. The system determines that there are no existing orders (current or historic) for the buyer.
  2. The system displays an appropriate information message informing the user that there is no order history for them. The system will additionally provide some contact details should they believe that this is an error.
  3. The use-case ends.
Review Order Detail

At step 5 of the Main flow when More detail required

  1. The user clicks on one of the orders in the list.
  2. The system displays further detailed information about the order such as price, invoice address and shipment address.
  3. The flow of events continues from step 5 of the Main flow.
Exception Flows
System exception

At step 2 of the Main flow when system exception , or at step 3 of the Main flow when system exception

  1. The system reports an exception.
  2. A helpful error message is presented to the user, reassuring them that this system error has not affected their order(s). The buyer will be advised to check back later.
  3. The use-case ends.
Specific Requirements
  • [RQ31] Restrict list of orders:The system shall restrict the list of orders visible to the user such that they cannot review orders that are not associated with them. (agreed)
  • [RQ30] Associate order line item with a vendor:The system shall associate order line items with a vendor via a unique vendor id. (proposed)
  • [RQ36] Order summary data:The following should be displayed on the order summary list. Order date/time, order (overall) status, order price, estimated compltetion date (if known), buyer and vendor details. (agreed)
  • [RQ35] Order list presentation order:When a user searches for orders the list should be presented with open orders first with secondary sorting being via order date in reverse chronological order (newest orders first). (proposed)
  • [RQ27] Permission based controls:The system shall only allow access to functions that are associated with the permissions of the current user. (agreed)
Activity Diagram