Keystroke Biometric: Test-Taker Setup and Data Collection

Keystroke Biometric Background: read & understand this section

Project

This semester we will develop a test-taker authentication application that uses the authentication system being refactored by Team 3. We will also obtain additional data samples from a controlled population of subjects.

Your primary tasks on this project are as follows:

Fast Agile XP Deliverables

We will use the agile methodology, particularly Extreme Programming (XP) which involves small releases and fast turnarounds in roughly two-week iterations. Many of these deliverables can be done in parallel by different members or subsets of the team. The following is the current list of deliverables (ordered by the date initiated, deliverable modifications marked in red, deliverable date marked in bold red if programming involved, completion date and related comments marked in green, pseudo-code marked in blue):

Deliverables Common to all Keystroke Projects

Deliverables specific to this project (these can be performed in parallel with the common deliverables):
  1. 10/8 For experimental purposes we need keystroke data samples over time at two-week intervals. Because we would like five sets of data, this will take nine weeks with data sets collected in weeks 1, 3, 5, 7, and 9. Thus, this deliverable will be ongoing from Week 5 (Oct 5) through Week 13 (Dec 10) and include the week of Thanksgiving. You need to sollicit each member of the three keystroke teams (total of 13 subjects) to record five keystroke samples in each of the 5 data collection weeks, for a total of 25 data samples (5 samples at each of 5 recording times). These data are to be collected using the existing data collection method. Obtain details, especially about using the existing data collection method, from your customer Robert Zack.
  2. 10/8 The existing data collection method is okay for obtaining experimental data but not appropriate in an actual test-taker authentication application. We need to deploy the data-capturing Java applet as a stealth method so student test takers will not likely be aware that their keystrokes are being captured. The idea is to create a test where there is one question requiring an answer of at least five 10-word sentences or 50 words (this shuld give us the desired 300 keystrokes, which is 50 words since an average word when including the space between words is six characters). For example, you could open the applet for the answer to the question. In addition to the keystroke data, we need to record the text so the instructor can grade the answer.
    In an actual test-taker setup, we also need five reference keystroke samples. These reference samples can be taken from each student at the beginning of the semester, using questions like "Why are you interested in becoming a computing professional?" or "Describe three outcomes you expect to realize by taking this course." Again, open the applet for answering each question. Then, for an actual test (say, midterm or final exam) the one typed-in answer would be compared to each of the five reference samples to authenticate the test-taker.