Project Part 2 Feedback

Requirements Specification -- Good (3)

In UC01: the order of basic flow 1 to 5 is not fixed, right? The user can do 5 first, then do 3, right? So, I will suggest you to merge these flows, and say 'User enters task info to the system.'
Put post-condition after pre-condition.
In UC02: what is contributor? The name of the use case is 'ViewLocalTask'. But there is no user in your use case. Confusing here. Same question for UC04.
You need to reorganize the layout of test cases after UC05 to make it consistent with UC01 to UC04.
Be careful when you design the test case. Make it more logic and technical. For example, 'As a user, I want to fulfill tasks'. To test it, you can say: 1. Select a task from the system to fulfill. 2. Fulfill the task and re-upload. 3. Check if the task is fulfilled. You need to design the test case in the way like this.
Use cases and test cases are all numbered and important ones are included.
The use cases doc is very good except for some missing or confusing part.

The class diagram for Task and Task related classes look good.
You only have one class for controller and one class for view? I guess you didn't include activity classes into your UML diagram. This is still important. When you start coding, you need to create activity classes too, right? You need to include these classes. These important entities are missing.
To clearly show M, V, C classes, you need to carefully design the classes and draw the diagram. It doesn't mean you can miss some classes.

Please update docs according to the feedback. Keep the old version and name the new one 'XX--update 1' or something like that. So I can track your progress.
Good luck with part 3! Enjoy the coding.