Paper details
EGL 1340 students will conduct usability tests of instructional documents in order to acquire feedback on
instructional documents. This feedback will assist teams in revising instructional documents in advance of
the inclusion of the documents in the Recommendation Report.
REQUIRED COMPONENTS
Project teams must supply the following documents for usability testing:
A 250-300-word minimum description of the test plan that describes the Scope, Evaluators, Objectives, and
Metrics as described in the next section.
Digital drafts of instructional documents* for users to test.
*Each team member must create a separate instructional document. Each instructional document should
address a different topic (e.g. download, install, and configure), audience (e.g. lay, managerial, or expert),
or user level (e.g. beginner, intermediate, or expert) related to the semester project.
A recommendation for a device that testers can use to test the instructional document such as a desktop
computer, notebook computer, or mobile device.
A test script* that facilitators will use to introduce testers to the test, guide testers through the test, and
conclude the test with a closing statement.
*Test script should be a minimum of 200-words.
A Survey Form* for testers and any questionnaires or other documents used to facilitate the test and gather
feedback from testers.; An example can be downloaded from Blackboard.
*Survey form should contain at least 5 questions.
A series of at least 3 post-test interview questions for all testers
Test Plan
Project teams must develop a Test Plan that describes the objectives listed below:
Scope:
The test plan identifies criteria team wants testers to evaluate. The test plan should indicate at least 5
criteria for testers to evaluate. Sample criteria include:
Clarity of language
Usefulness of information
Value of images
Structural clarity (i.e. user’s ability to navigate the instructional document).
Grammatical and Mechanical CorrectnessEvaluators:
The test plan should indicate the preferred number of testers the team requires for testing. The optimal
number of testers ranges from 3-5 testers. The plan should describe the preferred testers in terms of
demographic information; for example:
What are tester age ranges?
What are tester occupations?
What are testers’ experience levels with content?
How would testers use the content of the instructional document?
Objectives:
The test plan should indicate what the team hopes to learn from testing. The test plan should indicate at
least three testing objectives that determine success or failure of the document. For example:
Is the document clear?
Is the document useful to the target tester?
Does the document contain useful, informative images?
Metrics:
The test plan should indicate metrics for success by identifying. What kind of feedback determines
success? What kind of feedback determines failure?
For example:
Would high usability scores on two surveys be enough evidence of success?
Would one survey with a low usability score be enough evidence to determine failure?
FACILITATION
Imagine that testing will occur in a semi-controlled setting, such as a classroom or computer lab. Within thatspace, project teams should choose and describe the best testing methodology and monitoring approach.
For example, teams might choose:
Interactive monitoring (monitoring)
A form of testing monitoring where developers can interact with testers by answering questions and
providing solutions to tester challenges.
Hands-off monitoring (unmonitored option)
A form of testing monitoring where developers observe testers but do not interact with testers.
Feedback:
Project Teams are encouraged to use the following techniques to gather feedback from testers during and
after testing.
Surveys
Feedback Forms/Comment Cards
Observations (notes on observations)
Post-Test Interviews
SCORING
Total points possible: 50
Element
Strong
Above Satisfactory
Satisfactory
Weak
Does Not Meet Req.