Added by Geoff Sauer on Oct 07, 2003.
Average rating: 3.33/5.00 (n=6, std dev: 1.37)
 


As documentation is more and more built directly into the interface, and as technical communicators move into interface design and usability, it is important to have a theoretical framework within which to make decisions about what kind of information will be conveyed at any moment. We can build on basic principles of cognitive psychology to help us make these decisions. We start from a question: Why should users be aware of the difference between interface and documentation when all they want is to get something done?
 
  View all 62 works by Quesenbery, Whitney  
  View all 2240 works published by STC Proceedings  

Please share your rating/opinion of "Building Documentation into the Interface".
 PoorExcellent 
The link to this work seems to be broken.

Copyright © 2001-09 by the EServer. All rights reserved.Add a Work | Update this Work | Discussion Forum | Habitués