...
- Improved consistency accross dialogs: based on a somewhat misguided guideline, we had implemented some actions of our dialogs using hyperlinks (e.g., 'Cancel'), and uthers using buttons (e.g., 'Save'). Our users complained, and we got rid of the links and adopted buttons for all dialog actions.
- Combined similar actions: our users complained that the interface had similar actions (e.g., 'Create assignment' vs. 'Create multiple assignments') and that added some confusion, so we unified them ('Add asignments').
- Use attribute names consistent with the real world: in Rails, it is common to name timestamp attributes ending with the suffix '_at". This surfaced to the interface and the evalulators requsted it to be changed to 'Due at'. A similar problem happened with our implementation of a 'Class' object; because 'class' is a reserved word in Ruby, we named our structure 'Course', and it surfaced to the UI.
Implementation
Evaluation
...