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 KILowBites. It must not contain any incomplete features.

2 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.

3 UML Class Diagram

You must submit (using Canvas) a .vpp file (named design.vpp) containing an abstract (i.e., that does not include attributes or methods) UML class diagram of all of your Java code (in the correct packages).

This file must be created using the correct version of Visual Paradigm. (Before you submit it, you should ensure that it can be opened on a lab computer.)

Visual Paradigm does have the ability to create a UML diagram from code, but you will probably need to clean-up the result.