Recent accounts of accidents draw attention to ``automation surprises'' that arise in safety critical systems. An automation surprise can occur when a system behaves differently from the expectations of the operator. Interface mode changes are one class of such surprises that have significant impact on the safety of a dynamic interactive system. They may take place {\em implicitly} as a result of other system action. Formal specifications of interactive systems provide an opportunity to analyse problems that arise in such systems. In this paper we consider the role that an {\em interactor} based specification has as a partial model of an interactive system so that mode consequences can be checked early in the design process. We show how interactor specifications can be translated into the SMV model checker input language and how we can use such specifications in conjunction with the model checker to analyse potential for mode confusion in a realistic case. Our final aim is to develop a general purpose methodology for the automated analysis of interactive systems. This verification process can be useful in raising questions that have to be addressed in a broader context of analysis.

   

@ARTICLE{CamposH01,
 author = {J. C. Campos and M. D. Harrison},
 title = {Model Checking Interactor Specifications},
 journal = {Automated Software Engineering},
 year = {2001},
 volume = {8},
 pages = {275-310},
 number = {3/4},
 month = {August},
 note = {ISSN: 0928-8910},
 doi = {10.1023/A:1011265604021},
 hdl = {1822/687},
 abstract = {Recent accounts of accidents draw attention to ``automation surprises'' that arise in safety critical systems. An automation surprise can occur when a system behaves differently from the expectations of the operator. Interface mode changes are one class of such surprises that have significant impact on the safety of a dynamic interactive system. They may take place {\em implicitly} as a result of other system action. Formal specifications of interactive systems provide an opportunity to analyse problems that arise in such systems. In this paper we consider the role that an {\em interactor} based specification has as a partial model of an interactive system so that mode consequences can be checked early in the design process. We show how interactor specifications can be translated into the SMV model checker input language and how we can use such specifications in conjunction with the model checker to analyse potential for mode confusion in a realistic case. Our final aim is to develop a general purpose methodology for the automated analysis of interactive systems. This verification process can be useful in raising questions that have to be addressed in a broader context of analysis.}
}

Generated by mkBiblio 2.6.26