NDLI: Users invoked: How documents help readers assume user roles

Please wait, while we are loading the content...

Designing hypermedia help systems: problems and issues

Business planning in technical documentation organizations

Strategies for designing manuals for hacker styles of learning

Rhetoric and human-computer interaction: investigations into the writing of user-centered documentation

A writing course in user documentation for computer science majors

Writing online help when space is limited

Creating effective hypercard online documentation and training

The relationships between online help systems and print documentation: an empirical investigation

A survey of technical computer users resulting in guidelines for the development of technical computer documentation

Sentence first, verdict afterward: finding the prerequisites for good computer documentation

Users invoked: How documents help readers assume user roles

Conceptual foundations for computer documentation: new distinctions for a new er

A distributed architecture for document management

Software maintenance documentation

Manuals that meet market demands

Forms based documentation to support structured develomemt and C.A.S.E. implementation

The myth and realities of C.A.S.E. for documentation

Maintaining multiple versions of a document

Scribe support in GNU emacs

Usability planning for end-user training

Executable documentation: testing the documentation, documenting the testing

Users invoked: How documents help readers assume user roles

Content Provider	ACM Digital Library
Author	Simpson, M.
Abstract	A typical and often productive response to writing for documentation audiences is to think in terms of types or genres of documentation—reference manuals, tutorials, “using” manuals, quick reference books and cards, and so on. These categories can help writers think about readers, at least the general purposes for which readers consult documentation.Unfortunately these forms of documentation say little about the many local decisions computer users make as they read documentation. Sticht (1985), Diehl and Mikulecky (1981) and others have described how readers may read to do specific tasks or read to learn material. Sullivan and Flower (1986) show that users may not read a manual or section of a manual in its entirety, and that when they do read, they read to answer questions that arise during a task. The implication of this research is that users' purposes for reading are likely to vary and that these purposes may be determined by work-related tasks or problems which occur during the tasks.A question arises, however, about the role of texts in influencing how readers read computer manuals. If readers' purposes for reading come from outside text—a task or problem stemming from a task—do the text themselves influence the readers? Rhetorical theory suggests one answer: that cues in texts invoke reader roles which readers take on as they read.The theory comes to rhetoric by way of literary criticism and rhetoric. Gibson (1949-50), for instance, argues that tests imply a “mock reader,” an entity distinct from the real reader, by marshaling semantic and syntactic cues in a text. The rhetorician Walter Ong (1977) develops this idea further; he explains that the mock or fictionalized reader is actually a role created in the text and that the notion of reader roles is relevant to all writing, not just fictional writing: The “historian, the scholar or scientist, and the simple letter writer all fictionalize their audiences, casting them in a make-up role and calling on them to play the role assigned” (p. 74). Ede and Lunsford (1984) apply the concept of reader roles to composition theory and acknowledge that it is applicable to such nonfictional forms of writing as academic journal articles, business letters, and student academic writing.Although the concept of reader roles has been applied to several kinds of writing, the concept's relevance to computer documentation is largely unexplored. If computer documentation does invoke reader roles, then the notion of roles needs to be considered by writers as they plan and write documentation. Writers would have to be certain that their documents invoke a role consistent with their intended uses. To explore this issue, I decided to re-examine the results of user protocols made during a test of the Microsoft Works V2.0 documentation at the Microsoft Corporation. Microsoft Works is an integrated PC applications program that contains a word processor, spreadsheet, database, and communications program.A major goal of the original documentation test was to determine how well users could navigate in and use the Works V2.0 alphabetic reference.1 The reference combined the features of a typical reference—for example, an alphabetic arrangement of key topics and commands—with features of user's guide, such as conceptual explanations of topics as well as step-by-step guides to commands and tasks. My re-examination of the data from the Works test was prompted by two questions:What kinds of roles might computer documentation invoke, and what cues might invoke them?When users read computer documentation containing role cues, how do users respond to them?In this paper I will answer these questions and explain how the answers can affect the writing of computer documentation.
Starting Page	85
Ending Page	92
Page Count	8
ISBN	089791337X
DOI	10.1145/74311.74322
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1989-11-08
Publisher Place	New York
Access Restriction	Subscribed
Content Type	Text
Resource Type	Article

Central Library (ISO-9001:2015 Certified)
Indian Institute of Technology Kharagpur
Kharagpur, West Bengal, India | PIN - 721302

See location in the Map
03222 282435
Mail: support@ndl.gov.in

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in