Edc_2011_06 - Chapter 6 Reporting on User and Performance Testing CHAPTER 6 REPORTING ON USER AND PERFORMANCE TESTING Chapter outline The testing

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Chapter 6: Reporting on User and Performance Testing 83 CHAPTER 6: REPORTING ON USER AND PERFORMANCE TESTING Chapter outline The testing record Purpose of the testing record Ethics and the testing record Elements of the formal record Key guidelines for user and performance testing Structure formal summaries of your tests in this way: Methodology : provide details on the mockups, user test guides, and performance test procedures Results : summarize the results in an objective, well-organized way Analysis, conclusions, and limitations : explain what you learned and decided as a result of the tests, and discuss any limitations of the test methodology and results As explained in Chapter 5, testing is the hub of the design process. The ideas your team generates through brainstorming, research, and expert consultations must be tested repeatedly to help you understand how your design will behave and be used in a real-world context. Testing is an indispensable way to mea- sure your early ideas against user requirements so that you can eventually translate those requirements into measurable specifications. Design testing may take many different forms. In the first quarter of EDC, you typically assess your design ideas by asking users to interact directly with your mockups. In EDC 2, you often conduct user testing in addition to devis- ing other ways to evaluate the strengths and weaknesses of your early ideas. But whatever your methods, the information you gain from testing plays a vital role in helping your team determine the final design. For this reason, it is essential that readers of your reports and project note- books understand your testing strategy as fully as possible. What did you hope
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 6: Reporting on User and Performance Testing 84 to learn? What was the rationale behind your test methods? Did testing go well, or did you run into difficulties? Answers to all these questions and more must be provided in writing. This chapter explains the purpose of the testing record, ethical guidelines, and the basic elements of documentation. 6.1 THE TESTING RECORD: ITS FORMS AND FUNCTIONS What does documentation mean in the context of the design testing process? Broadly speaking, the testing record, or documentation, is the full record (including things like sketches, photos, and video) of your formal efforts to evaluate the capabilities of your design. It comprises both the team's prepara- tion for tests as well as what you learned from them, including results and interpretation. As an engineer, you have a professional obligation to document your work— good record-keeping is required, not optional. Every branch of the profession, however, has its own specific standards and practices regarding documenta- tion; you will learn more about them as you progress in your chosen field. This chapter is intended to make you aware of some fundamental principles
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 05/30/2011 for the course MATH 203 taught by Professor Xia during the Summer '00 term at Culver-Stockton.

Page1 / 6

Edc_2011_06 - Chapter 6 Reporting on User and Performance Testing CHAPTER 6 REPORTING ON USER AND PERFORMANCE TESTING Chapter outline The testing

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online