![]() The laser printer icon highlights and new things appearĪCTION 4: Click the On button under background printing. | - |ĪCTION 3: Click on current printer type, which is Laser. Window and the following menubar of pulldown File Edit Search Font UtilitiesĪCTION 2: Select "Chooser" from the menu. When you should be using the techniques described in thisĬhapter, either alone or as a group - don't wait until after System designer might use to describe a suggested system to ![]() We've presented this example in the rough format that a To look over the following description of the Chooser andĮxample: Selecting Background Printing with the Mac Chooser Take a few minutes before you read the rest of this chapter (See theĮnd of Appendix M for more thoughts on upgrading systems after The changes would be too disruptive to existing users. Possibly because the structure of the interface is too deeplyĮmbedded in the functionality of the system, or possibly because Later versions of the Mac operating system others haven't, Some of those problems have been corrected in System that was designed with usability and simplicity as The Chooser is an interesting example because it's part of a For our task-oriented evaluations, the task will The Chooser lets the user select printers and Is the "Chooser" in an early version of the Apple Macintosh We'll describe these techniques and show how each one applies to Requires several evaluators who have some knowledge of usability The third approach is heuristic evaluation, a kind ofĬheck-list approach that catches a wide variety of problems but Predict the time that an expert user would need to perform a task,Īnd which forces the designer to take a detailed look at the Second approach is action analysis, which allows a designer to The first approach is theĬognitive walkthrough, a task-oriented technique that fitsĮspecially well in the context of task-centered design. ![]() In this chapter we describe three approaches to evaluating an AnĮvaluation without users won't uncover all the problems either.īut doing both kinds of evaluation significantly improves the Problems that users might have after they get more experience. Every user will have a slightlyĭifferent set of problems, and the testing won't uncover problems Interface designed for a popular personal computer might be usedīy thousands of people, but it may be tested with only a few dozen Good evaluation can catch problems that an evaluation with only aįew users may not reveal. Making it more likely that they will give the design effortĪ second reason for evaluating a design without users is that a Helps build the users' respect for you as a professional, On trivial bugs that you could have caught earlier. Is a courtesy to the users, who shouldn't have to waste time When users do take time to look at yourĭesign, it should be as free as possible of problems. Own work to do, and they're able to devote only limited time However,Īs a designer you'll also need to evaluate the evolvingĭesign when no users are present. Throughout this book we've emphasized the importance ofīringing users into the interface design process. ![]() Credits and Pointers: Heuristic Analysis.Example: One Evaluator's Heuristic Analysis of the Mac Background Printing Controls.Table: Nielsen and Molich's Nine Heuristics.Example: Back-of-the-envelope action analysis.4.2.2 Back-of-the-Envelope Action Analysis.Table: Average times for computer interface actions.Credits and Pointers: Cognitive Walkthrough.Example: Cognitive Walkthrough of Setting Mac Background Printing.4.1.4 What do you do with the results of the walkthrough?.4.1.3 What should you look for during the walkthrough?.HyperTopic: Common Mistakes in Doing a Walkthrough.4.1.2 What's needed before you can do a walkthrough?.4.1.1 Who should do a walkthrough, and when?.Example: Selecting Background Printing with the Mac Chooser.Chapter 4: Evaluating the Design Without Users ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |