Spring Quarter 1997:Project Sponsor: Gregory Abowd |
Project Team:Jeffrey Corn (Manager) Travis Works (Architect) John Garrard (Programmer) Kesniel Acton (Technical Writer) Dinesh Krishna (Quality Assurance) |
To see a copy of the schedule click here.
II. Project Description
The CyberFridge project is to use Internet connectivity, vision and mechanical systems to create an intelligent and productive refrigerator. Many of our daily tasks revolve around the refrigerator, and a CyberFridge would allow the automation of many of these routine tasks. Our project is a specific subset of this area which will allow you to use a recipe system on the refrigerator to determine food items which are currently in the refrigerator. Our refrigerator will primarily serve the purpose of electronically making a shopping list based off of a recipe by telling which items are not currently in the fridge. Thus using a database of recipes and some simply searches the user can be notified about certain meals which are not an option at the moment due to the lack of the necessary ingredients. Our Cyberfridge will use a food inventory of the fridge against a recipe database in order to suggest what meals to make as well as those ingredients needed (grocery list) for other receipts. The recipe database will essentially have recipes of specific types of dishes (ex. Chinese, Italian, etc.) which the family living in the home would like to eat. The database will also keep track of the more popular dishes that are based off of previously selection. Our database can also be updated to add new recipes at the user's discretion.
Right now our only main link is to the domisilica web page. It should give a general idea of where our project fits in.
| Project Manager:
Jeffrey Corn |
1. Track Progress -- Make sure the tasks are getting
done according to schedule.
2. Schedule Meetings -- Group Communication. 3. Interacts for the Customer for various reasons. |
| Architect:
Travis Works |
1. Generates the Design Document.
2. Creates overall design of objects and their specification for the use of programmer. 3. Maintains the overview of the entire development stages of the product, and what the final product will be. |
| Technical Writer: Kesniel Acton | 1. Modifies and maintains the Web pages for the project.
2. Writes up the Requirement Document. 3. Overviews any document that develops during the project. |
| Programmer:
John Garrard |
1. Learns any Programming Environments need for the project.
2. Develops and Maintains any source code. 3. Works closely with the architect in developing the customer product. |
| Quality Assurance: Dinesh Krishna | 1. Tests the functionality defined by the requirements.
2. Tests the usability for the customer satisfaction. 3. Develops the Configuration Management Plan. 4. Reports information to the architect and programmer. |
Due: 4/18
Principal Responsibility of: Manager
A document introducing the project topic, team members and providing a schedule for activities to be performed during the quarter. This schedule will be the basis for monitoring progress throughout the quarter.
Due: 4/28
Principal Responsibility of: Technical Writer
An extended document that details all functional requirements of the
delivered prototype. A section of this document also indicates nonfunctional
requirements that will be used to test the system for acceptability and
a storyboard will be used (and potentially presented to the class) to demonstrate
how the system will look and be used.
This document describes how the software product will be tested and includes a section to be filled in later on test results.
Due: 5/16
Principal Responsibility of: Architect
A detailed description of how the system will be built, including, for example, a high-level software architecture and any component interfaces or interfaces object-oriented analysis and design to show the system structure.
Initial Demos: Week 7
Final prototype due: 5/30
Principal Responsibility of: Programmer
A demonstration of the final running prototype of the system that is to be demonstrated to the instructor and intended to meet all aspects of the revised requirements document. Part of the exercise in grading the final prototype will be the installation of the software system by the TA or instructor, with the aid of the Programmer. To assist this process, the team will have to produce an installation manual and brief user's guide.
Due: Week 10
Principal Responsibility of: Manager
A brief (10 minute) presentation to discuss your progress over the quarter in front of the whole class.
Due:end of quarter
A final collection of all of the above information in a well-organized Web page. Any revisions of documents must be clearly displayed and all documents and source code must be accessible.
Most of this info is from the project milestones page, off
the main cs3302 page.
Version 1.0 - 4/18/97. (everybody)