VULab Project Scope
Project Name: The Open Virtual Usability Laboratory (VULab)
Prepared by: Ron Owston
Date: October 20, 2008
| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Project Justification/Background
...
Project Goal
To develop and field test version 1.0 of VULab.
Project Description
Usability studies in VULab are organized by project. A project consists of a URL to be tested and optional pre- and post-session survey questions. The application consists of two modules: a researcher module and a tester module. In the researcher module all of the parameters of a project are set (e.g., the url to be tested, the pre- and post-survey questions, user directions, the activation and end date of the project); users are managed; and project results viewed. In the tester module users are presented with the pre-session survey, provided with task instructions, and re-directed to the website being tested. As the tester navigates the site being tested, all screen interactions are recorded; and if the user has a microphone and a 'talk-aloud' protocol to follow [PeterR: where would they get this protocol to follow?], all audio is captured. Once the website testing is completed, the tester is re-directed back to VULab where post-session questions are completed. The research is able to video the recordings and survey responses for each tester and export the data for detailed analysis.
Project Deliverables
VULab 1.0
VULab 1.0 will consist of the following components:
Researcher Module:
- user interface that meets Fluid standards for accessibility and usability
- a log in screen that provides self registration and automatic notification to the administrator of a new registration
- a project creation function to set the URL to be tested, the pre- and post-session questions, and assign users
- a survey tool that allows the researcher to set pre- and post-session questions for the tester
- a tester ID management function to create, modify, and delete tester IDs; assign testers to projects; and to automatically notify testers of their ID
- a reporting function that allows the research to view individual tester's survey responses and videos; view group aggregate survey responses; retrieve subsets of test who meet certain search criteria; and export survey responses and videos
Tester Module:
- user interface that is meets Fluid standards for accessibility and usability
- a project status screen that presents all active projects testers are enrolled in and their status i.e., completed pre survey, visited URL, completed post survey, fully completed. Users should have the option to redo a project which will delete all previous answers and video.
- A presentation module that contains the link to the (optional) pre-session questions, instructions giving the user the specific steps required for a given project, automatic re-direction to the URL to be tested, and the post-session questions
- A recording module (called RASCAL) that records audio from the tester's microphone and video of screen interactions. When testers finish the site navigation they are redirected to post survey.
- re-direction to the URL to be tested with a warning that the session is being recorded.
- A completion screen allowing the user to log out or return to do another project.
Release Schedule
- Release of web interface for testing by the community - Oct 15, 2008
- Release of mock up of RASCAL recording - Oct 17, 2008
- Completion of APIs for phpESP survey tool - Oct 31, 2008
- Integration of RASCAL into web component - Oct 31, 2008
- Full alpha version of VULab - Nov 20, 2008
- Testing and bug fixes completed - Dec 31, 2008
- User management component completed - Jan 15, 2009
- VULab 0.9 released - Jan 31, 2009
- Additional testing and bug fixes completed - Feb 28, 2009
- Version 1.0 released March 31, 2009
Project constraints
The deadline for completion of version 1.0 is March 31, 2009. However, since no tool with the features of VULab has been developed before, considerable research and trial-and-error testing will have to be done and and this makes it hard to accurately predict the time required to accomplish this.
Project assumptions:
...