Skip to content

Presentation

The final presentation will involve a live demo of your application. All team members are expected to be present and take part in the presentation. The key factors affecting your grade are organization and clarity.

Info

The presentation will be done via Zoom. It will be recorded.

Note

Sign up link for final presentation will be posted, here. Use this link to signup for presentation: https://calendly.com/madooei/oose-final-presentation

Danger

Show up -- if you are absent you will be heavily penalized.

Structure

You must structure your presentation as follows.

Info

Your presentation must take at least 15 and at most 30 minutes. We will consider another 10-15 minutes for Q/A (which may be interspersed with your presentation). Our questions may involve asking you to try certain inputs in your application during the live demo.

Opening remarks [1-3 minutes]

Remind us what your project is about and what problem does it solve.

  • We know what you've been working on but a brief overview helps to set the scene.
  • You must choose one team member to deliver the opening remarks.
  • You may use slides (or other visuals) to supplement the delivery.1

What does your application do? [7-10 minutes]

This is about the functional requirements (User Stories) you've written at the onset of your project. Here is the time to show us what your application does.

  • We need a live demo (don't use slides, screenshot, etc.)
  • Do not waste time showing us trivial features like how user can signup or login to the application. (Unless that's an essential aspect of the app.)
  • Strategize and prioritize: we want to see a demo of core "must-have" features that distinguishes your app from others.
  • Show us you've delivered what you've set out to do and pepper it up with features that make us go "Wow!"
  • You must aim to showcase about 4 User Stories. All team members must participate; perhaps plan for each member to demo one User Story.

Note

You should all have the app running and each take turn sharing your screen to show us a (2-3 minutes) demo involving one User Story.

Tip

Show the project works! Be sure your demo is iron-clad, test it in advance in exactly the same environment as the demo.

How does your application do it?! [5-7 minutes]

This is about the technical (behind the scene) stuff: design, architecture, code, backend, frontend, technology, APIs, databases, algorithms, etc.

  • You must have a slide show for this section.
  • Describe the high-level deployment architecture, in particular any distribution, web interaction, database used, etc.
  • Next, present a high-level overview of design, likely via a UML class diagram. Don't show us a huge busy diagram of all classes in your code-base. Instead, make it about most interesting sections of the design. In particular, the parts about the critical, core and unique aspects of your application.
  • Describe some of the complex algorithms or technologies, tools, ... you have implemented (no need to show the actual code).
  • You should organize the presentation delivery into sections divided up amongst group members.

Closing remarks [3-5 minutes]

We are interested to hear about:

  1. the limitation of your software (what it does not/cannot/will not do)
  2. the future of your software (what will happen to it after the course is over?!)
  3. the take-away from this project (yes! a moment of reflection, as a group)

You must choose one team member to deliver the closing remarks (preferably not the same person who delivered the opening remarks). You may use slides (or other visuals) to supplement the delivery.

Info

You must give a practice presentation during the last Tuesday of classes (i.e. April 28). The practice presentation will be delivered to your advisor. It will contribute to the grade of iteration 5. The practice presentation must not take longer than 20 minutes; you can eliminate the opening/closing remarks from it.

  1. If you are using slides, keep them simple. Especially, don't use too much text on the slides. ↩