Concept Demo

Concept Demo Checklist (Informational this quarter)

Overview

Build an at least minimally-running proof-of-concept system showing the "look and feel" of the class project this quarter. Your concept demo code does not have to be good to receive credit, but it must run . You are free to use dummy screens that simulate back-end running code as needed.

For online classes: prepare a video presentation, and upload it to D2L / Panopto before the due date listed on D2L, unless otherwise noted. For on-campus classes: prepare a live presentation. Your project must run during your demo to receive credit.

Default limit: ten minutes or less presentation running time.

The general idea of the proof-of-concept demo is to present a working, live demo showing the following:

Your group's technical prowess on short notice
Your group's robustness by having backup servers for the application.
Your understanding of formal requirements, design, and plan, with some brief, token presentations of each of them.
Your preparedness by having giving a polished, resiliant, formal demo.
Your group creativity.
Your critical thinking
Your quality salesmanship (in the best sense of the prefession) in using the time to effectively communicate to us how much you know, how much you can do, and how much we should trust your professionalism to get the job done.

For courses that use video presentations:

Start with a quick introduction to all members of the team: still photo with name, or ~five-second video intro with the member giving his or her name.
Show your Google Sheets time log for the first week. Make sure that the Google Sheets timelogs are available and shared with professor Elliott, read only.