User Tools

Site Tools


public:t-624-cgdd-14-1

Differences

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

Link to this comparison view

Next revision
Previous revision
public:t-624-cgdd-14-1 [2014/04/27 15:17] – created davidthuepublic:t-624-cgdd-14-1 [2024/04/29 13:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ======T-624-CGDD: Computer Game Design & Development, Spring 2014 ====== ======T-624-CGDD: Computer Game Design & Development, Spring 2014 ======
- 
-========UNDER CONSTRUCTION======== 
  
 ===== Basic Info ===== ===== Basic Info =====
  
-  * **Instructor: ** David Thue, Marco Bancale+  * **Instructors: ** David Thue, Marco Bancale
   * **Contact: ** David: Office in Venus floor 2, telephone 599-6412, e-mail davidthue[ ]ru.is   * **Contact: ** David: Office in Venus floor 2, telephone 599-6412, e-mail davidthue[ ]ru.is
-  * **Contact: ** Marco: marcob[ ]licorice.is+  * **Contact: ** Marco: marco[ ]licorice.is
   * **Presentations, Tests, and Discussions: ** Weekdays 10:00-12:00 (V108)   * **Presentations, Tests, and Discussions: ** Weekdays 10:00-12:00 (V108)
   * **Project Work (with Instructors on-hand): ** Weekdays: 13:00-16:00 (V108)   * **Project Work (with Instructors on-hand): ** Weekdays: 13:00-16:00 (V108)
Line 25: Line 23:
 ===== Intended Learning Outcomes ===== ===== Intended Learning Outcomes =====
  
-On completion of the course students are expected to be able to:+Upon completion of the coursestudents should be able to:
  
-  * Employ focused strategies to generate ideas for novel computer games 
   * Describe the formal elements of games and the relationships between them   * Describe the formal elements of games and the relationships between them
 +  * Employ focused strategies to generate ideas for computer games
 +  * Communicate game ideas clearly and concisely
 +  * Discuss the basic issues around intellectual property in game development
 +  * Describe the most common emotions that arise from playing games
 +  * Describe common forms and structures of narrative in games
 +  * Explain some common game AI techniques
 +  * Describe methods for assessing and tuning a game's balance
 +  * Discuss the influence of sound effects and music on player experiences
 +  * Conduct a play-test to evaluate a game
 +  * Describe some current directions in computer game research
 +  * Design and develop a game demo in a limited amount of time
  
  
-===== Events & Deliverables =====+===== Project Work: Events & Deliverables =====
  
-The term will consist of three major events. On “Pitch Day” (May 2, 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 9, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants.  On “Demo Day” (week of May 19final date 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” (May 2, 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 9, 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 209:00-12:00), 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 5 to May 16) each student team is expected to post brief daily progress updates using the course project tracking software. Each update is due by 7:00 on the weekday following the period of work covered (e.g., 7:00 on Wed for work done on Tue).  During weeks 2 and 3 of classes (May 5 to May 16) each student team is expected to post brief daily progress updates using the course project tracking software. Each update is due by 7:00 on the weekday following the period of work covered (e.g., 7:00 on Wed for work done on Tue). 
Line 41: Line 49:
 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 23). 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 23). Late submissions of Post-Mortems will incur a penalty of 15% per day including weekends and holidays.
  
-^Description^Material^Due^Weight^ +^Description^Material^Quantity^Due^Weight^ 
-|Pitch Day|Presentation| Fri May 2 (morning) |10%| +|Pitch Day|Presentation|1 per team| Fri May 2 (morning) |10%| 
-|Daily Updates|Cards on Trello| May 6 to Fri May 16 (by 7:00 daily) |5%| +|Daily Updates|Cards on Trello|10 per team| May 6 to Fri May 16 (by 7:00 daily) |5%| 
-|Alpha Test Plan|Document (1-2 pgs)| Wed May 7 (by 17:00) |5%| +|Alpha Test Plan|Document (1-2 pgs)|1 per team| Wed May 7 (by 17:00) |5%| 
-|Alpha Day|Testable Prototype & Alpha Test| Fri May 9 (morning) |10%| +|Alpha Day|Testable Prototype & Alpha Test|1 per team| Fri May 9 (morning) |10%| 
-|Demo Day|Presentation & Final Game Demo| Week of May 19, exact date TBA |30%| +|Demo Day|Presentation & Final Game Demo|1 per team| Tue May 20 (**9:00-noon**) |30%| 
-|Post-Mortem|Document (3-5 pgs)| Fri May 23 (by 23:59) |20%| +|Post-Mortem|Document (3-5 pgs)|1 per student| Fri May 23 (by 23:59) |20%| 
-^ ^ ^ Total^ 80%^  +^ ^ ^ Total^ 80%^ 
-===== Lab Projects ===== +
- +
-The practical classes on Wednesdays will be in the form of self-guided lab projects with assistance. The focus will be on C++ development using the Ogre 3D graphics engine and related game libraries. These projects will not be graded, but demonstrating successful results to the instructor will count towards participation grade. In addition, all source code should be uploaded into MySchool to register the completion.  +
- +
-===== Online Quizzes ===== +
- +
-Throughout the semester the instructor may provide several online quizzes in MySchool from the theoretical material. These quizzes are meant for students to review recently covered material and will not directly count towards the final grade. +
  
 ===== Discussion System ===== ===== Discussion System =====
  
-Please use this course discussion system for posting questions regarding labs, problems or projects - or in fact anything you wish related to the course - rather than sending us emails. That way we can build a shared repository of useful questions/answers (you can of course still send us emails, but consider first whether you can post things here instead).+Please use this course discussion system for posting questions regarding lectures or your projectsrather than sending us emails. That way we can build a shared repository of useful questions/answers (you can of course still send us emails, but consider first whether you can post things here instead).
  
-[[http://piazza.com/ru.is/spring2014/t637gede/home|Piazza Course Page]]+[[http://piazza.com/ru.is/spring2014/t624cgdd/home|Piazza Course Page]]
  
 +===== Student Speaking =====
  
-===== Tentative Schedule =====+On both Pitch Day and Demo Day, each team will deliver a presentation. During each presentation, each student will be graded individually on their presentation ability. For each student, the two resulting scores will have a combined weight of 5% on their final grade. The two scores (scorePitch and scoreDemo) will be combined as follows: if scoreDemo is higher than scorePitch, scorePitch will be ignored and the final score will be based entirely on scoreDemo. Otherwise, the final score will be based equally on both scores.
  
-^Week^Lecture (Tue)^Lab (Wed)^Lecture (Thur)^ Due ^ 
-| 01 (JAN 13-19)   | Chapter 1: Introduction  | [[Lab1|"LAB1: Ogre Startup Sequence"]]      | Chapter 2: Tools  |          
-| 02 (JAN 20-26)   | Chapter 7: Game Loop and Time (A)\\ + Ogre 3D | [[Lab2|"LAB2: Making a scene"]]  | Chapter 7: Game Loop and Time (B)\\ + Engine Review    | |          
-| 03 (JAN 27-02)   | Chapter 4: 3D Math for Games | [[Lab3|"LAB3: Applying Math"]]  | Chapter 5: Engine Support Systems    | PROB1    
-| 04 (FEB 03-09)   | Chapter 6: Resources | [[Lab4|"LAB4: Resources"]]  | Chapter 3: Software Engineering (A)    | |  
-| 05 (FEB 10-16)   | Chapter 3: Software Engineering (B) | Problem Set 1 Review | [[http://www.youtube.com/user/RUClassGEDE|Engine Presentations]]                | PRESENT  | 
-| 06 (FEB 17-23)   | Chapter 8: Human Interface Devices | [[Lab5|"LAB5: Human Interface Devices"]]        | No Class  |  |  
-| 07 (FEB 24-02)   | Chapter 10: Rendering (A) | [[Lab6|"LAB6: Scene Graph"]] | Chapter 10: Rendering (B) |      |  
-| 08 (MAR 03-09)   | Chapter 10: Shader Programming (A) | [[Lab7|"LAB7: Programmable Shaders"]]                | Chapter 10: Shader Programming (B)  | PROB2 |  
-| 09 (MAR 10-16)   | Guests: Svanhvít + Jon\\ CCP Tech Artists | [[Lab8|"LAB8: Particle Systems"]] | Chapter 14: Gameplay Foundation Systems  |          |  
-| 10 (MAR 17-23)   | Guests: Steve + Logi\\ CCP Graphics Programmers  | Final Status Meetings                | Guest: Patrick \\ CCP Engine Expert    |  
-| 11 (MAR 24-30)   | Guest: Harri \\ Atomstation Networking Expert  | [[Lab9|"LAB9: Physics Optional"]]   \\ Final Project Work | Guest: Claudio Pedica\\ Gagarín Animation and AI Expert | |  
-| 12 (MAR 31-06)   | Exam Review  | Final Project Work | Final Demos | PROJECT \\ PROB3 |  
-^ ^^^^^ 
 =====Attendance====== =====Attendance======
  
-Please note that there is a 70% attendance requirement. You must pass this attendance limit in order to take the exam. Please inform the instructor if this is hard for you for some reason such as scheduling conflicts or sick leave.+Please note that attendance during both morning and afternoon sessions is required. Please inform the instructors if this is hard for you for some reasonsuch as scheduling conflicts or sick leave.
  
 =====Participation Grade===== =====Participation Grade=====
  
-Participation grade will be based on: (1) Attendance(2Completing lab projects, (3) 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 instructor'subjective assessment).+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 10 * (0.5*(Labs_completed/8) + 0.5*(Portion of lectures attended)). The teacher can then add possible bonus points to this base grade based on optional lab points or 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=====
  
 ^Part of Course^Total Weight^ ^Part of Course^Total Weight^
-|Participation|  10%| +|**Group Work**| 
-|Problem Sets |  15%| +|  Pitch Day|  10%| 
-|Engine Presentation|  10%| + Daily Updates|  5%| 
-|Final Project|  35%| + Alpha Test Plan|  5%| 
-|Final Written Exam|  30%| + Alpha Day|  10%| 
-^  Total 100% ^^+ Demo Day |  30%| 
 +|**Individual Work**| | 
 +|  Participation|  15%| 
 +|  Student Speaking |  5%| 
 +|  Post-Mortem|  20%| 
 +^  Total^  100%^
/var/www/cadia.ru.is/wiki/data/attic/public/t-624-cgdd-14-1.1398611864.txt.gz · Last modified: 2024/04/29 13:33 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki