Project Plan

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)

I. Schedule

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 as well as those items which are not, but are needed to perform a particular meal recipe. Our refrigerator will primarily serve the purpose of electronically making a shopping list and telling to its user the items which are lacking for a certain recipe and those items which currently reside in the fridge. Thus using some type of system to notify the user that a certain meal is not an option at the moment due to the lack of the necessary ingredients or even because of the expiration of those ingredients.
Our Cyberfridge will therefore cross index the current inventory of the fridge and a recipe database in order to suggest what meals to make and what ingredients are to be bought( i.e. our grocery list). 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 record the more popular dishes selected previously, which are determined by the number of times a certain dish is requested in relation to other dishes. Our database can also be updated to add new recipes at the user's discretion.

III. Related Documents

Right now our only main link is to the domisilica web page. It should give a general idea of where our project fits in.

IV. Project Roles

Project Manager	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	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	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	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	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.

V. Deliverables

Project Plan

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.

Requirements Document

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.

Test plan

Due: 5/5
Principal Responsibility of: Quality Assurance

This document describes how the software product will be tested and includes a section to be filled in later on test results.

Design Document

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.

Configuration Management Plan

Due: 5/19
Principal Responsibility of: Quality Assurance

A description of the procedures to be followed by the team to provide for version control and other configuration management concerns for the whole project (structure of source code directories, documentation, procedures for checking out source code, tools used to support these activities).

Early demo and Final prototype

    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.

Final presentation

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.

Final project notebook due

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.

VI. Document Revision History
Version 1.0 - 4/18/97.