the features of the user interface that will be most important to novice users like Cindy. 2. The me of a systems development project team have gone out for lunch together, and as often happen conversation turns to work. The team has been working on the development of the user int design, and so far, work has been progressing smoothly. The team should be completing work interface prototypes early next week. A combination of storyboards and language prototypes ha used in this project. The storyboards depict the overall structure and flow of the system, but the developed language prototypes of the actuel screens because they felt that seeing the actual s would be valuable for the users. Chris (the youngest member of the project team]: I read an arti night about a really cool way to evaluate a user interface design. It's called usability testing, and it by all the major software vendors. I think we should use it to evaluate our interface design. H (systems analyst]: I've heard of that, too, but isn't it really expensive? Mark (project manager): I'm it is expensive and I'm not sure we can justify the expense for this project. Chris: But we really in know that the interface works. I thought this usability testing technique would help us prove we good design. Amy (systems analyst): It would, Chris, but there are other ways too. I assumed we thorough walkthrough with our users and present the interface to them at a meeting. We can [ each interface screen so that the users can see it and give us their reaction. This is probably th efficient way to get the users response to our work. Heather: That's true. but I'd sure like to s users sit down and work with the system. I've always learned a lot by watching what they do. where they get confused, and hearing their comments and feedback. Ryan (systems analyst): It se me that we've put so much work into this interface design that all we really need to do is re ourselves. Let's just make a list of the design principles we're most concerned about and ( ourselves to make sure we've followed them consistently. If we have, we should be fine. We want moving on the implementation, you know. Mark: These are all good ideas. It seems like we've a different view of how to evaluate the interface design. Let's try to sort out the technique that's b our project. Develop a set of guidelines that can help a project team like this one select the