Company Overview (not to be used for creating diagrams) Rocky Mountain Outfitters (RMO) is a sports clothing distributor for the western US. Outdoor recreation activities are very popular in this region of the country. RMO sells a variety of winter and summer sports clothes and accessories for an increasing variety of sports, including skiing, snow boarding, mountain biking, water skiing, jet skiing, kayaking, jogging, hiking, camping, fishing, and mountain climbing. RMO currently employs more than 300 people and produces almost $50 million annually in sales. The company originated as a mail-order (catalog) operation, but also has in-store retail sales, and runs a phone-order operation. RMO recently implemented a Web site to feature its products. However, it does not currently have the capability for customers to place orders over the internet. While they can view the complete RMO catalog online, they still have to call or place orders by mail. RMO ultimately hopes to have a complete customer support system that handles functionality including customer inquiries / catalog requests, order entry, order tracking, shipping, back ordering, returns, and sales analysis. Your task as a systems analyst is to help RMO develop basic online ordering and support capabilities for its Web site, as a prelude to implementing the full customer support system mentioned above at a later time. The requirements for the first phase of the system rollout are described below. PART 1. Use Case Diagram Dont forget that you MUST include a use case named PLACE WEB ORDER! Allowing customers to place orders from the online catalog is the most important task facing the development team. The steps for placing a web order will be as follows: From the home page, the customer will click on a link to go to the online catalog. The catalog can be either browsed or searched for a particular item. Searching/browsing the catalog is required in order to place a web order. When the customer finds something he wants to order, he will click on the Add to Shopping Cart button next to that item, and the item will be added to his cart. After the customer is done searching/browsing and adding items to his cart, he will click on the Checkout button, which will allow him to review all the items in his shopping cart. He can then change item(s) in the cart if desired, before clicking Continue. The system will then display the payment form, so that he can enter his shipping and payment information. After the system verifies the credit card information, the customer will have one last chance to cancel his order. Once he clicks the Submit button to submit the order, a confirmation page will be displayed, and a summary email will be sent to him that contains all of the order information. This order information will also be stored in the RMO database, so that RMO can fulfill the order later. Please note that uncompleted shopping carts will be deleted from memory as soon as the customer leaves the RMO website. NOTE: You may decide that there is more than one use case mentioned in the paragraph above. However, you must include a use case named PLACE WEB ORDER or you will lose points! Other Use Cases If desired, the customer can choose to set up a user account with a password so that each time she returns to the site, she does not have to enter her shipping and credit card information all over again. A link allowing users to set up an account appears on multiple pages of the Web site, including the order page. A customer may login either before beginning an order, or after completing her shopping cart but before entering payment and shipping data. In other words, logging in to a user account is optional for placing an order with RMO, but the customer can, if she has an account, log in prior to completing the order so that her information will be filled in automatically. A customer can also update her customer information whenever desired. By clicking on a button titled Update Your Account, which appears in various locations on the Web site, she will be taken to a new page where she can log in (if not logged in already), and update her name, address, phone, email, and payment information. There is a database table that stores this customer information. Customers may return to the web site whenever they want, and click on the Check Order Status link on the home page to see the status of a previously placed order. It is not necessary to have set up a customer account to check on an order. This is because the confirmation email that is sent out to the customer after placing an order contains a unique Order Number which can be used to look up past orders. Obviously, the products available for sale in the catalog are constantly changing. This means that the Merchandising Department must be able to update the catalog on a regular basis. There is a database table that stores information on all the products for sale in the catalog. Use Case Diagram Grading Rubric No title / heading on the UC diagram, identifying the system which it represents: -2. No system boundary box (or the boundary box surrounds both the actors & use cases): -2. A required UC plus its association(s) are missing altogether: -3. A required UC plus its association(s) and actor(s) are missing altogether: -4. UC is present but the association is wrong/missing: -2 for each incorrect / missing association. Extra use case or actor included based on information not in the narrative: -2 UC names arent a verb phrase: -2 for first occurrence; -3 maximum for assignment. Incorrect / missing or arrows: -2 each; -5 maximum for assignment. Having two or more uses cases where there should be only one: -2 per base use case. For example, if in one part of the diagram you have 4 use cases that should only be one, and in another part you have two uses cases that should only be one, this is two deductions of -2 each. Having one use case which should be multiple uses cases: -2 per omitted use case. For example, if one use case should be three separate use cases, this is two deductions of -2. Use Case Diagram missing entirely: -50. Maximum number of points taken off if the UC diagram was attempted and completed in its entirety and in good faith: -20 pts (NOTE: failure to complete the entire diagram in good faith will result in further deductions up to the maximum of 50 pts.)