RCS—a system for version control
Software—Practice & Experience
A shared, segmented memory system for an object-oriented database
ACM Transactions on Information Systems (TOIS)
Integrating noninterfering versions of programs
ACM Transactions on Programming Languages and Systems (TOPLAS)
Concurrency control in groupware systems
SIGMOD '89 Proceedings of the 1989 ACM SIGMOD international conference on Management of data
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
A Flexible Transaction Model for Software Engineering
Proceedings of the Sixth International Conference on Data Engineering
Design and Implementation of GORDION, an Object Base Management System
Proceedings of the Third International Conference on Data Engineering
Split-Transactions for Open-Ended Activities
VLDB '88 Proceedings of the 14th International Conference on Very Large Data Bases
An annotated bibliography of computer supported cooperative work
ACM SIGCHI Bulletin - Special issue: Computer supported cooperative work
“Lazy” consistency: a basis for cooperative software development
CSCW '92 Proceedings of the 1992 ACM conference on Computer-supported cooperative work
Combining local negotiation and global planning in cooperative software development projects
COCS '93 Proceedings of the conference on Organizational computing systems
Proceedings of the 43rd annual Southeast regional conference - Volume 2
Hi-index | 0.00 |
Development of any large system or artifact requires the coordination of many developers. Development activities can occur concurrently. The goal of coordination is to enhance, not restrict, developer productivity, while ensuring that concurrent development activities do not clash with one another.This paper presents a formal model of concurrent development, in which development consists of a collection of modification activities that change files, and merges that combine the changes. We define a notion of consistency called coordination consistency that ensures that changes are not inadvertently destroyed and that the changes of each modification activity are correctly propagated to subsequent modification activities. We briefly present a set of protocols for concurrent development using a hierarchy of stores that ensure coordination consistency.