Project #1553 - Java/UML

Using the use cases below, create a single use case diagram that best represents the use cases and contains all actors, use cases, actor-use case relationships, and use case-use case relationships.

Use Case: Log In

Main Scenario

  1. User enters name and password.
  2. System determines name and password are a valid combination.
  3. System displays user action menu.

Alternative: User Already Logged In

Alternative: Log In Failed

  1. The system determines the name and password are not a valid combination.
  2. The system displays an error message to the User for 15 seconds.
  3. The system returns to the log in screen.

Use Case: Add Account

Main Scenario

  1. Manager selects "Add Account".
  2. System displays "New Account" screen.
  3. Manager enters a new account name and selects "OK".
  4. System creates a new account with the given name.
  5. System displays temporary password.
  6. Manager selects "OK".
  7. System displays to main menu.

Alternative: Manager Not Logged In

  1. Include Log In, Manager plays role of User.
    Rejoin main scenario at step 1.

Alternative: Account Name Exists

  1. The system determines an account with the provided account name exists.
  2. The system displays an error message 15 seconds.
    Rejoin main scenario at step 2.

Alternative: Manager Cancels

  1. The manager selects "Cancel"
  2. System displays to main menu.

Use Case: Add Drink To Tab

Main Scenario

  1. Server selects "Add Drink".
  2. System displays "Open Tabs" list.
  3. Server selects tab.
  4. Server displays "Add Drink" dialog.
  5. [Extension: Missing Drink]Server selects drink from list and clicks "OK".
  6. System updates tab to include the new drink.
  7. System displays to main menu.

Alternative: Server Not Logged In

  1. Include Log In, Server plays role of User.
    Rejoin main scenario at step 1.

Alternative: Account Name Exists

  1. The system determines an account with the provided account name exists.
  2. The system displays an error message 15 seconds.
    Rejoin main scenario at step 2.

Alternative: Server Cancels Tab List

  1. The server selects "Cancel"
  2. System displays to main menu.

Alternative: Server Cancels Drink List

  1. The server selects "Cancel"
  2. System displays to main menu.

Use Case: Add Custom Drink

Extends: Add Drink To Tab at Missing Drink

Main Scenario

    • 5.1 Server selects "Add Custom Drink".
    • 5.2 System shows "Ingredients".
    • 5.3 Server selects ingredients for drink and presses "OK".

Return to step 6 in main scenario of Add Drink To Tab.

Alternative: Server Cancels Custom Drink

  • 5.3 The server selects "Cancel"
  • 5.4 System displays to main menu.

Problem 6

Using the methodology for class diagrams described in this course, create class diagrams (one each) for the classes POSSystem and DrinkMenu that best reflects what is modeled in the supplied sequence diagrams. Be sure to carefully consider the relationships between classes.

A sequence diagram for the creation of a POSSystem instance.

Figure 1. A sequence diagram for the creation of a POSSystem instance.

A sequence diagram DrinkMenu's resonse to showMenu().

Figure 2. A sequence diagram DrinkMenu's resonse to showMenu().

Subject Computer
Due By (Pacific Time) 12/16/2012
Report DMCA
TutorRating
pallavi

Chat Now!

out of 1971 reviews
More..
amosmm

Chat Now!

out of 766 reviews
More..
PhyzKyd

Chat Now!

out of 1164 reviews
More..
rajdeep77

Chat Now!

out of 721 reviews
More..
sctys

Chat Now!

out of 1600 reviews
More..
sharadgreen

Chat Now!

out of 770 reviews
More..
topnotcher

Chat Now!

out of 766 reviews
More..
XXXIAO

Chat Now!

out of 680 reviews
More..
All Rights Reserved. Copyright by AceMyHW.com - Copyright Policy