PLACE:
Professor Junk's office
TIME:
2:30 PM
ATTENDEES: Professor Junk
James Cooper
Jamie Marconi
Sam Gerlach
TOPIC:
Status
AGENDA:
Vision Statement
----------------
Professor Junk said that the Vision Statement was OK.
Risk Analysis
-------------
Professor Junk suggested that we modify the first risk listed (HummingBird
is a large project.) Either make it more specific with a concrete
date,
or remove it as a risk completely. We have decided to combine
it with the
steep learning curve risk and give it a more specific date.
The last risk (CS network problems may slow down the project) need
revision also. Jamie mentioned that a better risk would be that
we need
access to the crontab jobs.
Sam Gerlach will revise the risks.
Schedule
--------
Professor Junk said we needed to add the pre-proxy check to our low-level
schedule of the first month. He also noted that if we roll-down
the
schedule as the semester progresses, we need to keep a history of the
previous schedules in the notebook.
For the low-level schedule, we need to add the details of the software
support documents.
We agreed to do the pre-proxy check next Thursday. This will be
dove-tailed with a code freeze (approximately two days ahead of time.)
If
problems are discovered between the code freeze and the proxy walk
through, we are to note them. The February 2nd deadline implies
that
week, rather than the actual day.
James Cooper will revise the schedule.
Documentation
-------------
Professor Junk has revised Section 7 of the documentation. He
would like
it incorporated into the code. The documentation should have
a table
with the module name and a short description. The code needs
to be fully
documented for each walk through.
Sam Gerlach has been assigned the task of constructing Section 7.
Requirements
------------
The requirements were not included in this meeting...
Jamie Marconi is working on them.
Test Plan
---------
Professor Junk asked how feasible automated regression testing would
be
for this project. Jamie said highly feasible.
It has been decided that the following guidelines will be followed for
logging defects:
- not compiler errors
- any bug discovered after code is removed from private custody
Electronic Submission
---------------------
Professor Junk said that we need to submit a hard copy of our project
code/documentation. We can do it via html, but need to print
off copies
to submit.
This will be done 4 times:
- Proxy Walk Through
- Walk Through I
- Walk Through II
- Final Walk Through
Meetings
--------
Professor Junk requested that meeting be more formatted. They
will
primarily deal with the status of the project (i.e. what has
been
accomplished, what is happening, what problems have been encountered...)
We should have some discussion amongst ourselves prior to the meeting
with
Professor Junk. Also, we need to bring a hard copy of the agenda.
This is the responsibility of the acting Team Leader.