For this milestone, you should:
The latter two 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 first version of your system as part of Milestone M2.
The system should provide all functionality required for Milestone M1, plus significant additional functionality.
For this milestone, you must:
On the date associated with this experience on the Schedule page, you must have your project ready to be reviewed by Philip. He will review it online; you will not need to present it in-class.
To indicate that your project is ready to be reviewed, post a link to the project home page to the Slack #final-project channel.
The project home page should:
Use a theme that provides a link to the GitHub organization associated with this project and all of its repositories.
Include 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.
Include a “Developer Guide” section. The developer guide should guide a developer through the process of downloading, installing, running, and modifying the system.
Include a link to the running deployment of your system on Galaxy. Please make sure that the UH account ‘johnson’ is authorized to login. If different credentials are needed to illustrate certain functionality, you can provide those in class.
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.
A link to the M3 Project page, showing the issues expected to be addressed during the second Milestone period for this project.