Presentation #

Tell us what your project is about and what problem it solves.

This is about the functional requirements (user stories) you've written. You must aim to explain at least four "must-haves" and one "nice-to-have" user story. Present the user stories that capture requirements specific to your app (what makes it different from other apps). For example, do not present a user story about user authentication! Just about every app has that!

This is about your roadmap and software stack. Tell us what programming languages, tools, frameworks, ... you are planning to use. Show us the backlog for iteration-1 to 4; elaborate on your plan!

Remind us of what your project is about and what problem it solves. Then, enumerate four to five user stories that you have implemented. For each user story, show a live demo of your deployed app where the user story is realized.

Please note:

• We need a live demo (don't use slides, screenshots, etc.)
• Do not waste time showing us trivial features like how a 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 delivered what you've set out to do and pepper it up with features that make us go "Wow!"
• You should each take turn to show us a (2-3 minutes) demo involving one user story.
• Show the project works! Be sure your demo is iron-clad; practice it in advance!
• You must all work with the deployed application. But please keep the app running locally on your computer too (each team member must do this) in case the deployed app breaks/crashes/fails/stops/etc., during the demo.

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 architecture, in particular, frameworks, databases used, etc.
• Next, present a high-level overview of the design, likely via a UML class diagram. Don't show us a huge busy diagram of all classes in your application. Instead, make it about the 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, etc., you have implemented (no need to show the actual code).
• Describe how you tested your application (make sure to include a screenshot of code coverage).
• You should organize the presentation delivery into sections divided up amongst group members.

Remind us what your project is about and what problem it solves.

• 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 are encouraged to use slides (or other visuals) to supplement the delivery.^[1]

Remind us of what your project is about and what problem it solves. Then, enumerate four to five user stories that you have implemented. For each user story, show a live demo of your deployed app where the user story is realized.

Please note:

• We need a live demo (don't use slides, screenshots, etc.)
• Do not waste time showing us trivial features like how a 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 delivered what you've set out to do and pepper it up with features that make us go "Wow!"
• You should each take turn to show us a (3-4 minutes) demo involving one user story.
• Show the project works! Be sure your demo is iron-clad; practice it in advance!
• You must all work with the deployed application. But please keep the app running locally on your computer too (each team member must do this) in case the deployed app breaks/crashes/fails/stops/etc., during the demo.

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 architecture, in particular, frameworks, databases used, etc.
• Next, present a high-level overview of the design, likely via a UML class diagram. Don't show us a huge busy diagram of all classes in your application. Instead, make it about the 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, etc., you have implemented (no need to show the actual code).
• Describe how you tested your application (make sure to include a screenshot of code coverage).
• You should organize the presentation delivery into sections divided up amongst group members.

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 takeaway 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). We encourage you to use slides (or other visuals) to supplement the delivery.