Analysis Techniques For Man-Machine Systems Design
Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design
NATO UNCLASSIFIEDAC/243(Panel 8)TR/7 - 78 -Volume 24.4 INFORMATION/ACTION OR ACTION/INFORMATION TABULATIONSWhat the technique doesMasSfunThese are comparatively simple techniques for conducting a task analysis which emphasizes the informarion requiredby the operator to perform his or her task. Both analyses are hierarchical: they are based on those functions whichhave been allocated to the operator(s). Each function is analysed in turn to identify the operator's tasks. The 5.4.information/action analysis starts by analysing the information related to each function in sequence and defining theoperator's tasks, and the actions associated with each item of information (see Drury et. al., 1987; Meister, 1985;Woodson, 1981). The actionfinformation analysis is conducted by analysing an operator's tasks and actions insequence, as a series of discrete steps, to identify the information required for each action.Inputs to the techniquesThe analyst/user requires information on the actions tobe taken by the operator, or, conversely, the informationwhich the operator will be given by a specific systemstate.Outputs of the techniquesThe techniques produce tabulations of the informationprovided to the operator, the action taken upon receipt ofthe information, and optionally, the feedback to theoperator.5.4When to useThe techniques are of use in concept development, and particularly, in preliminary design. They may be preceded byone of several types of function analysis: Function Flow Diagrams (2.1), Sequence And Timing (SAT) analysis(2.2), Information Flow and Processing Analysis (2.4). They may be incorporated into Requirements AllocationSheets (3.5). Information/Action, or Action/Information analyses produce information which can be used either formore detailed task analyses (4.5), for display concept development or analysis of Critical Design Requirements (6.2),for Error Analysis (5.7), or for Link Analysis (6.3).MiFL1lRelatedtechniquesThe techniques are two of several tabular task-analysis techniques all of which analyse the operator's tasks as a seriesof actions in response to information inputs.Resources requiredThe analyst requires the information identified under "inputs." No technical resources are necessary, but a computersystem is recommended to keep track of the many details that are created, and to facilitate modification.tNATO UNCLASSIFIED- 78 -
NATO UNCLASSIFIED- 79 AC/243(Panel-8)TR/7Volume 2Table 4.2:Example of information/action analysis- Mission segment: Aircraft approach to sonar dip positionFunction: 5.4.7 Engage /Monitor Automatic Flight Control System (AFCS) for Automatic Approachc, Task No. & Task Initiating Action response(s)lstimulus/information5.4.7.1 (a) Engage AFCS for automatic Pre-approach checks completed. Adjust AFCS for approach to dip.e approach Aircraft within automatic approach "Approach to dip" mode indication.profile criteria.Required approach profile. Actuate AFCS engage.AFCS operating status.AFCS "Approach to dip enabled"Proceduresindication.5.4.7.2 (b) Monitor a/c during automatic AFCS approach to dip. Monitor (visuaIaircraftapproachperformance.Aircraft flight parameters (transition).AFCS operating status.Aircraft movement rclative to desiredhover poinLTable 4.3:Example of action/information requirements analysisYMission segment: Aircraft approach to base.Function: 1.0 Initiate pre-approach proceduresAction requirements Information requirements Related information,sources. and problems1.0.1 Review approach information 1.0.1.1 Approach orientation. Position data1.0.1.2 Approach constraints: Approach path data:RequirementsCourse & path dataObstaclesObstacle locations-izardsTerrain characteristicses Weather Minimum decision altitudes1.0.2 Coordinate approach with 1.0.2.1 Communication: Coordination & confirmation ofcontrol Path dcsienation approach clearance.Limitations & constraints Altimeter settingEnvironmental conditionsAdvantagesUsers report the techniques to be fast and easy, providedthat the level of detail does not become excessive. It hasbeen found useful for deriving test criteria for mockupreviews and for some test & evaluation (T&E) activities.DisadvantagesThe analysis can become time-consuming if the level ofdetail is not controlled. Standardization of terms for tasksand information is recommended to avoid confusion.NATO UNCLASSIFIED- 79 -
- Page 142 and 143: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 144 and 145: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 146 and 147: -NATO UNCLA,)irrILUAC/243(Panel 8)T
- Page 148 and 149: N A T O U N (.LA5\ 1I r i iL-AC/243
- Page 150 and 151: NATO UNCLASSIFIED EAC/243(Panel 8 T
- Page 152 and 153: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 154 and 155: NATO UNCLASSIFIEDA-AC/243(Panel 8)T
- Page 156 and 157: NATO UNCI ASSIFIEDC/-43(Panel 8)TR/
- Page 158 and 159: NATO UNCLAS.SIFIEDAC/243(Panel 8)TR
- Page 160 and 161: NATO UNCLASSIFIED 2AC/243(Panei 8)T
- Page 162 and 163: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 164 and 165: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 166 and 167: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 168 and 169: NATO UNCLASSIFTEDAC/243(Panel 8)TR/
- Page 170 and 171: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 172 and 173: NATO UNCLASSIFIEDAC/243(Panel 8 TR/
- Page 174 and 175: NATO UNCLASSIFIEDAC/24 3 (6PanelVol
- Page 176 and 177: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 178 and 179: NATO UNCLASSIFIEDAC/243(Panel 8'tTR
- Page 180 and 181: N ATO UNCLASSIFIEDAC/243(Panel 8')T
- Page 182 and 183: NATO UNCLASShi Ih I t LUAC/243(Pane
- Page 184 and 185: NATO UNCLASSIFIED,AC/243(Panel 8 TR
- Page 186 and 187: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 188 and 189: NATO UNCLASSIFTEDAC/243(Panel 8')TR
- Page 190 and 191: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 194 and 195: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 196 and 197: NATO UNCLASSIFIEDAC/243(Panel 8')TR
- Page 198 and 199: NATO UNCLASSIFIEDAC/243(Panel 8ITR/
- Page 200 and 201: NATO UNCLASSIFIUEUAC/243(Panel 8)TR
- Page 202 and 203: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 204 and 205: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 206 and 207: t NATO UNCLASSIFlEDAC/243(Panel 8)T
- Page 208 and 209: NATO UNoCLASSIFIEDAC/243(Panel 8)TR
- Page 210 and 211: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 212 and 213: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 214 and 215: NATO UN CL A S SIFIEDAC/243(Panel 8
- Page 216 and 217: NATO UNCLAS.SIFI.EDAC/243(Panei 8Vo
- Page 218 and 219: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 220 and 221: fl1106AC/243(Panel 8'TR/7- 106Volum
- Page 222 and 223: NATO UNCLASSIFIED -AC/243(Panel 8)T
- Page 224 and 225: .N AI U N C L A Itt110iAC/243(Panel
- Page 226 and 227: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 228 and 229: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 230 and 231: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 232 and 233: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 234 and 235: ] NATO UNCLASSIFIEDAC/243(Panel 8)T
- Page 236 and 237: VNATO UNCLASSIFIED;-AC/243(Panel 8'
- Page 238 and 239: NATO UNCLASSIFIED1111wAC/243(Panel
- Page 240 and 241: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
NATO UNCLASSIFIEDAC/243(Panel 8)TR/7 - 78 -Volume 24.4 INFORMATION/ACTION OR ACTION/INFORMATION TABULATIONSWhat the technique doesMasSfunThese are comparatively simple techniques for conducting a task analysis which emphasizes the informarion requiredby the operator to perform his or her task. Both analyses are hierarchical: they are based on those functions whichhave been allocated to the operator(s). Each function is analysed in turn to identify the operator's tasks. The 5.4.information/action analysis starts by analysing the information related to each function in sequence and defining theoperator's tasks, and the actions associated with each item of information (see Drury et. al., 1987; Meister, 1985;Woodson, 1981). The actionfinformation analysis is conducted by analysing an operator's tasks and actions insequence, as a series of discrete steps, to identify the information required for each action.Inputs to the techniquesThe analyst/user requires information on the actions tobe taken by the operator, or, conversely, the informationwhich the operator will be given by a specific systemstate.Outputs of the techniquesThe techniques produce tabulations of the informationprovided to the operator, the action taken upon receipt ofthe information, and optionally, the feedback to theoperator.5.4When to useThe techniques are of use in concept development, and particularly, in preliminary design. They may be preceded byone of several types of function analysis: Function Flow Diagrams (2.1), Sequence And Timing (SAT) analysis(2.2), Information Flow and Processing <strong>Analysis</strong> (2.4). They may be incorporated into Requirements AllocationSheets (3.5). Information/Action, or Action/Information analyses produce information which can be used either formore detailed task analyses (4.5), for display concept development or analysis of Critical <strong>Design</strong> Requirements (6.2),for Error <strong>Analysis</strong> (5.7), or for Link <strong>Analysis</strong> (6.3).MiFL1lRelatedtechniquesThe techniques are two of several tabular task-analysis techniques all of which analyse the operator's tasks as a seriesof actions in response to information inputs.Resources requiredThe analyst requires the information identified under "inputs." No technical resources are necessary, but a computersystem is recommended to keep track of the many details that are created, and to facilitate modification.tNATO UNCLASSIFIED- 78 -