Use Cases

USE CASE #1: Advanced Search

Actors : Any user, Meal Database System

Description : Any user can search for meals by keywords and some filtering options such as included/excluded ingredients, diets and ranges for calorie, protein, carbohydrate and fat amounts. If user is registered before his/her default preferences for diet and ingredients shall be selected on search form.

Stimulus : Search Request (keywords,ingredient options, diet selection, ranges for calorie, protein,carbohydrate and fat)

Response : Direct Results(Meals that fits search options), Semantically related results(Meals that don't fit search options but having same tags with direct results).

Comments : Results must contain only some of meal information like id, name, calorie amount.

USE CASE #2: Add Meal

Actors : Food Server, Meal Database System

Description : Food server can add new meal to the system. New meal is created by selecting ingredients with their amounts. The system calculates calories, protein, carbohydrate and fat amounts of the meal from ingredients.

Stimulus : Add Request (ingredients with amounts, tags)

Response : Confirmation(id of new meal)

Comments : While adding a meal, if food server can not find all of ingredients, state of meal adding form must be saved and user shall be directed to ingredient adding page. When user is done with ingredients, he/she must be directed back to meal adding page with previously saved state.

USE CASE #3

LOGIN :

Description : This Use case describes how registered user get login into the system.
Actors : Any user
Goal : The registered user logs in to authenticate his or her role in the system.
Precondition : A user account has been created for the user before.

Postconditions :

• If email and password both entered correct, user will be logged in to the system, and can access his or her profile.
• If any of email or password doesn't match, user will be notified that entered email or password is wrong and system state us unchanged.