Use Cases

Use Case #1

Name: Create food page

Actors: Server

Description: Food server may add food by creating a new food page.

Preconditions:

• To be logged in.
• To have a restaurant page.

Data: Information about the food and its image

Stimulus: Server clicks the button “Add Food”

Steps:

• Server clicks “Add Food”.
• Servers fills the information below about the food.
  1. allergen info
  2. diet info
  3. organic info
  4. cuisine info
  5. ingredients
• Server adds an image of the food.
• Server clicks “Add” button.

Postconditions:

• Calories, macronutrient and micronutrient values are calculated according to ingredients by the system.
• Food page is created.
• Restaurant page is updated. Food is added.
• Database is updated.
• Server is directed to the his/her profile page.

Response: Confirmation that food page is created and restaurant page is updated successfully.

Comments: Nutrition values and calories are seen in the food page.

Use Case #2

Name: View profile

Actors: Registered User (Regular User)

Description: User may see his/her profile page.

Preconditions:

• To be logged in.

Data: User’s information and history.

Stimulus: User clicks the button “Me”

Steps:

• User clicks “Me”.
• User sees the following sections:
  1. daily calorie consumption
  2. recommendations
  3. consumption history
  4. comment history
  5. rating history
  6. lists
• User may do the following actions:
  1. create new food list
  2. create new server list
  3. add food to “favorites”
  4. save search criteria

Postconditions:

• Database is updated if user does an action.
• Profile page is reloaded.

Response: Confirmation that profile is updated successfully if any change is done.

Use Case #3

Name: Manual Search

Actors: Registered User (Regular User) and Guest

Description: Food search may be done with filtering and sorting options.

Preconditions: -

Data: Search criteria and Foods

Stimulus: User clicks the button “Search”

Steps:

• User clicks “Search”.
• Search screen is opened.
• User may search a food with its name.
• User sees the following filters:
  1. servers
  2. working hours
  3. payment options
  4. diet preferences
  5. cuisine
  6. allergic ingredients
• User may sort the result in terms of:
  1. alphabetical order
  2. ratings
• User clicks “Search”.

Postconditions:

• Database is searched.
• All related results are provided.

Response: Foods are lined up according to the search criteria.

Comments:

• Calories and nutrition values are seen next to the food.
• For further information about the food, food may be clicked and the user will be directed to the food page.
• For detailed information about the server, server may be clicked and the user will be directed to the restaurant page.
• Regular user may label the food or the server as “Tasted it”, view comments, make comments, rank according to different criteria and agree or disagree with the other user’s comments.