Java Capstone Series Pt. 1

Source code

1. The code is properly formatted and indented.
2. When the code is imported to Eclipse and the path to the core.jar is fixed, Eclipse doesn't show any errors and warnings.
3. The code is well structured into packages and the responsibilities are properly distributed between classes.
4. The source code is well commented.

Documentation

1. The documentation contains a UML diagram of the project. The code follows this diagram.
2. The documentation shows screen shots of the running program, highlighting the implemented features, and the functionality of the features are explained.
3. In case that features included in the first design of the project (the UML diagram) have not yet been implemented, these missing parts are clearly indicated as future work or Todo.
4. The documentation contains a short introduction how to play the game. Which keys are used to control the paddles or the pac-man, how do I collect points, etc.

Lab Report

A report on how the project evolved, which steps have been taken when, which problems have been encountered, etc.

1. The report contains a clear description/story how the project evolved.
2. It contains screen shots that document the evolution process of the project. Including failures, problems that took you a lot of time to be solved, success stories.
3. If you discussed problems with other participants, they could also include screen shots of these forum discussions (make sure that these are anonymized)

The lab report serves two purposes. First of all it documents what you had to do to get things running and, therefore, serves as a valuable resource for your future projects. Second it documents that you've actually worked on the task yourself (or with your team) and, therefore, shows your reviewers that you didn't just copy an existing solution.

How to grade

1. The peer assessment system will assign you a number of submissions by other participants. You will have to review three submissions if you work alone, or two submissions if you work in a team. Additionally, you can volunteer to review two, respectively three submissions more. If you do not review a sufficient amount of submissions, you will not receive points for this assignment at all.

2. Download the source code, documentation, and lab report. Import the project to your Eclipse workspace (Best practice is to open a new workspace for the grading).

3. Fix the Build Path for the imported project so that it finds the core.jar. (We explain how to do that here starting from ~3:40)

4. Review the source code based on the given grading criteria. You do not need to run the code, for the purpose of grading.

5. Review the documentation and lab report based on the given grading criteria. All you need to know about the project should be contained in the documentation and the lab report.