Auction UC - Create Auction

Use Case Specification: Create Auction
1. Create Auction
http://cid-90dadd2e56b02895.skydrive.live.com/self.aspx/%e5%85%ac%e9%96%8b/Create%20Auction%20UC.DOC
1.1 Brief Description
The Create Auction use case allows a Seller to create an online auction. The Seller specifies auction information (including the start and end of the auction), his credit card information (if not provided or during account creation, see the Create Account use case, or different for this auction) and can provide an image of the item, and an online auction is created for the item. Buyers can then bid on the item in the auction (see the Bid on Item use case).
An end of auction timer is set for the entered end of the action day and time. When that auction time expires, the auction is closed (see the Close Auction use case).
The seller can use the credit card information that is stored with her/his account or input credit card information that will be used with this auction only.
The User must be signed in order to create an auction. See the Sign In use case.
If the User has any pending payment notices due, a message is displayed to the User informing him/her that an outstanding balance is due, and the User is not permitted to create an auction. The user must go into his/her account and modify the credit card information (see the Manage Account use case).
2. Flow of Events
2.1 Basic Flow
1. This use case starts when the Seller indicates to the system that he/she wishes to create an auction in order to sell an item.
2. The system prompts the Seller to enter the auction information and indicate if s/he wants to provide an image of the item.
3. The Seller enters the auction information. If the seller indicated that s/he wants to provide an image of the item, the systems prompts the seller to select the file with the item image (.gif or .jpag, …). The system validates the entered auction information.
4. The System displays the auction information and requests that the Seller confirm.
5. The Seller confirms the entered auction information.
6. The system prompts the Seller to enter credit card information to be used for payment of the auction fees. If the Seller provided credit card information when he/she created his/her account (see the Create Account use case), that credit information is displayed as the default values for the credit card information. The Seller can then use that credit card information (the credit card information “on file”), or the Seller can enter new credit card information.
Note: The new credit information is used for the auction being created (instead of the “on file” credit card information). The on file credit card information remains unchanged. The only way to change the on file credit card information is via the Manage Account use case.
Note: Any entered credit card information is not validated at this time since a credit card’s validity can change between when it is entered and when something actually needs to be charged to it. Thus, the credit card will be validated prior to charging something to it.
7. The system creates an auction with the entered information. The auction is now open for bidding.
8. The system sets an EndOfAuction timer to expire on the day and time specified for the auction duration.
9. The system displays an “auction created successfully” screen that the seller can print for his/her record.
10. The use case ends.
2.2 Alternative Flows
2.2.1 Seller Has Pending Payments
If the Seller has any pending payment notices, the following occurs at the start of the use case before the system prompts the Seller to enter the information for the new auction (i.e., before Step 2):
- The System displays a message to the Seller reminding him/her that he/she has pending payments that are due and that, until those payments are made, the Seller cannot participate in an auction, either as a Buyer or a Seller. To settle the payment notices, the Seller must enter new credit card information. Credit card information can be entered via the Manage Account use case.
- The use case ends (no auction is created).
-
2.2.2 Seller Cancels Create Auction Request
At any time, the User may choose to cancel the Create Auction request. In such a case, the use case ends and an auction is not created.
2.2.3 Seller Enters Invalid Auction Information
If the system determines that the Seller entered invalid auction information, the following occurs:
- The system describes which entered data was invalid and presents the Seller with suggestions for entering valid data.
- The system prompts the Seller to re-enter the auction information.
- The Seller re-enters the information and the system re-validates it.
- If valid information is entered, the auction information is stored.
- If invalid information is entered, the Seller Enters Invalid Auction Information alternative flow is executed again. This repeats until valid information is entered or the Seller cancels the create auction request.
3. Special Requirements
None
4. Pre-Conditions
4.1 Seller is Signed In
The Seller must be signed in before the Seller can create an auction. See the Sign In use case.
5. Post-Conditions
5.1 An auction is created.
An auction for the item with the entered auction characteristics has been created. Buyers may now bid on the item.
OR
5.2 An auction is not created because of pending payment notices or the Seller cancels the request
An auction for the item with the entered auction characteristics was not created because the User has pending payment notices (i.e., still owes the system money).
6. Extension Points
Step 2. If the Re-List Previously Listed Item use-case is implemented, the systems shows an potion to re-list as an extension of this use case.