Formal tasks and systems models as a tool for specifying and assessing automation designs

  • Authors:
  • Célia Martinie;Philippe Palanque;Eric Barboni;Marco Winckler;Martina Ragosta;Alberto Pasquini;Paola Lanzi

  • Affiliations:
  • University Paul Sabatier, IRIT, Toulouse Cedex;University Paul Sabatier, IRIT, Toulouse Cedex;University Paul Sabatier, IRIT, Toulouse Cedex;University Paul Sabatier, IRIT, Toulouse Cedex;DeepBlue Srl, Piazza Buenos Aires, Roma - Italy;DeepBlue Srl, Piazza Buenos Aires, Roma - Italy;DeepBlue Srl, Piazza Buenos Aires, Roma - Italy

  • Venue:
  • Proceedings of the 1st International Conference on Application and Theory of Automation in Command and Control Systems
  • Year:
  • 2011

Quantified Score

Hi-index 0.00

Visualization

Abstract

Designing interactive computing systems in such a way that as much functions as possible are automated has been the driving direction of research and engineering both in aviation and in computer science for many years. In the 80's many studies (e.g. [8] related to the notion of mode confusion) have demonstrated that fully automated systems are out of the grasp of current technologies and that additionally migrating functions [2] from the operator to the system might have disastrous impact on safety and usability and operationality of systems. Allocating functions to an operator or automating them, raises issues that require a complete understanding of both operations to be carried out by the operator and the behavior of the interactive system. This paper proposes a contribution for reasoning about automation designs using a model-based approach exploiting both task models and system models. Tasks models are meant to describe goals, tasks and actions to be performed by the operator while system models represent the entire behaviour of the interactive system. Tasks models and systems models thus represent two different views of the same world: one or several users interacting with a computing system in order to achieve their goals. In previous work we have demonstrated how these two views can be integrated at the model level and additionally at the tool level [7]. In this paper we present how such representations can support the assessment of alternative design options for automation.