pic of fridge
cyberfridge

Project Schedule

Version 3.1

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
0.3
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
  
 
 
 
    
Designing 
2.1
    
 
 
      
2.2
    
 
 
      
 Implementation I 
3.1
    
 
 
 
 
  
3.2
      
 
  
3.3
3.4
3.5
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
            
 
4.4
4.5
4.6
4.7
Documentation/Milestones 
5.1
             
5.2
             
5.3
  
         
5.4
    
       
5.5
    
 
      
5.7
          
 
5.8
            
5.9
            
5.10
5.11
            
 Planning/Setup
7.2
  
           
7.3
                
7.5
  
 
 
 
 
 
  
7.6
      
 
 
 
 
 Revision/Implementation II 
8.1
          
   
8.2
            
8.3
 

Task Lists 


General  Activities

Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
0.1 Weekly group meetings 
( by Manager) 		 Meetings to discuss progress from previous week and planning for the following week. 
25
40
0.2 Customer communication 
( by Manager) 		 Meetings with customer to discuss progress made regarding the project. 
20
14
0.3 Weekly Status Meeting 
( by Manager ) 		 Meet with Prof. Abowd to discuss progress made in the 
previous week and discuss plans for the following week. 
25
16
Learning
Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
1.1 Finding existing resources 
( by Manager ) 		 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 
( by Architect ) 		 Identify, locate and install necessary software. 
Pre-Cond: Determine what software is necessary. 
Post-Cond: Acquisition of all necessary software. 
5
5
1.3 Learn the environment as whole 
( by Programmer ) 		 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
32
1.4 Learn to program in Java 
( by Programmer ) 		 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
10
Designing 
Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
2.1 Define object attributes and methods 
( by Architect ) 		 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
20
2.2 User Interface design 
( by Architect ) 		 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
20
Implementation I 
Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
3.1 Generate programming schedule 
( by Architect ) 		 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
4
3.2 Food Inventory Programming 
( by Programmer ) 		 See Functional Requirement I. in the Requirements Doc.
15
22
3.3 Recipe Database Programming 
( by Programmer )		 See Functional Requirement II in the Requirements Doc.
15
10
3.4 Recipe Search Programming 
( by Programmer )		 See Functional Requirement III in the Requirements Doc.
30
-
3.5 Remote Access Programming 
( by Programmer )		 See Functional Requirement III in the Requirements Doc.
15
24
Usability
Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
4.1 Define testing for objects 
( by Quality Assurance ) 		 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
8
4.2 Test Food Inventory 
( by Quality Assurance ) 		 See Test 1 in Testing Doc.
5
5
4.3 Test Recipe Database 
( by Quality Assurance ) 		 See Test 2 in Testing Doc.
5
5
4.4 Test Recipe Search 
( by Quality Assurance ) 		 See Test 3 in Testing Doc.
10
-
4.5 Test Remote Access 
( by Quality Assurance ) 		 See Test 4 in Testing Doc.
10
15
4.6 Test User Friendly Interface 
( by Quality Assurance )		 See Test 5 in Testing Doc.
5
-
4.7 Test System Speed 
( by Quality Assurance )		 See Test 6 in Testing Doc.
1
1

Documentation/Milestones 

Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
5.1 Project Teams 
( by Manager ) 		 Project teams are finalized and topics chosen. 
Pre-Cond: None. 
Post-Cond: Project Team ready to begin. 
1
1
5.2 Project Plan 
( by 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. 
Pre-Cond: Project Team Formed (5.1). 
Post-Cond: Begin planning for Requirement Document (5.3). 
20
18
5.3 Requirements Document 
( by Technical Writer ) 		 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
20
5.4 Test Plan 
( by Quality Assurance ) 		 This document describes how the software product will be tested and includes a section to be filled in later on test results. 
Pre-Cond: Requirements Doc. Written (5.3). 
Post-Cond: Begin planning Design Document (5.5). 
15
15
5.5 Design Document 
( by Architect ) 		 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
25
5.7 Final prototype 
( by Programmer ) 		 There will be two opportunities to present pieces of your software product. The first will be an initial demo to show what work you have done to create a software artifact. The final opportunity will be 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. 
Pre-Cond: Testing of Implementation I is complete (4.2). 
Post-Cond: Prototype is ready. 
12
15
5.8 Final Presentation 
( by Manager ) 		 A brief (10 minute) presentation to discuss your progress over the quarter in front of the whole class. 
Pre-Cond: Implementation Testing II complete (4.3). 
Post-Cond: None. 
15
12
5.9 Project Notebook Due 
( by Technical Writer ) 		 A final collection of information in a well-organized Web page. Any revisions of documents must be clearly displayed and all documents and source code must be accessible. 
Pre-Cond: Final Presentation ready. (5.8). 
Post-Cond: None. 
2
10
5.10 Web Site Development 
( by Technical Writer ) 		 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
18
5.11 User Manual 
( by Programmer ) 		 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
3

Planning/Setup

Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
7.2 Implementation I Plan 
( by Programmer ) 		 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
3
7.3 Revision/Implementation II Plan 
( by Programmer ) 		 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.5 Creation of Directory Hierarchy 
( by Technical Writer ) 		 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
2.5
7.6 Identify high risks areas 
( by Architect ) 		 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
8
Revision/Implementation II 
Name of Activity 
(primary responsiblity of) 		 Activity Discription 
Hours Scheduled: 
Actual Hours Completed: 
8.1 Revision based on the Usability Test data 
( by Quality Assurance ) 		 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 
( by Programmer ) 		 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
-
8.3 Document Revisions 
( by Technical Writer ) 		 Modify any documents where editing is needed. 
15
22

Revision History:

Version 3.1

    Date: 6/5/97.
    Names: Whole Team
    Description of Revisions:
        1) Updated hours and visual diagram to reflect final hours.

Version 3.0

    Date: 5/16/97.
    Names: Jeff Corn, Kesniel Acton, Travis Works, Dinesh Krishna
    Description of Revisions:
        1) Note: Times only updated through week 6
        2) Replaced tasks 3.2,4.2,4.3
        3) Added tasks 3.3-3.5, 4.4-4.7. These tasks and the replaced tasks are scheduling for programming and testing, based off the                 requirements doc and the testing plan.

Version 2.6

    Date: 5/15/97.
    Names: Jeff Corn, Kesniel Acton
    Description of revisions:
        1) Updated hours of tasks to reflect final week 6 tally
        2) Deleted task 5.6 (conf management plan)

Version 2.5

    Date: 5/8/97.
    Names: Jeff Corn (Mgr), Kesniel Acton (Tech Writer)
    Description of revisions:
        1) Removed Tasks 1.5, 6.2, 7.1, 7.4
        2) Moved task 6.1 to task 0.3
        3) Updated hours of each task.
        4) Updated status of each task.
    Note: There are no more 6.x tasks.

Version 2.00

    Date: 4/30/97
    Names: Jeff Corn (Mgr), Kesniel Acton (Tech Writer)
    Discription of revisions:
        1) Added the General Activities to our pictorial graph.  These were not previously include. (task 0.1 & 0.2)
        2) Revised the Project Schedule to reflect the milestones in a better fashion.  Explained each one.
        3) Added task (8.3) to our Project Schedule.  We needed time for the revision of our documents.  I defined this task
         in the schedule and showed time for it.
        4) Revised the project plan schedule to reflect which team member was assigned to what activity.
        5) Updated tasks that have started and been compeleted so they reflect properly in the schedule.

Version 1.01 .

   Date: 4/27/97
   Name: Kesniel Acton (Tech Writer)
   Description of revision:
        1) Reorganized tables so they lined up properly.
        2) Added proper name mailing links and logo at top of page.
        3) Made task list section titles appear in white instead of black.

Version 1.0 created 4/18/97. (everybody)