KILowBites Final Deliverables

Obviously, all of your team's code must be in your GitHub repository and all other sprint-related materials must be in the sprint planning/management tool.

In addition, one member of each team must submit the deliverables discussed below before the start of class on the day of the final presentation.

1 Executable .jar File

You must submit (using Canvas) an executable .jar file (named kilowbites.jar) containing the final working version of Fragile. It must not contain any incomplete features.

2 Testing Report

You must submit (using Canvas) the following .pdf files.

A .pdf file (named coverage.pdf) that contains a snapshot of the EclEmma view(s) demonstrating the coverage of your unit tests.
A .pdf file (named systemtestingscripts.pdf) that contains the alpha testing scripts (i.e., the instructions for the human testers) that were used for system testing. The scripts most cover all features of the final product and must include precise instructions and the expected results from following those instructions.
A .pdf file (named systemtestingresults.pdf) that contains the system test results from at least one alpha tester (i.e., the actual results of following the scripts).

3 HTML Documentation of the Code

You must submit (using Canvas) a .zip file (named doc.zip) containing the HTML "javadocs" (i.e., the technical documentation for develoeprs) for your code.

For help creating the HTML "javadocs", see the CS Wiki.