sportsgoods.com Case Study Sportsgoods.com is an online retail store that allows sellers (companies and individuals) to sell sport products to consumers (buyers). The website acts as a platform that connects buyers and sellers (Similar to Amazon.com). A seller or a buyer must have an account to conduct purchase transactions. A user account can only be a buyer's account or a seller's account. Individuals that need to buy and sell at the same time must have two different accounts. Buyers can research products and add them to carts, enter shipping and billing information, pay through the system, and track delivery status. Sportsgoods.com provides updated delivery information to buyers and recommends products based on buyers' searching/purchasing history. The Sellers also need to access information from sportsgoods.com. They need to know about their orders by week, month, product, and so forth. They also need to enter information regarding products' prices, description, features, pictures, etc Sportsgoods.com is planning to provide a rating/review system in which verified buyers and rate sellers and products separately From a system/business analyst standpoint, answer the following questions: 1. Who are the stakeholders for sportsgoods.com? For each type of stakeholder, what aspects of the system are of particular interest? (10 points) What are the main functional requirements for the major subsystems? (10 points) Draw a use case diagram for these use cases. (20 points) Describe some usability requirements for sellers and buyers. (10 points) To collect information on functional requirements for the rating and reviewing subsystem, what are some techniques that might be used? Be specific and include some sample questions you might ask by using various techniques. (10 points) Draw a use case diagram for the rating subsystem only. (14 points) Using the event decomposition technique for each event you identify in the above description. Using a table identify: name the event, state the type of event, and the name of the resulting use case. Think in terms of the user goal technique to identify as many use cases as you can think of that you would like to have in the system. (6 points) 2. 3. 4. 5. 6. 7