Technical communication in information systems development : The use of cognitive mapping

Research output: Journal Publications and ReviewsRGC 21 - Publication in refereed journalpeer-review

36 Scopus Citations
View graph of relations

Author(s)

Detail(s)

Original languageEnglish
Pages (from-to)269-284
Journal / PublicationIEEE Transactions on Professional Communication
Volume48
Issue number3
Publication statusPublished - Sept 2005
Externally publishedYes

Abstract

Technical communicators can and should play an important role in the development of information systems to improve the usability of the systems. Besides writing user guides and training material, technical communicators can engage in four other tasks to add value to information systems development: acting as user advocate, writing online help, writing system and error messages, and providing advice on interface design. We assert that technical communicators' involvement in systems development should not be tied to a particular development methodology. Instead, they should be associated with four general tasks in systems development: system investigation, analysis, design, and implementation. We then discuss some notable human factors and their impacts on the tasks performed by technical communicators. Three cognitive mapping techniques - causal mapping, semantic mapping, and concept mapping - are introduced as a means to elicit an individual's belief system regarding a problem domain. These cognitive mapping techniques have great potential for overcoming some behavioral and cognitive problems as well as facilitating understanding among stakeholders in the development of information systems. We discuss how technical communicators can apply various cognitive mapping techniques to improve the usability of the resulting information systems. The use of these techniques is illustrated using a case study. © 2005 IEEE.

Research Area(s)

  • Cognitive mapping, Information systems development, Technical communication

Bibliographic Note

Publication details (e.g. title, author(s), publication statuses and dates) are captured on an “AS IS” and “AS AVAILABLE” basis at the time of record harvesting from the data source. Suggestions for further amendments or supplementary information can be sent to [email protected].