Use Case Specifications

of 24/24
Use Case: Manage User Happy Path – Basic Flow of Events Name: Manage User Description: This use case starts when a user attempt to be a member of the online auction system as seller, buyer or administrator. He or she has to fill up registration form to become as a member of this site. Besides, this use case is to authenticate the user (administrator, seller and buyer) to gain access into the system. Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah. Actor(s): Administrator, Buyer, Seller. Location(s): Malaysia. Status: Pathway defined Priority: 1 Assumption: An user will fill up a form that found at registration site in order to create an account besides become as a member. Pre-condition: Visitor creates new account to be the user of the website. Post-condition(s): Users are successfully log into the system. Primary (Happy) Path: User log into the online auction system. Alternate Pathway(s): Users are able to edit their personal information.
  • date post

    15-Dec-2014
  • Category

    Education

  • view

    599
  • download

    0

Embed Size (px)

description

 

Transcript of Use Case Specifications

Use Case: Manage UserHappy Path Basic Flow of Events

Name: Manage User

Description:

This use case starts when a user attempt to be a member of the online auction system as seller, buyer or administrator. He or she has to fill up registration form to become as a member of this site. Besides, this use case is to authenticate the user (administrator, seller and buyer) to gain access into the system.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.Actor(s): Administrator, Buyer, Seller.

Location(s): Malaysia.

Status: Pathway defined

Priority: 1

Assumption:

An user will fill up a form that found at registration site in order to create an account besides become as a member.

Pre-condition:

Visitor creates new account to be the user of the website.

Post-condition(s):

Users are successfully log into the system.

Primary (Happy) Path:

User log into the online auction system. Alternate Pathway(s):

Users are able to edit their personal information.

Users can delete their account if they wish to quit.

Users register before they get to log into the online auction system.

Users can logout from the auction system.

Companies must enter their Auction House registration number. Administrator will verify the registration manually and subsequently approve/disapprove the registration.Exception Pathway(s):

User login with invalid username.

User login with invalid password.

The user does not filled up the form neatly like leaving blank, registration would not take place.

Happy Path Detailed Flow of Events

Visitor selects register new user option in order to create an account for the system.

1. Once user enters the URL for the website, the home or main page navigated for users view.

2. User clicks the Register button to create an account with the online auction system.

3. Registration page in the kind of form will navigated to users view.

4. User then enter details about particulars:

a) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.

b) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.

5. After filling up the information mentioned above, user enters CAPTCHA code provided at bottom of the form.

6. User clicks the button that contains text I confirm that I am at least 18 years old and I agree with Terms and Conditions.

7. User clicks the Register button.

8. User successfully registered and navigated to home or main screen by a brief welcome message.

Alternate path detailed Flow of Events

Users can edit their personal information.

1. Once user enters the URL for the website, the home or main page navigated for users view.

2. User clicks the button of Login to login into the account.

3. User enters username and password and then clicks login button.

4. User successfully has logged into the system and directed to the main account or page.

5. User can select the account setting to change their personal information including the security setting such as passwords.

6. After done editing, user must save the setting so that the new information is updated.

Users are able to delete their account if they wish to quit.

1. Once user enters the URL for the website, the home or main page navigated for users view.

2. User clicks the button of Login to login into the account or system in order to add a lot or auction or to place the bid of price for auction.

3. User enters username and password and then clicks login button.

4. User successfully has logged into the system and directed to the main account or page.

5. User can select the deactivate account button in order to delete his/ her account from the system.

6. After selecting the option, an email will send to the user to confirm the deactivation of the account.

7. User does no longer exist in the system.

Users can log into the online auction system.

1. Once user enters the URL for the website, the home or main page navigated for users view.

2. User clicks the button of Login to login into the account or system in order to add a lot or auction or to place the bid of price for auction.

3. User enters username and password and then clicks login button.

4. User successfully has logged into the system and directed to the main account or page.

User has to logout from the system.

1. User finished the session with the online auction system such as seller has to add a lot or auction and buyer place bids of price on items.

2. User clicks logout button.

3. User successfully logout from the online auction system.

Companies must enter their Auction House registration number.

1. Once user(Companies) enters the URL for the website, the home or main page navigated for users view.

2. User clicks the Register button to create an account with the online auction system.

3. Registration page in the kind of form will navigated to users view.

4. User then enter details about particulars:

c) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.

d) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.

e) As a Auction House, they must enter their Auction House Registration Number.

5. After filling up the information mentioned above, user enters CAPTCHA code provided at bottom of the form.

6. User clicks the button that contains text I confirm that I am at least 18 years old and I agree with Terms and Conditions.

7. User clicks the Register button.

8. User successfully registered and navigated to home or main screen by a brief welcome message.

Administrator will verify the registration manually and subsequently approve/disapprove the registration.

1. Administrator enters the URL for the website, the home or main page navigated for users view.

2. Administrator clicks the button of Login to login into the account.

3. Administrator enters username and password and then clicks login button.

4. Administrator successfully has logged into the system and directed to the main account or page.

5. Administrator will check whether there is any new registration application.

6. Administrator will verify the registration manually.

7. Administrator will decide whether to approve or to reject the application.

8. Lastly, Administrator must save the setting so that the new information is updated.

Use Case: Manage Auction

Happy Path Basic Flow of Events

Name: Manage Auction

Description:

This use-case starts when an auction has been created.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Administrator, Buyer, Seller.

Location(s): Malaysia.

Status: Pathway defined

Priority: 3Assumption:

Bidding price of the auction will go through until the auction is ended. Administrator will remove the ended auction from the system. Users (sellers and buyers) are able to view the existing auction.

Pre-condition(s):

User (seller, buyer and administrators) must log into the online auction system before they do anything.

Post-condition(s):

Users successfully logout from the system.

Bid price for the auction keep on changing from time to time as different buyer will make different bid price.

Ended auction will be removed from the system.

Primary (Happy) Path:

Adminstrator add new auction and move unassigned lot into auction.Alternate Pathway(s): Administrator removes ended auction.

Buyer can place bid in the auction. User (Buyer and seller) can view the existing auction.

Exception Pathway(s):

Administrator adds a new auction without an item.

There is no auction to be deleted.

None of the auction has been ended.

Happy Path Detailed Flow of Events

Administrator pretends to add an auction in online auction house.1. Administrator enters the URL of website and navigated to the online auction site.

2. Administrator logged into the system successfully.

3. He or she goes to the part of add new lot/auction.

4. Administrator can post the details of auction, such as number of lots and lots ID.

5. Administrator finished adding new auctions.

6. Then, Administrator log out from the system.

7. The session finished.

Alternate path Detailed Flow of EventAdministrator removes ended auction.

1. Administrator enters the URL of website and navigated to the online auction site.

2. Administrator logs into the system.

3. When an auction is ended, administrator will receive a message about removing the auction.

4. Administrator will check on the finalization.

5. Administrator select remove option.

6. Administrator confirm remove.

7. Administrator has logged out from the system.

Buyer can place bid in the auction.

1. Buyer enters the URL of website and navigated to the online auction site.

2. Buyer logs into the system.

3. Buyer selects the auction before he/she makes any bid.

4. Any buyer is allowed to make the first bid.

5. The highest bid price will be the hammer price of the auction.

6. After placing the bid, buyer will log out from the system.

7. Session is ended.

Buyer purchases insurance to safeguard their interest.

1. Buyer enters the URL of website and navigated to the online auction site.

2. Buyer logs into the system.

3. Buyer selects the purchase insurance option before he/she wins the auction.

4. Any buyer is allowed to purchase the insurance for the bidding item.

5. After purchasing the insurance for the bidding item, buyer will log out from the system.

6. Session is ended.

User (Buyer and seller) can view the existing auction.

1. User enters the URL of website and navigated to the online auction site.

2. User logs into the system.

3. User can select the option to search for the specific auction to view.

4. User is able to view the auctions details.

5. After done viewing the details, user can log out from the system.

6. Session is ended.

Use Case: Manage Forum

Happy Path Basic Flow of Events

Name: Manage Forum

Description:

This use-case starts when the online auction system is created.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Administrator, Buyer, Seller.

Location(s): Malaysia.

Status: Pathway defined

Priority: 7Assumption:

Users (Buyer and Seller) will ask question when they do not understand how to use the application in a proper way. Administrator will prepare a FAQ section to answer all of the questions from the users.

Pre-condition(s):

User will log into the system if they want to post any questions.

Post-condition(s):

Users will be satisfied after their questions have been solved or answered by the administrator.

Primary (Happy) Path:Buyer attempts to search answers for his/her questions in FAQ section.

Alternate Pathway(s):

User can post his/her questions in the forum.

Administrator must answer all of the extra questions posted by the users in the forum. Admin and users (buyer and seller) chat through online when they are online.

Buyer or sellers leave their feedback in feedback section.

Users may contact through the hotline number that found in system.

Exception Pathway(s):

Administrator does not know how to answer the questions posted by users.

Users are not allowed to post unreasonable questions in the forum.

Happy Path Detailed Flow of Events

Buyer attempts to search answers for his/her questions in FAQ section.

1. User enters the URL of website and navigated to the online auction site.

2. User logged into the system successfully.

3. User can search for the question in the forum FAQ section.

4. User gets the solutions from the forum.

5. Then, user log out from the system.

6. The session finished.

Alternate path Detailed Flow of Events

User can post his/her questions in the forum.

1. User enters the URL of website and navigated to the online auction site.

2. User logged into the system successfully.

3. User can search for the question in the forum FAQ section.

4. If user fails to search for the answer in the forum, he/she selects the forum FAQ section to post his/her questions in there.

5. Then, user log out from the system.

6. The session finished.Administrator must answer all of the extra questions posted by the users in the forum.

1. Administrator enters the URL of website and navigated to the online auction site.

2. Administrator logged into the system successfully.

3. Administrator views the forum FAQ section to check whether there are any questions posted by the users.

4. Administrator answers all the reasonable questions.

5. Administrator ignores all of those unreasonable questions.

6. Then, administrator log out from the system.

7. The session finished.Admin and users (buyer and seller) chat through online when they are online.

1. User enters the URL of website and navigated to the online auction site.

2. User logged into the system successfully.

3. User goes to the chat room to check whether admin is in online or not.

4. If admin is in online, user asks him/her the doubts on using this service or updates about the items that they had purchased if they purchased any items earlier.

5. Then, user log out from the system.

6. The session finished.Buyer or sellers leave their feedback in feedback section.

1. User enters the URL of website and navigated to the online auction site.

2. User logged into the system successfully.

3. User goes to the feedback session to post any feedback or comments on using the website.4. User posts the feedback and clicks the submit button to send the feedback.

5. Then, user log out from the system.

6. The session finished.Users may contact through the hotline number that found in system.

1. User enters the URL of website and navigated to the online auction site.

2. User logged into the system successfully.

3. User goes to the forum section to check the Auction Companys Hotline Number.

4. User takes note of the contact number and call and interact with the company directly.5. Then, user log out from the system.

6. The session finished.Use Case: Manage Lots

Happy Path Basic Flow of Events

Name: Manage Lots

Description:

This use case is starts when a lot is added, updated or deleted.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Seller.

Location(s): Malaysia.

Status: Pathway defined

Priority: 2Assumption:

Seller adds new lot and allocates unassigned lots to upcoming auction for buyer to bid.

Pre-condition:

Seller registers as a member of the auction system before he/she posts any lots.

Post-condition(s):

Seller posted the lots in the online auction system to allow the buyer makes bids.

Primary (Happy) Path:

Seller attempts to add new lots in the auction to be placed bid by buyers.

Alternate Pathway(s):

Admin allocates unassigned lot to upcoming auction.

Seller provides details of the lot such as lot ID, textual description, reserve price, type and state.

Admin states the status for upcoming lot as assigned and lot that has not yet been assigned to an auction as unassigned.

Admin states the status for auction that has taken place and the lot has been sold as sold.

Exception Pathway(s):

Seller adds lot without adding item for sale.

Seller adds lot without login to the account.

Happy Path Detailed Flow of Events

Seller attempts to add new lots in the auction to be placed bid by buyers.

1. Seller enters the URL of website and navigated to the online auction site.

2. Seller logged into the system successfully.

3. He or she goes to the part of add new lot/auction.

4. The seller attempts to add new lots to the auction.5. Seller finished adding new lot to the auction.6. Then, the seller has logged out from the system.

7. The session finished.

Alternate path Detailed Flow of Events

Admin allocates unassigned lot to upcoming auction.

1. Admin enters the URL of website and navigated to the online auction site.

2. Admin logs into the system successfully.

3. Seller must have added lot(s).

4. Admin able to allocates unassigned lot to upcoming auction.

5. Then, admin log out from the system.

6. The session finished.

Seller provides details of the lot such as lot ID, textual description, reserve price, type and state.

1. Seller enters the URL of website and navigated to the online auction site.

2. Seller logs into the system successfully.

3. Seller must have added lot(s).

4. Seller will give a unique lot number to every single lot.

5. The unique lot number is given to lot(s) depends on different category.

6. Seller adds texture description on the existing lot(s) to describe the item(s).7. Then, seller set a price named as reserve price for the lots to buyer to place bids.

8. Finally, seller enters the type and state of the lots for buyers view.9. Buyers are able to view it once updated.

10. Then, seller logs out from the system.

11. The session finished.Admin states the status for upcoming lot as assigned and lot that has not yet been assigned to an auction as unassigned.

1. Admin enters the URL of website and navigated to the online auction site.

2. Admin logs into the system successfully.

3. Admin will state the status for the upcoming lot.

4. Then, admin logs out from the system.

5. The session finished.

Admin states the status for auction that has taken place and the lot has been sold as sold.

1. Admin enters the URL of website and navigated to the online auction site.

2. Admin logs into the system successfully.

3. Admin checks for lot(s) status and determine whether lot is sold or on sale.

4. Admin states auction status as sold if auction has been sold.5. Then, admin logs out from the system.

6. The session finished.Use Case: Manage Insurance

Happy Path Basic Flow of Events

Name: Manage Insurance

Description:

This use case is starts when a buyer purchases insurance for the bidding lots.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Administrator and buyer.

Location(s): Malaysia.

Status: Pathway defined

Priority: 6Assumption:

Some buyer will purchase insurance to safeguard their interest. And the Auction House will be taking the responsibility to any damage item.

Pre-condition(s):

Buyer decides to purchase insurance.

Post-condition(s):

Auction house will pay the refund for the buyer if there is any damage on the items.

Primary (Happy) Path:

Buyer can get refund if they purchase insurance if there is any damage on the items.Alternate Pathway(s):

Buyer reports about the item condition. Administrator will confirm whether buyer purchases any insurance before refund is made. Administrator will make refund for the buyer if the bided item is damage.Exception Pathway(s):

Buyer claims for refund without purchasing any insurance. Buyer purchases the insurance after he/she successfully bid the item.Happy Path Detailed Flow of Events

Buyer can get refund if they purchase insurance if there is any damage on the items.

1. Buyer enters the URL of website and navigated to the online auction site.

2. Buyer logs into the system successfully.

3. He or she goes to the part of claiming insurance to report the damage item.4. Administrator will check whether the buyer has bought the insurance for damaged item.5. Then, the buyer has logged out from the system.

6. The session finished.Alternate path Detailed Flow of Events

Buyer reports about the item condition.

1. Buyer enters the URL of website and navigated to the online auction site.

2. Buyer logs into the system successfully.

3. He or she goes to the part of claiming insurance to report the damage item.

4. Then, buyer logs out from the system.

5. The session finished.

Administrator will confirm whether buyer purchases any insurance before refund is made.

1. Administrator enters the URL of website and navigated to the online auction site.

2. Administrator logs into the system successfully.

3. Administrator will check the profile of the buyer.4. Administrator confirms whether any insurance is purchased for the damaged item.5. Then, administrator logs out from the system.

6. The session finished.

Administrator will make refund for the buyer if the bided item is damage.

1. Administrator enters the URL of website and navigated to the online auction site.

2. Administrator logs into the system successfully.

3. Administrator will check the profile of the buyer.

4. Administrator will make refund for the buyer by making the payment through PayPal.

5. Then, administrator logs out from the system.

6. The session finished.Use Case: Manage PaymentHappy Path Basic Flow of Events

Name: Manage PaymentDescription:

This use case is for the buyers, sellers and administrator of the Auction House to make payment among each other. Payment will be made by the buyer after he/she bids the lot from the Auction House. Commission will be taken from the full payment. V.A.T will be charged if the lot is a painting. The balance and deposit will be given to the seller.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Administrator, seller and buyer.

Location(s): Malaysia.

Status: Pathway defined

Priority: 5Assumption:

Buyers and sellers can make their payments through PayPal. This can avoid them from being so troublesome.

Pre-condition(s):

The auction is finalized and payment will be made.

Post-condition(s):

Status of the lot will be changed to sold after the payment has been generated.

Inventory of the seller will be reduced.

Primary (Happy) Path:

Buyer will make the payment to auction house.Alternate Pathway(s): Buyer purchases insurance to safeguard their interest. Full payment has been made through PayPal by the buyer.

Security deposit is returned to the seller.

The balance of the hammer price is given to the seller.Exception Pathway(s):

Buyers make their payment by cash or cheque.

Amount for each transaction made by the buyer is lower than the hammer price.

Happy Path Detailed Flow of Events

Buyer make payment to auction house.1. Buyer, seller and the administrator able to make their transaction by using PayPal.

2. They have to login to their PayPal account before any transaction is being proceed.

3. Lots will be given to the buyer after the transaction is completed.

Alternate path Detailed Flow of Event

Buyer makes full payment for the Auction House.

1. Buyer will login his/her account at the Auction House.

2. Buyer check and confirm with the hammer price before proceed to the next steps.

3. Buyer login to the PayPal account and transfer the hammer price to the Auction House.

4. Payment has been made successfully.

5. Receipt is printed as a proof for the transaction.

6. Lots will be given to the buyer after everything has been settled.

Security deposit is given back to the seller.

1. The Auction House login to the PayPal account.

2. Auction House will return the 5% security deposit back to the seller.

3. Auction House receives the full payment from the buyer.

Auction House will receive the commission from after payment is made.

1. The buyer pays full payment to the Auction House.

2. After the payment is received, the Auction House will get 10% commission from it.The Auction House will pay the balance to the payment.

1. The Auction House login to the PayPal account.

2. Auction House receives the full payment from the buyer.

3. 10% of the hammer price of the lot will be taken by the administrator as the commission.

4. If the lot is a painting, V.A.T which is 20% of the hammer price will be charged.

5. The balance of the lot sold is paid back to the seller.

Use Case: Finalize Auction

Happy Path Basic Flow of Events

Name: Finalize auction

Description:

This use case starts when every single auction is ended. It is use for the auction house to check bid price, calculate taxes, commissions and deduction on the hammer price and the amount that need to be return to the seller.

Author(s): Carmen Lee Kuan Ti, Chris Loo Wai Lok, Komalah.

Actor(s): Administrator.

Location(s): Malaysia.

Status: Pathway defined

Priority: 4Assumption:

Buyers can get the lots. Sellers and the Auction House can get their payment after finalizing the auction.

Pre-condition(s):

Once bid section ended.

Post-condition(s):

Buyer, seller and the Auction House will settle the payment among each other.

Primary (Happy) Path:

Auction House check bided price and calculate the amount that need to be pay by buyer and payment to be make for seller.

Alternate Pathway(s):

Auction House check whether bided price is lower, equal to or higher than the reserve price.

Auction House determines whether the item is sold or not sold.

Auction House calculates 10% commission of the hammer price. Buyer (Companies) are subjected to only 5% of commission. Auction House calculates the 20% VAT for paintings subjected to hammer price.

Exception Pathway(s):

Seller can get the payment before finalizing the auction.

Happy Path Detailed Flow of Events

Auction House check bided price and calculate the amount that need to be pay by buyer and payment that to be make for seller.

1. Auction must be bided and ended.

2. Auction House check price of ended auction.

3. Auction House calculate amount that need to pay by buyer.

4. Auction House calculates payment that need to be make for seller.

Alternate path Detailed Flow of Event

Auction House check whether bided price is lower, equal to or higher than the reserve price.

1. Auction must be bided and ended.

2. Auction House check price of ended auction whether is lower, equal to or higher than the reserve price.

Auction House determines whether the item is sold or not sold.

1. Auction House determines lot is sold if the auction price is equal to or higher than the reserve price.

2. Auction House determines lot is not sold if the auction price is lower than the reserve price.

Auction House calculates 10% commission of the hammer price.

1. Auction House must determine auction is sold.

2. Auction House calculates 10% commission of the hammer price as profit.

Buyer (Companies) are subjected to only 5% of commission.

1. Auction House checks the profile of buyer and determines the type of buyer.

2. Auction House calculates only 5% commission of the hammer price if the type buyer is company. Auction House calculates the 20% VAT for paintings subjected to hammer price.

1. Lots item sold must be paintings.

2. Auction House calculates 20% VAT for fine china subjected to the hammer price.