| Task Description |
Assigned to |
Scheduled Completion Date |
Actual Start Date |
Actual Completion Date |
| Determine time and schedule weekly meetings with your customer and instructor. |
Team |
14 Jan |
14 Jan |
14 Jan |
| Access Unix account and change password. |
Ray |
15 Jan |
10 Jan |
11 Jan |
| Set up Unix account mail to distribute incoming mail to all team members and to archive all in /out mail. |
Nate |
15 Jan |
13 Jan |
13 Jan |
| Hold a team meeting to discuss when each member with be the team leader. Similarly identify the team recorder. Communicate the decision to your instructor. |
Nate |
15 Jan |
10 Jan |
10 Jan |
| Hold team meeting to assign responsibility for individual project tasks. |
Team |
17 Jan |
17 Jan |
17 Jan |
| Hold a team meeting to discuss team values. Document a list of the things you consider to be important to your team. Provide a copy to your instructor and post to your team web site. |
Ray |
17 Jan |
17 Jan |
17 Jan |
| Make initial contact with your customer. Set up meeting to discuss project. |
Robbie |
15 Jan |
14 Jan |
14 Jan |
| Create web site on Unix account to support your project. |
Ray |
21 Jan |
14 Jan |
20 Jan |
| Prepare and distribute (e-mail) agenda for initial instructor meeting. Post agenda to project web site. |
Nate |
14 Jan |
Missed |
Missed |
| Hold initial meeting with instructor to discuss project and development strategy. |
Team |
15 Jan |
15 Jan |
15 Jan |
| Document results (minutes) of initial meeting with instructor. Distribute minutes via e-mail and post to web site. |
Nate |
16 Jan |
15 Jan |
16 Jan |
| Prepare and distribute (e-mail) agenda for customer meeting. Post agenda to project web site. |
Nate |
14 Jan |
Missed |
Missed |
| Prepare Concept Proposal Presentation. Post to team web site and present during customer meeting. |
Curt |
22 Jan |
15 Jan |
22 Jan |
| Hold meeting with customer and instructor to discuss project and identify needs (requirements). |
Team |
15 Jan |
15 Jan |
15 Jan |
| Document results (minutes) of initial meeting with customer. Distribute minutes via e-mail and post to web site. |
Nate |
16 Jan |
15 Jan |
16 Jan |
| Create a 1-2 paragraph project description for your instructor's CS 481 web page. E-mail to your instructor. |
Ray |
22 Jan |
17 Jan |
29 Jan |
| Create initial project schedule showing major milestones and activities. Post to team web site. |
Curt |
22 Jan |
17 Jan |
22 Jan |
| Create initial draft of Legal/Ethical Review document |
Ray |
29 Jan |
24 Jan |
29 Jan |
| Update Vision statement and Values based on Instructor feedback. Post to team web site. |
Curt |
29 Jan |
27 Jan |
27 Jan |
| Establish programming style guidelines. Post to team web site. |
Curt |
29 Jan |
24 Jan |
28 Jan |
| Investigate the possibility of using of svn diff to increase performance. |
Curt |
5 Feb |
2 Feb |
3 Feb |
| Investigate the possibility of using svn list --verbose to determine which files have changed and which to ignore to improve performance. |
Curt |
5 Feb |
2 Feb |
4 Feb |
| Review input from customer then identify and document a comprehensive set of use cases. Distribute via e-mail for customer review and post to project web site. |
Robbie |
24 Jan |
20 Jan |
24 Jan |
| Incorporate customer feedback into use cases. Distribute updated document and post to project web site. |
Robbie |
26 Jan |
24 Jan |
24 Jan |
| Create initial draft of Operational Specification. Distribute for review. Post to team web site. |
Robbie |
29 Jan |
22 Jan |
29 Jan |
| Update Op Spec based on reviewer feedback. Post to web site. |
Robbie |
12 Feb |
5 Feb |
9 Feb |
| Update Legal/Ethical Review document |
Ray |
5 Feb |
1 Feb |
5 Feb |
| Create initial draft of Output specification document |
Ray |
5 Feb |
2 Feb |
5 Feb |
| Create skeleton for Product Test Plan. Author the test strategy section. Distribute for review and post to team web site. |
Nate |
12 Feb |
30 Jan |
12 Feb |
| Update Legal/Ethical Review document |
Ray |
12 Feb |
8 Feb |
9 Feb |
| Update Output specification document |
Ray |
12 Feb |
8 Feb |
9 Feb |
| Determine configuration management strategy and tools to use. Set up CVS repository. |
Nate |
28 Jan |
20 Jan |
22 Jan |
| Develop release plan (major capabilities to deliver in each release). |
Curt |
12 Feb |
8 Feb |
11 Feb |
| Finalize content of first release. |
Curt |
11 Feb |
7 Feb |
11 Feb |
| Design product architecture. |
Ray |
12 Feb |
11 Feb |
11 Feb |
| Document architecture in Design Specification. Distribute for review & post to web site. |
Robbie |
19 Feb |
12 Feb |
17 Feb |
| Find a way to catch an abnormal exit to delete temporary files |
Ray |
19 Feb |
12 Feb |
19 Feb |
| Profile and Benchmark last release |
Nate |
28 jan |
21 Jan |
4 Feb |
| Compile last release into a single source file |
Nate |
28 jan |
21 Jan |
28 Jan |
| Add option to run the tool on single files in run_turmoil |
Curt |
11 Feb |
5 Feb |
8 Feb |
| Fix bug where the tool (after updating to coding guidelines) produces no output. |
Curt |
10 Feb |
9 Feb |
10 Feb |
| Develop regression test harness for first release |
Nate |
11 Feb |
5 Feb |
11 Feb |
| Implement defect log and tracking system. |
PRS |
07 Feb |
07 Feb |
07 Feb |
| Develop formal test cases (test suite) for first release. Document test cases in the Test Plan. |
Nate |
12 Feb |
08 Feb |
11 Feb |
| Perform release testing for release 1. |
Nate |
12 Feb |
11 Feb |
11 Feb |
| Update design spec for first release. Post to team web site. |
Robbie |
14 Feb |
07 Feb |
17 Feb |
| Prepare release presentation for release 1. Post to team web site. |
Ray |
12 Feb |
11 Feb |
12 Feb |
| Prepare & verify release 1 package. |
Curt |
11 Feb |
11 Feb |
11 Feb |
| Ship & post release 1. |
Curt |
11 Feb |
11 Feb |
11 Feb |
| Hold Release Presentation meeting. Distribute and post meeting minutes. |
Robbie |
13 Feb |
12 Feb |
13 Feb |
| Plan the activities for the next release. |
Curt |
19 Feb |
12 Feb |
15 Feb |
| Post "clean" release package on website. |
Curt |
19 Feb |
17 Feb |
17 Feb |
| Add content to the Testing Notes page on the website. |
Nate |
19 Feb |
19 Feb |
19 Feb |
| Merge Use Cases document into Operation Specifications document. |
Robbie |
19 Feb |
17 Feb |
21 Feb |
| Add a more descriptive header to the run_turmoil.pl file. |
Curt |
19 Feb |
17 Feb |
17 Feb |
| Make it easier to specify an alternate diff utility for the tool to use. |
Curt |
19 Feb |
18 Feb |
18 Feb |
| Register the team for the Engineering Design Expo. |
Team |
21 Feb |
20 Feb |
20 Feb |
| Implement cleanup on abnormal exit. |
Ray |
26 Feb |
21 Feb |
24 Feb |
| Decide on a new name for the tool. |
Team |
21 Feb |
21 Feb |
21 Feb |
| Investigate using SVN export to grab lots of files at once. |
Robbie |
21 Feb |
19 Feb |
21 Feb |
| Modify the tool to make it use local files when available to improve performance. |
Robbie |
26 Feb |
19 Feb |
26 Feb |
| Implement log file output. |
Ray |
26 Feb |
24 Feb |
26 Feb |
| Modify the tool to run on a full repository or directory when no filelist is given. |
Curt |
26 Feb |
18 Feb |
18 Feb |
| Find and fix the "File not found" issue |
Team |
26 Feb |
21 Feb |
6 Mar |
| Investigate reason for test harness failure on Bruce's system |
Nate |
26 Feb |
21 Feb |
6 Mar |
| Fix test harness for next release |
Nate |
26 Feb |
26 Feb |
16 Mar |
| Add a set of "Linux-stlye" options (--older-revision... --newer-revision...). |
Robbie |
28 Feb |
22 Feb |
26 Feb |
| Fix problem with log files in single file (-f) mode. |
Robbie |
13 Mar |
06 Mar |
13 Mar |
| Modify the tool to only record certain messages in the log files. Log revision numbers. |
Robbie |
13 Mar |
06 Mar |
13 Mar |
| Clean up code style and formatting for second release. Ensure that comments are accurate. |
Robbie |
17 Mar |
16 Mar |
17 Mar |
| Update design spec for second release. Post to team web site. |
Curt |
17 Mar |
21 Feb |
17 Mar |
| Update operational spec for second release. Post to team web site. |
Curt |
17 Mar |
24 Feb |
17 Mar |
| Prepare release presentation for release 2. Post to team web site. |
Nate |
17 Mar |
14 Mar |
17 Mar |
| Prepare release notes for second release. |
Robbie |
17 Mar |
17 Mar |
17 Mar |
| Prepare & verify release 2 package. |
Curt |
17 Mar |
17 Mar |
17 Mar |
| Ship & post release 2. |
Nate |
17 Mar |
17 Mar |
17 Mar |
| Hold Release Presentation meeting. Distribute and post meeting minutes. |
Curt |
18 Mar |
18 Mar |
18 Mar |
| Profile and benchmark release 2. |
Nate |
20 Mar |
17 Mar |
17 Mar |
| Post defect log to the team website. |
Nate |
25 Mar |
24 Mar |
24 Mar |
| Label the second release in Subversion. |
|
|
|
|
| Plan activities for third release. |
Team |
25 Mar |
20 Mar |
25 Mar |
| Investigate problems aborting the tool in Windows. |
Curt |
1 Apr |
30 Mar |
30 Mar |
| Create initial design for project poster. |
Ray |
1 Apr |
24 Mar |
1 Apr |
| Investigate and fix bug where tool reports too much deletion. |
Curt |
1 Apr |
25 Mar |
30 Mar |
| Fix file not found output |
Curt |
1 Apr |
28 Mar |
28 Mar |
| Implement Code Size Measurement. |
Robbie |
8 Apr |
20 Mar |
18 Mar |
| Implement Selective Downloading. |
Robbie |
8 Apr |
18 Mar |
1 Apr |
| Tweak Command Line Options. |
Robbie |
8 Apr |
18 Mar |
7 Apr |
| Update Test Harness output |
Nate |
7 Apr |
1 Apr |
6 Apr |
| Change Test Harness to include Unit tests |
Nate |
7 Apr |
1 Apr |
6 Apr |
| Check to ensure tool follows coding standards |
Curt |
8 Apr |
6 Apr |
7 Apr |
| Update design spec for third release. Post to team web site. |
Nate |
8 Apr |
1 Apr |
7 Apr |
| Run test suite on release 3 |
Nate |
8 Apr |
5 Apr |
7 Apr |
| Prepare release presentation for release 3. Post to team web site. |
Robbie |
8 Apr |
1 Apr |
7 Apr |
| Prepare release notes for third release. |
Curt |
8 Apr |
7 Apr |
7 Apr |
| Prepare & verify release 3 package. |
Curt |
8 Apr |
7 Apr |
7 Apr |
| Ship & post release 3. |
Nate |
8 Apr |
7 Apr |
7 Apr |
| Hold Release Presentation meeting. Distribute and post meeting minutes. |
Curt |
8 Apr |
8 Apr |
8 Apr |
| Profile and benchmark release 3. |
Nate |
8 Apr |
7 Apr |
7 Apr |
| Post updated defect log to the team website. |
Nate |
8 Apr |
7 Apr |
7 Apr |
| Finalize a digital copy of the poster for design expo |
Ray |
14 Apr |
1 Apr |
13 Apr |
| Print a final poster for design expo |
Ray |
21 Apr |
1 Apr |
23 Apr |
| Laminate final poster for design expo |
Ray |
22 Apr |
1 Apr |
24 Apr |
| Implement separate download algorithms for sparse and dense change. |
Robbie |
15 Apr |
1 Apr |
2 Apr |
| Prepare and verify pre-release package 1 for customer. |
Curt |
2 Apr |
2 Apr |
2 Apr |
| Test pre-release version 1. Log defects. |
Nate |
2 Apr |
2 Apr |
2 Apr |
| Ship pre-release version 1 for customer review. |
Curt |
2 Apr |
2 Apr |
2 Apr |
| Log defects based on customer feedback. |
Robbie |
5 Apr |
5 Apr |
5 Apr |
| Write test spec for final release. Post to team web site. |
Nate |
29 Apr |
29 Apr |
29 Apr |
| Get an initial documentation update checked over |
Ray |
22 Apr |
7 Apr |
22 Apr |
| Update operational spec for final release. Post to team web site. |
Ray |
29 Apr |
7 Apr |
29 Apr |
| Update design spec for final release. Post to team web site. |
Ray |
29 Apr |
7 Apr |
29 Apr |
| Run test suite on final release. |
Nate |
29 Apr |
29 Apr |
29 Apr |
| Write an initial "read me" file |
Ray |
21 Apr |
16 Apr |
21 Apr |
| Update "read me" file based on feedback |
Ray |
29 Apr |
22 Apr |
25 Apr |
| Prepare release presentation for final release. Post to team web site. |
Nate |
29 Apr |
29 Apr |
29 Apr |
| Prepare release notes for final release. |
Curt |
29 Apr |
28 Apr |
29 Apr |
| Prepare & verify final release package. |
Curt |
29 Apr |
28 Apr |
29 Apr |
| Ship & post final release. |
Curt |
29 Apr |
28 Apr |
29 Apr |
| Profile and benchmark final release. |
Nate |
29 Apr |
29 Apr |
29 Apr |
| Post updated defect log to the team website. |
Robbie |
29 Apr |
29 Apr |
29 Apr |
| Hold Final Release Presentation meeting. Distribute and post meeting minutes. |
Ray |
29 Apr |
29 Apr |
30 Apr |
| Create Project Archive CD. |
Ray |
2 May |
2 May |
7 May |
