Design and implementation of an object-oriented strongly typed language for distributed applications
Journal of Object-Oriented Programming
Experiences in the use of a media space
CHI '91 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
MMM: a user interface architecture for shared editors on a single screen
UIST '91 Proceedings of the 4th annual ACM symposium on User interface software and technology
Realizing a video environment: EuroPARC's RAVE system
CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The abstraction-link-view paradigm: using constraints to connect user interfaces to applications
CHI '92 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The MSM Framework: A Design Space for Multi-Sensori-Motor Systems
EWHCI '93 Selected papers from the Third International Conference on Human-Computer Interaction
Structuring the Space of Interactive System Properties
Proceedings of the IFIP TC2/WG2.7 Working Conference on Engineering for Human-Computer Interaction
| Hi-index | 0.00 |
Software tools for tile construction of interactive systems such as user interface toolkits, application skeletons, and user interface generators, alleviate the activity of programming but do not eliminate software architecture modelling. For example, the "callback" mechanism made popular by X-Window, does not enforce the distinction between domain-specific concepts and presentation-specific issues. Without a framework for prescribing the appropriate usage of callbacks, the software designer may develop an interactive system that cannot be maintained nor modified. Cooperative systems, which draw upon a wide variety of tools, techniques, and constraints, make architecture modelling even more crucial.In order to reason about software modelling for cooperative systems, we first need to clarify the nature of the problem space. The role of a problem space is to identify the set of concepts relevant to a particular domain of interest and to organize these concepts into a framework suitable for rising the appropriate questions, for clarifying the scope of the solution space, or for characterizing a particular design solution. The litterature reveals a wide variety of issues related to CSCW but these concepts are not organized in a way that supports software architecture modelling. We claim that one goal of the workshop is to define a problem space useful for reasoning about software architecture and use this framework as foundations for comparing, devising, and assessing current and future architecture models.In section 2, we present a draft proposal of the problem space for the software design of cooperative systems. In section 3, we describe PAC-Amodeus, our own conceptual architecture model, and show how it can support the issues made explicit in our problem space.