CS 481 - Team 49
Presentation 2 Minutes
 
Presentation 2 Meeting
Wednesday, October 31, 2007
10:30 - 11:30 AM
JEB 324
Recorder: Peter Brown-Hayes
--------------------------------
 
Summary: This meeting consisted of a presentation and discussion of the 
features and defects present in release 2, the upcoming release, and the requirements 
for the final product.
 
Attendees
     Brandon Riggers, Peter Brown-Hayes, Travis Thoroman, Shruti Upadhyaya,
Bill Junk, Bruce Mayes (over the phone).
 
 
Topics discussed:
 
The presentation started off the presentation by discussing the different 
topics within the release2 powerpoint presentation.  Each of the topics 
that were discussed in detail are listed below:
- Project Overview
  -- Run_turmoil tool
  -- Specific filelist
  -- Metrics Engine
- Release 2 contents
  -- Files needed for execution
    - SCS
    - run_turmoil (and all associated files)
- Documents
  -- Op-Spec v1.3
  -- Completed Design-Spec v1.0
  -- Exploratory Testing and Test-Spec v1.2
 
At this point, many issues were raised and new decisions were made which 
are listed below:
- We may need to change from checking out the entire 
repository to checking out 2 files at a time, calculate turmoil on them, and then deleting those 
two files before proceeding to the next set of files.
- It was noted that we need to stay on course, and not get off topic. 
Worry most about the run_turmoil command working properly and less about 
turmoilBetweenRevisions.
- It was mentioned that the team needs to sync the presentation slides so 
that all the names and ideas match (i.e. Metrics Caller on one slide, 
should reflect the actual name of the script).
- The topic of testing and performance testing was discussed and made a 
top priority due to the fact that it must be able to complete operation 
within a reasonable amount of time, or it is not useable.
- Discussion around when we need to 'jettison' the idea of 
turmoilBetweenRevisions brought up the idea that we need to meet and set a 
date pending some performance testing.
 
Final Action Items:
- 2 defects need to be handled as soon as possible.
- Performance testing needs to be done to evaluate our current tool.
- A date needs to be set to jettison thoughts of turmoilBetweenRevisions