CSE 403 project: Beta release

Overview

Solidify your toolchain and processes, implement the core components, and demo a first release of your project.

Set up

Work with your project group to (1) solidify your toolchain and processes, (2) provide an initial documentation, and (3) present a recorded demo of your project.

Instructions

1. Solidify your toolchain, processes, and instructions (40%)

  • 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 11/4 EOD.

2. Implement and integrate first versions of all your system’s major components (40%)

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.

3. Record your demo presentation (20%)

Record a video presentation of your project. The video must be at most 5 minutes long.

See the instructions for a demo presentation. However, because of the short time, you will only do #1-#3 in that list: a brief introduction, the demo itself, and a brief discussion of your plans.

Your demo must show your actual system running (for example, a screen recording), not screenshots or mockups. Each group member must participate in the video in some way.

What to submit (to Canvas)

  • A link to your recorded video (for example, an unlisted YouTube video or a UW Google Drive file). Make sure the course staff can view it without requesting access.

  • PDF of your slides.