Final Iteration

In your final iteration, do as many more use cases as possible in the 2 week period.

The Development Process

The process is essentially the same as for the previous iteration: Implement use cases of highest value: They reduce risk and/or increase business value.

Deliverables

Project Documents

Writing quality is important. In all your documents, including Java documentation, be clear, succinct, and precise.

All deliverables for previous iterations are deliverabe for this and subsequent iterations. Update these documents to reflect this iteration's use cases.

Javadoc

Javadoc all non-private attributes and methods for all classes. Publish your Javadoc on your project web site.

Project presentation artifacts

Make all your project presentation material (e.g., your Powerpoint file) accessible from your web site.

Project Build Artifacts

Make available on your team web site all the files needed to build and run your project.

Ant build.xml file

Automate at least 1 task that was not automated in the last iteration, for either your build, deploy, or client demonstration procedures. You may use a tool other than Ant, such as Maven.

JUnit

Have unit tests for at least 8 classes using JUnit. You do not need to write tests for methods that are "too simple to break" such as:

Submission Procedure

The procedure for this is the same as the previous iteration.

Client Demonstration

The procedure for this is the same as the previous iteration.


 cappello@cs.ucsb.edu © Copyright 2010 Peter Cappello                                           2010.05.12