{'fraction_non_alphanumeric': 0.014001077005923533, 'fraction_numerical': 0.0, 'mean_word_length': 5.588652482269503, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
On the representation of automation using a work domain analysis

Work domain analysis (WDA) has been applied extensively within cognitive engineering as an analytic framework for the evaluation of complex sociotechnical systems in support of design. However, the WDAs described in the literature have not explored the representation of automated system components, despite the documented problems associated with operator-automation interaction and the requirements for operator support in complex automated systems. The current research examines the application of WDA to model an example automated system – a camera – by representing the camera along with its automated components as separate systems using the abstraction hierarchy (AH). Additionally, we contrasted this modelling approach with the more typical approach of modelling automation within a cognitive work analysis (CWA) by performing a control task analysis using the decision ladder. The results of these analyses suggest that, similar to non-automated systems, considering a separate representation of an automated system within the WDA may provide useful system design guidance in terms of user support and information requirements. The comparison of the AH and the decision ladder (DL) models indicates that the models provide different information about the requirements and support different user needs: the AH provides information about specific subsystems and components of the automation that are used for control and how they support functions and purposes of the automation while the DL shows how the control tasks are achieved interleaving automated actions with those of the user. The information obtained from modelling automation with the AH is different from what would normally be obtained by performing only a control task analysis, yet is necessary for operator support.