ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1918 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
Designing from both sides of the Screen
Author:
Ellen Isaacs&Alan Walendowski
ISBN:
0 672 32151 3
Publisher:
New Riders Pub.
Pages:
336pp
Price:
£34-99
Reviewer:
Christopher Hill
Subject:
management
Appeared in:
14-6
Think of the old butler in a black and white movie; speaking when spoken to; anticipating employer's needs; remembering how things were done last time; doing the job with out complaining. Over time, the employer learns how to make requests, spotting that she gets better results if she asks one way rather than another, picking up on his feedback. They develop a good relationship and learn to work together without noticing the interaction. They learn to collaborate.

The premise of this book is that there should be a relationship of collaboration between the user and the software. The software should allow the user to quickly get into a state of flow, where they can focus on the work that needs doing, without having to stop and persuade the software to do the task at hand. Isaacs proposes a number of principles grouped under two main headings.

Don't Impose - make every click count, remember where they put things and remember what they told you.

Be helpful - use visual elements sparingly, make common tasks visible - hide infrequent ones, give feedback, follow conventions, solve problems - don't complain or pass the buck, be predictable and explain in plain language.

The book is split into two parts. The first part describes the principles with many examples of good and bad practice. The principles are easy to grasp and are full of those 'of course' moments. The second part takes the reader through the development of a real project, from talking with the customer to establish the requirement, through to laying out the user interface using storyboards. Only now are the programmers let loose to build the software and the architecture to support the user interface and we see how the initial problems are resolved and for use throughout the project, how to run Usage Studies.

A very easy to read book, yet packed with useful ideas for building collaborative software. Anyone designing and/or building any computer user interface should read the first part of the book and they will find they enjoyed the rest of the book as well. Highly recommended.