initial user stories using Powerpoint format.

967 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
967
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

initial user stories using Powerpoint format.

  1. 1. Test Taker Interface Mockup <ul><li>Create an HTML mockup of the Test Taker interface to support usability evaluation. </li></ul><ul><li>Interface should mockup the login, test type specification, and actual test questions. </li></ul>
  2. 2. Test Question Author Interface Mockup <ul><li>Create an HTML mockup of the Test question author interface to support usability evaluation. </li></ul><ul><li>Interface should mockup the login, test question type specification, and actual test question input procedures. </li></ul>
  3. 3. Administrator Interface Mockup <ul><li>Create an HTML mockup of the administrator interface to support usability evaluation. </li></ul><ul><li>Interface should mockup the login and all associated administrator functionality for the system. </li></ul>
  4. 4. Question Entry <ul><li>A test question author role should support entry of questions, answer(s), and associated explanation into the database. </li></ul><ul><li>Submitted questions do not immediately become available to test takers. First, they must be reviewed and approved by the administrator. </li></ul>
  5. 5. Test report history (test taker) <ul><li>The system can report to a test taker: </li></ul><ul><ul><li>how many times they’ve taken a test </li></ul></ul><ul><ul><li>what their scores were on each test </li></ul></ul><ul><ul><li>dates each test was taken, time required </li></ul></ul><ul><ul><li>percentage errors in each category for each test </li></ul></ul><ul><li>A tabular setting can help the user spot trends over time. </li></ul>
  6. 6. Test Report History (group) <ul><li>Maintain records on: </li></ul><ul><ul><li>How many times any member of the group has taken a particular question, and the percentage of times the question has been answered successfully. </li></ul></ul><ul><ul><li>How many times any member has taken an exam, and trends in scores. </li></ul></ul><ul><li>Useful in establishing what the group needs to focus on, and how close they are to being ready to take the certification exam. </li></ul>
  7. 7. Test Question Improvement <ul><li>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. </li></ul><ul><li>As a test question author, I should be able to review (anonymous) feedback and improve the quality of my questions. </li></ul><ul><li>As administrator, I should be able to both of the above. </li></ul>
  8. 8. Test format options <ul><li>As a test taker, I should be able to choose from among various testing formats: </li></ul><ul><ul><li>“Actual” timed tests, just like the JCE. </li></ul></ul><ul><ul><li>Practice test, no time. </li></ul></ul><ul><ul><li>Category specific test. </li></ul></ul>
  9. 9. User account <ul><li>The administrator role can: </li></ul><ul><ul><li>add users </li></ul></ul><ul><ul><li>delete users </li></ul></ul><ul><ul><li>specify their role </li></ul></ul><ul><ul><li>provide an initial password </li></ul></ul>
  10. 10. Question import/export <ul><li>The database of questions can be exported in XML format. </li></ul><ul><li>A database of questions in XML format can be imported. </li></ul><ul><li>These two features allow question databases to be shared among different groups. </li></ul>
  11. 11. Multi-user login <ul><li>Implement machinery to support multi-user logins. </li></ul><ul><li>The user must log in as one of: test taker, test question author, or administrator. </li></ul>
  12. 12. Question assignment history <ul><li>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. </li></ul>
  13. 13. Change password <ul><li>Test takers, question authors, and administrators should all be able to change their password. </li></ul><ul><li>Administrator should be able to reset a user’s password if they forgot it. </li></ul>
  14. 14. Help File <ul><li>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. </li></ul>
  15. 15. Database repository <ul><li>Implement a database and associated schemas to support one or more of the following: </li></ul><ul><ul><li>Questions and answers </li></ul></ul><ul><ul><li>Category types </li></ul></ul><ul><ul><li>User account information </li></ul></ul><ul><ul><li>User history information </li></ul></ul>

×