<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>ACM SIGDOC</title>	<link>http://tc.eserver.org/publisher/ACM_SIGDOC</link>
	<description>A listing of works published by ACM SIGDOC in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>ACM SIGDOC</title>
		<link>http://tc.eserver.org/dir/ACM_SIGDOC</link>
	</image>
	<item>
		<title>Pragmatic DITA on a Budget</title>
		<link>http://tc.eserver.org/35039.html</link>
		<guid>http://tc.eserver.org/35039.html</guid>
		<description>A small documentation team working on a tight budget can now &#xD;use the tool ecosystem enabled by the DITA standard to create the &#xD;sophisticated content that previously required long and expensive &#xD;projects. The author spent just nine person-weeks over three years &#xD;to replace a custom XML system with a DITA system based on a &#xD;combination of off-the-shelf software, authoring conventions, and &#xD;custom scripts.</description>
	</item>
	<item>
		<title>Agile Documentation with uScrum</title>
		<link>http://tc.eserver.org/35040.html</link>
		<guid>http://tc.eserver.org/35040.html</guid>
		<description>uScrum (uncertainty Scrum) is an agile process developed by a &#xD;small team at Altitude Software to manage the process of writing &#xD;user documentation. uScrum manages uncertainty and the unknown, allowing writers to quickly react to changing conditions. &#xD;uScrum uses orders of ignorance to understand the difficulty of &#xD;tasks, allowing the team to effectively prioritize regular work &#xD;together with difficult creative work.</description>
	</item>
	<item>
		<title>Content Management and the Production of Genres</title>
		<link>http://tc.eserver.org/34585.html</link>
		<guid>http://tc.eserver.org/34585.html</guid>
		<description>In this paper, I suggest that granularized content management introduces as-yet-unexplored issues to genres of technical communication. I argue that content management, while it can, as advertised, free content and make it easy to reuse that content in multiple genres, that flexibility can create new problems for genres and genre systems, leading to problematic reuse, inflexible genre systems, rigid and proprietary genres, and uncritical internationalization.</description>
	</item>
	<item>
		<title>Technical Communication Degrees for the 21st Century</title>
		<link>http://tc.eserver.org/33578.html</link>
		<guid>http://tc.eserver.org/33578.html</guid>
		<description>The practice of technical communication, especially for professionals just entering the workplace, is rapidly changing. Companies have higher expectations for degrees in technical communication, a strong foundation in technology, and the ability to function on cross-disciplinary teams alongside technical experts in the design and development process. As the practice of technical communication shifts its focus, academics have the responsibility to be certain that technical communication degree programs have a strong component of such topics as engineering design, programming, human factors, usability, instructional design, and project management, in addition to traditional communication skills. Academic programs have lagged behind practice, largely due to the location of degree programs, departmental reward systems, faculty deficiencies in technology, little depth in fields beyond rhetoric, and lack of exposure to best industry practices. This paper addresses these issues and makes some practical recommendations for catching academe up to practice.</description>
	</item>
	<item>
		<title>Technologizing Change: Rhetoric of Software Implementation at a University Campus</title>
		<link>http://tc.eserver.org/29924.html</link>
		<guid>http://tc.eserver.org/29924.html</guid>
		<description>This paper reports on a study of new software implementation at a university. Seven emails distributed by a central Office of Information Technology were examined for semantic (content) meaning and syntactic (grammatical) function. Semantic findings show a high degree of topical shift. Syntactic findings show a high number of clauses and complements. The analysis also shows how determiners were used to construct &apos;new&apos; information as &apos;given&apos; (presupposition). The paper argues that discursive stability was created by technologizing the rhetoric of implementation. The study concludes by suggesting that a heavy reliance on dependent clauses, along with other features, may be indicative of technologized discourse.</description>
	</item>
	<item>
		<title>How Document Design Helps English Learners Master Science</title>
		<link>http://tc.eserver.org/26855.html</link>
		<guid>http://tc.eserver.org/26855.html</guid>
		<description>Explores how basic, scaffolded technical-writing exercises can help ESL students gain cognitive maturity, practice science literacy, improve their note taking, and use text signals and science idioms more effectively.</description>
	</item>
	<item>
		<title>A Critical Assessment of the Minimalist Approach to Documentation</title>
		<link>http://tc.eserver.org/24090.html</link>
		<guid>http://tc.eserver.org/24090.html</guid>
		<description>Carroll&apos;s (1991) minimal manual has been considered an important advance in teaching first-time users the basics of computer programs. Unfortunately, it is not very clear what minimalism really means. Practitioners, for example, will find it difficult to create their own minimal manual because the principles of minimalism have not been described in enough detail (see Horn, 1992; Tripp, 1990). It is also not yet settled that a minimalist approach is the most effective one because critical experiments have hardly been conducted. This study therefore closely examines the minimalist principles and claims. This paper describes the basic ideas of minimalism, its design principles and how they can be operationalized. A parallel is drawn between a minimalist and constructivist perspective on learning and instruction. Like minimalism, constructivism places a high value on experience-based learning in context-rich environments. Like minimalism, it stresses the need to capitalize on the learner&apos;s prior knowledge as much as possible. And like minimalism, constructivists urge learners to follow their own plans and goals, to make inferences, and to abstract principles from what they experience (see Duffy &amp; Jonassen, 1991, 1992). An experiment is reported that examines the claims of minimalism. Strong and significant gains on several factors were found, all favoring the minimal manual over a control (conventional) manual. The discussion points to several issues that minimalism has yet to address.</description>
	</item>
	<item>
		<title>Declarative Information in Software Manuals: What&apos;s the Use?</title>
		<link>http://tc.eserver.org/22260.html</link>
		<guid>http://tc.eserver.org/22260.html</guid>
		<description>Declarative information is often considered to be of little value to software manual users, for two reasons: some research results state that it is consistently skipped by users, and other research results show that declarative information does not enhance task performance. This study puts these conclusions to the test, because the research underlying them does not support such general conclusions. Two experiments are conducted to collect quantitative data about the selection and use of procedural and declarative information and to investigate whether or not the use of declarative information affects task performance and knowledge. A new technique for measuring information selection was developed for this purpose: the click and read method.</description>
	</item>
	<item>
		<title>Making Sense of Step-by-Step Procedures</title>
		<link>http://tc.eserver.org/22259.html</link>
		<guid>http://tc.eserver.org/22259.html</guid>
		<description>Procedural instructions that consist of only a sequence of steps will probably be executable, but nevertheless &apos;meaningless&apos; to users of technical devices. This paper discusses three features that can make procedural instructions more meaningful: adding functional coordinating information, adding information about the use of the technical device in real life, and adding operational information about how the device works. The research literature supports the effectiveness of the first feature, but offers little evidence that real life elements enhance understanding of instructions. As for operational information, the research suggests that users are willing to read it, and that it contributes to better understanding and performance in the long term, but only if it is closely related to the procedure. As a conclusion, we propose a theoretical framework that assumes three levels of mental representation of instructions: syntactical, semantic, and situational.</description>
	</item>
	<item>
		<title>Educational Models and Open Source: Resisting the Proprietary University</title>
		<link>http://tc.eserver.org/19056.html</link>
		<guid>http://tc.eserver.org/19056.html</guid>
		<description> This paper presents an educational model derived from open source methods for computer programming. The article places this search for an alternative model within a framework of proprietary educational practices that are driven by a need for efficiency and rationalization. As an alternative model, the paper suggests that an open source derived educational process would emphasize collaborative problem based learning, working through drafts, risk taking, mentoring, user testing, releasing early and often. . . . </description>
	</item>
	<item>
		<title>Full Text Available Documentation, Participatory Citizenship, and the Web: the Potential of Open Systems</title>
		<link>http://tc.eserver.org/19057.html</link>
		<guid>http://tc.eserver.org/19057.html</guid>
		<description> Technical communicators have become increasingly interested in how to &apos;open up&apos; the documentation process - to encourage workers to participate in developing documentation that closely fits their needs. This goal has led technical communicators to engage in usability testing, user-centered design approaches, and, more recently, open source documentation. Although these approaches have all had some success, there are other ways to encourage the participatory citizenship that is implied in these approaches. One way is through an open systems approach in which workers can consensually modify a given system and add their own contributions to the system. </description>
	</item>
	<item>
		<title>There&apos;s More Than One Way To Wire That: When Assembly Workers Are Technically Writers</title>
		<link>http://tc.eserver.org/18253.html</link>
		<guid>http://tc.eserver.org/18253.html</guid>
		<description>While technical writing is becoming a more obvious part&#xD;of undergraduate education, it is not uncommon for an&#xD;engineer to face the task of writing documentation&#xD;without much training in the craft of communication.&#xD;Other members of production teams may have received&#xD;even less training, and yet have an equal or greater need&#xD;to have a say in how documentation is produced and what&#xD;it contains.&#xD;In this paper, we will examine a situation in which an&#xD;assembly worker, or system integrator, demanded the&#xD;opportunity to document the appropriate ways to&#xD;assemble complex Test and Measurement systems (for&#xD;evaluating the electronic components of products such as&#xD;PC’s, cars, and cellular phones), and the effects her&#xD;change in roles has had on the production processes for&#xD;both systems and their documentation.</description>
	</item>
	<item>
		<title>Publishing on the Cheap: One Idea That Worked</title>
		<link>http://tc.eserver.org/18242.html</link>
		<guid>http://tc.eserver.org/18242.html</guid>
		<description>For computer centers to eliminate paper documentation is cutting off one’s nose to spite one’s face.</description>
	</item>
	<item>
		<title>ACM SIGDOC Undergraduate Scholarship</title>
		<link>http://tc.eserver.org/15019.html</link>
		<guid>http://tc.eserver.org/15019.html</guid>
		<description>One non-renewable scholarship of $500 will be granted toward school tuition and expenses for the 2003-2004 academic year. The award will be paid directly to the school for crediting to the student&apos;s account.&#xD;&#xD;To assist a student who is pursuing an established degree program in an area of technical or professional communication.&#xD;&#xD;A committee set by the SIGDOC board will evaluate each application with respect to potential future contribution to the field of technical communication. Financial need is not a factor.</description>
	</item>
	<item>
		<title>Web Design Issues When Searching for Information in a Small Screen Display</title>
		<link>http://tc.eserver.org/14077.html</link>
		<guid>http://tc.eserver.org/14077.html</guid>
		<description>In this paper, we report preliminary findings from an experimental study in which twenty-eight users answered questions by performing strategic information searches on web pages. Pages,&#xD;which varied in length from 100 to 850 words, were displayed on&#xD;either a standard, desktop monitor (full-sized) or a palm handheld&#xD;interface (small-screen). Overall, users took more time to perform&#xD;the tasks on the small screen interface, with the break in efficacy&#xD;appearing between 225 and 350 word-lengths. Finally, contrary to&#xD;our hypothesis, participants were similarly accurate across&#xD;conditions.</description>
	</item>
	<item>
		<title>Editing Computer Hardware Procedures for Multimedia Presentation</title>
		<link>http://tc.eserver.org/13961.html</link>
		<guid>http://tc.eserver.org/13961.html</guid>
		<description>Traditionally, technical editors have ensured consistency in the voice, grammar, and terminology of print documentation. As publications departments have moved to delivering online documentation, the role of the editor has varied and expanded. Editing multimedia documentation requires an even wider scope of skills than editing online documentation.</description>
	</item>
	<item>
		<title>Hypermedia Systems in the New Millennium</title>
		<link>http://tc.eserver.org/13963.html</link>
		<guid>http://tc.eserver.org/13963.html</guid>
		<description>This article revisits three past articles about the implications of hypermedia in the 21st century.&#xD;&#xD;Each August, the ACM Journal of Computer Documentation reprints a&#xD;classic article, book chapter, or report along with several analytical commen-&#xD;taries and a response by the author of the classic document. In this context, a&#xD;&apos;classic&apos; document means one that was published at least five years ago but is&#xD;no longer in print. It also means one that raises issues of lasting importance to the profession.</description>
	</item>
	<item>
		<title>Reflections on NoteCards: Seven Issues for the Next Generation of Hypermedia Systems</title>
		<link>http://tc.eserver.org/13964.html</link>
		<guid>http://tc.eserver.org/13964.html</guid>
		<description>NoteCards, developed by a team at Xerox PARC, was designed to support the task of transforming a chaotic collection of unrelated thoughts into an integrated, orderly interpretation of ideas and their interconnections. This article presents NoteCards as a foil against which to explore some of the major limitations of the current generation of hypermedia systems, and characterizes the issues that must be addressed in designing the next generation systems.</description>
	</item>
	<item>
		<title>Successfully Crossing the Language Translation Divide</title>
		<link>http://tc.eserver.org/13962.html</link>
		<guid>http://tc.eserver.org/13962.html</guid>
		<description>Going global is a familiar phrase in today’s competitive business environment. When we hear the phrase “going global” what comes to mind? Most of us think of products being sold in a foreign country. Providing documentation in your customer’s language gives your company the competitive advantage in the global marketplace. For those products to be sold successfully, a clear understanding and communication of the language is imperative. Language translation into each target language presents a host of challenges and choices that must be anticipated and resolved in the source language prior to translation.</description>
	</item>
	<item>
		<title>Cognitive Strain as a Factor in Effective Document Design</title>
		<link>http://tc.eserver.org/13940.html</link>
		<guid>http://tc.eserver.org/13940.html</guid>
		<description>People have a limited amount of cognitive resources.&#xD;Coping with the increasing amount of information&#xD;presented via a software interface strains a user’s&#xD;cognitive resources. If a person has to use documentation, whether on-line or paper, additional cognitive resources are consumed, often overloading the user.&#xD;Using several windows or multi-media&#xD;elements can compound the problem. Unfortunately,&#xD;as Wickens (1992) states, humans are unable to&#xD;manage excessive cognitive strain and they respond&#xD;by getting frustrated, committing errors, shedding&#xD;tasks, or reverting to known methods.</description>
	</item>
	<item>
		<title>Communicating Effectively With Interaction</title>
		<link>http://tc.eserver.org/13943.html</link>
		<guid>http://tc.eserver.org/13943.html</guid>
		<description>The ability to build interactions that support, enable, and improve communication is a valuable skill for help developers, Web-site designers, multimedia content developers, information-rich user interface designers-anyone who designs and develops information to be used online. This paper presents the basics of interaction design for information products and describes some basic underlying human factors and user-interface design principles.</description>
	</item>
	<item>
		<title>Decision Making: A Missing Facet of Effective Documentation</title>
		<link>http://tc.eserver.org/13942.html</link>
		<guid>http://tc.eserver.org/13942.html</guid>
		<description>The old school of software interface design and document writing took the view that if the user could find the information someplace, the user could use it. But simply sticking in details ignores how readers access and process information.</description>
	</item>
	<item>
		<title>Information Design Considerations for Improving Situation Awareness in Complex Problem-Solving</title>
		<link>http://tc.eserver.org/13939.html</link>
		<guid>http://tc.eserver.org/13939.html</guid>
		<description>The conventional techniques for task analysis derive the basic tasks that make up user actions. However, in the complex-problem solving environment, attempts to describe step-by-step actions break down because no single route to a solution exists. Although individual tasks can be defined, task-analysis normally results in the tasks being divorced from context. However, to support complex problem-solving, the design must place the information within the situation context and allow users to develop and maintain situation awareness.</description>
	</item>
	<item>
		<title>Learnability in Information Design</title>
		<link>http://tc.eserver.org/13945.html</link>
		<guid>http://tc.eserver.org/13945.html</guid>
		<description>Design of information used for technical communication of complex products should consider how learnable that information is, and strive to deliver materials that are inherently learnable.The speed of information interchange and the demands of the workplace and school curricula require increasingly minimalist approaches to the material that is made available. People are frustrated by long learning times, and new users of software tools demand rapid absorption of tool capabilities. In addition, many readers of technical information are people for whom English is not their native language.Methods and practices that worked in the period when people were willing to commit to hours of study to understand a topic, or days of practice to master a tool, no longer work in a world based on ?internet time.? To assist our understanding of these trends in learning, this paper addresses three key areas related to learnability: proposing a definition of learnability, showing where learnability and usability intersect, and providing a basis for learnability based on some attributes of human beings.</description>
	</item>
	<item>
		<title>Single Sourcing for Translations</title>
		<link>http://tc.eserver.org/13949.html</link>
		<guid>http://tc.eserver.org/13949.html</guid>
		<description>OCLC Online Computer Library Center has reduced costs and improved quality by using single sourcing in the localization of its services. For its FirstSearch reference service (which provides access to 80 databases for 18,000 libraries in 64 countries), OCLC has been through three phases of localization. Each phase has increased consistency and efficiency and lowered our translation costs. In the first phase of localizing FirstSearch in 1999, we introduced French and Spanish versions. The translation included the user interface screens and the help system. During this phase, we had minimal reuse of text in the interface and help files. The next year, OCLC released a major redesign of that service-with three levels of searching and greatly expanded database help. A separate administrative service and help system were also included. The translation task became much larger, and we needed to optimize the opportunities for text reuse in the system interfaces, help systems, and documentation. In the interfaces, all text strings were categorized and defined as entity strings-reused as needed among functions, databases, and user levels. For help and documentation, the needed content was analyzed and defined in an SGML DTD. Scripts were used to generate 240 help topics from a few SGML files. This approach reduced translation costs and facilitated consistency. Now in the third phase of localization, we are integrating our tool set, implementing a content management system, and adding support for Asian languages. Through this phase, we expect to reduce translation costs and improve quality.</description>
	</item>
	<item>
		<title>&quot;Yes, But Does it Scale?&quot;: Practical Considerations for Database-Driven Information Systems</title>
		<link>http://tc.eserver.org/13946.html</link>
		<guid>http://tc.eserver.org/13946.html</guid>
		<description>This paper explores the process of designing and implementing a database-driven system of online documentation, and putting it live on the web for customers to use. Using real-life examples, it discusses practical considerations for balancing performance, scalability, and reliability.</description>
	</item>
	<item>
		<title>Building a Home-Grown Knowledge Base: Don&apos;t Wait for the Resources—Build a Prototype</title>
		<link>http://tc.eserver.org/14889.html</link>
		<guid>http://tc.eserver.org/14889.html</guid>
		<description>In this presentation, we will discuss why and how we came to build a knowledge base for the Computing Help Desk at MIT. We discuss MIT’s re-engineering&#xD;effort and its impact on the various Help Desk groups&#xD;who were brought together as a single team; how this&#xD;centralizing of Help Desk services created a new&#xD;requirement of getting useful, just-in-time knowledge&#xD;to student consultants, and professional staff; and how&#xD;that requirement helped us approach another goal of our&#xD;re-engineered processes-helping our customers to help&#xD;themselves. We then describe the tool we created and&#xD;how we are using it.</description>
	</item>
	<item>
		<title>The Changing Face of Technical Communication: New Directions for the Field in a New Millennium</title>
		<link>http://tc.eserver.org/13736.html</link>
		<guid>http://tc.eserver.org/13736.html</guid>
		<description>Identifies four different factors shaping the future of technical communication: user-centered design, corporate universities, cross-disciplinary collaboration, and knowledge management. The authors each address how factors once considered external to the field of technical communication are now becoming thoroughly integrated with it. These four studies, in conjunction, suggest how the field of technical communication is becoming increasingly complex and how participants (practitioners, researchers, and educators) will need to adapt to this new terrain.</description>
	</item>
	<item>
		<title>Finding a Home for Technical Communication in the Academy</title>
		<link>http://tc.eserver.org/13737.html</link>
		<guid>http://tc.eserver.org/13737.html</guid>
		<description>The placement of technical communication within an academic curriculum presents an interesting challenge for university administrators and faculty.&#xD;Technical communication is a young discipline that&#xD;borrows content from several older, more established&#xD;disciplines. As a younger discipline, technical&#xD;communication must combine its borrowed&#xD;ingredients from other areas into a new and complete&#xD;offering that can attract research funding for&#xD;professionals in the academy and deliver job&#xD;opportunities for its students preparing to enter&#xD;industry.&#xD;The credibility of technical communication as a new discipline is dependent on its ability to develop a cohesive body of basic and applied research, its ability to manage technological&#xD;change, and its ability to promote its identity among&#xD;an army of competing disciplines.</description>
	</item>
	<item>
		<title>Annual Awards for Contributions to the Field of Technical Communications</title>
		<link>http://tc.eserver.org/13524.html</link>
		<guid>http://tc.eserver.org/13524.html</guid>
		<description>The ACM SIGDOC Executive Board welcomes letters of nomination for the SIGDOC Rigo and Diana Awards. The Rigo Award celebrates an individual&apos;s lifetime contribution to the field of information design, technical communication, and online information design; the Diana Award celebrates the contribution of an organization, institution, or business.</description>
	</item>
	<item>
		<title>ACM SIGDOC (Special Interest Group on Design of Communication)</title>
		<link>http://tc.eserver.org/10178.html</link>
		<guid>http://tc.eserver.org/10178.html</guid>
		<description>The ACM Special Interest Group on documentation provides a forum on documentation and user support for computer products and systems. The SIG studies processes, methods, and technologies for communicating information via printed and online text, hypermedia, and multimedia. Members include technical communication professionals, educators, and researchers, as well as system designers, developers, usability specialists, and managers responsible for producing or supervising the creation of documentation, online help systems, and end user interfaces. SIGDOC offers conferences, a high-quality Web site, and &lt;i&gt;The Journal of Computer Documentation,&lt;/i&gt; a respected quarterly publication.</description>
	</item>
	<item>
		<title>Journal of Computer Documentation</title>
		<link>http://tc.eserver.org/10051.html</link>
		<guid>http://tc.eserver.org/10051.html</guid>
		<description>This quarterly publication of SIGDOC features refereed original articles and classic reprints, always accompanied by open peer commentary essays and multiple, comparative book reviews.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/ACM_SIGDOC.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>