Iteration 2
In Iteration 2, do as many more use cases as possible in the 2 week period. You now:
- expand the Javadoc coverage
- use Ant tasks that you author
- unit test with JUnit
In a real project, you would produce Javadoc and unit tests from the beginning. Since this is a course about projects, we cannot expect you to do all these things from the beginning.
The Development Process
The process is essentially the same as the one for iteration 1: 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, as before, all non-private attributes and methods for all domain model classes and all controller classes. The number of classes that you Javadoc should be no less than 10.
The Project Itself
Make available on your team web site all the files needed to build and run your project.
Deliver the following new artifacts:
An Ant build.xml file
The build.xml file should include at least 2 targets that you have written. Identify those targets that you have written. The targets should ease either your development process, your deployment process, or your client demonstration process.
The Resources page has some links about Ant that you may find useful.
JUnit
Unit test all your model classes. At least 5 classes should be unit tested with JUnit. You do not need to write tests for methods that are "too simple to break" such as:
- Pure get methods
- Pure set methods
- Forwarding to super methods - e.g.,
public boolean isEmpty() { super.isEmpty(); }
The Resources page has some links about JUnit and unit testing that you may find useful.
Submission Procedure
Jar all Java source files, including your test classes, and non-Java files that you need to build and run your project. Include in that jar file all deliverable documents. If including such documents in a jar file is, for any reason, inappropriate, propose as soon as possible an alternate method for transmitting this information when it is due.
Client Demonstration
Your client demonstration, after building your system, starts by running all your unit tests.