Feedback

Code base of Prototype -- Good (2)

• The code is of good quality.
• Requirements have been completed.
• You put manager classes and model classes into t03_model package. Why don't you create a new folder to put manager classes?

Tangible Demo -- Excellent (3)

• The demo is good. I appreciate your teamwork.

Code Documentation -- Excellent (3)

• Javadoc looks good. Clear description.
• Clear comments in code.

Test Cases -- Good (2)

• In some test cases, you create or add some objects, but it seems you don't clean this object. So, if you run the test case again and again, you have to clean the test environment by your own. However, we usually need test cases to be clean, which means we create object in setUp, clean all the objects in tearDown.

OOD -- Good (1)

• The diagram looks good in general.
• If you put some description about your sequence diagram, then the reader can easily understand the scenario.

Release Planning -- Excellent (1)

Addressing Feedback -- Excellent (1)

Refactoring -- Excellent (2)

• The refacotring has been clearly documented.

Requirement Specification -- Excellent (3)

• The new requirement has been documented.
• Test cases are included.

Video Demo -- Good (1)

• If the demo can be more interactive, it will be more interesting and attractive. For example, you can make it more like an ad, put more creativity into your video demo :).

Summary -- (19)