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 required for Milestone M1, plus significant additional functionality.

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.
• Find at least five UH community members (not from ICS 314) to try out your system and provide feedback. (You may need to log them in using your own UH credentials.) After they try out your system, find out what they found interesting and useful about your application, and what they feel needs improving at the current time.

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 it online; you will not need to present it in-class.

To indicate that your project is ready for review, post a link to the project home page to the Slack #final-project channel.

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 “Community Feedback” section. In this section, summarize your findings from having 5 community members try out your application.

• 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 Galaxy.

• A link to the M2 Project page, showing what issues were completed for this milestone. It is appropriate that by the time of the presentation, there are no issues in the BackLog or In Progress for this milestone.