User Tools

Site Tools


public:t-624-cgdd-17-3: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-17-3:main [2017/11/25 17:24] davidthuepublic:t-624-cgdd-17-3:main [2024/04/29 13:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
-======T-624-CGDD: Computer Game Design & Development, Fall 2017 (tentative information) ======+======T-624-CGDD: Computer Game Design & Development, Fall 2017 ======
 ===== Basic Info ===== ===== Basic Info =====
  
Line 46: Line 46:
 During weeks 2 and 3 of classes (December 4 to 15), 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 weeks 2 and 3 of classes (December 4 to 15), 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 Dec. 6). **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 18:00 on Dec. 5). **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 Dec. 18), including all source code, assets, launch & gameplay instructions, and an attribution list for all found resources that they used. On Demo Day, each team is expected to submit their game project for evaluation (due by 00:01 on Dec. 18), including all source code, assets, launch & gameplay instructions, and an attribution list for all found resources that they used.
Line 56: Line 56:
 |Pitch Day|Presentation|1 per team| Fri Dec 1 (morning) |7%| |Pitch Day|Presentation|1 per team| Fri Dec 1 (morning) |7%|
 |Daily Updates|Progress on Trello|n per team per day| Mon Dec 4 to Mon Dec 18 (by 7:00 daily) |5%| |Daily Updates|Progress on Trello|n per team per day| Mon Dec 4 to Mon Dec 18 (by 7:00 daily) |5%|
-|Alpha Test Plan|Document (1-2 pgs)|1 per team| Wed Dec (by 17:00) |5%|+|Alpha Test Plan|Document (1-2 pgs)|1 per team| Tue Dec (by 18:00) |5%|
 |Alpha Day|Testable Prototype & Alpha Test|1 per team| Fri Dec 8 (morning) |10%| |Alpha Day|Testable Prototype & Alpha Test|1 per team| Fri Dec 8 (morning) |10%|
 |Demo Day|Hand-in + Presentation & Public Demo|1 per team| Mon Dec 18 (Hand-in by 00:01, Demo Time TBA) |30%| |Demo Day|Hand-in + Presentation & Public Demo|1 per team| Mon Dec 18 (Hand-in by 00:01, Demo Time TBA) |30%|
/var/www/cadia.ru.is/wiki/data/attic/public/t-624-cgdd-17-3/main.1511630651.txt.gz · Last modified: 2024/04/29 13:32 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki