Soup-Project_part1x - Csel Cs Colorado

hundredcarriageSoftware and s/w Development

Nov 3, 2013 (3 years and 5 months ago)

62 views




The
Kitch
-
Tech 3000










Team Soup

Robert Stimpfling

George McCabe

William Scott Hanes

John Martin














Introduction:


Hi, John Martin here for the
Kitch
-
Tech 3000
.
The
Kitch
-
Tech 3000

is a revolutionary
new program that will

help

your
family manage its food and meals. Never again will you be stuck without an answer to the question: What can I make
for dinner tonight with the ingredients

I have?

The
Kitch
-
Tech 3000

will aid you in keeping an inventory of current
food supply along
with information such as amount and expiration date. You will be notified by
Kitch
-
Tech 3000
,
through the easy to use graphical interface, when items spoil or you run out of key h
ouse
-
hold items such as milk or

bread. The
Kitch
-
Tech 3000

is also equipped t
o store user defined recipes and allow you to browse through them. If
you’re wondering if you have the necessary ingredients to make a meal, the
Kitch
-
Tech 3000

will let you know if you
have enough, and if not, exactly what you’re missing. Sometimes you’ll

just want to know what you can make right
now with what you have

and the
Kitch
-
Tech 3000

will let you know. The
Kitch
-
Tech 3000

also provides support for
parent and child privileges. Get your
Kitch
-
Tech 3000

today!




Feature List:


1.

We have to be able
represent a kitchen inventory.

2.

We have to be able to store
recipes.

3.

We have to be able to query the system for useful information.


More Specific Feature list:

1.

Easy to use

GUI in Java swing.

2.

Support at least a child and parent user with different
privileges.

3.

Be able to store an inventory of the current food in your kitchen including amounts and
expiration dates.

4.

Be able to update the inventory after you use an item.

5.

Be able to store user defined recipes.

6.

Be able to query and find out if you have th
e ingredients necessary to make a certain recipe, and
if not what items do you need.

7.

Be able to query and find out what recipes you could make with the current items in your
kitchen.

8.

Be notified when items expire or your run out of key items



Use Case
Diagram:
























Child


Parent

Add food item

Modify Amount of food
item

Add Recipe

Browse
all r
ecipes

What items do we need
to make a specified
recipe?

What recipes can be made
with what’s in the kitchen

Browse
all food

We have to be able to represent a kitchen inventory.

We have to be able to query the system for useful information.


We have to be able to store recipes
.


Module Breakdown:

1.

Inventory


contains list of all ingredients owned and recipes known.

a.

We decided to use a single inventory to containing recipes and
ingredients so that we can easily access the ingredient list when
querying the recipe list for possible recipes.


2.

Viewer


Displays recipes and ingredients

a.

This module is necessary to view the recipes so that the users can
use them to cook.


3.

Loader


gets files containing ingredient list and recipe list and loads
them into the inventory (either done through a database or a file, we
haven’t decided which will be better yet)


4.

Database/File


used for long term storage of inventory and recipes.


a.

This is necessary so that when the system is shut down, the
information gathered is not lost. It would be very tedious to re
-
enter recipes every time you used the system. Storing this
information in a file/database make use of the system much easier
for

the user.

















Architecture Diagram
: