Date	Saturday, January 31, 2004
Time	11:00 a.m. to 4:00 p.m. (pizza lunch will be provided)
Location	Goodwin 233/235
Eligibility	Queen's University undergraduate students Others are welcome, but they will not be eligible for prizes
Prizes	Each winner (determined by year of study) will receive either a copy of Microsoft Visual Studio .NET, Windows XP, or an Xbox game. In addition, each winner will receive a plaque from the School of Computing and ECE

Description

The School of Computing and Department of Electrical and Computer Engineering are proud to announce the fifth annual Queen's Internal Programming Contest. The format of the contest will be very similar to the annual ACM programming contest . Each contestant will be given five questions to solve individually. The solution must be written in C, C++, or Java. You are allowed to use any non-electronic reference, so you can bring any books or notes, but no searching in the Internet.

Contestants are judged based on their year of study, i.e., second year contestants will compete with other second year contestants, fourth year (and above) contestants will compete with other fourth year contestants. The problems are the same for all contestants. The year of a student is determined by the number of years he/she studied at Queen's.

There will be four winners, one from each year, and each of them will receive a plaque, and their names will be engraved on a plaque which is on display the School of Computing. We are pleased to have Microsoft as our corporate sponsor again this year, and Microsoft will provide software prizes for each of the winners.

To register for the contest, please send your name, current year, and degree of study to acmteam@cs.queensu.ca. As spaces are limited, you must register for the contest.

Schedule

Format of the Contest

There will be five questions. You are allowed to use a Unix workstation or a PC to program the solutions. The solution must be in standard C, C++, or Java. Solutions will be judged on a Unix workstation.

To test the correctness of your solution, we have a set of input and the corresponding set of model output. Your solution is judged as correct if your output matches the model output. You do not have to handle invalid input - the input to test your solution will always be valid (according to the specification of the question).