-- BnuttinG - 03 Mar 2004

Here is a list of the requirements we translated from the customer...

-Multiple-users
-Add a user
-Edit a user
-Remove a user
-Edit a users email
-Calendar feature for 1 week
-Weekly Shopping List
-Add an item to buy
-Set what day is grocery day
-Sticky Grocery Items
-Ability to change Recipes
-Add a recipe
-Must be able to parse XML
-Edit remote repository URL
-Edit a remote recipe and save it under a new name locally
*Donít store all items locally OR on server. Only get what u need
-Linux and windows compatible for server
-Multiple browsers for client
-Add a time when I will cook something (bring up a search on all recipes, then after you choose one, pick a time, then add it to the calendar) (can be recurring)
-Plan for one meal per day or none

We decided to make use case diagrams out of the 3 major user-interface tracks...
-Recipe Management
-User Management
-Adding a meal to Cook

We decided on the following jobs...

Add meal Use case - Dan
user management use case -
recipe management use case -
formalizing requirements list and finalizing document - Ben
presenting - mark

We decided to meat weekly on thursdays at 5:30 in the library.

I think it would be a good Idea to have all of our pieces ready for this thursdays meeting and to go over it.

Topic revision: r2 - 2004-03-03 - BnuttinG
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UMass CS EdLab? Send feedback

mersin escort adana escort izmir escort gaziantep escort