Difference between revisions of "256a-fall-2014/final"
From CCRMA Wiki
(Created page with '= Final Project Specifications = Due dates: * '''initial design / research''': 2014.11.10, submit via email, present in-class Monday * '''milestone 1''': 2014.11.17, submit prog…') |
|||
| Line 18: | Line 18: | ||
* for Monday (11/10), present this in a 1-2 minute presentation | * for Monday (11/10), present this in a 1-2 minute presentation | ||
* as you did with hw3.part1, please EITHER 1) send design sketch/research to imdone256 OR 2) put on webpage, and submit URL to imdone256 | * as you did with hw3.part1, please EITHER 1) send design sketch/research to imdone256 OR 2) put on webpage, and submit URL to imdone256 | ||
| + | |||
| + | == Milestone 1 == | ||
| + | * in-class demo; progress report due by class time (via email to imdone256, can include link to your webpage in-progress) | ||
| + | * 1-2 minutes | ||
| + | * show something working that is core to your system! | ||
| + | * this is about what you've done, and will enforce the following rules: | ||
| + | ** talking about design is '''strictly prohibited'''! | ||
| + | ** talking about what you would like to have done is '''strictly prohibited'''! | ||
| + | ** you can only talk about what you've done AND what you've tried | ||
| + | * have fun! | ||
| + | |||
| + | == Milestone 2 == | ||
| + | * in-class demo; progress report due by class time (via email to imdone256, can include link to your webpage in-progress) | ||
| + | * 1-2 minutes | ||
| + | * system should be have ALL ESSENTIAL CORE FEATURES WORKING | ||
| + | * like milestone 1, this is about what you've done, and will enforce the following rules: | ||
| + | ** talking about design is '''strictly prohibited'''! | ||
| + | ** talking about what you would like to have done is '''strictly prohibited'''! | ||
| + | ** you can only talk about what you've done AND what you've tried | ||
| + | * have fun! | ||
| + | |||
| + | == Milestone 3 == | ||
| + | * final presentation; product webpage due by beginning of presentation (via email to imdone256) | ||
| + | * 3-7 minutes | ||
| + | * must include the following | ||
| + | ** main component: a killer demo! | ||
| + | ** briefly present vision + motivation | ||
| + | ** briefly speak to experiential design + system design | ||
| + | * you will also be graded by the fluidity and strength of your presentation, so really craft/optimize your demo + PRACTICE! | ||
Revision as of 18:21, 16 November 2014
Contents
Final Project Specifications
Due dates:
- initial design / research: 2014.11.10, submit via email, present in-class Monday
- milestone 1: 2014.11.17, submit progress via email, present in-class Monday
- milestone 2: 2014.12.1 submit progress via email, present in-class, Monday
- final presentation: 2014.12.10 submit website/all material by noon, public final presentation, Wednesday
Project Proposal
- do initial design / research, and put together a proposal for your final project
- must involve real-time sound + graphics + interaction somehow, and "with aesthetics!"
- check out this project page template
- should be in implementation language (c++) -- if other languages intended, talk to me
- recommended number of people on team: 1 or 2 (if more than 2, must justify / talk to me)
- craft some preliminary design for the product (the vision, for end users)
- architect the software (the engine/framework, for developers)
- make some realistic milestones (2 to 3) leading up the final presentation (in class, finals week)
- for Monday (11/10), present this in a 1-2 minute presentation
- as you did with hw3.part1, please EITHER 1) send design sketch/research to imdone256 OR 2) put on webpage, and submit URL to imdone256
Milestone 1
- in-class demo; progress report due by class time (via email to imdone256, can include link to your webpage in-progress)
- 1-2 minutes
- show something working that is core to your system!
- this is about what you've done, and will enforce the following rules:
- talking about design is strictly prohibited!
- talking about what you would like to have done is strictly prohibited!
- you can only talk about what you've done AND what you've tried
- have fun!
Milestone 2
- in-class demo; progress report due by class time (via email to imdone256, can include link to your webpage in-progress)
- 1-2 minutes
- system should be have ALL ESSENTIAL CORE FEATURES WORKING
- like milestone 1, this is about what you've done, and will enforce the following rules:
- talking about design is strictly prohibited!
- talking about what you would like to have done is strictly prohibited!
- you can only talk about what you've done AND what you've tried
- have fun!
Milestone 3
- final presentation; product webpage due by beginning of presentation (via email to imdone256)
- 3-7 minutes
- must include the following
- main component: a killer demo!
- briefly present vision + motivation
- briefly speak to experiential design + system design
- you will also be graded by the fluidity and strength of your presentation, so really craft/optimize your demo + PRACTICE!
