Center for Analysis and Design of Intelligent Agents

User Tools

Site Tools

Trace:
public:t-624-cgdd-16-1:main

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
public:t-624-cgdd-16-1:main [2016/04/15 15:18] – [Project Work: Events & Deliverables] davidthuepublic:t-624-cgdd-16-1:main [2024/04/29 13:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ======T-624-CGDD: Computer Game Design & Development, Spring 2016 ====== ======T-624-CGDD: Computer Game Design & Development, Spring 2016 ======
-===== UNDER CONSTRUCTION =====+
 ===== Basic Info ===== ===== Basic Info =====
  
Line 20: Line 20:
 =====Books===== =====Books=====
  
-There is no course textbook, but you have access to several books in the library: Game Programming Gems 1 through 8 (various), GPU Gems 3 (Nguyen), CryENGINE 3 Cookbook (Tracy), Unity 3.x Game Development Essentials (Goldstone). You also have access to Game Developer's Magazine (several years). There are also many helpful tutorials online, hosted by the makers of game engines like Unity and Unreal.+There is no course textbook, but you have access to several books in the library: Game Programming Gems 1 through 8 (various), GPU Gems 3 (Nguyen), and CryENGINE 3 Cookbook (Tracy). You also have access to Game Developer's Magazine (several years). There are also many helpful tutorials online, hosted by the makers of game engines like Unity, Unreal, and Godot.
  
 ===== Intended Learning Outcomes ===== ===== Intended Learning Outcomes =====
Line 32: Line 32:
   * Communicate game ideas clearly and concisely   * Communicate game ideas clearly and concisely
   * Discuss the basic issues around intellectual property in game development   * Discuss the basic issues around intellectual property in game development
-  * Describe the most common emotions that arise from playing games+  * Apply some practical paradigms for game design & development
   * Describe common forms and structures of narrative in games   * Describe common forms and structures of narrative in games
   * Explain some common game AI techniques   * Explain some common game AI techniques
Line 43: Line 43:
 The term will consist of three major events. On “Pitch Day” (April 29, morning), each student team will present their game idea to the class and receive feedback from a panel of judges (comprised of both their peers and industry professionals). On “Alpha Day” (May 6, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants.  On “Demo Day” (May 17, Time TBA), each student team will present their finished game demo and run a station where students and guests can play their game. The term will consist of three major events. On “Pitch Day” (April 29, morning), each student team will present their game idea to the class and receive feedback from a panel of judges (comprised of both their peers and industry professionals). On “Alpha Day” (May 6, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants.  On “Demo Day” (May 17, Time TBA), each student team will present their finished game demo and run a station where students and guests can play their game.
  
-During weeks 2 and 3 of classes (May 2 to May 13) each student team is expected to demonstrate their activity on their project using the course project tracking software (Trello). All updates to Trello for a given work period are due by 7:00 on the weekday following that period (e.g., 7:00 on Wed for work done on Tue). +During week 1 of classes (April 25 to 29), each student team is expected to analyze the design of some specific commercial games (TBD). Each team will hand in a short document discussing the results of these analyses (due by 18:00 on April 27). 
 + 
 +During weeks 2 and 3 of classes (May 2 to May 13), each student team is expected to demonstrate their activity on their project using the course project tracking software (Trello). All updates to Trello for a given work period are due by 7:00 on the weekday following that period (e.g., 7:00 on Wed for work done on Tue). 
  
 Before Alpha Day, each team is expected to write and submit an Alpha Testing Plan (due by 17:00 on May 3). **NB**: Any team that fails to submit their Alpha Test Plan on time will be eligible to receive at most half of the maximum grades for both the Alpha Test Plan and Alpha Day. Before Alpha Day, each team is expected to write and submit an Alpha Testing Plan (due by 17:00 on May 3). **NB**: Any team that fails to submit their Alpha Test Plan on time will be eligible to receive at most half of the maximum grades for both the Alpha Test Plan and Alpha Day.
 +
 +On Demo Day, each team is expected to submit their game project for evaluation (due by 00:01 on May 17), including all source code, assets, launch & gameplay instructions, and an attribution list for all found resources that they used.
  
 After Demo Day, each student is expected to write and submit a Post-Mortem that gives their personal account of working on their team’s game (due by 23:59 on May 18). Late submissions of Post-Mortems will incur a penalty of 15% per day including weekends and holidays. After Demo Day, each student is expected to write and submit a Post-Mortem that gives their personal account of working on their team’s game (due by 23:59 on May 18). Late submissions of Post-Mortems will incur a penalty of 15% per day including weekends and holidays.
Line 55: Line 59:
 |Alpha Test Plan|Document (1-2 pgs)|1 per team| Tue May 3 (by 17:00) |5%| |Alpha Test Plan|Document (1-2 pgs)|1 per team| Tue May 3 (by 17:00) |5%|
 |Alpha Day|Testable Prototype & Alpha Test|1 per team| Fri May 6 (morning) |10%| |Alpha Day|Testable Prototype & Alpha Test|1 per team| Fri May 6 (morning) |10%|
-|Demo Day|Presentation & Final Game Demo|1 per team| Tue May 17 (Time TBA) |30%|+|Demo Day|Hand-in + Presentation & Public Demo|1 per team| Tue May 17 (Hand-in by 00:01, Demo Time TBA) |30%|
 |Post-Mortem|Document (3-5 pgs)|1 per student| Wed May 18 (by 23:59) |20%| |Post-Mortem|Document (3-5 pgs)|1 per student| Wed May 18 (by 23:59) |20%|
 ^ ^ ^ ^ Total^ 80%^  ^ ^ ^ ^ Total^ 80%^ 
- 
 ===== Discussion System ===== ===== Discussion System =====
  
Line 77: Line 80:
 The participation grade will be based on: (1) Attendance (both mornings and afternoons), and (2) Participation in online discussion. To the extent possible, this will also be based on how actively the student participates in in-class discussion (based on the instructors' subjective assessment). The participation grade will be based on: (1) Attendance (both mornings and afternoons), and (2) Participation in online discussion. To the extent possible, this will also be based on how actively the student participates in in-class discussion (based on the instructors' subjective assessment).
  
-The base participation grade will be calculated as 7.5 * (portion of mornings attended) + 7.5 * (portion of afternoons attended)). The instructors can then add possible bonus points to this base grade based on a subjective evaluation of the student's participation throughout the semester (into which the online discussion may factor). +The base participation grade will be calculated as 7.5 * (portion of mornings attended) + 7.5 * (portion of afternoons attended). The instructors can then add possible bonus points to this base grade based on a subjective evaluation of the student's participation throughout the semester (into which the online discussion may factor). 
  
 =====Grading===== =====Grading=====
Line 89: Line 92:
 ^Part of Course^Total Weight^ ^Part of Course^Total Weight^
 |**Group Work**|  | |**Group Work**|  |
-|  Pitch Day|  10%|+|  Game Analysis|  3%| 
 +|  Pitch Day|  7%|
 |  Daily Updates|  5%| |  Daily Updates|  5%|
 |  Alpha Test Plan|  5%| |  Alpha Test Plan|  5%|
/var/www/cadia.ru.is/wiki/data/attic/public/t-624-cgdd-16-1/main.1460733529.txt.gz · Last modified: 2024/04/29 13:32 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki