 | |  |  | 

I was excited to receive my copy of Practitioner's Handbook for User Interface Design and Development, because I was in the middle of a new software development project and would be responsible for approving the look and feel of the user interface (UI). I was interested in learning more about evolving standards, the proper selection of interface controls based on users' tasks, the best way to decide on and create UI style sheets for use by the development staff, and the problem of quantifying that elusive quality called usability. I hoped this book would enlighten me with practical examples I could put to immediate use. Unfortunately, in that regard, Practitioner's Handbook for User Interface Design and Development was mostly a disappointment. It might have been better titled A Project Manager's Handbook, because the author's treatment of the topic is extremely broad but not very deep. View both works by Anderson, Darrill View all 350 works published by Technical Communication Online |
 Practitioner's Handbook for User Interface Design and Development http://www.ingentaconnect.com/content/stc/tc/2003/00000050/00000002/art00011
access restricted (by the publisher) to members/subscribers/customers only
Anderson, Darrill Technical Communication Online 2002
Abstract: I was excited to receive my copy of Practitioner's Handbook for User Interface Design and Development, because I was in the middle of a new software development project and would be responsible for approving the look and feel of the user interface (UI). I was interested in learning more about evolving standards, the proper selection of interface controls based on users' tasks, the best way to decide on and create UI style sheets for use by the development staff, and the problem of quantifying that elusive quality called usability. I hoped this book would enlighten me with practical examples I could put to immediate use. Unfortunately, in that regard, Practitioner's Handbook for User Interface Design and Development was mostly a disappointment. It might have been better titled A Project Manager's Handbook, because the author's treatment of the topic is extremely broad but not very deep.
|
 |
 |  |