International Game Developers Association

Games Education
Course

Table of contents 1 Teachers 1.1 Instructors 2 Course Background Information 2.1 Location 2.2 Time periods 2.3 Required Text 3 Course Structure 3.1 Course description 3.2 Course Objectives 3.3 Student Learning Outcomes 3.4 Content 3.5 Grading 3.6 Attendance 3.7 In Class 3.8 Late or Missed Work 3.9 Academic Dishonesty 3.10 Grade Worksheet

[edit] Teachers

[edit] Instructors

• Ian Schreiber

[edit] Course Background Information

[edit] Location

Ohio University

[edit] Time periods

• This class was taught in Fall 2006
• Class met two hours per session, twice per week, for over ten weeks.

[edit] Required Text

Introduction to Game Development, by Steve Rabin. ISBN: 1584503777. Please do not be intimidated by the size of the book; the book is overkill for the purposes of this class, but will serve you well when taking other classes involving game development. It’s also a nice reference if you want to make games as a hobby, as it covers everything you could possibly want to know about the actual making of games (or at least gives you a great starting point).

[edit] Course Structure

[edit] Course description

An examination of the producer’s role in the development of digital games. Students will gain experience with creative and technical processes involved in the creation of projects of their own design.

[edit] Course Objectives

In this class, we will describe how to express and communicate ideas through the medium of games. We will also discuss the different forms of communication and documentation in digital game development, and when it is and isn’t appropriate to use each form.

[edit] Student Learning Outcomes

At the end of this course, when you have a great idea for a game, you will have the tools to show someone your idea and why it is fun, through the use of documentation and/or prototyping.

[edit] Content

Date	Reading	Homework due	Topics Covered
W 9/6			Course introduction. Brief description of game dev roles. Ground rules of prototyping.
M 9/11 W 9/13	p. 167-169		Design Documents: When to use written documentation. Writing style. Project 1 assigned (due 9/18)
M 9/18 W 9/20	[1]	P1 (Design Doc) due Monday 9/18	Paper Prototyping (Level 1): When to use paper prototypes. Prototyping turn-based systems. Project 2 assigned (due 9/25)
M 9/25 W 9/27		P2 (Turn-Based Prototype) due Monday 9/25	Paper Prototyping (Level 2): Prototyping real-time systems. Project 3 assigned (due 10/2)
M 10/2 W 10/4	§3.3	P3 (Realtime Prototype) due Monday 10/2	Digital Prototyping (Level 1): When to use digital prototypes. Evaluating authoring tools. Introductory programming concepts.
M 10/9 W 10/11	§3.5 and §6.1		Digital Prototyping (Level 2): Introductory debugging. UI design and prototyping. Project 4 assigned (due 10/16)
M 10/16 W 10/18	§5.3, esp. p. 539-554	P4 (UI Prototype) due Monday 10/16	Digital Prototyping (Level 3): AI design and prototyping. Project 5 assigned (due 10/23)
M 10/23 W 10/25		P5 (AI Prototype) due Monday 10/23	Digital Prototyping (Level 4): Game Systems prototyping. Project 6 assigned (due 10/30)
M 10/30 W 11/1	§3.6, esp. p. 272-281	P6 (Hidden System Prototype) due Monday 10/30	Game Prototyping: Core Systems design. “Functional” graphics and UI. Project 7 assigned (due at time of final)
M 11/6 W 11/8			Continuation of Final Project
M 11/13			Continuation of Final Project

[1] http://www.gamasutra.com/features/20060508/henderson_01.shtml and http://www.gamasutra.com/features/20051026/gabler_01.shtml

Note: All readings should be done by the start of the listed week. For example, the first reading (p. 167-169 in the text) should be finished before the start of class on M 9/11.

[edit] Grading

As this is a course on games, a game-related scoring system will be used. The grading will be out of a maximum 1,000,000 points...

Projects 1-6	100,000 pts each (x6 = 600,000 total)
Project 7 (Final Project)	300,000 pts

For each project, within a set of constraints, you will design a game or part of a game as a prototype. Points will be awarded for originality (20%), fun (40%), and clarity (40%).

There is no final exam in the class, but rather a final project completed over the last three weeks of the course. The project is due at the time of the scheduled final. At that time, each student will be able to demo their prototype to the rest of the class.

Class Participation/Attendance

100,000 pts

Class time will be invaluable for you to get feedback from the instructor and your peers while you’re just starting or just finishing your projects. Much of the time will be set aside for working on the projects.

Total

1,000,000 pts

[edit] Attendance

Class attendance is mandatory. This class is practical in nature; while there will be some reading, there are no written exams or tests of knowledge. You will learn most of what you need in class, in addition to receiving valuable advice and feedback on your current project.

If you miss class for any reason, it is your responsibility to contact the instructor and/or classmates to get any missed notes, project assignments, etc.

[edit] In Class

If you have a cell phone or similar device, please turn it off before class. Receiving a call or text message in the middle of class will distract others who may be concentrating intently.

[edit] Late or Missed Work

All projects are due at the beginning of class on the listed day. No late projects will be accepted. If you feel your project is not complete, turn in whatever you have done so far.

In most cases, a new project is assigned as soon as the old one is due, and it would be too easy to fall behind in the class if you have to work on two projects at once (the late one and the new one).

Projects are due electronically; email them to the instructor.

While you may turn in projects early, you are encouraged to continue playtesting and iterating on your design until it is due.

[edit] Academic Dishonesty

The Ohio University Student Code of Conduct prohibits all forms of academic dishonesty (cheating, plagiarism, forgery, etc.). In this class, cheating will be effectively impossible; there is simply no way you can copy anyone else’s ideas without it being blindingly obvious. Stealing others’ code is likewise obvious, and unlikely to be useful to you in any case since your concept will be different from everyone else’s. Plus, you’ll be working on your project in class, so the instructor can see your work while it is in progress.

If you are foolish enough to just turn in someone else’s assignment with your name on it anyway, you will receive no points for the project.

[edit] Grade Worksheet

Date Due	Assignment	Points
M 9/18	Project 1 (Design Doc)	/ 100,000
M 9/25	Project 2 (Turn-Based Prototype)	/ 100,000
M 10/2	Project 3 (Realtime Prototype)	/ 100,000
M 10/16	Project 4 (UI Protoype)	/ 100,000
M 10/23	Project 5 (AI Prototype)	/ 100,000
M 10/30	Project 6 (Hidden System Prototype)	/ 100,000
Final	Project 7 (Final Project)	/ 300,000
	Class Participation	/ 100,000
Total:		/ 1,000,000