The final project is a chance for students to flex their developmental muscles using the cumulative skills and knowledge they have obtained from this course. Students are required to design, develop, and test an application that pushes their creative and developmental skills to their limits. Ideally, each project should be designed around the specific interests of the individual students.

The application will be web-based, so it must be optimized accordingly. The application should run smoothly and cleanly under these specifications.

Students may choose from one of the possible options below.

Possible Project

• Interactive Animation or
• Scrolling Action Game or
• Database-Driven HTML5/jQuery/CSS intensive Application or
• Handheld / Mobile Project or
• Any combination thereof

Interactive Game

Specifications:

• Minimum one level
• Score keeping function
• Store persistent user data
• Life tracker
• Threats - enemies, falling stuff, mines, etc..
• Dynamically loaded assetts
• Dynamic data?.
• Energy?
• Power?
• Ammunition?
• Basic AI for the enemies?
• Multiple level

Database-Driven HTML5/jQuery/CSS intensive Application

As another option, students can create a dabase-driven HTML5/jQuery/CSS intensive application of their choice. The only limitations of doing so are that any application must:

• Use significant programming
• Use a database
• Include interactivity that is done through a highly user-friendly interface
• Obviously be web-based and optimized accordingly
• Challenging

Past Student Choice Projects

Other Possible Projects:

• Interactive Game (fun to play / for enjoyment)
• Interactive Educational Game (involves teaching / learning)
• 3D Project / Papervision type application
• Database-Driven Project
• Handheld / Mobile Project

How Much Interactivity Do We Need?

This is a question that is always asked, no matter what the project is. Fortunately, the answer is simple..."How much interactivity do you need?" Students should NEVER design around the limitations of what they know. Rather, the approach should be to design the best multimedia application possible with the provided content and THEN determine how to create it (easy to say, we know). Students who only create products they already know how to make are re-inventing the wheel and stagnating their own development. Pixel-pushers are not what we want here...

Of course, you have to know your own limitations because you have a finite amount of time to work with. With that in mind, the best way to create a program is to first design the best possible application that utilizes all the bells, whistles, and features you can possibly think of. Then, evaluate the design in order to determine what is feasible and what isn't. At that point, you can then develop a new design that integrates the components you feel gives you the best chance to succeed.

Preproduction Materials - Suggested, but not required this semester

1. Proposal - a brief but professional proposal that covers the goals of the project. Download the proposal template here.
2. Sketches / Storyboards / Interface Designs: Quick and dirty ideation sketches/ images intended for brainstorming various concepts such as graphics, interfaces, navigational systems, etc... Storyboard thumbnails template and Color Comp template
3. Flowchart: computer-generated chart that shows the associations between application segments and content. (A separate flowchart should be included for those groups utilizing a database)

 

Recommended Procedures

1. Develop a working calendar that takes into account the how much time you will need to develote to this project. Although you will have time to work on the projects in lab, outside work will be necessary. Failure to do so will likely result in a poor project.
2. Develop a rough design of your application based on the content for your particular project. Take into account your developmental strengths and weaknesses.
3. Develop the preproduction materials and get approval from your instructor. This includes the 1-page proposal, sketches, storyboards, interface designs, and flowcharts.
4. Once your design has been approved, begin production on the project.
5. Students should be able to demonstrate progress on a weekly basis, as they will be required to do at the progress checks. Students who show little to no progress from week to week will receive a lower grade.
6. Once you have your application finished, test it for bugs and usability. Once you have tested the application and identified problem areas, make the appropriate revisions to your application in preparation for final submission.
7. Submit your working application, proposal, test report, and any additional documentation.

 

Academic Dishonesty

I hate to say it, but cheating has been a problem in this class. Don't cheat. Don't follow a tutorial that somebody else did. Don't turn in somebody else's code. Don't get a game off the internet and try to modify it a little bit and turn it in as your own. I have had the unfortunate task of failing students and reporting them to the Dean of Students for academic dishonesty, hence this disclaimer. Do your own work.

You cannot do any of the following, if you do, you will receive a zero on the project and possibly be reported to the Dean of Students for Academic Dishonesty depending on the severity of the infraction.

• Anything that has code published on the web. Do your own work.

Deliverables

Students should be prepared to conduct an in-class critique/ peer evaluation of their projects. As such, students should submit their files to their share space on the web server so that it is readily accessible.

You are to deliver the following copies of the project:

1. One finished copy in your share space on the server. Do not modify the files after the due date/time. We will check the timestamp. Your Project2 folder will contain the checkpoint folders listed above with all associated files. You should also provide resources, that is a description of any materials that were not created by the student along with the location of where said materials were acquired (URLs, stock CD's, etc.)

Grading Criteria

If the project is not functional (does not work), then your project grade starts at 50%. If it is obvious that you only took your weekly assignments and made very little modifications, then your project grade starts at 50%. This is a professional project; we will not accept partial work. Late work will not be accepted. (In the real world, you would not get paid for a project you did not complete. In our world, you start at 50%)

• 35% Aesthetics & Usability
  • (Professional, effective navigation, common scheme across entire site, use of images, originality, creativity, usability features, intuitive, user friendly, easy to use, etc.)
     
• 40% Coding
  • (Proper indentation, neatness, free from errors, correct logic, follows typical coding standards, apparent planning, etc.)
     
• 10% Validation
  • (Your pages must validate as HTML5 with zero errors.)
     
• 10% Commenting
  • (Our general rule of thumb is 1 line of comment per line of code.)
     
• 5% Above and Beyond
  • Do it all in one page.
     

Total Possible Points: 100

Keys to an "A" Project

1. Meet all the expectations laid out in your proposal
2. Do more than follow a tutorial....
3. Thoroughly documented (testing, resource files, image files, problems, etc…)
4. App. functions perfectly on the Web – this includes optimization, preloaders
5. Amazing graphics, animation, media, and scripting
6. Professionally submitted project packet
7. THOROUGHLY COMMENTING YOUR CODE – will not be able to get anything above a “C” without it
8. Innovation
9. Going above and beyond
1. Flexible GUI’s
2. Integrating other technologies