Automatic verification of finite-state concurrent systems using temporal logic specifications
ACM Transactions on Programming Languages and Systems (TOPLAS)
Specifications are (preferably) executable
Software Engineering Journal
Design principles for interactive software
Design principles for interactive software
Symbolic Model Checking
Model Checking Interactor Specifications
Automated Software Engineering
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Usability-Supporting Architectural Patterns
Proceedings of the 26th International Conference on Software Engineering
Experimental Evaluation of Verification and Validation Tools on Martian Rover Software
Formal Methods in System Design
Coloured Petri Nets and CPN Tools for modelling and validation of concurrent systems
International Journal on Software Tools for Technology Transfer (STTT)
The temporal logic of programs
SFCS '77 Proceedings of the 18th Annual Symposium on Foundations of Computer Science
High-Fidelity Prototyping of Interactive Systems Can Be Formal Too
Proceedings of the 13th International Conference on Human-Computer Interaction. Part I: New Trends
ACM Transactions on Computer-Human Interaction (TOCHI)
Integrating model checking and HCI tools to help designers verify user interface properties
DSV-IS'00 Proceedings of the 7th international conference on Design, specification, and verification of interactive systems
JPF-AWT: Model checking GUI applications
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Formal analysis of ubiquitous computing environments through the APEX framework
Proceedings of the 4th ACM SIGCHI symposium on Engineering interactive computing systems
Hi-index | 0.00 |
During early phases of the development of an interactive system, future system properties are identified (through interaction with end users in the brainstorming and prototyping phase of the application, or by other stakeholders) imposing requirements on the final system. They can be specific to the application under development or generic to all applications such as usability principles. Instances of specific properties include visibility of the aircraft altitude, speed…in the cockpit and the continuous possibility of disengaging the autopilot in whatever state the aircraft is. Instances of generic properties include availability of undo (for undoable functions) and availability of a progression bar for functions lasting more than four seconds. While behavioral models of interactive systems using formal description techniques provide complete and unambiguous descriptions of states and state changes, it does not provide explicit representation of the absence or presence of properties. Assessing that the system that has been built is the right system remains a challenge usually met through extensive use and acceptance tests. By the explicit representation of properties and the availability of tools to support checking these properties, it becomes possible to provide developers with means for systematic exploration of the behavioral models and assessment of the presence or absence of these properties. This paper proposes the synergistic use two tools for checking both generic and specific properties of interactive applications: Petshop and Java PathFinder. Petshop is dedicated to the description of interactive system behavior. Java PathFinder is dedicated to the runtime verification of Java applications and as an extension dedicated to User Interfaces. This approach is exemplified on a safety critical application in the area of interactive cockpits for large civil aircrafts.