January 29, 1998

PLACE:          Professor Junk's office
TIME:           2:30 PM
ATTENDEES:      Professor Junk
                James Cooper
                Jamie Marconi
                Sam Gerlach
TOPIC:          Team Status

AGENDA:

Update
------

-James Cooper has been working on the web interface.  This is a priority
        for the Pre-proxy walk through.  It will deal with the
        manager/subordinate configuration.
-We discussed convenient times for the Pre-proxy walk through.  Friday at
        12:30 is taken.  Thursday after 1:30 is open all day.  Professor
        Junk advised us to nail down a time ASAP.  One hour should be
        long enough for the walk through.
-The User's Manual needs some updating, but is well under way.  James
        Cooper is working on this.
-We realized that our README is within our tar file.  Therefor, we need
        a README file for the untar'ing of the product.  Sam Gerlach is
        going to write this.
-Jamie Marconi is working on the auto testing.  It is not yet done, but
        will be available.
-Jamie Marconi has also constructed two man pages to date.
-On the updated checklist we omitted the shar'ing steps and added the
        man pages.  Professor Junk requested that we pretty it up.
-We have not identified any new risks yet.

Walk Through
------------

The walk through will be similar to last semester's final demo.  We will
need a hard copy of the agenda.  We should give a brief overview of the
project, explain how our part of the project fits in, explain what has
been going on so far (i.e. doc status, auto testing), identify known
defects in the frozen version, and show the technical features we have
implemented.

Jamie Marconi requested that we be able to run the demo, rather than have
the customer do it.  We will state up front what would cause the program
to crash and navigate around it.

James Cooper asked if he should read the overview out loud.  Professor
Junk said no, but rather hit on the important points.  The customer will
not have a copy of the documents yet, so we want to make sure we
understand and are on the right trail.

Jamie Marconi asked what a test harness is.  Professor Junk described it
as an environment to test data.  It is the essence of automated testing.

Jamie Marconi also asked if Professor Junk wanted us to print out all
90,000+ lines of code.  Professor Junk said he would like our modified
code.  It should be well written, well documented, production quality
code.

Professor Junk wants us to bring in our notebook and the checklist on the
Tuesday meeting.  The grading will be from 0-4.  A score of 0-2 will need
to be reworked, a 3 will need revision for the next go-around, and a 4
will mean we are where we need to be.

Next week:      Tuesday will be a project status meeting
                Thursday will be the demo.