Analysis Techniques For Man-Machine Systems Design
Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design
NATO UNCLASSIFIED"AC/243(Panel-8)TR17- 38 -Volume 1goals is to run a SAINT simulation, then the analysis should generate a description of the tasknetwork from Operational Sequence Diagrams (OSDs) or a similar technique.3.2.4 Related techniques55. As indicated in Figure 3.1, the classes of analysis are related to one another.Similarly, within each class, techniques tend to be related. For, example two techniques forfunction analysis, Sequence and Timing Diagrams (SATs) and Function Flow Diagrams (FFDs),are related; in task analysis, Operational Sequence Diagrams (OSDs) are developments of FlowProcess Charts with symbols for operator actions added.56. In reviewing the various human engineering techniques, one objective was toexamine their compatibility with other engineering processes. Several of the techniques reviewedare related to, or used for, systems engineering analyses. As might be expected, most of thosetechniques are used in the early stages of analysis. Such common techniques include Missionand Scenario Analysis, FFDs, SATs, Structured Analysis and Design Technique (SADT), StateTransition Diagrams (STDs), Petri Nets, and Behaviour Graphs. The latter is an integral part of asystems engineering approach called Requirements Driven Development tAlford. 1989).57. None of the human engineering techniques used for the function allocation stage ofanalvsis is used for mainstream systems engineering studies, although the basic technique ofcomparing the capabilities of different design solutions is by no means unique to humanengineering. It is tempting to conclude that human engineering specialists are the only onesconcerned with the systematic allocation of functions to humans, and that other engineeringspecialities do it by default, through the selection of hardware and software (Chapanis, 1970;Meister, 1985). However, the Requirements Allocation Sheet, described in some systemsengineering texts (Defense Systems Management College, 1990) is one technique whichcombines the functional allocations for hardware, software and personnel by identifying subsystemand personnel performance requirements.58. Several techniques for task analysis are common to other engineering analyses.These include Time Lines, Flow Process Charts, Decision Tables, Systems Analysis byIntegrated Networks of Tasks (SAINT), and Error Analysis. In the area of interface andworkspace design, only one of the three techniques reviewed, Critical Design Requirements, canbe said to be used for other engineering analyses.59. Overall, it can be concluded that there is a fairly high level of commonality betweenhuman engineering and systems engineering analyses. Fifteen out of the thirty-one techniquesreviewed are used for other engineering analyses, including the two most frequently used humanengineering analyses (Function Flow Diagrams and Narrative Mission Descriptions). Thisshould facilitate communication between human engineering specialists and other members of thedesign/development team. Despite the use of common techniques, however, different specialitiesconduct their analyses from different viewpoints. For example, systems engineering activitiesmay analyse scenarios, or complete functional decompositions, without including the humanoperator (Beevis, 1987). Thus the human engineer may have to revise or modify analysesconducted by other specialities in order to highlight human factors in system or equipmentdesign.3.2.5 Resources required60. Most of the techniques reviewed can be conducted using simple "paper and pencil"resources. For only five of the techniques reviewed was the use of a computer mandatory. PetriNets and Behaviour Graphs require Computer Aided Software Engineering (CASE) tools toA
NATO UNCLASSIFIED39 - AC/243(Panel-8)TR[7Volume Ikeep track of the analyses and ensure that logic requirements are maintained. SAINT, SWAT,and SIMWAM are software-based tools which require computing facilities (SIMWAM isproprietary, but is included because of its widespread use by some services).61. Human engineering analysesproduce large amounts of information. For exampie, asystem functional decomposition typically starts with seven to ten functions at the uppermostlevel. Decomposing those functions through three levels results some 1000 functions at thelower level. If the analyses are to be reviewed and reiterated (Figure 1.9) then a computer isessential to keep track of the data and facilitate modification. For these reasons, some analystsare now using relational data bases for all the human engineering analyses. The reviews ofeleven of the analysis techniques suggest that computer-based record keeping is desirable.62. Other resources which are required include information and experience. Informationfrom subject matter experts (i.e., operators or ex-operators of similar systems) is important,especially for the analyses used in early stages (Mission Analysis, Function Analysis andAllocation) and for detailed task analyses such as Decision Tables. It is also important that thehuman factors specialist be an expert in the relevant land, sea or air system andfoperations.Information on possible technical solutions, (i.e., the hardware and software to be used), is alsoimportant. All analyses benefit from experience in using the relevant technique, and functionaldecompositions in particular benefit from experience of previous analyses. A few, for example,SADT, Petri Nets, Behaviour Graphs, and SAINT. require a thorough understanding of thetheory underlying the technique.3.2.6 Advantages/disadvantages63. The reports from users of some of the techniques show that their effectiveness canvary widely between individual applications (see Section 2.1). The more general advantages anddisadvantages identified for each technique reviewed in Volume 2 also vary widely. Twocomments which appear frequently are that the analyses can become labour intensive, thereforetime-consuming, and that there is an element of subjectivity in them. This latter comment isparticularly true of functional decomposition techniques, which can be influenced by theviewpoint of the analyst. This can be seen in the examples of functional decompositions includedin Volume 2. In general, the mission and function analysis techniques are good forcommunicating with other engineering specialities (as noted in comments on Related Techniques,above), and for traceability of design features. Because these techniques try to represent what aremulti-dimensional concepts in only two dimensions, however, they present a limited view ofsystems.64. In general, the function allocation techniques are simple to perform. This advantageincurs the corresponding disadvantage that they are simplistic. Also, they can require a great dealof knowledge which is not easily available. Task analysis techniques can be fast and easy toapply, but they can become overly detailed, therefore labour intensive and hard to understand orreview. The advantages and disadvantages of performance prediction techniques are not easy tosummarize. In general they are flexible and easy to apply provided that the supporting analyseshave been completed. They suffer from a lack of demonstrated validity for many applications.The three techniques reviewed for interface and workspace design are effective for presentationand for accounting for design decisions. They can be labour intensive and subjective.3.2.7 Relative contribution65. The relative contributions made bv the different techniques are dependent on theproject phase and the type of application. For example, some types of task analysis are highlyrecommended as a basis for a Test and Evaluation Plan. The relative contribution of any one
- Page 3 and 4: N A T OU N C L A S S I F I E DREPOR
- Page 6 and 7: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 8 and 9: NATO UNCLASSIFIEDAC1243(Pane1-8)TRf
- Page 10 and 11: NATO UNCLASSIFIEDAC/243(Panel-8)TRf
- Page 12 and 13: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 14 and 15: NATO UNCLASSIFIEDAC/243(Panel-8)TR[
- Page 16 and 17: NATO UNCLAS S IFIEDAC/243(Panel-8)T
- Page 18 and 19: NATO UNCLASSIFTEDAC/243(Panel-8)=RJ
- Page 20 and 21: NATO UNCLASSIFTEDAC/243(Panei-8)TR1
- Page 22 and 23: NATO UNCLASSIFIED-143tPanei-8)Tw7n3
- Page 24 and 25: NATO UJNCLASS IFTEDACt243(Panei-8)T
- Page 26 and 27: NATO UNCLASSIFIEDIAC243(Panei-8)=Vo
- Page 28 and 29: NAT O UNCLAS SIFTEDAC/3(Panel-8 7 -
- Page 30 and 31: NATO UNCLASSIFIEDACP-43gne-)TRj714
- Page 32 and 33: NATO UNCLASSIFIEDAC/243(Panel-8)TRL
- Page 34 and 35: NATO UNCLASSIFIEDAC/243(Panel-8)TRn
- Page 36 and 37: NATO UNCLASSIFIEDrAC/243(Panel-8)TR
- Page 38 and 39: NATO UNCLASSIFIEDAC/243(Pane1-8)TR/
- Page 40 and 41: NATO UNCLASSIFIEDAC/243(Panel- 8)TR
- Page 42 and 43: AC/243(Panei-8)TR/7- 26 -Volume ist
- Page 44 and 45: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 46 and 47: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 48 and 49: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 50 and 51: NATO UNCLASSIFIEDAC/243(Panel-8)TR/
- Page 52 and 53: NATO UNCLASSIFIEDI! -.\Cf2 3(Panei-
- Page 56 and 57: NATO UNCLASSIFIEDACT243(Palel- 8 TR
- Page 58 and 59: NATO UNCLASSIFTED,AC/243(Panel-8)TR
- Page 60 and 61: NATO UNCLASSIFIED 7ACP'_43(PaneI-8)
- Page 62 and 63: NATO UNCLASSIFIED.AC/243(Panel-8)TR
- Page 64 and 65: NATO UNCLASSIFIED QAC/243(Pafnel-8'
- 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
NATO UNCLASSIFIED39 - AC/243(Panel-8)TR[7Volume Ikeep track of the analyses and ensure that logic requirements are maintained. SAINT, SWAT,and SIMWAM are software-based tools which require computing facilities (SIMWAM isproprietary, but is included because of its widespread use by some services).61. Human engineering analysesproduce large amounts of information. <strong>For</strong> exampie, asystem functional decomposition typically starts with seven to ten functions at the uppermostlevel. Decomposing those functions through three levels results some 1000 functions at thelower level. If the analyses are to be reviewed and reiterated (Figure 1.9) then a computer isessential to keep track of the data and facilitate modification. <strong>For</strong> these reasons, some analystsare now using relational data bases for all the human engineering analyses. The reviews ofeleven of the analysis techniques suggest that computer-based record keeping is desirable.62. Other resources which are required include information and experience. Informationfrom subject matter experts (i.e., operators or ex-operators of similar systems) is important,especially for the analyses used in early stages (Mission <strong>Analysis</strong>, Function <strong>Analysis</strong> andAllocation) and for detailed task analyses such as Decision Tables. It is also important that thehuman factors specialist be an expert in the relevant land, sea or air system andfoperations.Information on possible technical solutions, (i.e., the hardware and software to be used), is alsoimportant. All analyses benefit from experience in using the relevant technique, and functionaldecompositions in particular benefit from experience of previous analyses. A few, for example,SADT, Petri Nets, Behaviour Graphs, and SAINT. require a thorough understanding of thetheory underlying the technique.3.2.6 Advantages/disadvantages63. The reports from users of some of the techniques show that their effectiveness canvary widely between individual applications (see Section 2.1). The more general advantages anddisadvantages identified for each technique reviewed in Volume 2 also vary widely. Twocomments which appear frequently are that the analyses can become labour intensive, thereforetime-consuming, and that there is an element of subjectivity in them. This latter comment isparticularly true of functional decomposition techniques, which can be influenced by theviewpoint of the analyst. This can be seen in the examples of functional decompositions includedin Volume 2. In general, the mission and function analysis techniques are good forcommunicating with other engineering specialities (as noted in comments on Related <strong>Techniques</strong>,above), and for traceability of design features. Because these techniques try to represent what aremulti-dimensional concepts in only two dimensions, however, they present a limited view ofsystems.64. In general, the function allocation techniques are simple to perform. This advantageincurs the corresponding disadvantage that they are simplistic. Also, they can require a great dealof knowledge which is not easily available. Task analysis techniques can be fast and easy toapply, but they can become overly detailed, therefore labour intensive and hard to understand orreview. The advantages and disadvantages of performance prediction techniques are not easy tosummarize. In general they are flexible and easy to apply provided that the supporting analyseshave been completed. They suffer from a lack of demonstrated validity for many applications.The three techniques reviewed for interface and workspace design are effective for presentationand for accounting for design decisions. They can be labour intensive and subjective.3.2.7 Relative contribution65. The relative contributions made bv the different techniques are dependent on theproject phase and the type of application. <strong>For</strong> example, some types of task analysis are highlyrecommended as a basis for a Test and Evaluation Plan. The relative contribution of any one