P4: Prototype Presentation #

Feb 23/25 in class

By midterm, you should have explored some design options, implemented some basic features, and have a prototype to demonstrate the user experience of your app. The goal of prototype presentation is to evaluate your progress so far (focusing on the requirements and architecture/design phases rather than detailed implementations) and to provide timely feedback on that.

Requirements #

The presentation slot is 10 minutes, including 6 minutes for presentation and 4 minutes for questions and feedback. Check the schedule tables for your assigned slot.

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: the overall status of your project, and a demonstration of one of the proposed user scenarios of your app. Below is a template you can follow:

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

  • Introduce the domain and motivation of your project.
  • (optional) If you have a major modification to your project requirements since the project proposal, clarify the modifications.
  • Describe your architectural and design choices (if already implemented) or plans (if not yet implemented); the use of diagrams is encouraged.
  • Describe the user scenario you will be demonstrating.

• Demonstration (around 3 minutes)

  • Walk through the steps of the user scenario, focusing on the main success flow.
  • You can mention the alternative flows at the corresponding steps (but don’t diverge from the main flow too much).
  • Simulated data or mock features are fine as long as some portion of the functionality works (for example, your authentication page can just accept any username/password that always let the user in without actually checking against some backend system).

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: Feb 23
• TA Evaluators: Saarang Agarwal, Liliana Hotsko

MonPM Session #

• Date: Feb 23
• TA Evaluators: Liliana Hotsko, Larry Li

WedAM Session #

• Date: Feb 25
• TA Evaluators: Bihui Jin, Saarang Agarwal

WedPM Session #

• Date: Feb 25
• 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.

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.