CISC 370 Term Project Presentation Schedule for Spring 2000

CISC 370 Term Project Presentation Schedule

Spring 2000
Term Project Presentations Schedule
101-N Smith Hall
Thur/Fri, May 25/26, 2000
After the schedule you will find information about (1) what is due at the
presentation and (2) what you should do at the presentation.
| Day |
Time |
Name |
| Thursday, May 25, 101N Smith Hall |
9:00AM-9:30 |
Michael Feldman & Melissa Reich |
| |
9:30-10:00 |
Jared Katzman |
| |
10:00-10:30 |
Pete McNamara & Kenneth Miller |
| |
10:30-11:00 |
BREAK |
| |
11:00-11:30 |
Caroline Cronin |
| |
11:30-12:00 Noon |
Frank Pater |
| |
12:00-12:30 Noon |
|
| |
12:30-1:00 |
Harris Jay & Ryan McDonald |
| |
1:00-2:30 |
BREAK |
| |
2:30-3:00 |
Jason Griffiths |
| |
3:00-3:30 |
Mark Thomas |
| |
3:30-4:00 |
John Davidson & Joseph LaCotti |
| |
4:00-4:30 |
John Sampson |
| |
4:30-7PM |
BREAK |
| |
7:00PM-7:30 |
Jeff Hague |
| |
7:30-8:00 |
Pete Bretz |
| |
8:00-8:30 |
Christian Craven |
| |
8:30-9:00 |
Yuguang Liu |
| |
9:00-9:30 |
John Gephart |
| |
9:30-10:00 |
Shawanda Jones & Nicole Wedderburn |
| |
10:00-10:30 |
Janel Greene & John Roberts |
| Friday, May 26, 101N Smith Hall |
9:00AM-9:30 |
Monica Williams |
| |
9:30-10:00 |
Evan Herman & Dan Kohaut |
| |
10:00-10:30 |
Ryan Gillespie & David Reisz |
| |
10:30-11:00 |
BREAK |
| |
11:00-11:30 |
France Dewaghe |
| |
11:30-12:00 Noon |
Scott Peterson |
| |
12:00-12:30 |
Kurt Thomas |
| |
12:30-1:00 |
Rob Alekel |
| |
1:00-2:30 |
BREAK |
| |
2:30-3:00 |
Mwanze Lumumba & Jeff Savage |
| |
3:00-3:30 |
Jeremy Roethel |
| |
3:30-4:00 |
Jeff Isselee |
| |
4:00-4:30 |
Kalim Oldziey & Michael Yeager |
| |
4:30-7PM |
BREAK |
| |
7:00PM-7:30 |
Kevin Griffin |
| |
7:30-8:00 |
Jiangning Gong |
| |
8:00-8:30 |
Matt Bodnarchuk |
| |
8:30-9:00 |
David Tyler |
| |
9:00-9:30 |
  |
| |
9:30-10:00 |
  |
| |
10:00-10:30 |
  |
What is Due at the Presentation
A complete write-up of your project
This should include
- A brief 1-2 page high level overview of the project similar to
the project proposal.
- Specially interesting aspects of the project. These should
include aspects of which you are especially proud, things that
you found difficult, etc.
- Weaknesses, extensions, etc that you would change if you had
more time. If you identify weaknesses and/or existing errors
that you have not been able to rectify that will be less of
a detriment than if I identify them.
- A complete listing of the code with associated documentation.
The documentation can consists of well-commented code and
other short descriptions. Or it consists of undocumented code
and accompanying documentation. Use the way that code is documented
in the Horstmann and Cornell textbook as a model if you do not
put comments in your code. Normally, well documented code will
consist of both comments and additional explanations similar to
the examples discussed in lecture that have comments and
additional explanations in the lecture notes.
What You Should Do at the Presentation
- Give a brief oral overview (approximately five minutes)
of the project that covers items (1)-(3) above. You are
encouraged to use visuals for this presentation. They can be
online or I can help you prepare transparencies for viewing
with an overhead projector.
- A demo of the project. An IBM PC with Exceed (so that you can
access and demo code from other machines) will be available
or you may bring a laptop if you prefer.
- Be prepared to answer questions.
Term Project Ground Rules
- Term projects may be done in teams of two or alone. For team work,
- Handin one copy of required work with both names
- Each team member is expected to do an equal share of the work
- You may use existing code in your project as long as
- You do not violate any copyright laws
- You give full credit to the source of the code (otherwise representing
other's work as your own is plagarism).
- You add something significant and the part that you add is
clearly indentified.
Back to the
CISC 370 homepage.
Corrections, suggestions and comments to Bob Caviness
Last updated 26 May 2000
Copyright
2000 B. F. Caviness