Groupware and social dynamics: eight challenges for developers
Communications of the ACM
Coupling the user interfaces of a multiuser program
ACM Transactions on Computer-Human Interaction (TOCHI)
Quality function deployment usage in software development
Communications of the ACM
Using GOMS for user interface design and evaluation: which technique?
ACM Transactions on Computer-Human Interaction (TOCHI)
ACM Transactions on Computer-Human Interaction (TOCHI)
ACM Transactions on Graphics (TOG)
Supporting cognitive models as users
ACM Transactions on Computer-Human Interaction (TOCHI) - Special issue on human-computer interaction in the new millennium, Part 2
The keystroke-level model for user performance time with interactive systems
Communications of the ACM
A comparison of usage evaluation and inspection methods for assessing groupware usability
GROUP '01 Proceedings of the 2001 International ACM SIGGROUP Conference on Supporting Group Work
Groupware walkthrough: adding context to groupware usability evaluation
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
The Psychology of Human-Computer Interaction
The Psychology of Human-Computer Interaction
ACM Transactions on Computer-Human Interaction (TOCHI)
Computational GOMS modeling of a complex team task: lessons learned
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Revealing delay in collaborative environments
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Software requirements negotiation using the software quality function deployment
CRIWG'05 Proceedings of the 11th international conference on Groupware: design, Implementation, and Use
Hi-index | 0.00 |
We propose an analytic method to evaluate groupware design. The method was inspired by GOMS, a well-known approach to analyze usability problems with single-user interfaces. GOMS has not yet been amply applied to evaluate groupware because of several fundamental distinctions between the single-user and multi-user contexts. The approach described in this paper overcomes such differences. We also illustrate the application of the model by applying it to the design of a collaborative tool for software engineering requirements negotiation.