Post-mechanistic groupware primitives: rhythms, boundaries and containers
International Journal of Man-Machine Studies - Computer-supported cooperative work and groupware. part 2
Experiments with Oval: a radically tailorable tool for cooperative work
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Designing object-oriented synchronous groupware with COAST
CSCW '96 Proceedings of the 1996 ACM conference on Computer supported cooperative work
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
Flexible synchronization of shared groupware objects
ACM SIGGROUP Bulletin
Collaborative Virtual Environment Development: An Aspect-Oriented Approach
ICDCSW '01 Proceedings of the 21st International Conference on Distributed Computing Systems
Aspect-Oriented Analysis and Design
Aspect-Oriented Analysis and Design
Weaving a social fabric into existing software
Proceedings of the 4th international conference on Aspect-oriented software development
Service-Oriented Architecture: Concepts, Technology, and Design
Service-Oriented Architecture: Concepts, Technology, and Design
Multi-Dimensional Separation of Concerns in Requirements Engineering
RE '05 Proceedings of the 13th IEEE International Conference on Requirements Engineering
Aspect-oriented software development
Aspect-oriented software development
Science of Computer Programming
Hi-index | 0.00 |
Groupware must deal with a myriad of concerns. Some of them are typical of "conventional" software while others are idiosyncratic of CSCW applications (e.g., awareness). We claim that separating concerns fosters tailorability. While existing approaches for groupware design deal with the basic problem of separation of concerns (e.g., using well-known object-oriented techniques), they do not address the problems triggered by crosscutting concerns -i.e., when the realization of the same concern is scattered along multiple components, or when different concerns are "tangled" in the same component. This paper presents a concern-oriented approach to requirement specification of groupware, characterizing the situations in which crosscutting exists. It follows the Theme approach for identification and design of crosscutting concerns, uses AOP to eliminate tangling and scattering, and proposes a concern centric approach to groupware tailorability.