Friday, October 14, 2011
Software Engineering Fundamentals
Online Auction System (Use Case Specifications)
Use Case : Register Users
Happy Path – Basic Flow of Events
Name: Register Users.
Description:
This use-case starts when a user attempt to be a member of the online auction system as seller or buyer. He or she or has to fill up registration form to become as a member of this site. This will end when a user either buyer or seller logged into the system once filled up the registration form.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer, and Company.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 2
Assumption(s):
An user will fill up a form that found at registration site in order to create an account besides become as a member.
Precondition(s):
User has filled up the registration form.
Postcondition(s):
The particulars of the user entered will be saved in company’s Database Management System.
The user successfully logged into the online auction system by a brief welcome message (notification).
Primary(Happy)Path:
User filled up the registration form that found at registration site in order to create account besides become as a member.
Alternate Pathway(s):
User has to login into the online auction system.
User has to logout from the online auction system.
Exception Pathway(s):
The user does not filled up the form neatly like leaving blank, registration would not take place.
User enters existing username which was taken by another user previously.
User does not enter valid or right CAPTCHA code that provided by the site.
User has forgotten the password.
Happy Path – Detailed Flow of Events
A user will fill up a form that found at registration site in order to create an account besides become as a member.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s 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 Pathways (1) – Detailed Flow of Events
User has to login into the online auction system.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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.
Alternate Pathways (2) – Detailed Flow of Events
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.
Exception Pathways (1) – Detailed Flow of Events
The user does not filled up the form neatly like leaving blank, registration would not take place.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s 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.
5. Accidentally, user does not fill the form fully by leaving a place blank and send the form.
6. Then, java script will prompt the user by giving error messages.
7. User fills up the details that not entered previously and then resend the form again.
Exception Pathways (2) – Detailed Flow of Events
User enters existing username which was taken by another user previously.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s view.
4. User then enter details about particulars:
e) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.
f) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.
5. User sends form to register.
6. Then, java script prompts the user to choose another username if the username desired by particular user already exists.
7. User chooses another username and then resends the form again.
Exception Pathways (3) – Detailed Flow of Events
User does not enter valid or right CAPTCHA code that provided by the site.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s view.
4. User then enter details about particulars:
g) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.
h) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.
5. User sends form to register.
6. Then, java script prompts the user to enter the code again by giving other code.
7. User enters correct CAPTCHA code and then resends the form again.
Exception Pathways (4) – Detailed Flow of Events
User has forgotten the password.
1. Once user enters the URL for the website, the home page navigated for user’s view.
2. User click Login button.
3. User enters username and forgot the password or enters wrong password.
4. The java script prompts the user to input right password.
5. Then, user clicks the button of “Forgot Password”.
6. The site asks user for the email address to send the password to user’s inbox.
7. User enters his or her email address.
8. The site notifies user that “Your password had sent to your message inbox ready”.
9. Then, user checks his or her inbox.
10. User finds the email sent by online auction system regarding forgot password and knows the right password.
11. User re-enter the URL from the browser.
12. User goes to login page and inputs right username and password.
13. User has successfully logged into the system.
Use Case : Manage Auction
Happy Path – Basic Flow of Events
Name: Manage Auction.
Description:
This use-case starts when a user either seller or buyer has logged in and seller attempt to add a new lot or auction. Buyer will attempt to place bid on the lot or auction to win the certain auction or lot in the auction system. If the bid that placed by buyer less than the reserve price, the lot went unassigned and become available for future auction. This will end when buyer win a lot or auction through highest bidding of price.
Author(s): Komalah, Kok Jun
Actor(s): Seller, and Buyer.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 1
Assumption(s):
Bidding on price of the lot or auction will go through until the auction or lot receives highest bid price that truly more than the reserve price and it’s status will be as sold once win by certain buyer.
Precondition(s):
User either seller or buyer has logged into the online auction system.
Postcondition(s):
Users successfully logout from the system.
The company decides the highest bid of price and informs the winner through online.
After informing winner, the buyer who won the auction or lot has to pay for the lot or auction through online payment system.
Primary(Happy)Path:
The seller attempts to add a new lot or auction into the online auction system.
Alternate Pathway(s):
The buyer began to place bid of price on the lot or auction.
Auction Company will assign lots according to the bids of price from buyer.
Exception Pathway(s):
The bidding of price does not take place at all in certain duration.
Seller does not provide details about a lot or auction such as reserve price.
Seller deletes the post of a new lot or auction before buyer’s bidding.
Happy Path – Detailed Flow of Events
The seller attempts to add a new lot or auction into the online auction system.
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 posts the details of the items such as lot number, textual description, type, state, and reserve price.
5. Seller finished adding new lot or auctions.
6. Then, the seller has logged out from the system.
7. The session finished.
Alternative Pathways (1) – Detailed Flow of Events
The buyer began to place bid of price on the lot or auction.
1. Buyer enters the URL of website and navigated to the online auction site.
2. When buyer attempt to bid on the lots auction, he or she logged into the system.
3. After this, the buyer can view the lot or auction which are posted by seller previously at main page sometimes.
4. If not, he or she attempts to search his or her preferred lot or auction.
5. When the buyer finds what is he or she looking for, buyer place bid of price they preferred on the lot or auction.
6. The price they entered classified as hammer price.
7. Once finished, the buyer logged out from the system successfully.
Alternative Pathways (2) – Detailed Flow of Events
Auction Company will assign lots according to the bids of price from buyer.
1. Company server checks the bidding price of buyer.
2. If the price is higher or equal to the original price (reserve price), the buyer will win the bidding.
3. The lot or auction status will become as sold.
4. Company auction server will inform the winner.
5. The buyer began to pay for the lot or auction that he or she won via online payment system.
6. If the hammer price is less than the reserve price, the buyer will lose the lot or auction.
7. The lot/auction will be unassigned and become available for future auctions.
Exception Pathways (1) – Detailed Flow of Events
The bidding of price does not take place at all in certain duration.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. Then, the seller has logged out from the system.
5. Buyer logged into the system to attempt to bid on posted lot or auction.
6. Unfortunately, the lot or auction that added at the auction system does not have buyer’s bidding for the certain duration.
7. The lot or auction went inactive or company’s server will set the status as unassigned.
Exception Pathways (2) – Detailed Flow of Events
Seller does not provide details about a lot or auction such as reserve price.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. The seller unfortunately forgot to post the necessary details about a lot such as reserve price.
5. Then, the seller has logged out from the system.
Exception Pathways (3) – Detailed Flow of Events
Seller deletes the post of a new lot or auction before buyer’s bidding.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. If he or she added new lot or auction for bidding online previously, he or she deletes the posted auctions.
5. Seller has logged out from the system.
Use Case : Manage Payment
Happy Path – Basic Flow of Events
Name: Manage Payment.
Description:
This use-case starts when a buyer win the bidding at the online auction system. He or she began to pay via online payment system, PayPal to company in order to get the lot or auction. The payment made by buyer to company not handed fully to the seller. Company will deduct the commission and VAT (for lots classified as paintings only) and pays seller.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer, and Company, PayPal.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 3
Assumption(s):
Once buyer win an auction or lot, he or she began to make the payment to company and company will pay the seller.
Precondition(s):
Buyer has to win an auction or lot.
Postcondition(s):
The lot or auction that won by buyer shipped or sent to the respective buyer.
Primary(Happy)Path:
Once buyer won an auction or lot, he or she pays the full hammer price to company.
Alternate Pathway(s):
Seller paid by company with the amount of deducted commission and deducted VAT for the lots classified as “paintings” only.
Exception Pathway(s):
Buyer’s credit card is invalid.
Buyer’s does not have enough balance in his or her current account to pay for the lot.
Buyer does not want to pay the full amount of bidding price to company.
Happy Path – Detailed Flow of Events
Once buyer won an auction or lot, he or she pays the full hammer price to company.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Company will get full hammer price that the winner bid on the lot or auction.
4. The lot or auction shipped or sent to buyer after the payment had settled successfully.
5. The session finished successfully.
Alternate Pathways (1) – Detailed Flow of Events
Seller paid by company with the amount of deducted commission and deducted VAT for the lots classified as “paintings” only.
1. Company gets the hammer price from buyer in certain duration.
2. Company takes commission which is 10% from the hammer price which is paid by buyer.
3. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as ”paintings” only by Auction Company.
4. If the lot is fine china or jewelry, VAT is not deducted.
5. Auction Company will round up the total price that the seller should get.
6. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (1) – Detailed Flow of Events
Buyer’s credit card is invalid.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Unfortunately, buyer does not enter the credit card number correct previously.
4. The company will call the buyer regarding credit card details.
5. Buyer goes to the site to update the information about the credit card.
6. Money transaction will take place by company and company gets full hammer price.
7. The lot or auction shipped or sent to buyer after the payment had settled successfully.
8. Company takes commission which is 10% of the hammer price.
9. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as”paintings” by Auction Company.
10. If the lot is fine china or jewelry, VAT is not deducted.
11. Auction Company will round up the total price that the seller should get.
12. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (2) – Detailed Flow of Events
Buyer’s does not have enough balance in his or her current account to pay for the lot.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Unfortunately, buyer does not have enough balance in his or her current account to pay for the lot or auction fully.
4. The company will call the buyer regarding bank account status.
5. Buyer goes to the bank to update the savings by adding enough money into the account.
6. Money transaction will take place by company and company gets full hammer price.
7. The lot or auction shipped or sent to buyer after the payment had settled successfully.
8. Company takes commission which is 10% of the hammer price.
9. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as ”paintings” by Auction Company.
10. If the lot is fine china or jewelry, VAT is not deducted.
11. Auction Company will round up the total price that the seller should get.
12. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (3) – Detailed Flow of Events
Buyer does not want to pay the full amount of bidding price to company.
1. Buyer informed by the company about the winning of certain lot or auction.
2. Buyer does not want to settle the payment for the lot of she or he won on the online auction.
3. Company will cancel the winning bid and the lot had won by the buyer become as unassigned.
Use Case : Manage Auction List
Happy Path – Basic Flow of Events
Name: Manage Auction List.
Description: 3
This use-case starts when a user attempts to view active auctions that are happening and the auction history. It will end when user completes the listing and searching session.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority:
Assumption(s):
User lists their auction history information and active auctions that are happening (past and present) in the auction house.
Precondition(s):
User has logged into the system if they want to view their auction history.
Postcondition(s):
User either buyer or seller finished searching or listing the information of the past and present auctions.
Primary(Happy) Path:
User lists out the active auctions that are happening in the online auction system.
Alternate Pathway(s):
User either seller or buyer lists the auction that already past in their auction history which are assigned as “sold”.
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
Exception Pathway(s):
A user attempt to search or list auction but it is not found in the system.
Happy Path – Detailed Flow of Events
User lists out the active auctions that are happening in the online auction system.
1. User has logged into the system with right username and password.
2. User is authenticating as a registered user of the online auction system.
3. User types the details of the auction they desire and interested in at search box.
a. Type of Lot
b. ID of auction if known.
4. The system search for the auction that the user mentions.
5. The auction details are prompt to the user.
6. User clicks on the link of auction or lot details and this will direct to complete listings.
7. The listing session is complete.
Alternate Pathways (1) – Detailed Flow of Events
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User access the auctions that is already past in their auction history.
4. The auction history is prompt to the user.
5. User clicks on the link of auction or lot details and this will direct to complete listings.
6. The listing session is complete.
Alternate Pathways (2) – Detailed Flow of Events
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User accesses their lots that have not been assigned or registered to auction.
a. User type in the lot number.
b. User type in the type of the lot.
4. The lots that user desire is prompt to the user.
5. User clicks on the link of auction or lot details and this will direct to complete listings.
6. The listing session is complete.
Exception Pathways (1) – Detailed Flow of Events
A user attempt to search or list auction but it is not found in the system.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User types the details of the auction they desire and interested in at search box.
a. Type of Lots
b. ID of auction if known.
4. The system returns error because the auction or lot that user searching for is not found in the system.
5. The user can start another listing session by re-enter the auction details for the searching propose.
Use Case : Set Winner Bid
Happy Path – Basic Flow of Events
Name: Set Winner Bid
Description: 2
This use case starts when the duration of an auction is expired and the bid place by the buyer is equal or higher that the reserved price. The company has to set the winning bid and inform the winner.
Author(s): Komalah, Kok Jun
Actor(s): Company
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority:
Assumption(s):
The company set the winning bid or highest hammer price and inform the winner.
Precondition(s):
The current bid price must be higher or equal than the reserved price.
Postcondition(s):
The winning bid is set and winner is informed.
The particular auction or lot is sold and auction state is change to past.
Primary(Happy) Path:
Company administrator sets the winning bid and informs the winner.
Alternate Pathway(s):
A notice is send to the winner to inform about the success of the auction.
A notice is send to the seller to inform the success of the auction.
Exception Pathway(s):
There is no winner for an auction because the bidding does not reach the reserve price.
Happy Path – Detailed Flow of Events
Company administrator sets the winning bid and informs the winner.
1. Administrator login with a valid username and password into the system.
2. Administrator lists out the auction that has due to its duration.
3. For each auction the admin check the bidding and the reserved price.
4. If the bidding is equal or higher than the reserved price, the hammer price is set and a winner is chosen.
5. The set of winning bid is finalized.
Alternate Pathways (1) – Detailed Flow of Events
A notice is send to the winner to inform about the success of the auction.
1. Administrator login with a valid username and password into the system.
2. The system will auto generate a notice for informing the winner.
3. The administrator sends the notice through email to the buyer.
4. The administrator ends the session.
Alternate Pathways (2) – Detailed Flow of Events
A notice is send to the seller to inform the success of the auction.
1. Administrator login with a valid username and password into the system.
2. The administrator sends a notice through email that generates by the system to inform the seller the success of the auction.
3. The administrator will send notice that generate by the system to inform the seller if the auction is not successfully take place because the biding does not reach the reserved price.
4. The administrator end the session.
Exception Pathways (1) – Detailed Flow of Events
There is no winner for an auction because the bidding does not reach the reserve price.
1. Administrator login with a valid username and password into the system.
2. Administrator lists out the auction that has due to its duration.
3. For each auction the administrator check the bidding and the reserved price.
4. The bidding does not reach the reserved price; the auction is cancelled and waiting to be assigned again.
5. The administrator end the set winning bid session.
Use Case : Register Users
Happy Path – Basic Flow of Events
Name: Register Users.
Description:
This use-case starts when a user attempt to be a member of the online auction system as seller or buyer. He or she or has to fill up registration form to become as a member of this site. This will end when a user either buyer or seller logged into the system once filled up the registration form.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer, and Company.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 2
Assumption(s):
An user will fill up a form that found at registration site in order to create an account besides become as a member.
Precondition(s):
User has filled up the registration form.
Postcondition(s):
The particulars of the user entered will be saved in company’s Database Management System.
The user successfully logged into the online auction system by a brief welcome message (notification).
Primary(Happy)Path:
User filled up the registration form that found at registration site in order to create account besides become as a member.
Alternate Pathway(s):
User has to login into the online auction system.
User has to logout from the online auction system.
Exception Pathway(s):
The user does not filled up the form neatly like leaving blank, registration would not take place.
User enters existing username which was taken by another user previously.
User does not enter valid or right CAPTCHA code that provided by the site.
User has forgotten the password.
Happy Path – Detailed Flow of Events
A user will fill up a form that found at registration site in order to create an account besides become as a member.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s 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 Pathways (1) – Detailed Flow of Events
User has to login into the online auction system.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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.
Alternate Pathways (2) – Detailed Flow of Events
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.
Exception Pathways (1) – Detailed Flow of Events
The user does not filled up the form neatly like leaving blank, registration would not take place.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s 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.
5. Accidentally, user does not fill the form fully by leaving a place blank and send the form.
6. Then, java script will prompt the user by giving error messages.
7. User fills up the details that not entered previously and then resend the form again.
Exception Pathways (2) – Detailed Flow of Events
User enters existing username which was taken by another user previously.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s view.
4. User then enter details about particulars:
e) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.
f) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.
5. User sends form to register.
6. Then, java script prompts the user to choose another username if the username desired by particular user already exists.
7. User chooses another username and then resends the form again.
Exception Pathways (3) – Detailed Flow of Events
User does not enter valid or right CAPTCHA code that provided by the site.
1. Once user enters the URL for the website, the home or main page navigated for user’s 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 user’s view.
4. User then enter details about particulars:
g) First name, Surname, Gender, Date of Birth, Address, City, State, Zip, Mobile number, and House number which are classified as Personal Information.
h) Email, Username, Password, Confirm Password, and How did you find us which are classified as ID and Password Information.
5. User sends form to register.
6. Then, java script prompts the user to enter the code again by giving other code.
7. User enters correct CAPTCHA code and then resends the form again.
Exception Pathways (4) – Detailed Flow of Events
User has forgotten the password.
1. Once user enters the URL for the website, the home page navigated for user’s view.
2. User click Login button.
3. User enters username and forgot the password or enters wrong password.
4. The java script prompts the user to input right password.
5. Then, user clicks the button of “Forgot Password”.
6. The site asks user for the email address to send the password to user’s inbox.
7. User enters his or her email address.
8. The site notifies user that “Your password had sent to your message inbox ready”.
9. Then, user checks his or her inbox.
10. User finds the email sent by online auction system regarding forgot password and knows the right password.
11. User re-enter the URL from the browser.
12. User goes to login page and inputs right username and password.
13. User has successfully logged into the system.
Use Case : Manage Auction
Happy Path – Basic Flow of Events
Name: Manage Auction.
Description:
This use-case starts when a user either seller or buyer has logged in and seller attempt to add a new lot or auction. Buyer will attempt to place bid on the lot or auction to win the certain auction or lot in the auction system. If the bid that placed by buyer less than the reserve price, the lot went unassigned and become available for future auction. This will end when buyer win a lot or auction through highest bidding of price.
Author(s): Komalah, Kok Jun
Actor(s): Seller, and Buyer.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 1
Assumption(s):
Bidding on price of the lot or auction will go through until the auction or lot receives highest bid price that truly more than the reserve price and it’s status will be as sold once win by certain buyer.
Precondition(s):
User either seller or buyer has logged into the online auction system.
Postcondition(s):
Users successfully logout from the system.
The company decides the highest bid of price and informs the winner through online.
After informing winner, the buyer who won the auction or lot has to pay for the lot or auction through online payment system.
Primary(Happy)Path:
The seller attempts to add a new lot or auction into the online auction system.
Alternate Pathway(s):
The buyer began to place bid of price on the lot or auction.
Auction Company will assign lots according to the bids of price from buyer.
Exception Pathway(s):
The bidding of price does not take place at all in certain duration.
Seller does not provide details about a lot or auction such as reserve price.
Seller deletes the post of a new lot or auction before buyer’s bidding.
Happy Path – Detailed Flow of Events
The seller attempts to add a new lot or auction into the online auction system.
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 posts the details of the items such as lot number, textual description, type, state, and reserve price.
5. Seller finished adding new lot or auctions.
6. Then, the seller has logged out from the system.
7. The session finished.
Alternative Pathways (1) – Detailed Flow of Events
The buyer began to place bid of price on the lot or auction.
1. Buyer enters the URL of website and navigated to the online auction site.
2. When buyer attempt to bid on the lots auction, he or she logged into the system.
3. After this, the buyer can view the lot or auction which are posted by seller previously at main page sometimes.
4. If not, he or she attempts to search his or her preferred lot or auction.
5. When the buyer finds what is he or she looking for, buyer place bid of price they preferred on the lot or auction.
6. The price they entered classified as hammer price.
7. Once finished, the buyer logged out from the system successfully.
Alternative Pathways (2) – Detailed Flow of Events
Auction Company will assign lots according to the bids of price from buyer.
1. Company server checks the bidding price of buyer.
2. If the price is higher or equal to the original price (reserve price), the buyer will win the bidding.
3. The lot or auction status will become as sold.
4. Company auction server will inform the winner.
5. The buyer began to pay for the lot or auction that he or she won via online payment system.
6. If the hammer price is less than the reserve price, the buyer will lose the lot or auction.
7. The lot/auction will be unassigned and become available for future auctions.
Exception Pathways (1) – Detailed Flow of Events
The bidding of price does not take place at all in certain duration.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. Then, the seller has logged out from the system.
5. Buyer logged into the system to attempt to bid on posted lot or auction.
6. Unfortunately, the lot or auction that added at the auction system does not have buyer’s bidding for the certain duration.
7. The lot or auction went inactive or company’s server will set the status as unassigned.
Exception Pathways (2) – Detailed Flow of Events
Seller does not provide details about a lot or auction such as reserve price.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. The seller unfortunately forgot to post the necessary details about a lot such as reserve price.
5. Then, the seller has logged out from the system.
Exception Pathways (3) – Detailed Flow of Events
Seller deletes the post of a new lot or auction before buyer’s bidding.
1. Seller enters the URL of website and navigated to the online auction site.
2. Seller logged into the system.
3. He or she goes to the part of add new lot/auction and post the details of the items.
4. If he or she added new lot or auction for bidding online previously, he or she deletes the posted auctions.
5. Seller has logged out from the system.
Use Case : Manage Payment
Happy Path – Basic Flow of Events
Name: Manage Payment.
Description:
This use-case starts when a buyer win the bidding at the online auction system. He or she began to pay via online payment system, PayPal to company in order to get the lot or auction. The payment made by buyer to company not handed fully to the seller. Company will deduct the commission and VAT (for lots classified as paintings only) and pays seller.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer, and Company, PayPal.
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority: 3
Assumption(s):
Once buyer win an auction or lot, he or she began to make the payment to company and company will pay the seller.
Precondition(s):
Buyer has to win an auction or lot.
Postcondition(s):
The lot or auction that won by buyer shipped or sent to the respective buyer.
Primary(Happy)Path:
Once buyer won an auction or lot, he or she pays the full hammer price to company.
Alternate Pathway(s):
Seller paid by company with the amount of deducted commission and deducted VAT for the lots classified as “paintings” only.
Exception Pathway(s):
Buyer’s credit card is invalid.
Buyer’s does not have enough balance in his or her current account to pay for the lot.
Buyer does not want to pay the full amount of bidding price to company.
Happy Path – Detailed Flow of Events
Once buyer won an auction or lot, he or she pays the full hammer price to company.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Company will get full hammer price that the winner bid on the lot or auction.
4. The lot or auction shipped or sent to buyer after the payment had settled successfully.
5. The session finished successfully.
Alternate Pathways (1) – Detailed Flow of Events
Seller paid by company with the amount of deducted commission and deducted VAT for the lots classified as “paintings” only.
1. Company gets the hammer price from buyer in certain duration.
2. Company takes commission which is 10% from the hammer price which is paid by buyer.
3. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as ”paintings” only by Auction Company.
4. If the lot is fine china or jewelry, VAT is not deducted.
5. Auction Company will round up the total price that the seller should get.
6. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (1) – Detailed Flow of Events
Buyer’s credit card is invalid.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Unfortunately, buyer does not enter the credit card number correct previously.
4. The company will call the buyer regarding credit card details.
5. Buyer goes to the site to update the information about the credit card.
6. Money transaction will take place by company and company gets full hammer price.
7. The lot or auction shipped or sent to buyer after the payment had settled successfully.
8. Company takes commission which is 10% of the hammer price.
9. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as”paintings” by Auction Company.
10. If the lot is fine china or jewelry, VAT is not deducted.
11. Auction Company will round up the total price that the seller should get.
12. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (2) – Detailed Flow of Events
Buyer’s does not have enough balance in his or her current account to pay for the lot.
1. Buyer informed by the company about the winning of certain lot or auction.
2. He or she began to pay via credit card that he or she registers for the money transaction at the online auction system.
3. Unfortunately, buyer does not have enough balance in his or her current account to pay for the lot or auction fully.
4. The company will call the buyer regarding bank account status.
5. Buyer goes to the bank to update the savings by adding enough money into the account.
6. Money transaction will take place by company and company gets full hammer price.
7. The lot or auction shipped or sent to buyer after the payment had settled successfully.
8. Company takes commission which is 10% of the hammer price.
9. VAT, at a rate of 20% of the hammer price, is also deducted for lots assigned as ”paintings” by Auction Company.
10. If the lot is fine china or jewelry, VAT is not deducted.
11. Auction Company will round up the total price that the seller should get.
12. Then, company pays the seller via PayPal to seller’s credit card.
Exception Pathways (3) – Detailed Flow of Events
Buyer does not want to pay the full amount of bidding price to company.
1. Buyer informed by the company about the winning of certain lot or auction.
2. Buyer does not want to settle the payment for the lot of she or he won on the online auction.
3. Company will cancel the winning bid and the lot had won by the buyer become as unassigned.
Use Case : Manage Auction List
Happy Path – Basic Flow of Events
Name: Manage Auction List.
Description: 3
This use-case starts when a user attempts to view active auctions that are happening and the auction history. It will end when user completes the listing and searching session.
Author(s): Komalah, Kok Jun
Actor(s): Seller, Buyer
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority:
Assumption(s):
User lists their auction history information and active auctions that are happening (past and present) in the auction house.
Precondition(s):
User has logged into the system if they want to view their auction history.
Postcondition(s):
User either buyer or seller finished searching or listing the information of the past and present auctions.
Primary(Happy) Path:
User lists out the active auctions that are happening in the online auction system.
Alternate Pathway(s):
User either seller or buyer lists the auction that already past in their auction history which are assigned as “sold”.
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
Exception Pathway(s):
A user attempt to search or list auction but it is not found in the system.
Happy Path – Detailed Flow of Events
User lists out the active auctions that are happening in the online auction system.
1. User has logged into the system with right username and password.
2. User is authenticating as a registered user of the online auction system.
3. User types the details of the auction they desire and interested in at search box.
a. Type of Lot
b. ID of auction if known.
4. The system search for the auction that the user mentions.
5. The auction details are prompt to the user.
6. User clicks on the link of auction or lot details and this will direct to complete listings.
7. The listing session is complete.
Alternate Pathways (1) – Detailed Flow of Events
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User access the auctions that is already past in their auction history.
4. The auction history is prompt to the user.
5. User clicks on the link of auction or lot details and this will direct to complete listings.
6. The listing session is complete.
Alternate Pathways (2) – Detailed Flow of Events
User either buyer or seller lists the auction that have not been assigned classified as “unassigned” in their auction history.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User accesses their lots that have not been assigned or registered to auction.
a. User type in the lot number.
b. User type in the type of the lot.
4. The lots that user desire is prompt to the user.
5. User clicks on the link of auction or lot details and this will direct to complete listings.
6. The listing session is complete.
Exception Pathways (1) – Detailed Flow of Events
A user attempt to search or list auction but it is not found in the system.
1. User has logged into the system with correct username and password.
2. User is authenticating as a registered user.
3. User types the details of the auction they desire and interested in at search box.
a. Type of Lots
b. ID of auction if known.
4. The system returns error because the auction or lot that user searching for is not found in the system.
5. The user can start another listing session by re-enter the auction details for the searching propose.
Use Case : Set Winner Bid
Happy Path – Basic Flow of Events
Name: Set Winner Bid
Description: 2
This use case starts when the duration of an auction is expired and the bid place by the buyer is equal or higher that the reserved price. The company has to set the winning bid and inform the winner.
Author(s): Komalah, Kok Jun
Actor(s): Company
Location(s): Subang Jaya, Selangor.
Status: Pathways defined.
Priority:
Assumption(s):
The company set the winning bid or highest hammer price and inform the winner.
Precondition(s):
The current bid price must be higher or equal than the reserved price.
Postcondition(s):
The winning bid is set and winner is informed.
The particular auction or lot is sold and auction state is change to past.
Primary(Happy) Path:
Company administrator sets the winning bid and informs the winner.
Alternate Pathway(s):
A notice is send to the winner to inform about the success of the auction.
A notice is send to the seller to inform the success of the auction.
Exception Pathway(s):
There is no winner for an auction because the bidding does not reach the reserve price.
Happy Path – Detailed Flow of Events
Company administrator sets the winning bid and informs the winner.
1. Administrator login with a valid username and password into the system.
2. Administrator lists out the auction that has due to its duration.
3. For each auction the admin check the bidding and the reserved price.
4. If the bidding is equal or higher than the reserved price, the hammer price is set and a winner is chosen.
5. The set of winning bid is finalized.
Alternate Pathways (1) – Detailed Flow of Events
A notice is send to the winner to inform about the success of the auction.
1. Administrator login with a valid username and password into the system.
2. The system will auto generate a notice for informing the winner.
3. The administrator sends the notice through email to the buyer.
4. The administrator ends the session.
Alternate Pathways (2) – Detailed Flow of Events
A notice is send to the seller to inform the success of the auction.
1. Administrator login with a valid username and password into the system.
2. The administrator sends a notice through email that generates by the system to inform the seller the success of the auction.
3. The administrator will send notice that generate by the system to inform the seller if the auction is not successfully take place because the biding does not reach the reserved price.
4. The administrator end the session.
Exception Pathways (1) – Detailed Flow of Events
There is no winner for an auction because the bidding does not reach the reserve price.
1. Administrator login with a valid username and password into the system.
2. Administrator lists out the auction that has due to its duration.
3. For each auction the administrator check the bidding and the reserved price.
4. The bidding does not reach the reserved price; the auction is cancelled and waiting to be assigned again.
5. The administrator end the set winning bid session.
Subscribe to:
Posts (Atom)