TIVOO Presentation Guidelines
Each team must present the design of their API to the class. Each team should have a primary spokes-person, i.e., a master of ceremonies, but each team member must also have a chance to present their area of expertise. Each team will be given approximately six minutes to present.
The focus of your presentation should be on how a programmer could use the classes you designed to build a similar event aggregation system. Assume your audience knows about XML, the various event formats, etc. - just focus on how to use your team's API. Explain what you need to do to load in new kinds of XML files, how to control how those files are filtered, and how the output is set. If you have time, also explain what needs to be done to create a new kind of filter or new kind of input format.
A Basic Template For Your Talk
You can structure your talk however you like. One suggestion is:- Briefly present a Metaphor for your design as a whole
- Describe Primary Classes/Methods
- Examples (Examples are really important in helping folks understand how to do stuff with code)
- how to use your API to accomplish the task of generating a calendar (with whatever options you want to show off)
- how to extend your API to support new inputs, outputs, or processors
- Explain some alternatives to your design, and why you choose the one your did
Grading
80% of your overall grade in the talk will be about clarity. We'll use this rubric to rank your talk out of 8 possible points:| 8 | Your talk was polished, well practiced, clear, and ended on time. It was very clear how to use your APIs to develop an event filtering system. |
| 6 | Your talk was polished, well practiced, and ended on time. It was slightly confusing how to use your APIs to develop an event filtering system, but the audience got an approximate gist of it. |
| 4 | Your talk was poorly organized, you did not know who was speaking when or have appropriate visuals, or you ran over time. It was confusing how to use your APIs to develop an event filtering system, but the audience had some idea. |
| 2 | You talk seemed "off the cuff", or one person spoke for the majority of the time. You attempted to explain how to use the APIs to develop an event filtering system, even if it was not clear. |
| 0 | Your talk was on the wrong topic, or you did not seem to know the material. |
20% of your overall grade in the talk will be about the justifications you used for your design decisions. We'll use this rubric to rank your talk out of a possible 2 points:
| 2 | Your talk had justifications for your design that made sense and were persuasive. |
| 1 | Your talk attempted to present justifications for your design, but they were incomplete, hurried, or occasionally used design principles we discussed in class incorrectly. |
| 0 | You did not present justifications for your design or you frequently used design principles we discussed in class incorrectly. |
Submitting your slides
You likely will want to have a visuals to go with your talk. Because of the very tight time constraints for the class, you will not be able to use your own laptop. You will have to submit any visuals you want as powerpoint slides. Include any code you want to show as slides - you will not have time for live coding demos. You can try videos, but be aware that there can be problems playing videos on unfamiliar computers so you should have a backup in case the video does not play.All the powerpoint slides will be placed on Professors Duvall's laptop before class. For you slides to be included, you must submit slides electronically by 8am the day of the presintation. Late submissions/revisions will not be accepted past the deadline. If your team does not submit slides in advance, you will have to do your presentation without the benefit of visual aids.