You have read and thought about principles of good interface design, including Shneiderman's eight Golden Rules (Section 2.5 in Designing the User Interface). You have read about design processes and how they can be guided (through Section 3.4 in Designing the User Interface).
Work in teams of three or four people based on the number in the upper right hand corner of this page.
The Three Pillars of Design are features of the design process that "can help user interface architects turn good ideas into a successful system. They rest on established foundations. How can they help us to achieve the eight Golden Rules that characterize good interfaces?
Nothing is as obvious as it seems! When one group proposed that a particular pillar (say, expert reviews and usability testing) best supported a particular golden rule (say, be consistent), another group offered an alternative argument (for, say, guidelines documents and processes).
What exactly is the problem in Task 1? What are the pillars? How can we support a goal?
Which is what each golden "rule" is: a goal. As rules for how to act, they are distinctly unhelpful! The task is to answer this question: Which pillar do you want to rely on as your primary means for achieving the goal? If you could use neither of the other two, which of the three would you choose?
What are "user interface software tools"? Tools that allow programmers to create the interface elements of a program in terms of the interface (menu, window panel, dialog box), not those of a programming language (loops, selections, lines). They allow a sort of consistency among components, as well syntactic features such as short-cut definition.
Of course, all three pillars can and should support each of the golden rules. Answering the 'false question' of which one to use forces you to confront the strengths and weaknesses of each pillar and to identify the relationship between a pillar's support and the goal being achieved. Such "Mission Impossible" tasks can be great learning exercises, even if at the end you realize that the task was impossible. (You may even realize this up front!)
Some ideas to consider:
Several of you liked the emphasis that Beck places on listening, and in particular on deferring thought about how to build the system.
What else did you think of the patterns? Did you agree or disagree with the content? Did you like or dislike the form? Kent is a guy who claims to be "just a programmer" despite being a world-renowned analyst and designer. His patterns are a way for him to share what he has learned--even the obvious parts--in a way that newbies can become developers of good systems sooner.
By now, you should know the golden rules pretty well. Apply the same diligence (and maybe even some of the same exercise ideas!) to study the other material in Chapter 1-2...
You have read several news stories on the case of the killer robot, including a discussion of some of the behind-the-scenes issues in the development of the robot's software.
Work in teams of three or four people based on the number in the upper right hand corner of this page. If yours is an odd number, your magic word is for. If yours is an even number, your magic word is against.
Construct a convincing argument <your magic word> Ray Johnson's Ivory Snow theory. Be sure that your argument...
I realize that you may be put in the position of arguing for a position that you do not personally hold. Make that a part of the fun!