Browse Prior Art Database

Task Descriptions as Input to Task Analysis

IP.com Disclosure Number: IPCOM000122989D
Original Publication Date: 1998-Mar-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Sluiman, H: AUTHOR [+3]

Abstract

A set of task properties that make the collection of task descriptions useful for multiple task interaction configurations is disclosed. The properties are generic and encapsulated enough that the description of a task can be reused regardless of the various leading and following tasks. The association of tasks to each other is a separate piece of data collected that is linked to given tasks and their unique properties.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Task Descriptions as Input to Task Analysis

      A set of task properties that make the collection of task
descriptions useful for multiple task interaction configurations is
disclosed.  The properties are generic and encapsulated enough that
the description of a task can be reused regardless of the various
leading and following tasks.  The association of tasks to each other
is a separate piece of data collected that is linked to given tasks
and their unique properties.

      In the domain of doing user or task analysis, tasks are
described with sentences that are analyzed for objects and actions.
In the domain of workflow data flow is used to describe the input and
out put of a task.  The problem is that to provide a solution to a
user you need to actually deal with two different requirement
definition paradigms, and two different information collection
techniques. Neither  of these separate environments have a complete
or comprehensive definition of tasks in the context of task flow.

      Through techniques described in a separate disclosure we
collected data for both paradigms.  This data was captured using two
basic structures.  In our case the structures took form on paper, but
they could equally be done using various graphical techniques on a
computer.

      The first piece of information was what we called a "task
card".  It was simply a single sheet of paper with the following list
of areas to be filled in.
  o  Task Name - to contain a simple name for the task
  o  Task Description - a more verbose explanation of the task
  o  Goals - to contain a description of the objectives for the
      task
  o  Duration - the length of time typically spent doing the task
  o  Frequency - the number of times in a window of time such as
      a day this was executed, or the interval of time between
      executions
  o  Input - the information used as input to the task which is
      also sometimes referred to as the "Entry criteria"
  o  Output - the information that was produced or revised by
      this task
  o  Tools - the static tools used by the executor of t...