ENGR 112/CPSC 289-503 Project Specification (PRELIMINARY)
Due: 11:59 P.M. Monday, December 4, 2006

"The Inebriator"

The project is to write a C++ program which simulates the effect of alcohol
on a driver's response time.  You may use your imagination, but here is one 
idea: Ask the user's sex and weight and how many of what kind of drink how 
many minutes ago.  Randomly choose a vehicle speed and distance to the car 
ahead so that a sober driver can just barely stop in that distance.  Then at a 
random time 5 to 10 seconds later, flash a "STOP" sign on the screen and time 
how long it takes the user to press a button on the screen.  Scale the results 
for alcohol intake and report "You stopped safely" or "CRASH!"

You may work in a team of one to three students.  You may choose either the
Visual C++ environment in the lab or g++ with X windows on linux.cs.tamu.edu.
Your program must be written in C++ with a FLTK GUI and be submitted both to 
CSNET and also on a CD or a 3.5" 1.44MB diskette formatted for Windows.  The 
project report (described below) should be submitted on paper to your grader,
along with your CD or diskette.  You only need to submit one report and CD or 
diskette and CSNET file per team.  All team members will receive the same
project grade.  Write a report according to the outline below.

Extra credit (up to 10 points) will be given for additional features such as 
the following:
	(5 points) animation, e.g., a series of expanding circles for a crash,
	or an animated GIF or JPEG
	(5 points) sound effects (crash, screams, etc.)

If you wish, you may use "Blood Alcohol Content" and sex for part of the input;
here are some useful tables (thanks, Justin!):
http://cp.myvlp.com/courses/alcohol/tabc/materials/femalebacchart.jpg
http://cp.myvlp.com/courses/alcohol/tabc/materials/malebacchart.jpg 

REPORT OUTLINE

The project report must be printed on a laser printer.  The report should 
include the following sections:

1.  Team information (team name, members' names, who did what)
2.  Statement of the problem, significance, etc.
3.  Restrictions and limitations
4.  Explanation of your approach (analysis to choose a 
strategy for programming the project, how you coded it, etc.)
5.  Sample run (screen shots)
6.  Results and analysis
7.  Conclusions - What did you show?  What did you learn? 
8.  Future research (how your program could be improved or 
extended)
9.  Instructions on how to run your program
10. Listing of the COMMENTED program
11. Bibliography - What reliable sources did you use for stopping time, effect
of alcohol on response time, etc.?