Generating language-based environments
Generating language-based environments
Response time and display rate in human performance with computers
ACM Computing Surveys (CSUR)
Designing for usability: key principles and what designers think
Communications of the ACM
Software Engineering for User Interfaces
IEEE Transactions on Software Engineering
User Recovery and Reversal in Interactive Systems
ACM Transactions on Programming Languages and Systems (TOPLAS)
Optimization criteria for checkpoint placement
Communications of the ACM
Proceedings of the ACM SIGPLAN SIGOA symposium on Text manipulation
EMACS the extensible, customizable self-documenting display editor
Proceedings of the ACM SIGPLAN SIGOA symposium on Text manipulation
Descartes: A programming-language approach to interactive display interfaces
Proceedings of the 1983 ACM SIGPLAN symposium on Programming language issues in software systems
US&R: A new framework for redoing (Extended Abstract)
SDE 1 Proceedings of the first ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
Interactive structure-oriented computing
Interactive structure-oriented computing
The use of single family of languages for program development
CSC '89 Proceedings of the 17th conference on ACM Annual Computer Science Conference
Lessons on converting batch systems to support interaction: experience report
ICSE '97 Proceedings of the 19th international conference on Software engineering
| Hi-index | 0.00 |
Interactive systems have goals and characteristics that differ from those of batch systems. These differences lead to a need for new techniques, methods, and tools for manipulating and constructing interactive systems. The difference in structure between batch and interactive systems. The difference is considered, focusing on the distinction between command decomposition and component decomposition. The possible ways of solving a problem using an interactive system using action paths, which account for the relatively unconstrained actions of interactive users, are described. It is shown that interactivity is not an inherent characteristic of a system but rather a characteristic that depends on the error profile of its users. The requirements that interaction places on the underlying implementation, specifically the need for incrementality and integration, are considered. The results are applied to several existing classes of systems.