2.0 Updates:
It is required that you DEMONSTRATE the running program, and it cannot be allowed to lock up, crash, or otherwise exhibit implementation problems, or there is a very substantial deduction. Run your bullet-proof code. This is a major constraint!
See the Grading checklist , and audience.html.
Present your running project, and abbreviated forms of your completed requirements (linked to tests of those requirements), your plan and your design.
Your project must implement each of the specifications given in the project overview. Your demo must claim (clearly, even if briefly) how each of these specifications has been met.
Do you have backup servers on-line and ready to go? Do you have backup presentation materials, and presenters? Can you switch to your backups in less than a minute, while that time is covered by an alternate presentation? (Note: backups that take five minutes to bring up are effectively useless.)
Does your presentation communicate with the audience?
What is the user's problem? Did you motivate your project?
Well-organized groups will have a complete running project at this point, and will freeze the code until after the final demo. This is a good week for extensive final testing to make sure that nothing was missed. It is a very BAD week to add anything to the project not clearly marked as an alpha-test extension.
Remember that you already know how to efficiently show plans, designs, and code. Use those techniques now.
If you show code make sure that you do so in a thoughtful way.
People remember stories. Is there a story that can efficiently deliver your message, or part of your message?
Is there efficient humor that you can inject into your presentation to help keep the audience's attention?
You can get credit for good work toward your project goals in different ways. Along with the implemented project, you can additionally present designs, plans, requirements, business plans, risk assessments, HCI study designs, etc. for a larger project that is beyond the implementation scope of this class. However, NO VAPORWARE. We are looking for substantial work (albeit, in this case, not manifested as implementation). Beyond the minimal specifications, you can put your time in where your interests lie.
Have you reviewed the presentation? Is there some fat that can be cut?
Is your documentation coming along? Do you have your project booklet laid out?
Note that it is perfectly acceptable to present exactly the same, or close to exactly the same, demo for both the preview and the final project presentations. IF YOU CHOSE, you may vary the content of the presentation for the benefit of the class audience, but this is explicitly NOT necessary.