Realtime%20Commercial%20Bidding%20System - PowerPoint PPT Presentation

About This Presentation
Title:

Realtime%20Commercial%20Bidding%20System

Description:

Strong market demand for e-commerce systems. Few existing B-2-B commodities brokerages. Low market pricing means automation needed ... – PowerPoint PPT presentation

Number of Views:38
Avg rating:3.0/5.0
Slides: 38
Provided by: drbillm
Learn more at: http://www.cse.msu.edu
Category:

less

Transcript and Presenter's Notes

Title: Realtime%20Commercial%20Bidding%20System


1
Realtime Commercial Bidding System
  • Team 6
  • Brenda HarveyJohn JohnstonJason
    LaBumbardPeter Tirrell

2
Realtime Commercial Bidding System
  • Provides realtime bidding capabilities
  • Motivation for project
  • Strong market demand for e-commerce systems
  • Few existing B-2-B commodities brokerages
  • Low market pricing means automation needed
  • System fills a market niche and does so cost
    effectively

3
Overview of Features
  • Standard and reverse auctions
  • Realtime bidding and viewing
  • Self-serve auction setup
  • Administrator
  • Distributed auctioneer attributes operations
  • Account management functions
  • Combined account functionality

4
Overview of Features continued
  • Users may participate in multiple auctions
  • Forgotten password retrieval
  • On the fly account setup

5
Prototype
  • Login screen
  • Existing and new users
  • Auction list view/select
  • Join, bid in, and view an auction
  • Bid history, withdrawing
  • Client-side view of reverse auction

6
Login Screen
7
Auction Information Screen
8
Regular Auction Screen
9
Regular Auction Screen 2
10
Regular Auction Finished
11
Withdrawing a Bid
12
Auction Information Screen 2
13
Reverse Auction Screen
14
Reverse Auction Finished
15
Create Auction Screen
16
Grey Areas
  • What is an Auctioneer?
  • Automated piece of code
  • One approach handle as distinct class
  • Second approach divide functionality to other
    classes
  • Why an Administrator?
  • Can all site maintenance be automated?
  • What can be handled by auctioneer or user
    account functions and what cannot?

17
How Problems Were Solved
  • Auctioneer
  • Logically divide auctioneer data and
    functionsinto auction and user account classes
  • Avoid redundancy and simplify design
  • Site Administration
  • Create an administrator class
  • Administrator basically a special type of user
    account

18
Description of Class Model
  • Aggregated under Realtime Auction Site
  • Makes use of Administrator
  • Abstract classesAuction
  • User account aggregated for client and bidders
  • Client side login, sign-up, get password
  • Auctioneer attributes and functionality
    distributed among several classes

19
Class Model
20
Sequence Diagrams
  • Generalized overall sequence diagram
  • Many possible object interactions
  • Not a single stepwise progression of events
  • Most possible interactions presented
  • Use specific sequence diagrams
  • Depict major interaction scenarios
  • Single stepwise progression of events
  • Ack used to denote acknowledgement of messages

21
Sequence Diagram
22
Bidding in a Standard Auction
23
Bidding in a Reverse Auction
24
Setting up a Reverse Auction
25
Setting up a Standard Auction
26
Use Case Diagrams
  • Generalized use case diagram
  • Many possible actor/activity interactions
  • Actors include bidder, client, and administrator
  • Specific use case diagrams
  • Client interactions w/ in progress auctions
  • Setting up an auction
  • Bidder auction participation scenarios

27
Main Use Case Diagram
28
Seller Use Case Diagram
29
Bidder Use Case Diagram
30
State Diagrams
  • Used to show possible states of major objects
  • Administrator state diagram
  • Fail-safe site intervention capabilities
  • Auction state diagram
  • Describes progression of auction behavior
  • User state diagram
  • Describes user interaction in realtime
  • User account state diagram
  • On the fly account maintenance

31
Administrator State Diagram
32
Auction State Diagram
33
User State Diagram
34
User Account State Diagram
35
Critical System Properties
  • Summary of critical system properties
  • No distinct auctioneer class
  • Administrator
  • One user account, both client and bidder
    capabilities
  • Self-serve account maintenance
  • Auction abstract class and inheritance
  • Client-side functionality

36
Promela and XSpin
  • Analysis of two client-supplied state diagrams
  • Performed initial visual analysis of diagrams
  • Coded state machines in promela
  • Developed basic test case scenarios
  • Future work
  • LTL
  • Additional scenario analyses

37
Client State Diagram
  • Spin Analysis
  • Issue of end_auction signal in any state other
    than Idle results in deadlock
  • Failure of auctioneer to send bidok results in
    deadlock in User_Bid state
  • Dropped bids on timeout
  • Non-Spin Analysis
  • No bid-not-ok signal (timeout?)
  • What happens when client bid is not high bid?
Write a Comment
User Comments (0)
About PowerShow.com