P6: Final Presentation #

Mar 31 and Apr 02 in class

The final presentation will consist of two parts:

• Demonstration with TA (10min);
• Status report with the instructor (5min).

Demonstration Session #

You will have 10 minutes to meet with your assigned TA to showcase your final app. The primary goals include:

• Walk through the app, summarize what requirements are implemented and what are not;
• Demonstrate two user scenarios of your app
  • They can be the same as the ones you used in the proposals or previous iterations;
  • Plan to be challenged with alternative flows or edge cases during the demonstration;
• For each non-functional requirement that you claim to have met, show evidence on how that is achieved:
  • For NFRs like efficiency, usability, portability, accessibility, robustness, fault-tolerance: point them out during the demonstration of user scenarios;
  • For NFRs like privacy, security, survivability, safety: point out the specific design / algorithms / parts of the codebase that address such NFRs;
  • For NFRs like availability, reliability, scalability, evolvability: show supporting monitoring data and logs;
  • For NFRs like complexity, readability, heterogeneity: show supporting statistics of your codebase.

The demonstration (together with the P7 Final Report document) will be used to evaluate the completeness, utility, polish, and difficulty scaling factors of your project grade.

Status Report Session #

You will have a 5-minute meeting with the instructor to answer a few questions about the status of your team and project. The questions include:

• What are the main contributions of each team member to the project? In particular, is there anyone who did significantly less work than they should?
• Did you use generative AI tools (e.g., ChatGPT, GitHub Copilot, Cursor) during the development? If yes, how did you use them and what are the benefits and drawbacks?
• What is the future plan for the project (do you plan to release the app, continue working on it, develop something else related, etc.)?

The status report (together with the subjective coding metrics mined from your GitHub repositories) will be used the determine the individual effort scaling factor.

Through these questions, we also want to understand your learning process and challenges that you may have faced during the project, which will help us improve the course.

Presentation Slots #

---
displayMode: compact
---
gantt
    dateFormat  HH:mm
    axisFormat %H:%M
    title March 31 AM
    section Team 09
      TA (Amber): 10:00, 10m
      Inst.: 10:10, 5m
    section Team 05
      TA (Saarang): 10:05, 10m
      Inst.: 10:15, 5m
    section Team 03
      TA (Amber): 10:20, 10m
      Inst.: 10:30, 5m
    section Team 13
      TA (Saarang): 10:25, 10m
      Inst.: 10:35, 5m
    section Team 02
      TA (Amber): 10:40, 10m
      Inst.: 10:50, 5m

---
displayMode: compact
---
gantt
    dateFormat  HH:mm
    axisFormat %H:%M
    title March 31 PM
    section Team 14
      TA (Daniel): 13:00, 10m
      Inst.: 13:10, 5m
    section Team 12
      TA (Bihui): 13:05, 10m
      Inst.: 13:15, 5m
    section Team 10
      TA (Bihui): 13:25, 10m
      Inst.: 13:35, 5m
    section Team 20
      TA (Daniel): 13:40, 10m
      Inst.: 13:50, 5m
    section Team 19
      TA (Daniel): 14:00, 10m
      Inst.: 14:10, 5m
    section Team 04
      TA (Bihui): 14:05, 10m
      Inst.: 14:15, 5m

---
displayMode: compact
---
gantt
    dateFormat  HH:mm
    axisFormat %H:%M
    title April 02 AM
    section Team 07
      TA (Amber): 10:00, 10m
      Inst.: 10:10, 5m
    section Team 06
      TA (Saarang): 10:05, 10m
      Inst.: 10:15, 5m
    section Team 22
      TA (Amber): 10:20, 10m
      Inst.: 10:30, 5m
    section Team 16
      TA (Saarang): 10:25, 10m
      Inst.: 10:35, 5m
    section Team 01
      TA (Saarang): 10:40, 10m
      Inst.: 10:50, 5m

---
displayMode: compact
---
gantt
    dateFormat  HH:mm
    axisFormat %H:%M
    title April 02 PM
    section Team 08
      TA (Daniel): 13:00, 10m
      Inst.: 13:10, 5m
    section Team 23
      TA (Bihui): 13:05, 10m
      Inst.: 13:15, 5m
    section Team 11
      TA (Daniel): 13:20, 10m
      Inst.: 13:30, 5m
    section Team 15
      TA (Bihui): 13:25, 10m
      Inst.: 13:35, 5m
    section Team 24
      TA (Daniel): 13:40, 10m
      Inst.: 13:50, 5m
    section Team 18
      TA (Bihui): 13:45, 10m
      Inst.: 13:55, 5m
    section Team 21
      TA (Daniel): 13:55, 10m
      Inst.: 14:05, 5m
    section Team 17
      TA (Bihui): 14:00, 10m
      Inst.: 14:10, 5m

See presentation schedule for how this was assigned.

Please come to the classroom and meet with your assigned TA / instructor at your presentation slot. If you miss your slot, there is no make-up opportunity.

We encourage all team members to attend the presentation so that everyone can be on the same page. If you (one team member) cannot attend the presentation for any reason, please make sure your teammates are aware of that.

In case you want to swap your presentation slot with another team (you need to be assigned to the same TA to avoid scheduling conflicts), please make an agreement with the other team and send the instructor + TA an email in advance.

Presentation Format #

You will meet with the TA assigned to your team in the Mar 31 (Mon) or Apr 02 (Wed) class.

• Due to large number of teams, the demonstration session will be strictly limited to 10 minutes and the status report session will be limited to 5 minutes.
  • You are responsible to cover your presentations of all the iteration goals in this time.
  • You should come to the presentation prepared, e.g., have Android Studio and Emulator/Phone opened and ready to run.
• The TA and the instructor will make notes on your presentation and provide oral feedback. Grades (including the scaling factors) will be provided after finishing both P6 and P7 and considering the overall quality of the project.

The presentation is NOT a time for you to ask questions! You should ask them on Piazza, by emails, or by scheduling a separate office hour with TA/instructor. If you anticipate any question that needs to be resolved to complete your presentation, please ask them way before the presentation day.