Department of Computer Science Worcester Polytechnic Institute

Objective:	In this project, you will create an animation work of your own choosing, with approval of the instructor. The objectives are for you to push your abilities beyond what you have learned in the course, and create something cool. You are encouraged to do this project in groups of two.
Videos from Previous Years:	D Term, 2013 Roller Coaster: Andrew Feeney & Henrique Polido Metaballs: Crissy Guertin & Lukasz Zawada Battle Between Love & Hate: Kevin Hufnagle & Alex Lefoley Boids: Bryce Jassmond & Christian Walker Traffic Sim: Sam Kodzis & Alex Quartulli Plasma Globe: Alfredo Porras & Jeff Stokes
Programming:	Though the actual structure of this project is not well defined, you must write all the motion-control code for your project by yourself. You are (relatively) free to use any graphics/rendering language/system you like, as long as it allows you to add control of the elements of the animation in code.
Attacking the Problem:	As with all the other projects, it is best to start small and spiral up to a large result. Get the framework in place, then add new content once you have it working. There is a very short development fuse on this project, so please start early, and work efficiently!
Documentation:	You must create adequate documentation, both internal and external, along with your project. The best way to produce internal documentation is by including inline comments. The preferred way to do this is to write the comments as you code. Get in the habit of writing comments as you type in your code. A good rule of thumb is that all code that does something non-trivial should have comments describing what you are doing. This is as much for others who might have to maintain your code, as for you (imagine you have to go back and maintain code you have not looked at for six months -- this WILL happen to you in the future!). Create a README file containing all information you would like the TA to know when grading your work. I use these file and function (method) headers, in my code. Please adopt these (or some other consistent convention) for all your projects. The file header should be used for both ".h" and ".cpp/.java" files. Create external documentation for your program and submit it along with the project. The documentation does not have to be unnecessarily long, but should explain briefly what each part of your program does, and how your filenames tie in. Most importantly, tell the TA how to compile and run your program. In addition, submit a short description of what each member of the team did. Create a YouTube video of your work, upload it, and submit the URL along with your documentation.
What to Turn in:	Submit everything you need to compile and run your program (source files, data files, etc.) BEFORE YOU SUBMIT YOUR PROJECT, put everything in one directory, compile it, and make sure it runs. When you are ready to submit, zip everything up into a single archive file. Name the file LastName1_LastName2_final.zip. You will use the Web-based "Turnin" facility to submit your work. Information about submitting can be found here: https://turnin.cs.wpi.edu/. Use your WPI user ID to login, and you should have been emailed a password. The Turnin assignment ID is final.
Academic Honesty:	Remember the official WPI statements on Academic Honesty. You may discuss the project with others, but you are to do your own work.