Final Project: Milestone 2

For this milestone, you should:

  1. Significantly improve the functionality and quality of your application beyond M1.
  2. Significantly improve your software engineering process beyond M1.

These are closely related: if you improve your software engineering process, you are almost guaranteed to improve the functionality and quality of your application!

The M1 assessment includes suggestions on how to improve your product and your process. Make note of them and try to apply them during this milestone.

On the date and time listed on the Schedule page, you will deliver the second version of your system as part of Milestone M2.

Functional requirements

The system should provide all functionality desired for Milestone M1, plus significant additional functionality. More specifically, this means, at a minimum:

If you haven’t spent time with them before, you will probably want to look closely at Meteor Debugging Strategies and Branden’s AMA (Ask Me Anything) about Meteor. Branden was the ICS 314 TA from 2020-2022 and this is his material.

Software engineering requirements

For this milestone, you must:

For hints, see E62: Experience testing your final project.

Submission instructions

On the date associated with this experience on the Schedule page, you must have your project ready to be reviewed by the instructor. The instructor will review your almost-final version in class, but it is due at 11:00 that night.

To indicate that your project is ready for review, post a link to the project home page to the Discord #final-project channel. In addition, all members of your team must have submitted the URL to your project’s github.io page to Laulima.

The project home page should include:

Handy checklist for this milestone.