Analysis Techniques For Man-Machine Systems Design

Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design

ai.eecs.umich.edu
from ai.eecs.umich.edu More from this publisher
11.07.2015 Views

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-

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 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!