| |
|
| |
Introduction |
This report is intended to present a detailed design document for "Meal plan system" renamed for project "What can I make for dinner?" The purpose of this report is to provide a specific but concise design for the development team to carry on prototype implementation. Therefore, the report is broken down to four Parts:
I. Requirements Review
II. System Overview
III. Menu System
IV. System Functionalities
back to top
|
| |
Main Functions |
To simplify what the meal plan system main functions are, it is a home-use based program that mainly does two basic things:
1. Keep track of home grocery supply
2. Meal recipe recommendation
back to top
|
| |
Users |
Intended users can be stakeholders or part of them, they can be people who make the food, eat the food, do the grocery shopping, etc. But to conclude, users are people who can take advantages of "meal plan system" to satisfy their needs.
back to top
|
| |
Usability Goals |
Usability goals are the functionalities "Meal plan system" will have in the end. To summarize all the main functionalities of the system, they are listed as follows (more detailed sub-features will be covered):
1. Multiple user profile
2. Ingredients Input/Browse/Low Quantity Warning
3. Meal recipe Input/Modify/Display/Recommend
4. Meal recipe basic search
5. Meal recipe advance search
6. Recipe preference settings
7. Search history
8. System recovery
back to top
|
| |
User Experience Goals |
User experience goals are those non-functionality requirements that need to be paid attention to in order to implement "Meal plan system" in a user-friendly interface and user-efficient environment:
1. Organized, consistent program layout
2. Clarified, meaningful textual/ imagic menus, icons, buttons.
back to top
|
|