Jump to content

Task analysis

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 66.9.167.110 (talk) at 03:59, 12 December 2011 (→‎Applications of task analysis). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Task analysis is the analysis of how a task is accomplished, including a detailed description of both manual and mental activities, task and element durations, task frequency, task allocation, task complexity, environmental conditions, necessary clothing and equipment, and any other unique factors involved in or required for one or more people to perform a given task. Task analysis emerged from research in applied behavior analysis and still has considerable research in that area.

Information from a task analysis can then be used for many purposes, such as personnel selection and training, tool or equipment design, procedure design (e.g., design of checklists or decision support systems) and automation.

Applications of task analysis

The term "task" is often used interchangeably with activity or process. Task analysis often results in a hierarchical representation of what steps it takes to perform a task for which there is a goal and for which there is some lowest-level "action" that is performed. Task analysis is often performed by human factors professionals.

Task analysis may be of manual tasks, such as bricklaying, and be analyzed as time and motion studies using concepts from industrial engineering. Cognitive task analysis is applied to modern work environments such as supervisory control where little physical work occurs, but the tasks are more related to situation assessment, decision making, and response planning and execution.

Task analysis is also used in education. It is a model that is applied to classroom tasks to discover which curriculum components are well matched to the capabilities of students with learning disabilities and which task modification might be necessary. It discovers which tasks a person hasn't mastered, and the information processing demands of tasks that are easy or problematic. In behavior modification, it is a breakdown of a complex behavioral sequence into steps. This often serves as the basis for chaining.

The results of task analysis are often represented in task models, which clearly indicate the relations among the various tasks, An example notation used to specify task models is ConcurTaskTrees, whic is also supported by tools freely available.

Task analysis versus work domain analysis

If task analysis is likened to a set of instructions on how to navigate from Point A to Point B, then work domain analysis (WDA) is like having a map of the terrain that includes Point A and Point B. WDA is broader and focuses on the environmental constraints and opportunities for behavior, as in Gibsonian ecological psychology and ecological interface design.

Task analysis and documentation

Since the 1980s, a major change in technical documentation has been to emphasize the tasks performed with a system rather than documenting the system itself.[1] In software documentation particularly, long printed technical manuals that exhaustively describe every function of the software are being replaced by online help organized into tasks. This is part of the new emphasis on usability and user-centered design rather than system/software/product design.

This task orientation in technical documentation began with publishing guidelines issued by IBM in the late 1980s. Later IBM studies led to John Carroll's theory of minimalism in the 1990s.

With the development of XML as a markup language suitable for both print and online documentation (replacing SGML with its focus on print), IBM developed the Darwin Information Typing Architecture XML standard in 2000. Now an OASIS standard, DITA has a strong emphasis on task analysis. Its three basic information types are Task, Concept, and Reference. Tasks are analyzed into steps, with a main goal of identifying steps that are reusable in multiple tasks.

See also

Further reading

  • Crandall, B., Klein, G., and Hoffman, R. (2006). Working minds: A practitioner's guide to cognitive task analysis. MIT Press.{{cite book}}: CS1 maint: multiple names: authors list (link)
  • Kirwan, B. and Ainsworth, L. (Eds.) (1992). A guide to task analysis. Taylor and Francis.{{cite book}}: CS1 maint: multiple names: authors list (link)
  • Hackos, JoAnn T. and Redish, Janice C. (1998). User and Task Analysis for Interface Design. Wiley.{{cite book}}: CS1 maint: multiple names: authors list (link)
  • Brockmann, R. John (1986). Writing Better Computer User Documentation – From Paper to Online. Wiley-Interscience.
  • Carroll, John M. (1990). The Nurnberg Funnel – Designing Minimalist Instruction for Practical Computer Skill. MIT.

Notes

  1. ^ Hackos and Redish, 1998

External links