1988
DOI: 10.1109/47.7821
|View full text |Cite
|
Sign up to set email alerts
|

Factors affecting level of documentation required for user-developed applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

1991
1991
1991
1991

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 17 publications
0
1
0
Order By: Relevance
“…Researchers in the field of rhetoric are in a unique position to critically examine the discourse of the software programming culture because of our interest in the ways in which social practices, particularly discursive practices, function in the making of meaning in the world. However, much of our research into software has focused on increasing the effectiveness of software use by examining issues of documentation (see Liebhaber, 2002;Selber et al, 1996;Walters and Beck, 1992;Barker, 1990;Pierson et al, 1988), usability (see Mirel, 2002;Mirel and Olsen, 1998;Mehlenbacher, 1993), or some combination of the two (see Guillemette, 1989;Velte, 1989). Walters and Beck, for example, argue for a "rhetorical stance" to software documentation that improves the efficacy of the documentation for users through the inclusion of examples, structural frameworks, and persuasive writing techniques.…”
Section: The Symbolic Power Of the Software Programming Culturementioning
confidence: 99%
“…Researchers in the field of rhetoric are in a unique position to critically examine the discourse of the software programming culture because of our interest in the ways in which social practices, particularly discursive practices, function in the making of meaning in the world. However, much of our research into software has focused on increasing the effectiveness of software use by examining issues of documentation (see Liebhaber, 2002;Selber et al, 1996;Walters and Beck, 1992;Barker, 1990;Pierson et al, 1988), usability (see Mirel, 2002;Mirel and Olsen, 1998;Mehlenbacher, 1993), or some combination of the two (see Guillemette, 1989;Velte, 1989). Walters and Beck, for example, argue for a "rhetorical stance" to software documentation that improves the efficacy of the documentation for users through the inclusion of examples, structural frameworks, and persuasive writing techniques.…”
Section: The Symbolic Power Of the Software Programming Culturementioning
confidence: 99%