TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>An oversimplification if there ever was one. The devil is always in the
details.
>For instance, if there's a data entry slot in a UI form, and there are
upper
>and/or lower limits to the values that can be entered therein, those limits
>are not explicitly apparent to the user, but they should be in the written
>specification. If the range of valid values is stated in the documentation,
>it contributes to the user's conceptual model.
In years past this was certainly the state of things, but I think the point
is that good UI design attempts to build this kind of information into the
UI itself.
