Task Generation The tasks that constitute a parallel algorithm may be generated either statically

or dynamically. Static task generation refers to the scenario where all the tasks are known
before the algorithm starts execution.

Certain decompositions lead to a dynamic task generation during the execution of the algorithm.
In such decompositions, the actual tasks and the task-dependency graph are not

Task Sizes The size of a task is the relative amount of time required to complete it. The
complexity of mapping schemes often depends on whether or not the tasks are uniform; i.e.,
whether or not they require roughly the same amount of time. If the amount of time required by
the tasks varies significantly, then they are said to be non-uniform.

Knowledge of Task Sizes The third characteristic that influences the choice of mapping scheme
is knowledge of the task size. If the size of all the tasks is known, then this information can often
be used in mapping of tasks to processes

Size of Data Associated with Tasks Another important characteristic of a task is the size of data
associated with it. The reason this is an important consideration for mapping is that the data
associated with a task must be available to the process performing that task, and the size and
the location of these data may determine the process that can perform the task without incurring
excessive data-movement overheads.

TYPES OF TASK

System Tasks
Comparison — the system provides information that is useful for comparing pieces of
information
GenerateAlerts — the system generates an alert
Feedback — the system provides feedback about some intensive computational activity
Grouping — the system provides pieces of information that are somehow grouped
Locate — the system provides information useful to locate something
Overview — the system provides an overview of some data
Interaction Tasks
Single Selection — the user interacts with the system to select one piece of information
Multiple Selection — the user interacts with the system to select multiple pieces of
information
Edit — the user interacts with the system to change some piece of information
Control — the user interacts with the system to trigger some functionality
Zooming — the user interacts with the system to change the level of detail presented,
e.g. zooming on a map or photograph
Filtering — the user interacts with the system to filter how some data is visualised, e.g.
to show some aspects and to hide others
DetailOnDemand — the user interacts with the system to ask for some detail on some
item
User Tasks
ProblemSolving — the user performs a cognitive activity to solve a problem
Comparing — the user performs a cognitive activity to compare pieces of information
Planning — the user performs some activity to plan what to do
Abstract Tasks
Search Information — the user performs an iterative search for a piece of information
ELEMENTS OF TASK

 Description: a human-readable task description

 Precondition: a structured pre condition on the task execution
 Postcondition: a structured post condition on the task execution
 ContextOfUse: the suitable context for carrying out the task
 DomainObject: the list of objects manipulated by the current task

CIDRO ZEVASCHEN YZMAEL P.

LAVIÑA JAY MARC B.