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

NATO UNCLASSIFIEDAC/243(Panel 8')TR/7Volume 2Inputs to the techniqueThe analyst requires information on the sequence andperformance criteria for the opermtor's tasks, and detailsof the human-machine interface design.Outputs of the techniqueCritical task analyses are usually presented as tabulationsof the required information. There is no standard format.Annotated Opcrational Sequence Diagrams are sometimes.used.When to useBecause of the amount of detail required for the analysis, usually it cannot be prepared prior to the design definitionphase of a project It requires input from other task analyses and from an interface design concept. Some usersrecommend that a mock-up of the interface be used as a basis for the analysis, which would determine the schedule ofthe work.RelatedtechniquesCritical task analyses are characterized more by the lcvel of detail of the analysis, than by the specific technique used.The approach is related to Operational Sequence Diagrams (4.3). and to Information/Action tabulations (4.4).ResourcesrequiredDetailed operator task information and details of the human-machine interface are needed. Use of a computer isrecommended, to handle editing and updating.AdvantagesDisadvantagesIn general, users report the technique to be effective. The The level of detail provided can be overwhelming, so thatanalysis is straightforward to conduct, and forces the the reviewer has difficulty understanding the overall patterndesigners to develop a thorough understanding of what of operator activities. Users report that the technique doesthe operators of a system will be required to do. not deal well with parallel, multi-task situations. It isreported to be of medium difficulty, and quite timeconsuming.The time requirement can limit the extent ofapplication of the analysis. Analysts should choose theapplication carefully.Relative contributionSome users find the technique quite effective. One user, however, indicated that it had low effectiveness on theirproject. It has been found very effective for identifying the tests which are to be run in the test & evaluation phase.ApplicationsThe technique has been widely called up in system requirements documents, but there are few reports of its use. It wasused for the development of a European stike aircraft, for a tank, US helicopter system (Parks, 1987), naval sensorsystems, and a naval ship.NATO UNCLASSIFIED- 82 -

NATO UNCLASSIFIED- 83 - AC/243(Panel-8)TR/7Volume 2:ionslat.:menQuality assurance considerationsCritical task analyses are very difficult to check for consistency and completeness because of the amount of detailinvolved. An hierarchical approach, developing the analyses from preceding task analyses, is recommended, togetherwith the use of a computer-based editing system. Customer and contractor should agree clearly on the extent of thework.)n | Relationship to system performance requirementsofThe final output can be related directly to operator job aids such as checklists and instruction manuals. The analysisi. can also be used to identify criteria for test and evaluation.- I* References and BibliographyId. 1. NATO MAS, (1991). Application of human eng'inecrin to advanced aircraft systems. Brussels: NATO MiliLtIryAgency for Standardization (MAS) Aircraft Instrument Panel. STANAG 3994 (Edition 1) (Ist Draft).2. Parks, R.E., (1987). Development and testing of a predictive methodology for optimization of man-machineinterface in future avionics systems. In: The design. developmcnt and testing of complex avionics systems, (pp.14-1 - 14-9). AGARD-CP-417.3. US Department of Defense (1987). Human engineering procedures guide. Washington D.C.: DoD-HDBK-763.4. US Department of Defense (1979) Human engincering requirements for military svstems. equipment and facilities.Redstone Arsenal, AL: US Army Missile R & D Command. MIL-H-46855B.//aNATO UNCLASSIFIED- 83 -

NATO UNCLASSIFIEDAC/243(Panel 8')TR/7Volume 2Inputs to the techniqueThe analyst requires information on the sequence andperformance criteria for the opermtor's tasks, and detailsof the human-machine interface design.Outputs of the techniqueCritical task analyses are usually presented as tabulationsof the required information. There is no standard format.Annotated Opcrational Sequence Diagrams are sometimes.used.When to useBecause of the amount of detail required for the analysis, usually it cannot be prepared prior to the design definitionphase of a project It requires input from other task analyses and from an interface design concept. Some usersrecommend that a mock-up of the interface be used as a basis for the analysis, which would determine the schedule ofthe work.RelatedtechniquesCritical task analyses are characterized more by the lcvel of detail of the analysis, than by the specific technique used.The approach is related to Operational Sequence Diagrams (4.3). and to Information/Action tabulations (4.4).ResourcesrequiredDetailed operator task information and details of the human-machine interface are needed. Use of a computer isrecommended, to handle editing and updating.AdvantagesDisadvantagesIn general, users report the technique to be effective. The The level of detail provided can be overwhelming, so thatanalysis is straightforward to conduct, and forces the the reviewer has difficulty understanding the overall patterndesigners to develop a thorough understanding of what of operator activities. Users report that the technique doesthe operators of a system will be required to do. not deal well with parallel, multi-task situations. It isreported to be of medium difficulty, and quite timeconsuming.The time requirement can limit the extent ofapplication of the analysis. Analysts should choose theapplication carefully.Relative contributionSome users find the technique quite effective. One user, however, indicated that it had low effectiveness on theirproject. It has been found very effective for identifying the tests which are to be run in the test & evaluation phase.ApplicationsThe technique has been widely called up in system requirements documents, but there are few reports of its use. It wasused for the development of a European stike aircraft, for a tank, US helicopter system (Parks, 1987), naval sensorsystems, and a naval ship.NATO UNCLASSIFIED- 82 -

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

Saved successfully!

Ooh no, something went wrong!