Texts
·
Thomas T. Barker, Writing Software
Documentation: a Task-Oriented Approach (Longman) [Barker]
***
·
David Farkas, "The Logical and Rhetorical
Construction of Procedural Discourse," Technical Communication
46.1 (1999) 42-54.
·
Julie Fisher, “Technical communicators and online help: The developers' and users'
perspectives,” Technical
Communication 46.3 (1999) 360-365.
·
Trevor Grayling, "Fear and Loathing of the
Help Menu: A Usability Test of Online Help," Technical Communication
45.2 (1998) 168-179.
·
Trevor Grayling, “If we build it, will they come? A usability test of two browser-based
embedded help systems,”
Technical Communication 49.2 (2002) 193-209.
·
Jean A. Pratt, "Where Is the Instruction in
Online Help Systems?" Technical Communication 45.1 (1998)
33-37.
·
Roberta Shroyer, “Actual readers verus implied readers: Role conflicts in Office 97,”
Technical Communication 47.2 (2000) 238-240.
·
Jan H. Spyridakis, “Guidelines for
Authoring Comprehensible Web Pages and Evaluating Their Success,” Technical
Communication 47.3 (2000) 359-382.
·
Tomasi and Mehlenbacher, "Re-engineering
Online Documentation: Designing Examples-Based Online Support Systems," Technical
Communication 46.1 (1999) 55-66.
·
Zubak, "What Does HTML-Based Help Look
Like?" News & Views 33.4 (1998) 1, 9-12.
***
·
Karen Shriver, Revising Computer
Documentation for Comprehension: Ten Exercises in Protocol-Aided Revision
CDC Technical Report No. 14,