1 / 10

notes and outstanding items/issues:

first attempt -leads to questions. notes and outstanding items/issues: finish truck – has no operations because “load the truck” and “accept the load” do all the work -so must remove this from activity diagram

gratia
Télécharger la présentation

notes and outstanding items/issues:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. first attempt -leads to questions • notes and outstanding items/issues: • finish truck – has no operations because “load the truck” and “accept the load” do all the work -so must remove this from activity diagram • arrange truck – the same truck may be used on several occasions – need some kind of schedule possibly – or can assign trucks to order items and check to see if truck is available/suitable

  2. high-level use case: customer accepts order actor action log in choose shipment accept fn. identify order select next item enter/accept quantity received accept order alternate.... customer rejects order * =separate use case system response retrieve customer data display list of customer’s orders retrieve order details present item details store quantity received release truck create invoice data* create carrier payment data* { {

  3. actor + system actions responsible class (control class to be added later) log in interface(note 1) retrieve customer data customer + interface choose shipment accept fn.order (show all orders) display customer’s orders interface identify shipment order + order detail retrieve order interface select next item order detail present item details interface enter/accept qty. rec’d order item store quantity received order item close order order release truck truck create invoice data invoice create carrier payment data payment {

  4. based on specs so far, here are some attributes

  5. event use case truck states add a truck to carrier’s fleet maintain carrier truck is available customer accepts shipment accept order truck is available (again) arrange for a truck to be used scheduling truck is booked shipper identifies/loads truck shipping/loading truck is in use remove truck from list maintain carrier truck is retired

  6. Class name: Order Responsibilities Collaborations provide order information give list of items OrderItem has the details add/change items OrderItem creates/updates self accept reservation of truck(s) Truck will determine feasibility select/release truck Truck status change create carrier payment Payment created create invoice Invoice created close order

  7. Class name: Payment Responsibilities Collaborations create payment calculate item cost OrderItem for quantity Product for weight and dimensions add base rate calculate total cost prepare record for A/P Carrier for payment terms

  8. Class name: Invoice Responsibilities Collaborations create invoice calculate item cost Product for prices OrderItem for quantity calculate shipping cost Payment for costs calculate total prepare record for A/R Customer for billing agreement

More Related