The purpose of this assignment is to demonstrate the importance of the final test report and to illustrate the complex rhetorical challenges of preparing such a report. Usability reports are often the only part of the process seen by other developers and other departments. They can also have implications for external bodies, including government agencies, licensing and safety boards, consumer groups, the media, and even the general public. The most difficult rhetorical challenge in a test report is that of offering areas for improvement to the developers who created the item you have tested in a persuasive way.
Using the examples provided by Barnum (Chapter 9), previous student examples, and our discussions in class, prepare a final test report for internal distribution in the organization whose product or service you have tested.
Your report should include both the results of your testing and recommendations for action to be taken to improve the document you tested, including priorities for each of the recommendations you make.
- onboarding to website NCSU’s SciStarter home.
- onboarding to projects within NCSU’s SciStarter home.
- creating projects
- data contributions to projects
- to recruit inclusive or potentially underrepresented users
- to lower cognitive burden for participation
- to improve information architecture for install base
- Usability test report document
- Google document and with comments enabled
- 20ish pages
- all drafts and work should be submitted through Moodle using a single Gsuite link.