Analysis Techniques For Man-Machine Systems Design
Analysis Techniques For Man-Machine Systems Design Analysis Techniques For Man-Machine Systems Design
NATO UNCI ASSIFIEDC/-43(Panel 8)TR/7- 42 -Jo!',.e 2Relationship to system performance requirementsPcrfo....ance requirements are specified as an integral part of the model. Additionally, by establishing item arrivaltimes az- .or duration times for the functions, time performance requirements can bc identified by executing themooz..Referencesand Bibliography1. .ifard. M.W. (1985a). SREM at the agc of eight The distributed design system. IEEE Comnuter. 1. 36-46.2. . rd. M.W. (1985b). A graph model based approach to specification. In: M. Paul & HJ. Siegert (Eds.),Dipruted systems: methods and tools for specification. Springer-Verlag.3. .±dfard. M.W. (1989).Implementing scenario definition techniques using RDD-IOO. Proceedings of the IEEE realtirnsvstem sYmnosiuni EEE Press.r- 13.A.M. (1990). Software requirements: analysis and sccifications. New York: Prentice Hall.:--i. -. D. (1987). Statecharts: a visual formalism for complex systems. Science of Computer Programing, a (3),6. K-_s-r. G.V. & Tischer, K. (1987). Engineering the man-machine interface for air traffic control. IEEEC -r ( 2 ), 47-62./ Lzorovitz, D.R.. & Phillips, M.D. (1987). Human factors requircments for air traffic control systems. In: G.Saivendv (Ed.), Handbook of human factors.(pp. 1771 - 1789). New York: John Wiley & Sons.S. Phllips. M.D., Bashinski, H.S., Ammerman, H.L., & Fligg, C.M. (1987). A task analytical approach to--zocue design. In: E. Helander (Ed.), Handbook of human-computer interacLion. New York: North-Holland.9. Ve:M. KA., & Kramarics, A.M.S. (1990). Requirement driven development a system engineering method. In:?-cdines of the Norwecian Informatics Conferencc (NIK '90), (pp. 81-91). Tapir.NATO UNCLASSIFIED-42 -
NATO UNCLASSIFIED-43 -- AC/243(Panel-8)TR/7Volume 23 FUNCTION ALLOCATION- scenanoanalysis ; 7a3.a5sllocationWhat the tec3 analysis o inteaacei&3.1 * d hocfunction alctoianalysis d3.4 ioFunctionalctetask tis|predictionl3.t w For function allocationofutntpel(iw ),funtins anRevsks of theehuman compoenatofrh sysbiltiemThs i tclrytu fapiain cmuestsofwar is neessaryefreotimAllsystedsign. Fhnctios loainaaye rvd tebssfrsbeun otreclatig.t sueviin dcrwiors moioig e aoperto irection, d. task aunalyios otnsutiloeation andrdescriptonsopertorperftormance candtabiningaenties ue i analysis, ucina dipaye mande nlssrih imlcntrly inlectioordesign all.aio (including of Functions homunithslcation beauellocatin systeqimsesin), bevaluatifidonl and crwsotwar.Athonghsapoconefncinaloainteiioshvixe desgdvlpent hand ealueration. ad.Nn oinpartit culari,190,sc decisions ontealocyo of fuciosaffec crewhort opserator wonsdrklioad and thaei imasinfcat influene onmanntingsecto, and t huainin rsso requireents (Uo eafeto Dfne the system.Tiisprcual 97.I ueoapiains engineering tprocsks, functio aloctonircnuce promdanly.Aathrough formallyRaluirementsoAllocations (US Depefense) Sys dwre.msMotanaemesnteColeger 1990) othea sytemhniqesreiewed heretion a]lcatin conaibues trovthe Rhequaiemns Alocaubeqetio pffrocssBecauseg thcewooprtras analysesaeiaesoh functionswhchrcpin rpequredtor promeece systemis reqirmns.pthy seldcomto reflectpathecunadctioswichsemerge alonceadciionofuntns havfebee madew aout sysrtem moklanning Typ igiicalycrwfnctionsfsuech assuarviiong, moiornliection,cnutto rqient(UDpartenot and trainingifDfnclued 197In fntione anaystems onieringthallocatinso functions blcauseothey candu bed idenllytihedonly oneqfuirmnctio Allocation decisioenshae besenmad.Nnof five functional analyses of major military systems reviewed at random included these human crew functions (seethe examples in Part 2). Yet the performance of such functions can have a major influence on the design of mannedsystems (Beevis, 1987). Analyses must reiterate their function allocation decisions to include human crew functions.NATO UNCLASSIFIED-43 -
- 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 116 and 117: ACP243(Panel-8)TRn 2.Volume 2INTROD
- 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 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 192 and 193: 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/
NATO UNCI ASSIFIEDC/-43(Panel 8)TR/7- 42 -Jo!',.e 2Relationship to system performance requirementsPcrfo....ance requirements are specified as an integral part of the model. Additionally, by establishing item arrivaltimes az- .or duration times for the functions, time performance requirements can bc identified by executing themooz..Referencesand Bibliography1. .ifard. M.W. (1985a). SREM at the agc of eight The distributed design system. IEEE Comnuter. 1. 36-46.2. . rd. M.W. (1985b). A graph model based approach to specification. In: M. Paul & HJ. Siegert (Eds.),Dipruted systems: methods and tools for specification. Springer-Verlag.3. .±dfard. M.W. (1989).Implementing scenario definition techniques using RDD-IOO. Proceedings of the IEEE realtirnsvstem sYmnosiuni EEE Press.r- 13.A.M. (1990). Software requirements: analysis and sccifications. New York: Prentice Hall.:--i. -. D. (1987). Statecharts: a visual formalism for complex systems. Science of Computer Programing, a (3),6. K-_s-r. G.V. & Tischer, K. (1987). Engineering the man-machine interface for air traffic control. IEEEC -r ( 2 ), 47-62./ Lzorovitz, D.R.. & Phillips, M.D. (1987). Human factors requircments for air traffic control systems. In: G.Saivendv (Ed.), Handbook of human factors.(pp. 1771 - 1789). New York: John Wiley & Sons.S. Phllips. M.D., Bashinski, H.S., Ammerman, H.L., & Fligg, C.M. (1987). A task analytical approach to--zocue design. In: E. Helander (Ed.), Handbook of human-computer interacLion. New York: North-Holland.9. Ve:M. KA., & Kramarics, A.M.S. (1990). Requirement driven development a system engineering method. In:?-cdines of the Norwecian Informatics Conferencc (NIK '90), (pp. 81-91). Tapir.NATO UNCLASSIFIED-42 -
Change language