AWebFactory
Depot UC3
(Based on Use Case Text Template)
Depot Use Case Specification UC003 Ship Orders
Brief Description
The Use Case allows the Seller to ship orders.
Actors
Shipping person (assuming role of Seller).
Flow of Events
Basic Flow
BF List Unshipped Orders
The Use Case starts when the Seller invokes the System in order to ship orders. The System confirms that the Seller is properly logged in and lists the unshipped orders.
BF Confirm Shipped Order
After fulfilling an order manually, the Seller changes the shipping status of one or more orders to “shipped”. The Seller commits the information to the System.
The System registers the change in the shipping status of the orders marked for shipping by the Seller. The Use Case continues at BF List Unshipped Orders.
Alternative Flows
AF Administrator Login
At BF List Unshipped Orders the System determines that the Seller is not logged in and requests the login information from the Seller. The Seller enters and commits the login information to the System. The System determines that the login information is valid and updates the Buyer’s session accordingly by logging in with his user name and password.
AF Bad Login
At AF Administrator Login the System determines that the login information is invalid, and displays a notice to that effect. The Seller confirms that he has read the notice and the Use Case continues at AF Administrator login.
AF End Session
At any point the Seller indicates to the System that he wishes to end the session. The Use Case ends.
Notes
At BF List Unshipped Orders, if an order has just been marked as “shipped” at BF Confirm Shipped Order, it will no longer be listed. No prevision is made in the Use Case at present for the viewing of order shipping history.
The customer requirements for shipping aren’t mentioned until Chapter 10! Login is an afterthought in Chapter 11. While this may follow from the need to present the coding in a gradual fashion, in real world Object Oriented Process this is not very good practice, since after so much development has taken place, not to have iteratively progressed with this Use Case could reveal major architectural changes or important design decisions: very costly!
——
See Robustness Diagram Depot UC3
Content
Victor Kane (ProjectMaster) and awebfactory.com.arEmail me at info at awebfactory dot com dot ar
Full content (RSS 2.0) and Headlines (RSS 2.0)