Example Project - Budget Recipe Shopping ListEdit
Write a short description of what your smart phone application will do. This example is for creating and managing shopping lists for specific recipes that also tracks how much you have budgeted and spent on your shopping. Users will be able to create any number of recipe shopping lists and mark off when the lists or items on the list have been purchased or if they already have the item. They can also compare what they expected to spend and actually spent while shopping.
Budget Recipe Shopping List - TerminologyEdit
This section will list the terminology specific to this project that will help readers unterstand the goal of the project and the data it users or displays. This application works with recipes and shopping lists so we will describe them below.
|Recipe||A list of items that go into a recipe including a name, quantity and estimated cost. Each ingredient will also be flagged with whether or not you have it in your pantry. Each recipe will also have a type such as Snack, Entree, Desert, etc.|
|Meal Recipe List||A list of the recipes you would like to make. The user might have dozens of recipes and select a couple of apetizers, a main course and a desert to add to their active Shopping List.|
|Shopping List||All of the ingredients from the selected Recipes that the user hasn't flagged that they already have. When ever a new recipe is added to the Meals list, all of the ingredients not flagged as in the pantry are added to this list. As items are purchased the user will flag these items which will remove the m from the list and mark them as in the Pantry.|
Budget Recipe Shopping List - Use CasesEdit
Here we will list the 'Use Cases' for the application you plan to build. Each 'Use Case' will explain the steps the user will go through in your app to complete a task. Use cases are used in software engineering to describe the functionality of an application in an easy to understand way for users and testers. Each use case is a sequence of steps where the user takes an action and the application responds to that action. Everything you plan to have the application do should be listed in a use case, including opening the application. When working on your user interface design you can reference the use cases to keep track of which features you have completed and which you still need to do. Use Cases are a helpful way to design your application as they force you to think of how to break down a project into smaller features you can develop one at a time.
|Use Case Name||Steps|
|Open the Budget Recipe Shopping List application||
|Create a new Recipe Shopping list||
|Add an item to the Recipe shopping list||
|Add a recipe to your shopping list||
|Check off an item that has been purchased||
Budget Recipe Shopping List - User Interface MockupsEdit
This section will include mock ups of the UI that will be built while implementing the app. The mockups can be drawn in Paint or taken from screenshots of the UI in Android Studio.
|Main Shopping List View|
Budget Recipe Shopping List - Open ItemsEdit
This section will be a list of items that you still need to figure out or have questions about. When you come across soething that you don't know how to do or an error that you are running across, capture it here so others can see and maybe help out.
|Want to be able to text a contact the shopping list||Not sure how to generate a text message to be sent to one of you contacts so they can help you shop for your grocery list.|