|
|
|
ADDIE Development:
Quality Assurance
Learning Objective: The learner will be able to state why quality assurance is necessary and who should perform it.
Those developing the instruction have been working closely with it making it possible for them overlook problems. Quality Assurnace (QA) staff will be new to the content being able to spot problems and inconsistencies as well as deviations from style.
In addition, the quality assurance staff is trained to “torture” the software to the limits of the stated requirements for taking part in the instruction.
QA staff will:
- Lend a fresh eye
- "Torture" the software
- Seek out inconsistencies and unusual behaviors
|
Quality assurance staff is also trained to think like end users and try all kinds of possible controls. They might test running the instruction with keyboard keys only vs. mouse controls. They might click on intuitive and non-intuitive buttons or links to anticipate what would happen if a learner strays.
The feedback from quality assurance needs to be taken seriously and as many of their suggestions as possible should be incorporated. If some suggestions are not possible due to technical limitation, costs, or because the feature is not deemed helpful, document this under the “help” option so that users can find why the interface might have such limitations.
For non-web instrucitons (CD ROM for example), if the issues are with the launching of an application it is standard practice to include the information in the “Readme” text file that may be accessed prior to launching or installing an applicaiton.
If QA suggestions cannot be implemented:
- Document them in the HELP file
- For non-web applications, document install issues in the README file
|
Next go to ADDIE Implementation: Promotion
|
|
|
Top