Communicating sequential processes
Communicating sequential processes
Systematic software development using VDM
Systematic software development using VDM
Where do we draw the line? - Derivation and evaluation of user interface software separation rules
Proceedings of the Second Conference of the British Computer Society, human computer interaction specialist group on People and computers: designing for usability
Statecharts: A visual formalism for complex systems
Science of Computer Programming
The myth of the infinitely fast machine
Proceedings of Third Conference of the British Computer Society Human-Interactio on People and computers III
The Z notation: a reference manual
The Z notation: a reference manual
Designing the user interface (videotape)
Designing the user interface (videotape)
Formal aspects of human-computer interaction
Formal aspects of human-computer interaction
ACM Transactions on Programming Languages and Systems (TOPLAS)
An old-fashioned recipe for real time
ACM Transactions on Programming Languages and Systems (TOPLAS)
Specifying user interfaces in DisCo
ACM SIGCHI Bulletin
Temporal reasoning over deontic specifications
Deontic logic in computer science
IEEE Transactions on Software Engineering
System Specification and Refinement in Temporal Logic
Proceedings of the 12th Conference on Foundations of Software Technology and Theoretical Computer Science
Hi-index | 0.00 |
Typically formal notations for interactive systems previously presented in the literature (e.g. [2, 6, 18]) synthesize two or more languages. We contend that it would be preferable if one were able to use a single soundly based specification language which is expressive enough to capture HCI issues. Taking a lead from Lamport's Temporal Logic ofActions, (TLA), [14] we outline a language for expressing models of systems based on temporal logic, and make clear the design process we intend this language to be a part of. We discuss two equivalent specification styles using this language; firstly describing the functionality of the system and secondly describing the interactions of the system. We contend that the second is more 'HCI-centric' than the first. We discuss other issues raised by the use of the language and set down an agenda for future work.