Object-oriented programming for the Macintosh
Object-oriented programming for the Macintosh
Human-computer interface development: concepts and systems for its management
ACM Computing Surveys (CSUR)
Object-oriented analysis and design with applications (2nd ed.)
Object-oriented analysis and design with applications (2nd ed.)
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
An object-oriented, distributed architecture for large-scale Ada systems
TRI-Ada '94 Proceedings of the conference on TRI-Ada '94
Optimization criteria for checkpoint placement
Communications of the ACM
Building Decision Support Systems
Building Decision Support Systems
Iterative User-Interface Design
Computer
Beyond Abstract Data Types: Giving Life to Objects
Proceedings of the First International Eurospace - Ada-Europe Symposium on Ada in Europe
Using Patterns to Model Variability in Product Families
IEEE Software
Programs = Data + Algorithms + Architecture: Consequences for Interactive Software Engineering
Engineering Interactive Systems
| Hi-index | 0.00 |
Dialogue independence -- the decoupling of the Computer-Human Interface from the core application software -- can be achieved simply through an appropriate architectural framework, with no loss of efficiency. We show that the objective of dialogue independence can be decomposed into three separate subgoals that a software architecture must resolve: existence, property, and transition. We identify architectural patterns that satisfy all three subgoals, and give a rough sketch of their design and implementation.We chose an air-traffic-control system to illustrate our proposed decomposition because of our experience with it and because it exposes many of the difficulties inherent in a typical, large CHI software architecture. We use the terminology of object-oriented software architecture, but we propose a decomposition that is independent of the methodology used.