►Software Engineering
▼In-Class Reviews
    contents    up   

Evaluating a Panelist🔗

As a panelist, you will play three different roles:

  • head panelist; as such you are responsible to keep the presentation on track;

  • assistant panelist; you and the head panelist find mistakes, omissions, and questionable design decisions;

  • recorder; you keep track of the questions that the other panelists ask, notes discoveries of problems, takes notes, and summarizes the to-do items as a memo.

When we evaluate the quality of the panelists, we are focusing on these points:

  1. OK+ means the panelist discovers solid problems and articulates them well. This appears to depend on the quality of the code basis. Because all code bases are somewhat flawed, however, the quality of the presented code doesn’t really affect your ability to get this grade.

  2. OK means the panelist asks pertinent questions and discovers some problems.

  3. OK- means the panelist asks questions and some of them are pertinent.

  4. ZERO means the panelist didn’t ask any questions or asked too few questions pertinent to the code/design at hand.

A recorder who asks pertinent questions receives bonus points.

    contents    up