Analysis Techniques For Man-Machine Systems Design
Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design
ACP243(Panel-8)TRn 2.Volume 2INTRODUCTION: OVERVIEW OF HUMAN ENGINEERING ANALYSISTECHNIQUESThis Volume consists of two parts and three appcndices. In this. Part 1. thirty-one analysistechniques which have been used by human engineering specialists are reviewed to a standard format in Part2, examples are given of different functional analyses of systems. Part I is divided into six sections whichcorrespond to the classes of human engineering analysis techniques:(1) system missions(2) system functions(3) system operator and maintainer functions(4) system operator and maintainer tasks(5) workload and possible errors of the system personnel(6) requirements for displays, controls, workspace and inter-personnel communicationas discussed in Volume 1. Most of the techniques reviewed permit the designers and developers of equipment andsystems to define, structure and decompose relevant information: they are not algorithms which transform input data.Thus they require some learning or experience. Each stage of analysis produces information for subsequent analyses(Figure 0.1).task sequences,Submissn.8-- ....... frequencies .|wtimes ands a2-dedn6; inteface &s -:-: .: ......... .ga atysi.rerequremensn/seq nt A -......Ioperatoractions-E--3. function :: D& times dictated-Aaocationperthemission phase, - -1 Iteracdistance, threat 0 I for tions fo in t analyses:&corresponding , V f- : : -- :iegnNo\requirementsIenvironmental to mission ,data phases operator/ \\ dictated by-, decomposed maintainer r X operatorto lower level functions A performance jfunctions corresponding ask sequence< om sinfrequencies, ...... ..... .:phases tie n -p~frmance.x v ~performance |requirements g : :tsk & tasksqec A/times, probityocompletionwrlaand likely errorsFigure 0.11: Information flow in the sequence of human engineering analysesN ATO U.N-C-LA S.SIFIED-2 -
NATO UNCLASSIFIED-3 - AC/243(Panel-8)TR/7Volume 21 MISSION AND SCENARIO ANALYSISmission &scenarioanalysis -bfunctionndinterface\functionworkspaced t b allocartiona aasi codesign1.1 * Narrative missiondescriptionss \ I ~analysis ; =1.2 Graphic T mission profilespredictionWhat the techniques doanalyses oese define the overall requirements of the system under developmeGs, in terms which provide informationfor subsequent human engineering analyses. They are uscd to devrl e what the system must do (the operationalrequirement) and the circumstances and environment in which it must be dones.BackgroundIdeally, the basis for the development of mission and scenario analysis should be the operational analysis conducted Loestablish the requirements for a new system (NATO Mission Need Document). In practice, however, the operationalanalyses are seldom available to the project personnel resign criter ign and developmBnt. The operationalf rM e terms most frequently used for these activities arr mission analysis, mission profiles, and scenarios.The user should be aware of possible problems with these terms. Generally, a scenario is a "sketch or plot of aplay, giving particulars of the scenes, situations etc." (Oxford English Dictionary), and a mission is "a clear,concise statement of the task of the command and its purpose" (NATO Glossary of Terms and Dcefiitions).Thus a "scenario' is often taken as the higher, overall level from which the analysis starts, and the "mission" istakcen as a lower, more specific level of analysis.In the USA, however, the term mission analysis is taken as "the first step in the system development,required for the establishment of human factors design criteria" (DoD-HDBK-763), and "scenarios are developedfrom the threat/concept and the mission profiles, and they must fully describe Mhe events implied by the profile."In practice these differences in terminology can lead to confusion, particularly in discussions between theprocuring agency and the performing agency (whether government or contractor).NATO UNCLASSIFIED-3-
- Page 66 and 67: NATO UNCLASSIFIEDAC/243(Panel-8Y)1=
- Page 68 and 69: NATO UNC LAS SIFIE.DAC/243(Panel-8)
- Page 70 and 71: NATO UNCLASSIFIEDAC,243(Panel-8)TRt
- Page 72 and 73: NATO UNCLASSIFIEDAC/243(Panel-8)TR1
- Page 74 and 75: I1.AC/243(Panei-89)TRP.Volume INATO
- Page 76 and 77: AC/243(Panel-87TR/7Volume I- 60 -Ta
- Page 78 and 79: NATO UNCLASSI.FIEULACP243(Panel-8)T
- Page 80 and 81: NATO UNCLASSIFIEDAC/243(Panel-8)TR1
- Page 82 and 83: NATO UNCLAS SIFIEDAC8243(Pane1-8)TR
- Page 84 and 85: NATO UNCLASSI-ItLAC/243(Panei-8)TR1
- Page 86 and 87: NATO UNCLASSIFIED.,AC1243(Panel-8)T
- Page 88 and 89: NATO UNCLASSIFIEDACM43(Panel-g)T1-7
- Page 90 and 91: NATO UINCLASSII ri.uACP243(Panei-8)
- Page 92 and 93: NATO UNCLASSIFtiEUACI243(Panei-8)TR
- Page 94 and 95: AC1243(Panel-8)TRnVolume I- 78 -.al
- Page 96 and 97: ANNEX I toA~43(Panei-9)TRf7-Volume
- Page 98 and 99: ANNEX I toAC/243(Panei-8)1=7 -Volum
- Page 100 and 101: ANNEX Ito6Aca41(Pane}-8)TRn7VolumL
- Page 102 and 103: ANNEX I toAC43(Pane-8TR7 - 8 -Volum
- Page 104 and 105: N1 A l O oJN k-~ L i-* 3 3 1 i- XAN
- Page 106 and 107: NATO UNCLASSIFIED. aNORTH ATLANTIC
- Page 108 and 109: N A T OU N C L A S S I F I E DREPOR
- Page 110 and 111: NATO UNCLASSIFIEDACQ243(Panei-88)TR
- Page 112 and 113: AC243(Panel-8)TR7-Volume 25.6 NASA
- Page 114 and 115: N A T O U N CLASIF l IE DAC/243(Pan
- Page 118 and 119: N ATO UN CLA .3 -c,,i! EAC/243(Pane
- Page 120 and 121: NATO UNCLASS.IFIED-AC/243(Panel 8)T
- Page 122 and 123: AC/243(Panel 8)TR/7 -8 -Volume 21.2
- Page 124 and 125: AC/243(Panel 8)TR/7 10Volume 2weath
- Page 126 and 127: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 128 and 129: N A I UU N k L A A a Ir I DAC/243(P
- Page 130 and 131: NATO UNCLASSIFIEDMAC/243(Panel 8ITR
- Page 132 and 133: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 134 and 135: NATO UNCLASSIFIEDAC/243(Panel 8)TR/
- Page 136 and 137: N ATIO U N C LA . 3 i F L- < D-AC/2
- Page 138 and 139: NATO UNCLAS S I.FIEDAC/243(Panel 8'
- Page 140 and 141: NATO UNCLASSIFIEDAC/243(Panel 8TR/7
- 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/
ACP243(Panel-8)TRn 2.Volume 2INTRODUCTION: OVERVIEW OF HUMAN ENGINEERING ANALYSISTECHNIQUESThis Volume consists of two parts and three appcndices. In this. Part 1. thirty-one analysistechniques which have been used by human engineering specialists are reviewed to a standard format in Part2, examples are given of different functional analyses of systems. Part I is divided into six sections whichcorrespond to the classes of human engineering analysis techniques:(1) system missions(2) system functions(3) system operator and maintainer functions(4) system operator and maintainer tasks(5) workload and possible errors of the system personnel(6) requirements for displays, controls, workspace and inter-personnel communicationas discussed in Volume 1. Most of the techniques reviewed permit the designers and developers of equipment andsystems to define, structure and decompose relevant information: they are not algorithms which transform input data.Thus they require some learning or experience. Each stage of analysis produces information for subsequent analyses(Figure 0.1).task sequences,Submissn.8-- ....... frequencies .|wtimes ands a2-dedn6; inteface &s -:-: .: ......... .ga atysi.rerequremensn/seq nt A -......Ioperatoractions-E--3. function :: D& times dictated-Aaocationperthemission phase, - -1 Iteracdistance, threat 0 I for tions fo in t analyses:&corresponding , V f- : : -- :iegnNo\requirementsIenvironmental to mission ,data phases operator/ \\ dictated by-, decomposed maintainer r X operatorto lower level functions A performance jfunctions corresponding ask sequence< om sinfrequencies, ...... ..... .:phases tie n -p~frmance.x v ~performance |requirements g : :tsk & tasksqec A/times, probityocompletionwrlaand likely errorsFigure 0.11: Information flow in the sequence of human engineering analysesN ATO U.N-C-LA S.SIFIED-2 -