Project 6 grading

project-6/rubric.md

@@ -0,0 +1,61 @@
+# GRADE: 47/48 
+
+## Functional and implementation requirements: 28/28 points total
+
+### Menu: 2/2 points
+
+Earned|Possible|Requirement  | Comments
+------|--------|-------------|-
+1|1|Add **Undo** and **Redo** menu items to the **Edit** menu. The **Undo** menu item should have a keyboard equivalent of Ctrl/Cmd-Z. The **Redo** menu item should have a keyboard equivalent Ctrl/Cmd-Shift-Z.
+1|1|Put a separator between them and the other **Edit** menu items.
+0|0|**Undo** is disabled when the program starts and when all actions have been undone; it is enabled when the first action is taken. | _Addressed in the Project 7 rubric_
+0|0|**Redo** is disabled unless there is an action to redo.
+0|0|**Group** is disabled when there are fewer than two items selected.
+0|0|**Ungroup** is disabled when the selection is not (or does not contain) a gesture.
+0|0|**Delete** is disabled when nothing is selected.
+0|0|**Play** is disabled when there are no notes.
+0|0|**Stop** is disabled when the composition is not playing.
+
+### Undo/redo operations: 18/18 points
+
+1 pt each|Undo|Redo
+---------|----|----
+Add      |1|1
+Select   |1|1
+Delete   |1|1
+Move     |1|1
+Stretch  |1|1
+Group    |1|1
+Ungroup  |1|1
+
+Earned|Possible|Requirement
+------|--------|------------
+4|4|If notes are deleted, edited, or selected as a group, for example, through a gesture or by using the **Select All** menu item, then an undo operation should affect all of the notes.
+
+### Undo/redo stack: 6/6 points
+
+Earned|Possible|Requirement
+------|--------|------------
+4|4|The user should be allowed to undo actions repeatedly, all the way back to the original blank composition pane when the application was first started.
+2|2|Similarly, if a sequence of undo actions was performed, then the user should be allowed to redo the whole sequence.
+2|2|Taking a new action should clear the redo stack.
+
+### No regressions - 0/0 points
+
+All prior requirements are met, unless they have been superseded by new requirements.  (I will not replicate points taken off in Project 5.) _Not assessed to avoid double jeopardy_
+
+## Release - 2/2 points
+Earned|Possible|Requirement
+------|--------|------------
+2|2| The release is tagged as project-6-release.
+
+## Reflection and elegance - 17/18 points
+
+Earned|Possible|Requirement
+------|--------|------------
+3|4| UML diagram is accurate and complete. | _It doesn't show how ```UndoRedo``` is related to other classes. BTW, this is a strange name for a class since it lacks a noun._
+3|3| Design overview addresses strategy for Undo/Redo.
+3|3| Design overview addresses strategy for disabling/enabling menu items. | _Letting this slide - I think I assessed it in Project 7. Thanks for commenting on your refactoring tasks!_
+6|6| Assessment of what is elegant and what is not thoughtfully addresses object-oriented design principles. | _Well done. I'm curious if you returned to the things you flagged as inelegant here; it sounds like you had plans to._
+1|1| Velocity is presented. | _There's nothing wrong wrong with having a low velocity; it's valuable that it proved fairly consistent. That probably helped you estimate your chosen tasks for Project 8._
+1|1| Team retrospective is presented.