Final Project: Milestone 2

For this milestone, you should:

Significantly improve the functionality and quality of your application beyond M1.
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:

Four pages in addition to the Landing page should be available in the deployment. (The Sign In/Register pages provided as part of the template don’t count.)
At least one page in the deployment should read data from the database (i.e. from MiniMongo).
At least one page in the deployment should write data to the database (i.e. using a form).

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:

Use GitHub issues and a GitHub project called “M2” to manage the development of this release of the system.
Use Issue Driven Project Management practices.
Update your organization’s GitHub Page to document the current version of your system following GitHub hosting guidelines.
All branches are named according to IDPM guidelines.
Implement TestCafe “availability” tests for all pages. That means testing to see that all pages in the application are displayed, and that all forms operate correctly with legal inputs.
Put your system under contiguous integration using GitHub Actions. That means that each time a commit is made to the master branch, the system is checked for ESLint errors and that all TestCafe tests are run.
Display the current results of continuous integration via a badge on your project home page.

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:

A link to the GitHub organization associated with this project and all of its repositories.
An “Overview” which summarizes what the system does and the problems it is intended to solve for the UH Community.
A “User Guide” section. The user guide should guide the user through all of the currently implemented functionality of the system. The user guide should include up-to-date screen shots with textual descriptions of what the user can accomplish on the page.
A “Developer Guide” section. The developer guide should guide a developer through the process of downloading, installing, running, and modifying the system.
A link to the running deployment of your system on Digital Ocean.
A link to the M2 Project page, showing what issues were completed for this milestone. It is appropriate that by the time of the due date, there are no issues in the BackLog or In Progress for this milestone.
A link to the M3 Project page, showing what tasks you have defined in order to immediately make progress on your third and final milestone. There should be an In Progress issue for every team member, plus at least one issue per team member in the Backlog.