The best learning comes from doing, thus the project you choose will be a most important means for getting familiar with one area, aspect, or technique of computer animation.
This particular offering of the course is unique in the sense that it will be offered in Second Life. All projects should be demonstratable in-world.
One can get started on picking a project by asking the question, "What would I like to do with animation?" Your project should be an attept to realizing whatever answer you came up with for this question.
Note that if you have an idea for a project but are unsure how you might go about doing it, please see the instructor early during the quarter and, together, we can see what we can work out.
Team projects are acceptable, however, the complexity of the project should reflect the number of members of the team and all team members are expected to contribute equally to the final project. There can be no more than 3 members on a team.
Ultimately, this project will provide an opportunity for each of you to get experience with whatever it was that interested you enough about Computer Animation to sign up for this course. So choose wisely and have fun!
Proposal - The proposal is a short document that describes the project to be undertaken. Note that the proposal should include ideas on how the project might be implemented within SecondLife.
Mid-Quarter presentation - A quick 3-5 minute presentation that indicates your progress in completing your project. It is appropriate to include any unexpected problems you have run into, and any changes in the project scope based on these problems.
Project Code - This is the bulk of your work...essentially the implementation of your project.
Final Report - This is a written summary of the project. The report should be written as if you were going to pass the work on to another person. The report should have enough details so that one, upon reading it, will have a clear idea of what you set out to do, how you went about doing it, and what you didn't get to. It should be detailed enough so that the reader will be able to knowledgably start working on your code base after reading it.
Presentation / Demonstration The final exam for this course will be demonstration of the final projects during finals week and Week 10.
Students will also be given the opportunity to review each presentation via Peer Review.
Team Member Evaluations - For team projects, each member of the team will have the opportunity to rate the effectiveness of the other team members and give feedback on the effectiveness of the team as a whole. Teammate evaluation forms will be available via mycourses.
Points | Due Date: | |
Proposal |
10 | Dec 18 |
Mid-Quarter Update | 20 | Jan 13 |
Documentation/Report | 20 | Feb 24 |
Code | 20 | Feb 24 |
Presentation |
20 | Feb 22 |
Peer
Reviews |
10 |
Feb 22 |
Team
Evaulations |
+/- bonus points | Feb 24 |
It is extremely important to continue to make progress as the course progresses. If you forsee any problems with meeting deliverable deadlines, and see the instructor well in advance (at least one week) of the deadline that might be missed we can attempt to work out alternate arrangements. Late submissions without prior permission or notification will be heavy penalized.
last updated 11/24/10