Rubric for grading A06,A07,A08

A06: 50 points

Link on web site: 5 pts
Link to Java Code is present	5
build.xml is present: 10 pts
includes a task to compile tde code	5
includes a task to run JUnit tests	5
Java Code itself: 35 pts
includes at least one example of stub for a relevant model class	5
includes at least one example of doing a reasonable unit test	10
includes a fairly complete "first cut" at a model for the scheduling servlet	10
includes a fairly complete set of tests	10

It's ok if for now the tests fail (i.e. because the body of your methods is all in stub form.)

Making all your tests pass (do this in a separate directory from A06... and link to this directory from your group's web site (20 pts)

Documenting the role of each team member on a web page called "A07 team roles", linked to from your group's main web page. (20 pts)

More detail on documenting team member's roles:

Each team member should be primarily responsible for at least one of the source files, a fact reflected in the comments at the top of the source file (for build.xml, use XML comments:  ) (10 pts)
Your entire team should have a web page indicating the contributions of each team member to A07. For each team member list (10 pts)
- names of all source files for which that team member had primary responsibility (at least one per person) (make them hyperlinks to the source file itself)
- any other roles that team member filled (e.g. presenter, documentation on the web site, organizing and running the group meetings, investigating how to do Ant, investigating how to do JUnit, investigating how to do Javadoc, etc.)

Adding Javadoc documentation to all of your classes, and including a link to the this documentation on your A07 web page. (10 pts)

The Web app itself as seen by an end user: 25%
	Correctness: TA will actually try your web app with a variety of inputs.	10
	Style: The pages should look neat, and it should be clear to a user what he/she is to do with your page.	5
	Usefulness: How useful is the final delivered app, as compared to other delivered apps (e.g. does it have restrictions such as only certain blocks of time, does it have additional nice features, etc.)	10
Deliverables: 50%
	Web page with WAR file, TAR file to make the WAR file, and links to all other deliverables.	10
	A build.xml file that can make the WAR file (there are five required components---details on A08.html)	10
	JavaDoc documentation (should be linked to from the group's web site) 5 points for doing it at all—another 5-10 points based on how useful the documentation looks.	10
	General description of the project (see A08.html for details)	10
	Documentation of each team member's roles (see A08.html for details)	10
Code: 25%
	Style of the Java code—readability, maintainability, following MVC pattern, etc.	10
	Style of the HTML/JSP code—readability, maintainability, etc. Does the code validate (as far as possible)	10
	Style of other aspects of the project (e.g. build.xml, web.xml, text descriptions, etc.)	5