Test Taker Interface Mockup

1
Test Taker Interface Mockup

• Create an HTML mockup of the Test Taker interface
  to support usability evaluation.
• Interface should mockup the login, test type
  specification, and actual test questions.

2
Test Question Author Interface Mockup

• Create an HTML mockup of the Test question author
  interface to support usability evaluation.
• Interface should mockup the login, test question
  type specification, and actual test question
  input procedures.

3
Administrator Interface Mockup

• Create an HTML mockup of the administrator
  interface to support usability evaluation.
• Interface should mockup the login and all
  associated administrator functionality for the
  system.

4
Question Entry

• A test question author role should support entry
  of questions, answer(s), and associated
  explanation into the database.
• Submitted questions do not immediately become
  available to test takers. First, they must be
  reviewed and approved by the administrator.

5
Test report history (test taker)

• The system can report to a test taker
• how many times theyve taken a test
• what their scores were on each test
• dates each test was taken, time required
• percentage errors in each category for each test
• A tabular setting can help the user spot trends
  over time.

6
Test Report History (group)

• Maintain records on
• How many times any member of the group has taken
  a particular question, and the percentage of
  times the question has been answered
  successfully.
• How many times any member has taken an exam, and
  trends in scores.
• Useful in establishing what the group needs to
  focus on, and how close they are to being ready
  to take the certification exam.

7
Test Question Improvement

• As a test taker, I should be able to provide
  feedback about the quality of the question. I
  should not be able to see who authored the
  question.
• As a test question author, I should be able to
  review (anonymous) feedback and improve the
  quality of my questions.
• As administrator, I should be able to both of the
  above.

8
Test format options

• As a test taker, I should be able to choose from
  among various testing formats
• Actual timed tests, just like the JCE.
• Practice test, no time.
• Category specific test.

9
User account

• The administrator role can
• add users
• delete users
• specify their role
• provide an initial password

10
Question import/export

• The database of questions can be exported in XML
  format.
• A database of questions in XML format can be
  imported.
• These two features allow question databases to be
  shared among different groups.

11
Multi-user login

• Implement machinery to support multi-user logins.
  
• The user must log in as one of test taker, test
  question author, or administrator.

12
Question assignment history

• Keep track of which questions the user has
  answered correctly and incorrectly before, and
  use this information to (a) reduce the odds of
  getting a question they already answered
  correctly, and (b) increase the odds they get a
  question they got wrong before.

13
Change password

• Test takers, question authors, and administrators
  should all be able to change their password.
• Administrator should be able to reset a users
  password if they forgot it.

14
Help File

• Provide help button that explains how to use the
  system. Help should be specific to the role of
  the current user test taker, test question
  writer, and administrator.

15
Database repository

• Implement a database and associated schemas to
  support one or more of the following
• Questions and answers
• Category types
• User account information
• User history information