For designers and engineers ,analysis is very important. analysis is the genesis of understanding , sorting through and categorizing and correlating the random but creative ideas with user requirements. there are various ways in which analysis can be conducted for use in design and their use can depend on the designers / engineers to implement in the design process
17. Task analysis may be of manual tasks, such as bricklaying, and
be analyzed as time and motion studies using concepts from
industrial engineering.
Information from a task
analysis can 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.
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.
18. Task analysis
Task analysis is the process of
learning about ordinary users by
observing them in action to
understand in detail how they
perform their tasks and achieve
their intended goals.
19. •DEFINITION :
•IT IS A METHODOLOGY TO ASSESS AND REDUCE HUMAN
ERROR
•THE TERM TASK ANALYSIS ( TA ) IS APPLIED TO
ENCOMPASS A WIDE VARIETY OF HUMAN FACTORS
TECHNIQUES.
•USAGE :
•REDUCE POSSIBILE ERRORS / ISSUES / PROBLEMS
IN A TASK OR A COMBINATION OF TASKS.
•AID IN THE DESIGN STAGES OF A NEW SYSTEM
•THE MODIFICATION OF AN EXISTING OR OLD SYSTEMS .
•AS A RETROSPECTIVE MODE DURING DETAILED
INVESTIGATION OF MAJOR INCIDENTS.
20.
21.
22. Task analysis the analysis of how a task is
accomplished, it includes
A detailed description of both
manual and mental activities,
Task and element durations
Task frequency,
Task allocation,
Task complexity,
Environmental conditions,
Necessary clothing & equipment,
&
any other unique factors
involved in / 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.
24. WHAT INFORMATION DOES A TASK ANALYSIS PROVIDE ?
• A DESCRIPTION OF OBSERVABLE ASPECTS OF USER/ OPERATOR
BEHAVIOUR AT DIFFERENT LEVEL OF DETAILS .
• THE STRUCTURE OF THE TASK.
25. A RETROSPECTIVE MODE
AND EXISTING SYSTEM
HOW THE
INCIDENT
OCCURRED / HOW
THE TASK WAS
PERFORMED
PRESCRIBED WAY
OF PERFORMING
A TASK
DIFFERENCE
BETWEEN
THESE WILL
YIELD ISSUES
27. 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 means learning
about users' goals and users'
ways of working. Task analysis
can also mean figuring out
what more specific tasks users
must do to meet those goals
and what steps they must take
to accomplish those tasks.
Along with user and task
analysis, we often do a third
analysis: understanding users'
environments (physical, social,
cultural, and technological
environments).
28. 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.
29. 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.
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.
30. 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
31. Activity analysis
Identification and description of activities in an organization, and
evaluation of their impact on its operations.
Activity analysis determines
(1) what activities are executed,
(2) how many people perform the activities,
(3) how much time they spend on them,
(4) how much and which resources are consumed,
(5) what operational data best reflects the performance
of activities, and
(6) of what value the activities are to the
organization.
This analysis is accomplished through direct observation, interviews,
questionnaires, and review of the work records.
job analysis, performance analysis and task analysis.
32.
33.
34.
35. Performance analysis
1. Finance: Examination of
various financial performance
indicators (such as return on
assets and return on equity) in
comparison with the results
achieved by the competing firms
of about the same size.
2. Human resource
management: Examination of
the performance of current
employees to determine if
training can help reduce
performance problems such as
low output, uneven quality,
excessive waste. See also
activity analysis, job analysis,
and task analysis.
36. job analysis
Also called occupational analysis / human resource audit …….
Detailed examination of the (1) tasks (performance elements) that make up
a job (employee role), (2) conditions under which they are performed, and
(3) what the job requires in terms of aptitudes (potential for achievement),
attitudes (behavior characteristics), knowledge, skills, and the physical
condition of the employee. Its objectives include (a) determination of the
most efficient methods of doing a job, (b) enhancement of the employee's
job satisfaction, (c) improvement in training methods, (d) development of
performance measurement systems, and (e) matching of job-specifications
with the person-specifications in employee selection. Comprehensive job
analysis begins with the study of the organization itself: its purpose, design
and structure, inputs and outputs, internal and external environments, and
resource constraints. It is the first step in a thorough understanding of the
job and forms the basis of job description which leads to job specification.
Also called human resource audit, job study, or occupational analysis. See
also activity analysis, performance analysis, and task analysis.
37. The primary notion of usability
is that an object designed with
a generalized users'
psychology and physiology in
mind is, for example:
More efficient to use—takes
less time to accomplish a
particular task
Easier to learn—operation can
be learned by observing the
object
More satisfying to use
The Think aloud protocol
is a method of gathering
data that is used in both
usability and psychology
studies. It involves
getting a user to
verbalize their thought
processes as they
perform a task or set of
tasks.
38. A USE CASE describes the
interaction between an individual and
the rest of the world. Each use case
describes an event that may occur for
a short period of time in real life, but
may consist of intricate details and
interactions between the actor and
the world. It is represented as a series
of simple steps for the character to
achieve his or her goal, in the form of
a cause-and effect scheme.
Use cases are normally written in the
form of a chart with two columns: first
column labelled actor, second column
labelled world, and the actions
performed by each side written in
order in the respective columns.
User-centered
design (UCD) is
a process (not
restricted to
interfaces or
technologies) in
which the needs,
wants, and
limitations of
end users of a
product, service
or process are
given extensive
attention at each
stage of the
design process.
39. SUMMARIZING :
THE GOAL IS TO ,
UNDERSTAND USER REQUIREMENTS
THE STRUCTURE OF THE SYSTEM
THE ENVIRONMENT IN WHICH THE ACTIVITY
IS CONDUCTED
IN ORDER TO
MINIMIZE UNNECESSARY WORK ,ACTIONS
IDENTIFYING PROBLEMS AND ISSUES
FIND APPROPRIATE SOLUTIONS