CISC 367 Learning Game Development
Calendar
CISC 367 Learning Game Development
|
Topic |
Date |
In-class Activity
|
DEADLINES:
|
CCCS Partnering |
| Introduction,
Overview, Context |
8/31 |
ice breaker, Survey,syllabus |
For Thursday: 1. Reading Asgn 2. Examine CT4Y, CCCS, OLPC sites details |
|
| 9/2 |
quiz,laptops,
readings discussion; team name photo release |
Quiz on CT4y,CCCS,OLPC
For Tuesday: 0. Read Game design article 1. Take online course survey - see email 2. Explore 3 xo activities and write analysis for each activity: list of positives; list of negatives 3. Explore use of xo features details |
||
| XO Laptop and Game Design Analysis | 9/7 | XO game design analysis presentations and discussions |
For Thursday, 1. Prepare to teach non-technical person how to use XO and activities details |
|
| 9/9 | individual XO teaching to non-technical people |
For Tuesday, 1. Prepare by team to meet the teachers and observe Team info sheet AND First Teacher Meeting Guide details |
||
| Youth Game Play Observation and Teacher Meeting Prep | 9/14 | Quick review of Team Information Sheets Review/discuss First Meeting guides and service learning expectations role play teacher introductions |
For Thursday, 1. Revise first Teacher meeting guide and team info sheet details For Friday, read CCCS visit logistics |
|
| 9/16 |
No Thursday Class Friday CCCS Class Observation |
For Tuesday, 1. Write a reflective journal entry on CCCS Visit |
Classroom Observation | |
| Reflecting on target audience Towards programming the xo's |
9/21 | Discuss classroom observations and implications
Brainstorm language features for game development |
For next Tuesday, In teams, write small python demonstration programs covering features. details |
|
| Giving good demos and working in teams |
9/23 |
Role play good and bad demos Delveop rubric for presentations Develop good/bad characteristis of teams |
For Tuesday,
prepare "teaching demos" on python language features decide how team will collaborate in coding details Contact your teachers for first teacher meeting next week; put meeting date on wiki by next Monday |
|
| Python Programming and First Teacher Meeting Prep |
9/28 | Python teaching demos | ||
| 9/30 | Peer Leader presentations on more sophisticated Python programming on XO | For Tuesday, revise teacher meeting guide For next Thursday, 10/7, Individual python GUI-based program with classes details |
||
| 10/5 |
Finish peer leader presentations Class revision of Teacher meeting guide |
For Thursday, complete GUI program and practice demo presentations |
||
| 10/7 | Present GUI program demos | For Tuesday, bundle your gui with icon on wheel and running on xo. details | Meet your teachers and obtain initial ideas of requirements
|
|
| Requirements Analysis and Design | 10/12 | Show your gui on the xo with new icon. Short lecture on Requirements analysis and storyboarding ideas |
For Thursday, Initial requirements analysis presentation of requirements from teachers.
Write a reflective journal entry on the teacher meeting
details |
|
| 10/14 | Present requirements of each system Class discussion of use cases and detailed requirements |
For Tuesday, examine pssa requirements and create wiki
page on your discoveries
details |
||
| 10/19 |
Cecily Selling, Learning Specialist
team peer evaluations |
For Thursday, targeting different learning levels
presentation
details |
||
| 10/21 | Learning level game ideas | For Tuesday, present software design as storyboards |
Email teachers for design critique meeting first week of Nov, before 11/4 cc Lori |
|
| Design Revisions | 10/26 | Present storyboards of designs from user perspectives | ||
| 10/28 | Continue presenting storyboards of designs | Based on class feedback, prepare for teacher design critique meeting |
||
| 11/2 |
Election Day No class |
Start prototype of confirmed components | teacher design critique this week before 11/4 | |
| 11/4 |
Present report of teacher design critique
Discuss schedule for rest of semester |
For Tuesday, revise your final design and put on team wiki | ||
| Software Implementation and Testing | 11/9 | Team meetings in class | For Thursday, prepare progress presentation | |
| 11/11 | Implementation Progress Reports and first prototype demo |
Continue software development | ||
| 11/16 | Team meetings in class |
Prepare Second prototype demo Progress Report |
||
| 11/18 |
Present Second prototype demo Progress Report |
Continue implementation Email teachers for demo week after Thanksgiving |
||
| 11/23 | In-class Testing other teams' projects | For next Tuesday, Complete working version and Overview slides sent to UD review panel; details |
||
| 11/25 | Thanksgiving Day No Class |
|||
| Demos to Teachers, Iterative Improvements, Presentations | 11/30 | Demo Presentation to UD Review Panel for feedback for final version |
Demo Prototype to CCCS Teachers before Thursday Schedule classroom deployment/observation for next week |
|
| 12/2 | 2 Groups Report on Teacher Feedback and Planned Revisions | Make revisions for final version |
||
| 12/7 | 2 Groups Report on Teacher Feedback and Planned Revisions | |||
| Finals Week | UD Demo Reception | TBA |