Module 1 Guided Project

Lunch Ordering Service Overview

BloomTech has decided that lunch is a new benefit of the Backend Development program, with the one condition that we build a service to manage the orders.

The instructor team has been busy building the first part of the service. There is an API (just a fancy way of saying a set of methods) to create a new lunch order, and to retrieve a lunch order once it has been created. The lunch orders will be persisted in a database and we will retrieve all RECEIVED orders at 11:30 am each day and execute the orders so lunch will arrive around noon.

Creating an Order

To create an order a user must send a create request to the order API with the following information: who is ordering the lunch, the id of the restaurant to order from, and the menu item to order. Below is an example of request data necessary to create a lunch order from Ba Bar.

{
  "customerName": "Ada",
  "restaurantId": "21a70111-52ba-4c81-b4d8-ded39f48808f",
  "menuItem": "Coconut Curry with Chicken"
}
                

Using Use Cases for Testing

For any software system, we need to identify:

• The preconditions that must be true before we can use the system
• The invariants that shouldn't change during the use of the system
• The postconditions that should be true after we use the system
• The steps that a user would take while using the system

In our Lunch Ordering Service, we'll need to formally document the use cases for both creating a new order and retrieving an existing order, and then execute tests to verify the system behaves according to our use cases.