CFP'S

   April 2006
 S  M Tu  W Th  F  S
 9 10 11 12 13 14 15
16 17 18 19 20 21 22
      ^due
23 24 25 26 27 28 29

PROJECT I3-2:

NEW SPECS FOR A SOCCER SIM FOR FUTURE SALE

The entire project specs (GUI, world, agents, quality, testing, reporting,
excluding Freiman and Gargoyle) re-thought, redesigned, and rewritten for
a soccer simulator:  similar physics, no onside kickoff, different
penalties, different interaction types?, slightly different low-level
agent ideas, very different high-level agent ideas, similar QTR.  These
should be repackaged as a 10-15pp document as a product proposal for a
venture capitalist.

Due 4/18.

Competition format: $15k, $10k, $10k




   April 2006
 S  M Tu  W Th  F  S
 9 10 11 12 13 14 15
16 17 18 19 20 21 22
      ^due
23 24 25 26 27 28 29


PROJECT K:  PORT OF BROWSER SHELL Halley/Greiner or Chen/Buchman WITH TESTING

A port of one of the BROWSER SHELLS (either one) to a slightly different
platform.  If it is on Linux, move to Solaris or Windows.  If it is on
Solaris, move to Linux or Windows.  If it is on Windows, move to Linux or
Solaris.  This must include exhaustive testing of correctness, including
testing to reveal original weaknesses that remain unaddressed after porting
the code (or perhaps you improved or fixed something, even added a feature).

Original group leaders MUST be cooperative in releasing code, but MAY 
NOT provide support or assistance in the actual transformation.  Help
on how it works falls into the gray area in between.  Halley and Greiner may
not port their version, but any of their workers CAN.  Similarly for
Chen and Buchman.

Due April 25.

Competition format:  $16k, $12k, $8k




   April 2006
 S  M Tu  W Th  F  S
 9 10 11 12 13 14 15
            ^due
16 17 18 19 20 21 22


PROJECT T:  ERROR INTROSPECTION

A one page two-column list of the most common software errors you make
(mostly programming, but can include design and revision, documentation,
delivery) ... and i mean, you tend to make them a lot, or when you make
them, they are bad.  Errors listed on the lhs.  On the rhs, the
steps you take to try to minimize the frequency or severity of those
specific kinds of errors.  For example, one line might be
"MY ERROR:  i tend to open a lot of files, then run out of filehandles;
MY FIX:  i discipline myself to write a close of a file when i first
write the while loop reading from it; i don't write the body of the
while loop until i do this."

6 best get $3-5k.

Due 4/13.