A Review of the Event Analysis of Systemic Teamwork Methodology

More documents

Recommendations

Info

HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 HTA. Data regarding the task steps involved, the technology used, interaction between man and machine and team members, decision making and task constraints should be collected. There are a number of ways to collect this data, including observations, interviews, and questionnaires. The technique used is dependent upon the analysis effort and the various constraints imposed, such as time and access constraints. Once sufficient data regarding the task under analysis is collected, the development of the HTA should begin. Step 3: Determine the overall goal of the task The overall task goal of the task under analysis should first be specified at the top of the hierarchy i.e. ‘Land aircraft X at New Orleans Airport using the Auto-land system’ (Marshall et al 2003), ‘Boil kettle’, or ‘Listen to in-car entertainment’ (Stanton and Young 1999). Step 4: Determine task sub-goals Once the overall task goal has been specified, the next step is to break this overall goal down into meaningful sub-goals (usually four or five but this is not rigid), which together form the tasks required to achieve the overall goal. In the task, ‘Land aircraft X at New Orleans Airport using the Auto-land system’ (Marshall et al 2003), the overall goal of landing the aircraft was broken down into the sub-goals, ‘Set up for approach’, ‘Line up aircraft for runway’ and ‘Prepare aircraft for landing’. In a HTA of a Ford in-car radio (Stanton & Young 1999) the overall task goal, “Listen to in car entertainment”, was broken down into the following sub-goals, ‘Check unit status’, ‘Press on/off button’, ‘Listen to the radio’, ‘Listen to cassette’, and ‘Adjust audio preferences’. Step 5: Sub-goal decomposition Next, the analyst should break down the sub-goals identified in step four into further subgoals and operations, according to the task step in question. This process should go on until an appropriate operation is reached. The bottom level of any branch in a HTA will always be an operation. Whilst everything above an operation specifies goals, operations actually say what needs to be done. Thus operations are actions to be made by the operator in order to achieve the associated goal. For example, in the HTA of the flight task ‘Land aircraft X at New Orleans Airport using the Auto-land system’ (Marshall et al 2003), the sub-goal ‘Reduce airspeed to 210 Knots’ is broken down into the following operations, ‘Check current airspeed’ and ‘Dial the Speed/MACH selector knob to enter 210 on the IAS/MACH display’. Step 6: Plans analysis Once all of the sub-goals and operations have been fully described, the plans need to be added. Plans dictate how the goals are achieved. A simple plan would say Do 1, then 2, and then 3. Once the plan is completed, the operator returns to the super-ordinate level. Plans do not have to be linear and can come in any form such as Do 1, Or 2 and 3. The different types of plans used are presented in Table 15. 35
HFIDTC/WP1.1.3/10 Version 2/ 31 October 2005 Table 15 - Example HTA plans Plan Example Linear Do 1 then 2 then 3 Non-linear Do 1, 2 and 3 in any order Simultaneous Do 1, then 2 and 3 at the same time Branching Do 1, if X present then do 2 then 3, if X is not present then EXIT Cyclical Selection Do 1 then 2 or 3 Do 1 then 2 then 3 and repeat until X Advantages Disadvantages • HTA is a technique that is both easy to learn and easy to implement. • The output of a HTA is extremely useful and forms the input for numerous HF analyses, such as error analysis, interface design and evaluation and allocation of function analysis. • Quick to use in most instances. • Comprehensive technique covers all sub-tasks of the task in question. • HTA has been used extensively in a wide range of contexts. • Conducting an HTA gives the user a great insight into the task under analysis. • HTA is an excellent technique to use when requiring a task description for further analysis. If performed correctly, the HTA should depict everything that needs to be done in order to complete the task in question. • The technique is generic and can be applied to any task in any domain. • Tasks can be analysed to any required level of detail, depending on the purpose. • Provides mainly descriptive information rather than analytical information. • HTA contains little that can be used directly to provide design solutions. • HTA does not cater for the cognitive components of the task under analysis. 36
Page 1 and 2: Analysing C4i Activity: A Review of
Page 3 and 4: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 37: HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 89 and 90:
HFIDTC/WP1.1.3/10 Version 2/ 31 Oct
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113:
show all

A Review of the Event Analysis of Systemic Teamwork Methodology

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?