Project Presentation

Presentation Time

The final presentation must be made during final examinations period (Monday, December 14–Wednesday, December 23). The deadilne to request to schedule your presentation time is Friday Dec 11th, 11pm EST.

Scheduling The Presentation

First, you need to coordinate among yourselves as a group on your availabilities. Next, you need to coordinate with your advisor to get his/her availabilities (use Piazza, Email, Slack if needed). Finally, once you know for certain what date and time works for everyone, go to this link and request to schedule your final presentation. When scheduling, use your team name for the "Name" field and a member's email for "Email". Keep in mind that all members as well as group advisors must be present for the final presentaion. Once you request to schedule the final presentation via the link, wait to hear from the instrcutor (via email) to confirm your presentation date and time.

Presentation details

The presentation must last about 30 minutes. You must also leave about 10-15 minutes (at least 10 minutes) for Q&A, for a total of 40-45 minutes. Manage your time well. Our questions may involve asking you to try certain scenarios or inputs in your application during the live demo as well as asking about details of implementation/design.

Deployed App must be used

It is required to use the deployed app online (as opposed to running it locally) for the final presentation.

danger

Show up -- All members must be present for the presentation. Absent members will be heavily penalized on their grade.

Structure

You must structure your presentation as follows.

Opening remarks [2-4 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? [10-12 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!"
  • All team members must participate; perhaps plan for each member to demo one User Story.
info

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/functionality.

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?! [10-12 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 [2-4 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.

danger

Everyone must take a part in the final presentation; that is, all members must actively take a role in presenting and demoing the app. Members who do not participate (or underperform) in the presentation will receive a penalty on their grade.

Presentation Scheduling Link

https://calendly.com/ali_darvish/oose-final-presentation-fall-2020

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