Rating: 
Summary: Excellent, practical how-to book
Review: "Usability Engineering" explains the principles of softwareusability, and clearly outlines techiniques for assesingthe usablility of your product. His techniques give a lot of bang for the buck. There is no excuse not to use them. He makes convincing arguments for the value of incorporating usability into the entire software design and development process. This book is an excellent companion to Cooper's User Interface bible,"About Face".
Rating:
Summary: Excellent, practical how-to book
Review: "Usability Engineering" explains the principles of software
usability, and clearly outlines techiniques for assesing
the usablility of your product. His techniques give a lot of bang for the buck. There is no excuse not to use them.
He makes convincing arguments for the value of incorporating usability into the entire software design and development process. This book is an excellent companion
to Cooper's User Interface bible,"About Face".
Rating: 
Summary: Overly wordy.
Review: Although Neilsen has a lot of good information in here, the information is hidden beneath layers of writing. Every point is repeated several times, and the author is incredibly wordy. As a professional writer, it astounds me that someone could go on about usability without having the faintest idea of how to make his own writing usable. If edited properly, this volume could be reduced to half the size and give exactly the same information. The passive voice just about slaughters this book. One gets the impression that the author thinks he must write in this boring, textbook style in order to be considered "The Book" in the industry. This is unfortunate, because many readers simply won't make it through this book, despite the important information it has to impart.
Rating: 
Summary: 20/20 vision on only 60 percent of the problem
Review: As a Web site designer, I've long been an advocate of JakobNielsen's ideas -- to an extent. Usability is arguably the mostimportant aspect of any design project, and an aspect too often ignored by many software and Web site designers.Mr. Nielsen, in his book, very aptly points out typical errors and common stumbling blocks of interface design, and presents very convincing arguments and methods for solving these problems. However, strict adherence to Mr. Nielsen's interface design techniques, at the expense of less easily measured human factors, will often result in a sterile and boring product. Both are eminently efficient and usable, but are also wonderful examples of visual blandness -- nearly devoid of the human and aesthetic factors that contributes to a depth of personality and a richness of sensory stimulation. Although Mr. Nielsen never specifically advocates this, the logical conclusion of his approach is an interface design whose personality and soul have been stripped away in a slavish preference for pure, unencumbered efficiency and usability. Contrary to Mr. Nielsen's examples, the quest for usability should not abrogate the need to avoid ugliness. For the sake of efficient usability, I wonder if Mr. Nielsen has replaced his impractical, hard-to-maintain backyard lawn with efficient asphalt paving. Or maybe pulled out his expensive, hard-to-clean, dirt collecting, living room carpet and replaced it with an efficient concrete floor. I'm joking of course, but even if Mr. Nielson thinks this way, most do not. Yet, this is the result achieved by many of his user interface examples. Perhaps on the planet Vulcan where everyone thinks like Mr. Spock, Mr. Nielsen's conclusions and methods might be the eminently rational final word on good interface design. But on Earth the value of his conclusions and usability tests must be weighed against the somewhat hard-to-measure and difficult-to-quantify factors of illogical human personality and perception. Although Mr. Nielsen's observations, conclusions and suggestions continue to be very valuable in helping to pull interface design towards much needed greater usability and functionality, his mistake seems to be that this is all he sees as being important. Cory Maylett
Rating:
Summary: A Classic, The Textbook on Usability
Review: I've read some of the criticisms of this book - its wordy, hard to read, etc. I have to say I don't agree. Whenever people ask me to recommend books on software usability, this is always one of the top 5 that I suggest. Its a textbook, not a novel, and it has all the advantages (precise, scientific language) and all the drawbacks of a textbook (dry, dense). However, there isn't any better source on things like how to put together a usability test, how to cost justify usability in the overall design process, or even simply, what the usability process is all about. You can't be serious about software usability if you haven't read this book! And while Jakob's book "Designing Web Usability" is more popular, to me, this one is the better book.
Rating:
Summary: Save your money, read this review:
Review: If his own principles had been applied to the book it could be reduced to a a few bullet points. *the web is slow, less is more. *tell people what a link leads too before they press it, and make sure it does. *use standard fonts in easy to read colours. *use standard web conventions where ever possible as they are familiar. *check for spelling mistakes and grammar errors. *write concisely and arrange depth of detail in hierarchies, like they do in errr reference books. *tell the user where they are, and how they got their, um like a path prehaps. *some people have small screens, some don't even use microsoft browsers, not everyone has the latest plug ins, allow for it. *don't employ frustrated artists to design your site, use an engineer. Jakob proudly states he has multiple patents in the field of usability, maybe following this book will infringe them, or maybe he just kept the good stuff for himself.
Rating: 
Summary: Well worth a read if you want people to use your software
Review: If you are an experienced user interface designer who thoroughly understands what usability is about you probably don't need to read the book (although I would find it strange that you are experienced and did not read this book which is attributed to have coined the term "Usability Engineering"). So who should read the book. Everybody that is going to develop any form of software. No, it won't make you an expert, but it will get you thinking. On the negative side, some of the examples may some be slightly old (but its a 1993 book!). Sometimes you're also going to feel that you could stress this concept in half the space. However, the information and the thought process behind the information is extremely relevant and is well-worth the effort of reading the book. If you are new in software development this book is an absolute must. In a sense it helps you develop "a way of thinking" rather than giving any specifics. However, if you are looking for specifics, Chapter 5 deals with usability heuristics, presenting 10 of them. When looking at the list of 10 heuristics, they may seem obvious, trivial almost. It is quite amazing, however, how often those seemingly trivial things are overlooked or ignored. Just use some programs on your PC... I think it would be worthwhile any software developers time to read Chapter 5 and think long and hard about what is said - then go back to your software and be honest with yourself. It might be some of the best lessons you'll ever learn. In lots of ways this book has everything that classics are made of - except occasionally the ease of reading.
Rating:
Summary: Very good starter
Review: If you are not familiar with usability engineering methods than read this book. It will give you a good overview about the most common techniques. If you are in a big hurry read the executive summary which is also an informative primer, standing for the whole book. The book also provides some usability exercises and includes an extensive and annotated bibliography. The book is very well structured and only shows one "usability problem": it lacks of an index of tables and figures. Therefore I give the book 4 out of 5 stars.
Rating:
Summary: Good for user interface pros, too much for developers
Review: If your specialty is the user interface, you need to read this book. If you are interested in developing a user interface design process, you should read this. If you are a software developer who wants to know how to build good interfaces, skip it. It is too much about perfecting the design process. I was looking for 'use this button for x and this widget for y'. In other words, here are the rules for a good user interface. What I got was 'here is the process for studying users and their interfaces, and here is a mountain of statistics to back it up'. No fault of the author, I just mis-understood what I was getting. Having said that, if you want to make your living studying and perfecting interface design, read this book.
Rating:
Summary: Good for user interface pros, too much for developers
Review: If your specialty is the user interface, you need to read this book. If you are interested in developing a user interface design process, you should read this. If you are a software developer who wants to know how to build good interfaces, skip it. It is too much about perfecting the design process. I was looking for 'use this button for x and this widget for y'. In other words, here are the rules for a good user interface. What I got was 'here is the process for studying users and their interfaces, and here is a mountain of statistics to back it up'. No fault of the author, I just mis-understood what I was getting. Having said that, if you want to make your living studying and perfecting interface design, read this book.
| 
