ATEC 3370: Game System Design
Mondays, 7:00 – 9:45 PM
ATC 3.914
Fall 2016
Instructor: Prof. Mike Breault (office: ATC 1.403)
Office Hours: by appointment only
Email: [email protected]
COURSE DESCRIPTION
This class explores game design concepts and the systems that bring them to life.
COURSE OBJECTIVES



For students to understand the purpose and uses of game documentation.
For students to understand the interactions between game systems.
For students to design a game of their own, fully detailing and quantifying all the game systems
needed to create the intended player experience.
TEXTS AND MEDIA
Online reading assignments.
SYLLABUS
This syllabus is subject to change at the discretion of the instructor (all changes will be furnished to
students in writing). Note that assignments and readings are due the following week. All assignments
are listed in e-Learning/Blackboard. See details for each assignment there.
Mon. 8/22 – Introductions, Class Goals & Expectations, Syllabus, Game Systems.
Assignment 1: Write an analysis of the game mechanics/systems of a video game.
Due by 8/28.
Mon. 8/29 – Discussion: Game genres & players, systems; concept docs. Workshop (board
game play).
Assignment 2: Write an analysis of the systems in a board game played in class.
Due by 9/4.
Workshop: Play various board games.
Mon. 9/5 – NO CLASS – LABOR DAY!
Assignment 3: Write a one-page concept doc (following template provided) for a game
you’d like to design. Due by 9/11.
Mon. 9/12 – Discussion: Concept docs, Game Design Docs. Workshop reading & feedback.
Assignment 4: Starting from your concept doc, create a first draft of a Game Design
Doc for that game, based on a template provided. Due by 9/18.
Workshop: Review and give feedback on concept docs.
Mon. 9/19 – Discussion: GDD issues. Workshop reading & feedback.
Assignment 5: Using feedback from your classmates and instructor, revise your initial GDD. Due
by 9/25.
Workshop: Review first draft GDDs, offer feedback and suggestions for improvement.
Mon. 9/26 – Discussion: Game settings. Workshop reading & feedback.
Assignment 6: Starting with the Game World section in your original GDD, greatly expand and
revise your thoughts on the setting for your game. Due by 10/2.
Workshop: Review GDDs, focusing on the setting, environments, and denizens, offering
suggestions for improvement and expansion.
Mon. 10/3 – Discussion: Gameplay and the player experience. Workshop reading & feedback.
Assignment 7: Greatly expand upon the gameplay ideas presented in your original GDD. Greater
depth, breadth, and detail is expected in this assignment. Due by 10/9.
Workshop: Review the Gameplay section of GDDs, offering suggestions for improvement and
expansion.
Mon. 10/10 – Discussion: Game UIs and the player experience. Workshop reading & feedback.
Assignment 8: Expansion and revision of the existing UI section of your GDD. Devise a complete
set of screens and messaging to convey all the information the player needs to receive from
your game. Due by 10/16.
Workshop: Review the UI section of GDDs, giving feedback on existing screens and messaging
and how they could be improved.
Mon. 10/17 – Discussion: Game system interactions. Workshop reading & feedback.
Assignment 9: Report on your Microlite20 gaming session, analyzing the systems that affected
gameplay, how well they worked (and worked together), and offer suggestions for
improvement. Due by 10/23.
Workshop: Gameplay session using Microlite20 game system.
Mon. 10/24 – Discussion: Game systems. Translating a video game into paper. Workshop reading &
feedback.
Assignment 10: First iteration of a paper or board game based on the game design in your GDD.
Due by 10/30.
Workshop: Review GDDs, especially gameplay sections, for a round of critiques, feedback, and
suggestions.
Mon. 10/31 – Discussion: Game design issues. Workshop reading & feedback.
Assignment 11: Continue developing game. Work in progress due by 11/6.
Workshop: Play student games, provide feedback in box.com file.
Mon. 11/7 – Discussion: Game design issues. Workshop reading & feedback.
Assignment 12: Continue developing game. Work in progress due by 11/13.
Workshop: Play student games, provide feedback in box.com file.
Mon. 11/14 – Discussion: Game design issues. Workshop reading & feedback.
Assignment 13: Continue developing game. Work in progress due by 11/20.
Workshop: Play student games, provide feedback in box.com file.
Mon. 11/21 – Discussion: Game design issues. Workshop reading & feedback.
Assignment 14: Continue developing game. Work in progress due by 11/27.
Workshop: Play student games, provide feedback in box.com file.
Mon. 11/28 – Discussion: Game design issues. Workshop reading & feedback.
Assignment 15: Turn in final versions of your game and your GDD to box.com and Blackboard,
due by 12/4.
Workshop: Play student games, provide feedback in box.com file.
Mon. 12/5 (FINAL CLASS) – Discussion: Course and content wrapup, post-mortem.
In-Class Assignment: Write a reflection paper about the process to create your game, what
worked and what didn’t, and what you learned, as well as suggestions for improving the class.
GRADING





20% attendance and participation (including feedback to classmates)
5% each for Assignments 1 - 14
10% for Assignment 15 (final game implementation and final GDD)
Late work will be docked a letter grade for each day late.
Attendance will be taken for each class. Each absence after the first will result in the
drop of a letter grade, unless prior instructor approval is obtained.
COMET CREED
This creed was voted on by the UT Dallas student body in 2014. It is a standard that Comets choose to
live by and encourage others to do the same:
“As a Comet, I pledge honesty, integrity, and service in all that I do.”
UT DALLAS SYLLABUS POLICIES AND PROCEDURES
Please go to http://go.utdallas.edu/syllabus-policies for these policies and procedures.