Solidify your toolchain and processes, implement the core components, and demo a first release of your project.
Work with your project group to (1) solidify your toolchain and processes, (2) provide an initial documentation, and (3) record a first demo of your project.
All technical processes (version control, bug tracking, build system, testing and CI) must be fully functioning and documented.
We expect proper use of version control, including coherent commits with descriptive commit messages.
Your public GitHub repository must provide a top-level README with:
Clearly labeled instructions for how to build and test the system. (Strive for a high degree of automation.)
Clearly labeled instructions for how to run the system.
Based on the provided instructions, the course staff must be able to build and test the system without issues.
Complete this in the main branch of your repository by Tuesday 02/13 EOD.
Implement and demo a first prototype. At least one use case that touches all major components of your system must be operational. For example, in the case of a client-server web application, a user command invoked from the front end should be able to return data from the back end.
The top-level README in your repository must reflect which use case(s) are operational.
Complete this in the main branch of your repository by Tuesday 02/13 EOD.
See the instructions for a demo presentation.
The presentation will take place on Feburary 14th and 15th, and you have a strict 8 minutes in total. Aim to leave about a minute for questions at the end.
You will present your slides and do your demo from your own laptop. However, you will not plug your laptop into a projector, because that takes too long. Instead you will connect to a Zoom link and show your demo by sharing your screen.