DC3 Grades

by Mike Gleicher on December 16, 2019

DC3 Feedback

You should get DC3 feedback soon on Canvas. This is for the final handin.

Grades – the letter grades sometimes have a +/-. A “AB-” means “an AB, but on the low side of AB” – it gets the same grade as an “AB +”, but we kept it in our notes so we can compare things for consistency.

The numbers are A=90, B=80, etc.

We had to grade very quickly, so we may have missed some of the good things in your assignment. To make up for this, we are adding 2 points to everyone’s assignment. (this is why the number posted on Canvas is two higher than what is posted in the explanation).

Because grading was done quickly, the comments we provide may not be that extensive.

Any assignment turned in by the time we started grading on Sunday morning was not penalized for being late. We thank everyone for being prompt with turning in assignments on time.

We categorized assignments into a few basic “types”. For each type, we had things we were looking for in a good assignment. These can give you an idea of what we were thinking.

  1. Single Standard design to show hierarchy (TreeMap, Sunburst, Tree)

    • suggested design
    • deals with overlap somehow
    • consider interactions (details, navigation)
    • actually shows hierachy (vs. level at a time, require interaction)
    • talks about tasks (potential use cases)
    • describes design in detail
    • rationale for details
    • rationale for high level choice (i.e., to use a colored treemap)
    • describes implementation details and how to run
    • extra bells and whistles
    • discussing findings (use case)
    • scalability discussion
  2. Multiple, task-specific designs integrated

    • multiple designs that work together in a system
    • each design is described
    • each design has tasks associated
    • use cases use designs
    • discusses rationale / encoding choices for each design
    • deals with category sharing questions
  3. Multiple Designs, Not-Integrated

    • multiple designs used independently
    • each design is well described
    • rationale for each design given and discussed
    • tasks for each
    • anti-tasks for each (to know when not to use each design – motivation for others)
    • Standard (suggested) vs. Non-Standard designs
  4. Single, Non-Standard (or semi-standard) Design

    • considers multiple tasks with one design
  5. Analysis of a Data Set Using Multiple Views

  6. Sketch of Multiple View System

    • rationale and task thinking must be really good to make up for lack of implementation
    • needs to consider multiple tasks thoroughly
    • needs to consider how different views work together to solve harder tasks
    • discuss encodings and designs and interactions
    • must show creativity in designs (not just standard views)

Previous post:

Next post: