Use
Case Descriptions
1. Register Use case
a. Main Flow
i. The user enters the
details (like Name, Login, Password, City, E-mail-id, ....). (E1)
ii. User registers
either as buyer or seller.
b. Alternate Flow
i. E1: If the
Login already exists or both the Passwords do not match, the system
takes the user back to
the Register page.
ii. E1: If all
the details are not provided, the system takes the user back to registration
page.
2. Login Use case
a. Assumptions
i. The user is already
registered in the system as a Buyer /Seller/Monitor.( User
Registration may be an
off-line process)
b. Main Flow
i. The User enters
his/her User name and password.
ii. The System
determines whether the particular user is registered. (E2)
iii. If the user is
registered, the system determines his category (e.g., Buyer, Seller,
Monitor).
iv. The system
displays the corresponding interface for the particular user category.
v. For each user the
system allows him/her to change his profile as part of his interface
in all the pages that
follow. (E3)
c. Alternate flow
i. E2: User
name/ Password are incorrect. The System takes the User back to the
Login page and prompts
for a re-login.
ii. E3: Inputs
are invalid.
iii. The System
provides the parameter input interface again for correcting his inputs.
3. Logout Use Case
a. Main Flow
i. The User Exits
ii. The system
persists the user activity history.
4. Setup New Auction
Use case
a. Main Flow
i. The
buyer/seller/monitor chooses to setup a new auction.
ii. He chooses the
product(s) to be auctioned from the catalog of products.
iii. He sets the rules
for the auction.
iv. He sets the
Starting/Closing Date/Time of the auction.
v. He chooses the
algorithms for determining winners and price.
5. Bid Use case
a. Main Flow
i. The buyer provides
the information on the products he would like to buy.
ii. He chooses a
business model offered by VIPANI or define his own business
model
b. Alternate flow
i. If buyer provides
invalid information, system takes back to bidding page.
6. Offer Use case
a. Main Flow
i. The Seller provides
the information on the products he would like to sell
ii. He chooses a
business model offered by VIPANI or define his own business
model
b. Alternate flow
i. If seller provides
invalid information, system takes back to offering page.
7. Add /Choose
Product Use case (uses Browse Catalog Use case)
a. Main Flow
i. The
buyer/seller/monitor browses through a catalog of available products.
ii. He selects the
product(s) to be auctioned (E4)
b. Alternate Flow
i. E4: Product
not present in the catalog
ii. The monitor
creates new product(s) and adds it to the catalog (subject to authorization
by Purchasing
Management to ensure new products are qualified and
not duplicated
somewhere else in the system.).
8. Create Auction
Rules Use case
a. Main Flow
i. The buyer/seller
sets the limit on the set of winners.
ii. The buyer sets the
limit on the amount he is willing to pay to each winning supplier.
iii. The buyer sets
the limit on the total amount he is willing to pay.
9. View Bids Use case
a. Main Flow
i. The buyer browses
the catalog of auctions set up by him.
ii. The system
displays the auction status.
10. View
Offers Use case
a. Main Flow
i. The seller browses
the catalog of auctions set up by him.
ii. The system
displays the auction status.
11. Close Auction Use
case
a. Main Flow
i. The
buyer/seller/monitor chooses to close an auction.
ii. The system
determines the winner of the auction and informs both the
buyer, seller and the
monitor (subject to business model) about the details.
iii. The system closes
the auction and updates the list of auctions.
12. Notify User Use
case
a. Main Flow
i. The system sends
the message to the users (buyers/sellers).