Technical Game Development I

Breakdown

Final grades will be computed as follows:

Project 1	Catch a Dragonfly	10%
Project 2	Dragonfly (Egg, Naiad, Dragonfly)	50%
Project 3	Dragonfly Spawn (Plan, Alpha, Final)	25%
Quizzes	All, minus lowest grade	15%

The bulk of the course grade involves programming. This can be done on either Windows, MacOS or Linux but must be in C++. C++ will not be taught (although various C++ techniques will be re-introduced), and it is assumed students have had signficant exposure to C++ before starting this course. The grading policy for each project is provided at the time of the assignment. In general, for each project there is a basic objective for the majority of the assignment points. There may be an extended objective for demonstrating additional work and understanding. Projects, including all data and source code, as appropriate, are to be turned in online as specified in the writeups.

The first two projects (and any sub-projects) are to be done individually, without partners. The third project, developing a game using your own engine, must be done in groups of exactly two (no more, no less).

There will be a quiz every class. These are designed to test important class concepts from the previous class(es), especially concepts that may not have been adequately demonstrated in the programming projects. Quizes are closed book and closed notes, unless otherwise indicated. All quizes have an equal weight, except for the lowest score which is dropped.

Final grades reflect the extent to which understanding of the material has been demonstrated and the assigned projects completed. The base level grade is a "B" which indicates that the basic objectives on projects and exams have been met. A grade of an "A" indicates significant achievement beyond the basic objectives. A grade of a "C" indicates not all basic objectives were met, but work was satisfactory for credit. No incomplete grades are assigned unless there exist exceptional, extenuating circumstances. Similarly, no project dealine extensions or makeup exams are given unless there are exceptional, extenuating circumstances.

Late Policy

Exams are done, and due, in class. Projects are due online at 11:59pm on the due date, unless otherwise noted. Late projects are accepted up to two days late, with the weekend (Saturday plus Sunday) counting as one day. Any late project is penalized 10% of the total assignment value per day, unless otherwise noted.

Class Conduct

This course is intended for serious students. Participants are expected to adhere to all rules of professional behavior. It is to be emphasized that knowledge of material and professional behavior are tied together; failure in one of them negates any excellence in the other.

All work is to be done individually, unless otherwise specified. Students are encouraged to discuss their program designs, bugs and and issues with each other, but are expected to do the actual programming by themselves.