Official Rules and Regulations

No purchase necessary to enter or win. Void where prohibited.

Summary of the Tournament
The DoubleClick™ 2005 Coding Challenge ("DCCC") is being offered by DoubleClick Inc. ("DoubleClick") and TopCoder, Inc. ("TopCoder"). The DCCC will take place between Tuesday, February 22 and Wednesday, March 2, 2005. It begins with an eight day online registration, after which all registered employees will be eligible to participate in the programming tournament. The tournament takes place online and consists of one (1) competition round. All participants who compete in the competition round will receive a DoubleClick 2005 Coding Challenge, Powered by TopCoder T-shirt and a personally engraved memento. In addition, DoubleClick will award prizes worth over $20,000 in a combination of prizes for overall finalists and for the top 10% of finishers by region in the tournament.

Eligibility
All DoubleClick employees as of February 22, 2005 are eligible to compete in the DCCC. For the purpose of this tournament, "employee" is defined as full-time employee, part-time employee, or intern. Consultants are not eligible to participate.

Registration
Registration will open on Tuesday, February 22 at 9:00AM ET and will close on Tuesday, March 1 at 6:00PM ET. Employees may only register once.

Competition Schedule

Round	Date and Time (all Eastern Time)
Registration and practice	Starts: Tuesday, February 22, 2005 at 9:00 AM Ends: Tuesday, March 1, 2005 at 6:00 PM
Competition Round	Wednesday, March 2, 2005 Sign in: 10:00 AM - 10:50 AM START: 11:00 AM
NOTE: In the event the competition round must be cancelled for any reason, all reasonable attempts will be made to run the round the following business day at the same time.

About the Tournament

Use of Plugins in the Competition Arena
The use of external TopCoder Arena plugins or any modifications to the Competition Arena functionality is strictly prohibited.

Logging in Tournament
In order to compete in the tournament, registrants must log in to the Competition Arena no later than ten minutes prior to the start of the round.

Scoring
After the results of the competition have been compiled, the top five overall scorers will be identified and will be awarded a grand prize, and in each region the top 10% of finishers will be awarded a prize. Each participant must have positive (i.e., greater than zero) points to win a prize, so if there are less than five participants who score positive points, only those participants with a positive point total will win grand prizes. Similarly, participants must score positive points to qualify for a prize as a regional winner. Participant placement is determined by aggregating the total point values from all three phases of the round for each participant.

Competition Round Structure
The round of competition consists of three phases: the Coding Phase, Challenge Phase, and System Testing Phase.

• The Coding Phase is a timed event where all participants are presented with the same three questions representing three levels of complexity and, accordingly, three levels of point earnings potential. Points for a question are awarded upon submission of any solution that successfully compiles and are calculated based on the total time elapsed from the time the question was opened to the time it was submitted.
• The Challenge Phase is a timed event wherein each participant has a chance to challenge the functionality of other participants' code. A successful challenge will result in a loss of the points originally attributed to the defendant for the code submission points, and a 50-point reward for the challenger. Unsuccessful challengers will incur a point reduction of 25 points as a penalty, applied against their total score in that round of competition.
• The System Testing Phase is a series of automated tests applied to all submitted code that has not already been successfully challenged. If the TopCoder System Test finds code that is flawed, the author of that code submission will lose all of the points that were originally earned for that code submission. The automated tester will apply a set of inputs, expecting the output from the code submission to be correct. If the output from a participant's submission does not match the expected output, the submission is considered flawed. All successful challenges from the Challenge Phase will be added to the global set of test cases that are used to test all submitted code in the System Testing Phase.