New Menu Item

Use Case

ASSUMPTIONS

PRE-CONDITIONS

TRIGGER

BASIC COURSE OF EVENTS

• The new product is created in the system of record. The product is named, attributes are added (such recipe items in the example of Boss

Burger, One White Bun, Chicken Patty, Tomato, Mayo, etc.).

• The system must be live and connected to the edge points to share menu updates. The system must be able to connect to the edge at any point of time to trigger the change in the menu.

• The item creation and associated actions such as time and date.

• The menu publisher will add a new item to the system, tag a date and time for when it’s live, add any attributes; the restaurant(s), channel(s), images. Based on the criteria, the system will push the changes.

POST-CONDITIONS

• The updates to the edge are received, the application level adds, edits and publishes on the edge. This step may include manual intervention.

EXCEPTION PATH

• The precondition is not met of connection at the event time. A pull request generated from the edge to receive all updates or full menu for that date and time.

ALTERNATIVE PATHS • Complete menu pull request from the edge to the system of record.

Message Flows

MENU SETUP

User

User

1: createItem() 2. setPrices() 3: addDetails() 4: mapItemToMenu() 5: mapItemToBrandsAndSites() 6: mapItemToCalendarClock() 7: publishItem() : menuPublisher

8: newItem() : menuSubscriber

1: createItem() 2. setPrices() 3: addDetails() 4: mapItemToMenu() 5: mapItemToBrandsAndSites() 6: mapItemToCalendarClock() 7: publishItem() : menuPublisher : menuSubscriber