P5: Final Presentation #

Mar 30/Apr 01 in class

The goal of final presentation is to evaluate your final product, namely how well it is designed and implemented and whether it meets the requirements set in the beginning of the project. We will evaluate that through a slideshow (which should be brief) and demonstration (which will be more extensive than the prototype presentation).

Requirements #

The presentation slot is 10 minutes, including 8 minutes for presentation and 2 minutes for questions. Check the schedule tables for your assigned slot.

The time limitation will be strictly enforced. Except for delays caused by other factors (e.g., graders being late or power outage), each team is expected to start and finish the presentation on the exact time marked on the schedule. It is your responsibility to start on schedule by getting your devices connected during the buffer times in between presentations. Your presentation will be terminated if it exceeds the end of your scheduled slot, which may result in lower grades.

Regardless of your assigned slot in a session, please attend the entire session (from the beginning to the end) to show your support for other classmates’ presentations; you may learn from their presentations, and questions and comments are welcomed.

We also recommend all team members to join and take charge of some parts of the presentation (or handle some questions during Q&A), because that helps you to split the preparation workload and make sure everyone is on the same page. If you have to miss your team’s presentation for any reason, we ask you to inform your teammates in advance + discuss with them after the presentation about how to address the feedbacks.

Content #

The presentation should primarily cover two parts: a slideshow summarizing your project, and a demonstration of complete user scenario(s) of your app. Below is a template you can follow:

• Slideshow (around 3 minutes, each item with 1-2 slides)

  • Quickly remind us what your project is about.
  • (optional) If you have a major modification to your project requirements since the project proposal, clarify the modifications.
  • What are the top-3 most significant design decisions in your project (can be usage of certain architectural styles or design patterns, adoption of certain software engineering practices, usage of certain frameworks, etc.)?

• Demonstration (around 5 minutes)

  • This should include the primary user scenario(s), giving a complete picture of how a user would find your app useful. Since the granularity can vary, we do not set an exact number, please find out what are the most important ones that fit in the presentation time.
  • We will evaluate your app across the following aspects, which you should prepare to show evidence during the demonstration:
    • Completeness: whether core functional and non-functional requirements are implemented;
    • Utility: whether the app sufficiently addresses the stakeholders’ needs, and whether critical human values are properly considered;
    • Polish: whether the app is carefully designed, e.g., user interactions are intuitive and natural, no bugs and glitches, minimal waiting time, etc. (consider how you can optimize the app to meet the non-functional requirements) [for this aspect, getting 80% of the points means meeting normal expectations];
    • Difficulty: whether the project is sufficiently challenging for a term of work [for this aspect, getting 80% of the points means meeting normal expectations].

Logistics #

See Presentation Tips for more details on the equipments and connection.

The demonstration can be done with an emulator on your laptop or a physical phone. Please do a practice run of your demonstration on your selected device, so that you know how long it takes and make adjustments if needed. Right before your presentation, please get your demonstration device prepared, e.g., have Android Studio + emulator or phone opened and ready to run.

The projector in the classroom accepts HDMI inputs, and the instructor will bring a USB-C to HDMI adapter. The instructor can also borrow an Android phone for demonstration, if you contact the instructor at least 3 days in advance and schedule an office hour to test run your demonstration on the phone.

If some team members plan to attend remotely, please setup video conferencing yourselves; consider using a different laptop than your demonstration device (if using emulator) to avoid latency issues.

Schedule #

MonAM Session #

• Date: Mar 30
• TA Evaluators: Saarang Agarwal, Liliana Hotsko

MonPM Session #

• Date: Mar 30
• TA Evaluators: Liliana Hotsko, Larry Li

WedAM Session #

• Date: Apr 01
• TA Evaluators: Bihui Jin, Saarang Agarwal

WedPM Session #

• Date: Apr 01
• TA Evaluators: Larry Li, Bihui Jin

Evaluation #

Your presentation will be evaluated by three course staff members: the instructor, the TA who is assigned to your team, and another TA who evaluates the presentations from an outsider’s perspective. The grade will be posted on Learn after the presentations.

You do not need to submit anything (slides etc.) on Learn. The dropbox on Learn for P5 is a placeholder for posting your grades.

Grading Rubric #

60% of the points are given based on subjective factors: covering the required presentation and demonstration items, walking through the user scenario successfully, etc. The rest 40% of the points are awarded based on the aesthetics values: clarity of the presentation, whether the architectural and design choices/plans are logically sound and well-thought, some important NFRs relevant to your user scenario (e.g., usability, efficiency), etc.

Feedback #

Verbal feedback will be provided on site after your presentation. You should note them down yourselves if needed.

Since each session will have different graders, the course staff will meet after all presentations are completed to calibrate the grading criteria. The grades will be posted on Learn by the end of the week.