public:t-624-cgdd-17-3:main
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| public:t-624-cgdd-17-3:main [2017/10/25 10:22] – [T-624-CGDD: Computer Game Design & Development, Fall 2017] davidthue | public: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: | + | ======T-624-CGDD: |
| ===== Basic Info ===== | ===== Basic Info ===== | ||
| Line 5: | Line 5: | ||
| * **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: marco[ ]licorice.is | * **Contact: ** Marco: marco[ ]licorice.is | ||
| - | * **Presentations, | + | * **Presentations, |
| - | * **Project Work (with instructors on-hand): ** Weekdays: 13:00-16:00 (TBD) | + | * **Project Work (with instructors on-hand): ** Weekdays: 13:00-16:00 (M201) |
| * **Project Work (on your own): ** budget for ~25+ hours each week | * **Project Work (on your own): ** budget for ~25+ hours each week | ||
| * **Online Forum: ** [[https:// | * **Online Forum: ** [[https:// | ||
| Line 40: | Line 40: | ||
| ===== Project Work: Events & Deliverables ===== | ===== Project Work: Events & Deliverables ===== | ||
| - | The term will consist of three major events. On “Pitch Day” (December 1, 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 5, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants. | + | The term will consist of three major events. On “Pitch Day” (December 1, 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” (December 8, morning), each student team will conduct an evaluation of a playable prototype of their game with their peers as test participants. |
| During week 1 of classes (November 27 to December 1), 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 November 29). | During week 1 of classes (November 27 to December 1), 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 November 29). | ||
| 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, | 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, | ||
| 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 6 (by 17:00) |5%| | + | |Alpha Test Plan|Document (1-2 pgs)|1 per team| Tue Dec 5 (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.1508926944.txt.gz · Last modified: 2024/04/29 13:32 (external edit)