http://www.crystaliz.com/research/pubs/a4.doc Consistency Management for Distributed Collaboration JONATHAN REES, SARAH FERGUSON, and SANKAR VIRDHAGRISWARAN Crystaliz, Inc., 9 Pond Lane, Concord, MA 01742 Collaborative enterprises, such as the development of complex software systems or web sites, are vulnerable to accidental conflicts between participants activities. They face the twin threats of information loss, where one person accidentally erases or overwrites another work, and inconsistency, where one s person alters the context of another work so s as to make that work invalid. The primary purpose of collaboration support tools should be to enable participants in a collaboration to proceed with confidence, knowing that their work is safe from direct and indirect threats, and that they are not accidentally compromising the work of the other participants. The general problem of concurrency control and consistency management in such collaborative projects is addressed by configuration management (CM) systems, which have been the subject of two decades of academic research and industry experience [Feiler 91]. Most CM systems assume central or tightly coupled object repositories, a high degree of trust between participants, and/or implicitly understood consistency criteria. These conditions that fail to apply in many situations in which distributed collaboration is called
/lp/association-for-computing-machinery/consistency-management-for-distributed-collaboration-wffM6Fxik6