in CS Using WeBWorK in CS1 Fall 2005 (Java) –For in-class tests (multiple choice / matching) Spring 2006 (Python) –For in-class tests (multiple choice) –For homework exercises

in CS Preparation More time upfront, less after (currently) Mitigating plagiarism: random ordering of answers in multiple choice questions, parameterization of code in matching questions; x out of y questions Importance of quality assurance Logistics - check clock synchronization, printing individual test papers

in CS Student’s Perspective Positive: –Instant feedback & self-assessment Issues & questions: –Consequence of no hardcopy: annotations, answer elimination? –Matching questions: text box size, multiple answers? –Context: % complete, visibility of progress? –Single attempt: answer commitment (Shock to see results at the click of a button: Where did I go wrong V so what?) –Multiple attempts: can lead to trial & error (How assess?) –Transfer of understanding between own programs & variants: demonstration of real understanding?

in CS Lessons – Professor’s Perspective Positive: –Class size (a helpful teaching assistant!) –Can see who is attempting homework –Quite straight forward to change questions to other programming languages Negative: –Going through solutions in class –Granularity of feedback

in CS Future Tailor questions dynamically to support specific student needs (to challenge or support) Compare mechanism for student learning – references, hints, easier/harder questions Need more granular & visual feedback on performance for students & professors Possibility for alerts: any common problems, trends?