﻿<rubric course="LIS653" name="final presentation">

<note>
  This document should be read in conjunction with the instructions for the final presentation, as available at 
  http://openlib.org/home/krichel/courses/lis653/admin/final_presentation.html.
</note>
<note>
  According to the syllabus, this assessment has a weight of 10/21 of the final grade, that's just under 50 percent.
</note>
<note>
  The objective assessed in all rubric criteria is Palmer Learning Objective 2.E.
</note>

<crit goal="2E" id="purpose">
  <enun>purpose and history</enun>
  <level val="10">
    containing precise dates, names, version numbers, being clear on the purpose
  </level>
  <level val="8">
    being vague on one of them
  </level>
  <level val="4">
    being vague on two of them
  </level>
  <level val="1">
    being vague on three of them
  </level>
  <reason>
    The students need to understand the factors surrounding the development of the software to be able to make an informed choice about installing it.
  </reason>
</crit>

<crit goal="2E" id="update">
  <enun>development and package update</enun>
  <level val="10">
    numbers on package installation, developer groups, recent development, and planned features
  </level>
  <level val="9">
    missing only one of them
  </level>
  <level val="7">
    missing two of them
  </level>
  <level val="2">
    missing three of them
  </level>
  <reason>
    The students need to assess the dynamics of the uptake of the software before making an choice about installing it.
  </reason>
</crit>

<crit goal="2E" id="architecture">
  <enun>overall architecture</enun>
  <level val="10">
    sets out a clear picture, showing all key concepts, including chronological, locational, logical
  </level>
  <level val="7">
    missing one of them
  </level>
  <level val="5">
    missing two of them
  </level>
  <level val="2">
    missing three of them
  </level>
  <reason>
    This assesses objective 2E, because an understanding of the architecture of the software is critical to its deployment, in particular, in view of the maintenance of dependencies.
  </reason>
</crit>

<crit goal="2E" id="related">
  <enun>related packages</enun>
  <level val="10">
    names at least four related package, is clear on the relationships
  </level>
  <level val="9">
    missing or unclear on relationship with one package
  </level>
  <level val="7">
    missing or unclear on relationship with two packages
  </level>
  <level val="2">
    missing or unclear on relationship with three packages
  </level>
  <reason>
    Information management systems typically feature different software packages that are in relationships to each other. Understanding these relationships is critical to the maintenance of digital information systems. 
  </reason>
</crit>

<crit goal="2E" id="step-by-step">
  <enun>step-by-step instruction documentation</enun>
  <level val="10">
    step by step instructions detail, consistently formated and successful
  </level>
  <level val="4">
    instructions detail and successful but formating is inconsistent
  </level>
  <level val="2">
    installation details missing and have to be supplemented on the day
  </level>
  <level val="1">
    installation unsuccessful
  </level>
  <reason>
    The students need to understand the information system itself so that they can explain it to the others. They also also have to install it to show how the installation works.
  </reason>
</crit>

<crit goal="2E" id="purpose">
  <enun>timing of installations as relative to the complexity of it</enun>
  <level val="10">
    timing exactly to fit into the material 
  </level>
  <level val="9">
    some extra time is available
  </level>
  <level val="4">
    time is missing so that other parts have to be cut
  </level>
  <level val="1">
    time is so short that installations remain incomplete 
  </level>
  <reason>
    The students need to have an understanding the complexity of the task ahead to plan for its execution by others.
  </reason>
</crit>

<crit goal="2E" id="purpose">
  <enun>pedagogical support and error correction</enun>
  <level val="10">
    answers all question successfully, paced so that all can advance 
  </level>
  <level val="9">
    some errors appear but the presenter is able to fix them quickly
  </level>
  <level val="6">
    some stopping time comes from audience members getting stuck 
  </level>
  <level val="1">
    lack of competence of presenter causes frequent long pauses
  </level>
  <reason>
    Without an swift ability to correct problems of others students will not have understood the information management system as a whole. 
  </reason>
</crit>

<crit goal="2E" id="purpose">
  <enun>customization</enun>
  <level val="10">
    overview of all main avenues of customization with three examples
  </level>
  <level val="7">
    overview of most avenues of customizations with fewer examples
  </level>
  <level val="5">
    incomplete overview of main customization avenues
  </level>
  <level val="2">
    most important avenues of customization are left out 
  </level>
  <reason>
    The system needs to be configured for a target user group. The extend of the customization depends on software and the target user group. This rubric element assumes that there will be a least three avenues for customization. I expect at this time, that three avenues for customization can be found for any software package that will be presented.  
  </reason>
</crit>
</rubric>