150 likes | 255 Views
Amazon.com Infomediator. The NoZama Group. Amazon.com Infomediator. The NoZamazons:. Toshiaki Majima Chih Po Chiang Jeff Wong Lance Bohy. General Idea. High level of abstraction. First implementation of UML. First use of PowerPoint. CIS 422 Use Cases :: Core Functionality.
E N D
Amazon.com Infomediator The NoZama Group
Amazon.com Infomediator The NoZamazons: Toshiaki Majima Chih Po Chiang Jeff Wong Lance Bohy
General Idea High level of abstraction First implementation of UML First use of PowerPoint
CIS 422Use Cases :: Core Functionality 3 Common Use Cases Price Comparison Book Recommendation Customer Profile Customer
Customer CIS 422Use Case 1: Core Functionality Price Comparison
Use Case 1: Core Functionality Name: Price Comparison Performing Actor: Customer (human), other infomediators, Amazon.com (?) Entry Condition: User wants to buy book. User knows specific information about how to search for book. User has PC connected to Internet Exit Condition: listing of prices of book
Use Case 1: Core Functionality Event Flow: Customer selects search category (optional) Customer enters search criteria Customer submits search criteria by pressing button System determines price comparisons by utilizing infomediators Price comparison chart is displayed for the Customer (exit condition reached)
Customer CIS 422Use Case 2: Core Functionality Book Recommendation
Use Case 2: Core Functionality Name: Book Recommendation Participating Actor: Customer, Other Infomediators Entry Condition: Customer sits in front of a computer and visits Multishelf.com Exit Condition: Customer receives listing of recommended books
Use Case 2: Core Functionality • Event Flow: • System automatically checks if the user is new or already an existing customer. • If the customer is new, the system gives it a generic recommendation of books (e.g.. Top 10 books) • If the customer exists (and thus has a user profile) the system gives specific recommendation based on the profile data (such as hobby).
Customer CIS 422Use Case 3: Core Functionality Customer Profile
Use Case 3: Core Functionality Name: Customer Profile Participating Actor: Customer Entry Condition: Customer has initialized profile request Exit Condition: Web confirmation displayed in browser window.
Use Case 3: Core Functionality Event Flow: System prompts customer for information Customer inputs information Customer clicks Submit button to send request for new profile for processing System checks to see if user already has a profile If no previous profile exist new profile is created and the appropriate message of such is sent to user via HTML
Concerns Defining proper Actors Overcoming desire for quick implementation Scheduling & Communication