Syllabus for

Game Programming

COSC 592

(TTh 5:30-8:10, PH302)

Instructor: Matt Evett ; Dept. Computer Science; Pray-Harold 512E
Tel: 734-487-1227;
e-mail: mevett@emich.edu;
www.emunix.emich.edu/~evett/GameProgramming; webcaucus.emich.edu (the cosc592_evett caucus).

Office Hours: M 12:00-2:00, T 1:00-5:00
You may drop by at times other than office hours, but in that case I cannot guarantee that I'll be able to see you.

Prerequisite: Significant programming experience, COSC311.

Textbooks:

Course Summary: Students will become familiar with the basic processes of creating a computer game including design, implementation and testing. Students will implement an arcade-style game and an interactive fiction game. Students will study software technologies related to game development, as well as the art and design principles needed to create compelling games.

Course Calendar:

Due dates for projects are underlined.
 
5/9 History of Computer Games 5/11 Game Design Principles
  HW1: Game Review   Game Architecture
5/16 Game Design Process 5/18 Graphics in Allegro
  HW2: Arcade Game (concept)    
5/23 Graphics in Allegro, sprites input 5/25 Animation, collision detection
  HW3: Arcade Game (design)    
5/30 Timers, Handlers, Multi-threading 6/1 Terrain editing (tile editors), Sound & Music
      HW4: Interactive Fiction
6/6 Interactive Fiction, plot 6/8 Networking, Multiplayer Games
  HW4: Interactive Fiction    
6/13 AI in Games 6/15 AI in Games
      Alpha-release of game is due
6/20 First Person Shooters, Strategy, RTS  6/22 Final release of game.  DEMOS
       
6/27 Final Exam    
       

 

Grading Policy:

The final course grade will be a weighted average of the grades received in each of the following categories, as specified: Final Assignment 50%, Other assignments 30% FinalExam 20%

Tardiness Policy: Programming and other homework assignments will be due at the beginning of class. After that, assignments will be accepted through the start of the next scheduled class, but will suffer a full grade penalty. E.g., if a late programming assignment is worthy of an 'A', I will mark it a 'B'. Assignments more than one class late will not be accepted, and will receive a grade of 'F'.

Attendance Policy: We're all grown-ups, when and whether you attend class is up to you. However, missed assignments shall only be excused by a doctor's written note, verifying that the student was medically indisposed to attend class that day.

Announcements and the Web Page:

Students should view the course web page regularly for announcements regarding programming assignments, readings, etc. I update course web pages frequently!

Cheating policy:

Students are required to attend to the policy on academic irregularity outlined in the EMU student handbook. In addition, collaboration among students in solving programming and homework assignments is forbidden. If I receive programs or homework assignments that are substantially equivalent, or which are not the original work of the student submitting the material, I will not hesitate to punish all involved parties to the fullest extent, up to and including assignment of a failing grade for the course, and referral to the Office of Judicial Student Services for possible punitive action at the University level, which may include expulsion from the University. In addition, the University and the computer science department maintain policies regarding proper behavior on its computer systems. Failure to adhere to these policies can result in loss of computer privileges, and possible legal action.