Object-Oriented Software Engineering

Overview and Code Review Presentations

The big picture goal is to get across the ideas of the current state of your project to the audience, which will be members of other groups.

Give an overview of your project, i.e. the purpose and what the user expects to get out of it; showing GUIs or GUI sketches would be helpful here.
Describe the high-level deployment architecture, in particular any distribution, web interaction, database used, etc.
Next, present a high-level project code overview, likely via a UML class diagrams and perhaps a UML component diagram.
Describe some of the complex algorithms or protocols you are needing to implement. It is very helpful to present some sequence diagrams that go into complex interactions, or do whatever you think is best to get the complex ideas across to your peers.
Finally briefly describe what the status of your implementation is at this point.

Prepare a review of the most interesting sections of code in advance. You don't need to overview all of the code; do some of the critical, core and unique aspects.
Generally the person that wrote most of the part being reviewed is leading the presentation on that part.
Give a very brief review of the project context around each fragment, so the code won't be totally out of the blue to people.
Your goal is for your peers to get some understanding of how you coded particular parts.
Use UML diagrams to better illuminate the code. In particular, sequence diagrams and class diagrams.
If you have part of your project to briefly demo, that is great. Make sure you test your demo in the same environment as the presentation (same laptop(s), etc) because it is very likely your demo will not work if you don't.
Be prepared for questions and to show additional pieces of code to answer questions.

Here are the logistics for the presentations.

We are going to divide up into two different sub-groups so each group will have enough time to present.
Each sub-group is going to meet in a different room; room announcements will be made on the forum.
Some groups will go Monday, and the rest Wednesday, as per the announced schedule.
Your project group will have around 20 minutes to present.
Each room will have an LCD projector to use for the presentation.
You are a critical member of the presentations both as a presenter and an observer---one of the goals is to get some good discussions going on the different projects, and we hope you learn something from seeing how the other project groups are tackling various problems.

The keys are organization and clarity.

Show up -- if you are absent on any presentation day (even if your group is not presenting) you will be heavily penalized.
Have an organized presentation that you ran through in advance, and have different duties divided up amongst group members.
Nerd-heavy presentations are fine, we are not expecting fancy speeches or cool wardrobes. Just understandable presentations.
In terms of the form of the presentation, powerpoint slides are a good choice, but use of powerpoint is not required.