Awareness and coordination in shared workspaces
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
Program integration for languages with procedure calls
ACM Transactions on Software Engineering and Methodology (TOSEM)
Using a configuration management tool to coordinate software development
COCS '95 Proceedings of conference on Organizational computing systems
Coordination, overload and team performance: effects of team communication strategies
CSCW '98 Proceedings of the 1998 ACM conference on Computer supported cooperative work
Parallel changes in large-scale software development: an observational case study
ACM Transactions on Software Engineering and Methodology (TOSEM)
Test Driven Development: By Example
Test Driven Development: By Example
Software Configuration Management Patterns: Effective Teamwork, Practical Integration
Software Configuration Management Patterns: Effective Teamwork, Practical Integration
High-Level Best Practices in Software Configuration Management
ECOOP '98 Proceedings of the SCM-8 Symposium on System Configuration Management
"Breaking the code", moving between private and public work in collaborative software development
GROUP '03 Proceedings of the 2003 international ACM SIGGROUP conference on Supporting group work
Building Collaboration into IDEs
Queue - Distributed Development
Chianti: a tool for change impact analysis of java programs
OOPSLA '04 Proceedings of the 19th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
ACSC '06 Proceedings of the 29th Australasian Computer Science Conference - Volume 48
CVS integration with notification and chat: lightweight software team collaboration
CSCW '06 Proceedings of the 2006 20th anniversary conference on Computer supported cooperative work
FASTDash: a visual dashboard for fostering awareness in software teams
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Supporting distributed software development by modes of collaboration
ECSCW'01 Proceedings of the seventh conference on European Conference on Computer Supported Cooperative Work
Awareness in the Wild: Why Communication Breakdowns Occur
ICGSE '07 Proceedings of the International Conference on Global Software Engineering
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Empirical evidence of the benefits of workspace awareness in software configuration management
Proceedings of the 16th ACM SIGSOFT International Symposium on Foundations of software engineering
Speculative analysis: exploring future development states of software
Proceedings of the FSE/SDP workshop on Future of software engineering research
A theory of branches as goals and virtual teams
Proceedings of the 4th International Workshop on Cooperative and Human Aspects of Software Engineering
Proactive detection of collaboration conflicts
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Making software integration really continuous
FASE'12 Proceedings of the 15th international conference on Fundamental Approaches to Software Engineering
Improving early detection of software merge conflicts
Proceedings of the 34th International Conference on Software Engineering
Assessing the value of branches with what-if analysis
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Computer Supported Cooperative Work
| Hi-index | 0.00 |
Today, most developers work in parallel inside private workspaces to ensure stability during programming, but this provokes isolation from what co-workers are doing. Isolation may result in conflicts, which must be detected as early as possible to avoid bugs and expensive rework. Currently, frequent integration and awareness are used for early conflict detection. Frequent integration detects actual conflicts using automated builds, although only when merging checked in changes. Awareness informs about ongoing changes in private workspaces, however developers must find actual conflicts by themselves. This paper proposes the novel concept of real-time integration. This automates the detection of actual conflicts emerging during programming, involving checked in and ongoing changes, and affecting two or more developers. Cooperative resolution of conflicts is explicitly supported by sharing fine-grained changes among private workspaces. Software versions will also improve quality as integration builds are run before checking in.