With constantly changing deadlines and last minute major revisions, how can technical writers ever hope to create quality documents? Members of the STC Quality Special Interest Group (SIG) will present some basic concepts that will provide insights into ways you can improve the quality of your documentation. They will look at what is meant by 'quality documentation', how documentation quality can be measured, how quality can be implemented in documentation processes, how ISO 9000 requirements can be adapted to help improve the documentation process, and how the relationship between developers and writers can impact documentation quality.
Rupel, Roberta A., Lori H. Fisher, Donald S. Lenk, Ralph E. Robinson and Richard Colvin. STC Proceedings (1999). Articles>Writing>Quality>Technical Writing
Developing a Documentation Process that Works in a Regulated Environment 
Working in a regulated environment (for example, an ISO-certified company or a company regulated by the FDA) necessarily changes the way documentation is developed and managed. The documentation development process must exist and must meet all of the requirements set by the governing body, yet not be so mired in detail that it overwhelms the writers and managers.
Rupel, Roberta A. STC Proceedings (2000). Presentations>Documentation
Going Online: A Case Study in the Development and Implementation of Netscape NetHelp 
Computerized Medical Systems, Inc. (CMS) - the worldâ*™s leading radiation therapy planning (RTP) company with over 1000 installed RTP systems and over 400 installed dosimetry systems - decided in late 1996 to move existing FOCUS documentation online. Reasons for this included: the existing documentation set perceived as too difficult to use; increasing printing cost; and customer feedback. Using Netscape NetHelp as a basis, the CMS documentation staff reduced printed documentation size by two-thirds while making the information more accessible. Reactions to FOCUSHelp have been highly favorable. Future plans include migrating to the NetHelp2 framework and reducing topic lengths.
Rupel, Roberta A., Ellard Douglas, Bill Bledsoe and Frank Watson. STC Proceedings (1998). Articles>Content Management>Documentation>Help
Users have goals when they use software applications. Their goal is NOT to 'use' the application. Their goal is to complete an activity or task using the application. Performance support is defined as providing users what they need to be successful in completing their activity or task when they need it – at the point of need. Technical communicators can benefit from incorporating performance support elements into their work, even if they are not creating a performance support system.
Rupel, Roberta A. STC Proceedings (2003). Articles>User Interface>Usability>EPSS
Online Help: You Think It's Documentation but Your Company Thinks It's Software 
As help systems become more complex, integrating text with multimedia, scripting languages, search engines, etc., the line between documentation development and software development blurs. Some companies, especially those that have to adhere to federal or ISO-regulated procedures, are starting to look at online help as a product with its own development needs. This shift is changing the online help from documentation into software, subjecting it to the same controls and processes. This paper looks at how one company is handling this transition.
Rupel, Roberta A. and Peggy Schillinger. STC Proceedings (1999). Articles>Documentation>Online>Help
Processes, Roles, and Regulations: (Re)defining What Technical Communicators Do 
Understanding how you work (process) and understanding what you do (roles) are two important aspects of a successful documentation group that works within a regulated environment. These items will help writers produce better documentation and provide a way to better define (or redefine) their roles in the development process.
Using HTML to Deliver Context-Sensitive Online Help 
Computerized Medical Systems needed to develop content-sensitive online help for a UNIX-based application. We found that this could be done using standard HTML, with each help topic in its own file and displayed in a web browser. With careful planning, we were able to create a map of the applications coded pages to our help files, giving us context sensitivity. We were able to add both keyword and full-text search capabilities. Site management is done using a source control system and a set of link check and HTML validators.
Rupel, Roberta A. STC Proceedings (1999). Articles>Documentation>Online>Help
Looking at the evolution of quality may help to explain how we got to this point.
Rupel, Roberta A. STC Proceedings (1999). Presentations>Quality
There are 14 readers currently online: 1 registered user and 13 guests. Register.

![]()
![]()


![]()
![]()
![]()