I.

INTRODUCTION
1) Project Overview
2) Problem Statement
II. SYSTEM ANALYSIS
1) Requirements Determination
A) Functional Requirements
1. Create Item Listing
1.1.

User sends a request to offer an item for sale.

1.2.

The system receives the request, executes user authorization (see

requirement 6) and displays form of creating item.
1.2.1.

If user is unauthorized, the system executes user log-in (see

requirement 3).

1.3.

User fills form by providing required information (e.g., title,

description, duration, starting price).
1.3.1.

User can either preview to see how listing will appear or post
their listing when they're ready.

1.4.

The system receives the submitted form, executes inputs validation (see
requirement 5).

1.5.

User can edit if they'd like to change something.

1.6.

The system save listing information in database.

2. Place Bid
2.1.

User access system to find an item to buy by searching a specific item

or browsing by selecting a category link.

2.2.

User select an item he or she wants from search results for reading item
details.

2.3.

User "place a bid" by entering an amount he or she willing to pay.

2.4.

The system receives the request, verifying user authorization (see

requirement 6).

2.5.

If user is unauthorized, the system asks user to log-in (see requirement

3).

2.6.

The system validates the bid before place it on item to make a change.
2.6.1.

If there are no previous bid, the system verifies that the

received bid is either larger than or equal the starting bid.

2.6.2.

If there are bids are made, the system verifies that the received
bid is larger than the current highest bid.

2.7.

The system increase users bid, up to their maximum (to maintain

users position as the high bidder or to meet the item's reserve price).
The users will be notified each time their bid is increased or if they've
been outbid.

3. Log-in
3.1.

When there are either any log-in request from user or execution from
system itself, the system displays a log-in interface.

3.2.

If user is a guest (unregistered user), he or she can register an account

(see requirement 4)

3.3.

User submits filled form by providing identification information (e.g.

email, password).

3.4.

The system receives the form, executes inputs validation (see

requirement 5).

3.5.

The system receives the request, verifying user authorization (see

requirement 6).

4. Register
4.1.

When there are either any register request from user, the system
displays a register interface.

4.2.

User submits filled form by providing personal information (e.g. email,

password, name, address).

4.3.

The system receives the form, executes inputs validation (see

requirement 5).

4.4.

The system save the information in database.

5. Validate form inputs

5.1.

The system verifies input field with predefined rules (e.g., email
standard form, type of input, range of value, nonempty field).

5.2.

The system verifies inputs related to user authentication with database

(e.g., existing, duplicating, matching information).

5.3.

If the inputs are invalid, the system re-display inputs form and requires
user to correct them.

5.4.

User can either correct the information until theyre accepted or give
up.

6. Authorize accessing resources

6.1.

The system verifies unregistered users roles (e.g., guest).

6.1.1.

If user is guest, they can not either create item listing or place a

bid.
6.2.

The system verifies registered users roles in database (e.g.,

administrator, item creator, bidder).
6.2.1.

If user is item creator, they can not place bid on their items.

6.2.2.

If user is item creator, they can cancel bid of underrated bidder.

7. End a listing
7.1.

When due date of an item is reached, the system close the auction.

7.2.

The system notifies to all parties the winner and the winning bid.

7.3.

User who wins the item will check out by providing payment
information (e.g.,credit card, bank account), and information regarding
the shipping (e.g., shipping service, contact).

7.4.

The system will verifies the users credit card information with an
online credit card clearance center and either accept or reject it.

B) Nonfunctional Requirements
1. Operational
1.1.

The system should be able to work on any Web browser

2. Performance
2.1.

Any number of people to work concurrently

3. Security
3.1.

Customers can only create auction during log in session

3.2.

Customers can only place bid on item during duration of auction

session

4. Cultural and Political

4.1.

The system should be able to distinguish between United States and

Vietnamese currency

4.2.

The system should be able to display the user interface in English and
Vietnamese

2) Functional Modeling
A) Business Process Modeling
1. Create item listing

2. Place bid

B) Use-case Description
1. Create item listing
Use Case Name:

Create a listing

ID:

Importance Level: High

Primary Actor:

Seller

Use Case Type:

Overview

Stakeholders and Interests:

Seller wants to list an item for sale
Brief Description:
Trigger:

This use case describes how we create a listing

Seller visits Websites and requests to sell an item

Type: External
Relationships:
Association: Seller
Include:

Log in

Extend:
Generalization:
Normal Flow of Events:
1.

The Seller submits a sell request to the System

2.

The System executes User Authentication

3.

The Seller provides the System with required information

4.

The System executes the Create a listing use case

5.

The System provides the result to the Seller

Sub-flows:
S-1:

Executes the Log-in use case

Alternate/Exceptional Flows:
2a:

The System
2. Bid on item

Use Case Name:

Bid on item

ID:

Importance Level: High

Primary Actor:

Buyer

Use Case Type:

Detail

Stakeholders and Interests:

Buyer wants to make an amount of bid on item that willing to buy
Brief Description:
The use case describes how current bid will be updated from the automated bidding system
Trigger:

Buyer chooses item and makes a bid on it

Type: External
Relationships:
Association: Buyer
Include:

Log in

Extend:
Generalization:

Normal Flow of Events:

1.

The Buyer submits a search request to the System

2.

The System provides a list of recommended items

3.

The Buyer chooses one of the items to find out additional information

4.

The Buyer provides the System with an amount of bid

5.

The System verifies that the Buyer is authorized

6.

The System executes the Place a bid use case

7.

The System validates whether sum of current bid and increment is less than amount of

bid
8.

The System updates current bid by adding an increment and the highest bidder

9.

The System provides the updated result to the Buyer

Sub-flows:
S-1:
Alternate/Exceptional Flows:
3a-1.
3a-2.
up.
5a:
7a:

The Buyer submits a new search request to the system.

The Buyer iterates over steps 2 through 3 until satisfied with search results or gives
The System executes the Log in use case
The Buyer iterates over steps 4 through 7 until satisfied condition or gives up

C) Use Case Diagrams

3) Structural Modeling
Front:
Class Name: User

ID: 1

Type: Concrete Domain

Description: An individual wishing to be seen at Online Auction Associated Use Cases: 1, 2, 3

System
Responsibilities
Offer item

Back:
Attributes:
Email

Collaborators
Item

Address
Name

Relationships:
Generalization (a-kind-of): Generalization1,

4)

Aggregation (has-parts):

Aggregation1

Other Associations:

Item,