Dr. Sun, 

For hw#4 I believe there was another part that you were suppose to give us as it may conflict with our hw#3 structure. Did you upload that part to svn already or is it somewhere else?

I said the CSNS2 examples we discussed in class could be checked out from the SVN repository mentioned above. Because it also has the csns2 project name, you may need to change the project name when you check it out to avoid a name conflict with your own csns2 project.

Note that it's just some sample code, not part of HW4.

aligh1979 wrote:

Do we need to upload a text file for the created/changed files as we did for homework 3? there is no upload link by the way for homework 4

No. And the upload link is added. Thanks for reminding me.

aaronyen wrote:

Hi Dr. Sun,

Allow users to edit rubrics. Specifically, the following functions should be implemented:

• Add criteria.
• Delete criteria.
• Edit criteria descriptions.

For the "Edit criteria descriptions" part, do you mean an user can change the rating descriptions (ex. descriptions under 1~4) for each criteria or only the criteria name?  My program currently allows users to change each rating descriptions but not the criteria name.  Is that correct?

 

And also, will jdoe1, etc users be able to add and edit the rubrics?

1. Change rating descriptions.

2. Yes.

3. Yes.

Harshil wrote:

Dr Prof,

Is it fine if we implement only these 3 functions as Edit Rubrics. ?

• Add criteria.
• Delete criteria.
• Edit criteria descriptions.

Or User should be allowed to change the rubric name and rubric rating scale also? if user can change the rubric rating scale, specifically, if he decreases the scale, lets say from 4 to 3, what should be the the case of existing criterion descriptions, should we remove the last criterion desc from each criterion?

Thanks

For this assignment implementing the 3 functions listed in the assignment description is enough.

Allowing editing rubric/criteria names is fairly simple, but changing rating scale, as you pointed out, would affect the rating descriptions. A reasonable implementation would drop the last rating description(s) if the scale is reduced, and add empty description(s) if the scale is increased.