Imagine that you are on a project team to develop a new information system to support the functionality described below, for Fast Freddy’s, a local hamburger chain. This is a business automation project, so your goal is to create a computer system that supports the functionality desired by Freddy (the chain owner).

1. Review the use case diagram, narrative, and “paper prototype” screenshots provided on the pages that follow.

2. Write an “Overview, Essential” use case description for only the “Make Menu Assignments” use case. Remember that an “Overview” UC description provides only a high-level overview of the requirements, and an “Essential” UC description is not technology / implementation dependent. In other words, it can be created on any system or platform.

3. If the narrative does not give you all the information that you need to complete the assignment, complete it to the extent possible and make a list of questions or assumptions for which you would need answers or verification to finish it according to Freddy’s wishes.

   The Use Case Diagram

   Assume that you have already worked with Freddy to finalize the use case diagram for his new system:

   Use Case Diagram for the New Fast Freddy’s System

   The “Make Menu Assignment” Use Case

   Freddy has previously described the expected functional for assigning new menu items to stores, as follows:

   “My sales have dropped lately, due to my competitors selling a much greater variety of menu items than I do. So I want to expand my business by selling new menu items, but I can't afford to waste a lot of time and money offering items at all of my stores that aren't going to sell well. So I need to be able to test out new menu items at selected stores before deciding to sell them everywhere. And my store managers need to know what new items they will be responsible for testing out.

   Thus, at the beginning of each month, I want to be able to log in and tell the system to randomly assign 3 untested menu items to each store. Then I want it to show me what items it has assigned to each store. I want this done in a window where I can replace one item with another if I don’t like the random assignments that were made by the system. Once I’m done tweaking the assignments, the system should email each store manager a list of the untested menu items that their store(s) will be offering for sale that month.”

   You have also worked with Freddy in the past to produce some preliminary sketches of how he wants the new system to look, and how he wants it to functions. You can see the resulting “paper prototype” on the next page

   Sample Class Diagram for Freddy’s New System (useful for writing up a fully detailed use case description for “Make Menu Assignments”) Use Case Description for “Make Menu Assignments”

4. Use Case Name:		ID:	Importance Level:
   Primary Actor:	Use Case Type:
   Stakeholders and Interests:
   Brief Description:
   Trigger: Type:
   Relationships: Association: Include: Extend: Generalization:
   Normal Flow of Events: 1. 2. 3. (add numbers as needed – delete this note when finished!)
   SubFlows:
   Alternate/Exceptional Flows: