pic of fridge 
cyberfridge 

Project Schedule

Version 1.01


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) 



General Activities  
Actvities  Week 3 
4/13 - 4/19  		Week 4 
4/20 - 4/26  		Week 5 
4/27 - 5/3  		Week 6 
5/4 - 5/10  		Week 7 
5/11 - 5/17  		Week 8 
5/18 - 5/24  		Week 9 
5/25 - 5/31  		Week 10 
6/1 - 6/7 
0.1                 
0.2


Learning
Actvities  Week 3 
4/13 - 4/19  		Week 4 
4/20 - 4/26  		Week 5 
4/27 - 5/3  		Week 6 
5/4 - 5/10  		Week 7 
5/11 - 5/17  		Week 8 
5/18 - 5/24  		Week 9 
5/25 - 5/31  		Week 10 
6/1 - 6/7 
1.1   
1.2
1.3
1.4
1.5

Designing  
2.1
2.2

 Implementation I  
3.1
3.2

 Usability  
Actvities  Week 3 
4/13 - 4/19  		Week 4 
4/20 - 4/26  		Week 5 
4/27 - 5/3  		Week 6 
5/4 - 5/10  		Week 7 
5/11 - 5/17  		Week 8 
5/18 - 5/24  		Week 9 
5/25 - 5/31  		Week 10 
6/1 - 6/7 
4.1
4.2
4.3

Documentation/Milestones 
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11

 Presenation  
Actvities  Week 3 
4/13 - 4/19  		Week 4 
4/20 - 4/26  		Week 5 
4/27 - 5/3  		Week 6 
5/4 - 5/10  		Week 7 
5/11 - 5/17  		Week 8 
5/18 - 5/24  		Week 9 
5/25 - 5/31  		Week 10 
6/1 - 6/7 
6.1
6.2

 Planning/Setup 
7.1
7.2
7.3
7.4
7.5
7.6

 Revision/Implementation II  
8.1
8.2
8.3




Task Lists  


General  Activities 
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
0.1 Weekly group meetings  Meetings to discuss progress from previous week and planning for the following week. 
25
1
0.2 Customer communication  Meetings with customer to discuss progress made regarding the project. 
20
2


Learning 
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
1.1 Finding existing resources  Locating projects from previous groups and resources which can be used in the implementation of the project. 
Post-Cond: Located pre-existing resources 
20
10
1.2 Acquire software for development  Identify, locate and install necessary software. 
Pre-Cond:  Determine what software is necessary. 
Post-Cond: Acquisition of all necessary software. 
5
-
1.3 Learn the environment as whole  Identify and become familiar with all environments in which we will be developing the project. 
Pre-Cond:  Determine what environments will be used 
Post-Cond: Familiarity with all working environments 
20
-
1.4 Learn to program in Java  Obtain and study programming manuals, examine existing code, and gain a working knowledge of the language. 
Pre-Cond:  Familiarity with environments (1.3) 
Post-Cond: Enough knowledge for programming (3.2) 
30
-
1.5 Learn LambaMoo  Obtain and study programming manuals, examine existing code, and gain a working knowledge of the language. 
Pre-Cond:  Familiarity with environments (1.3) 
Post-Cond: Enough knowledge for programming (3.2) 
20
-


Designing  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
2.1 Define object attributes and methods  Identify the internal data and data structures for each object, and define all procedure used to manipulate the objects. 
Pre-Cond:  Finished Design Document (5.3) 
Post-Cond: Ready for implementation (3.0) 
15
-
2.2 User Interface design   Determine the features and attributes of the interface to develop a good human interaction system. 
Pre-Cond:  Get requirements from Customer Communication (0.2) 
Post-Cond: Detailed design ready for programming (3.2) 
25
-


Implementation I  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
3.1 Generate programming schedule  Divide programming into sub-programs, schedule the programmer, order of programming and testing each sub-program. 
Pre-Cond:  Finished Design Documentation (5.3) 
Post-Cond: Schedule ready for Programming (3.2) 
5
-
3.2 Programming  Generate code for each sub-program according to the programming schedule. 
Pre-Cond:  Finished Programming Schedule (3.1) and learning (1.3)-(1.5) 
Post-Cond: Code ready for Usability Testing (4.2) 
75
-


Usability  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
4.1 Define testing for objects  Determine which features of the project need to be tested, and define criteria for each of these features. 
Pre-Cond:  Finished Requirements Document 
Post-Cond: Criteria ready for Usability Testing (4.2) & (4.3) 
12
-
4.2 Test the implementation I  Apply the testing criteria to each of the features of the implementation, and determine which features need to be revised to meet these criteria. 
Pre-Cond:  Finished Programming (3.2) 
Post-Cond: Testing data ready for (8.1) 
10
-
4.3 Test the implementation II  Apply the testing criteria to each of the features of the implementation, and verify that the project satisfies all of these criteria. 
Pre-Cond:  Finished Programming (8.2) 
Post-Cond: Program ready for final presentation 
10
-


Documentation  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
5.1 Requirements Document  Determine all requirements set by the customer for the implementation of the project. 
Pre-Cond:  Get requirements from Customer Communication (0.2) 
Post-Cond: Requirements ready for development of 
Design Document (5.3) 
15
-
5.2 Web Site Development  Design and implement the web site for the project, and update the web site to stay up-to-date with all developments in the project. 
13
6
5.3 Design Document  Determine the design of the program, including all data structures, relationships, and  major procedures. 
Pre-Cond:  Finished Requirements Document (5.1) 
Post-Cond: Design Document ready for submission 
15
-
5.4 Configuration Management Plan  Prepare version control system and communication line 
between the different versions and the members working on each version. 
Post-Cond: CMP ready for Implementation (3.0) 
12
-
5.5 User Manual  Prepare a manual explaining the purpose of the system and how it can be used by the customer. 
Pre-Cond:  Finished Requirements Document (5.1) 
and Design Document (5.3) 
Post-Cond: User Manual ready for final presentation 
20
-


Presentation 
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
6.1 Weekly Status Meeting  Meet with Prof. Abowd to discuss progress made in the 
previous week and discuss plans for the following week. 
25
-
6.2 Final Presentation  Prepare and present the finished project to the customer, 
along with all documentation. 
Pre-Cond: Finished Code Revision (8.2), 
 Final Usability Testing (8.3), and final revisions of all documentation (5.1) - (5.5) 
25
-


Planning/Setup  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
7.1 Project Plan  Determine which activities are necessary to complete the project, and in which order these activities should be accomplished. 
Post-Cond: Plan ready for scheduling 
12
12
7.2 Implementation I Plan   Plan the steps necessary to complete the first implementation of the project. 
Pre-Cond:  Finished Design Document (5.3) 
Post-Cond: Plan ready for Implementation (3.0) 
6
-
7.3 Revision/Implementation II Plan  Plan the steps necessary to revise the program in the time allowed. 
Pre-Cond:  Finished Usability Testing (4.2) 
Post-Cond: Plan ready for Implementation (8.0) 
6
-
7.4 Testing Plan  Design a plan for testing the implementation against the testing criteria. 
Pre-Cond:  Finished Requirements Document (5.1) 
Post-Cond: Ready for Usability Testing (4.2)-(4.3) 
5
-
7.5 Creation of Directory Hierarchy  Set up all necessary directories to meet the Configuration Management Plan, and verify that all files are in the proper locations. 
Pre-Cond:  Finished Configuration Management Plan (5.4) 
Post-Cond: Directories ready for Implementation (3.0) 
1
-
7.6 Identify high risks areas  Determine which areas of the implementation will be most prone to error, and what can be done to minimize the risks. 
Pre-Cond:  Finished Design Documentation (5.3) and Learning (1.3)-(1.5) 
Post-Cond: Ready for Programming Schedule (3.1) 
6
-


Revision/Implementation II  
Name of Activity  Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
 8.1 Revision based on the Usability Test data  Determine what revisions are necessary for the project to satisfy all testing criteria, and which of these revisions are feasible in the time allowed. 
Pre-Cond:  Finished Usability Testing from (4.2) 
Post-Cond: Requirements ready for modification in (8.2) 
15
-
8.2 Modification of code  Modify the source code of the program to implement all revisions which are determined necessary. 
Pre-Cond:  Finished revisions in (8.1) 
Post-Cond: Code ready for final testing 
30
-


Created 4/18/97. 
Version 1.01 4/27/97. Last Modifed 4/27/97.