Maintaining Shared Workspaces Consistency during Software Development

The development of large software is always done by teams of people working together and struggling to produce quality software within their budget. Each person in these teams generally knows his job and wants to do it, without being bothered by other people. However, when people work towards a common goal they have to exchange data and create dependencies between each other regarding these data. If these people have to follow a process, cooperating and synchronizing with co-workers and trying to reach one's own goal becomes too difficult to manage. This may leads to frustration, lower productivity and reluctancy to follow the predefined process. This is why some support is needed to avoid common mistakes that occur when people exchange data. In this paper, a hybrid approach to support cooperation is presented. The originality of this approach is the ability to enforce general properties on cooperative interactions while using the semantic of applications to fit particular situations or requirements. This paper gives a brief idea about the general enforced properties on activity interactions. It describes in detail the semantic rules that control activity results, the impacts of the cooperation on these rules and how both of dimensions interact.

[1]  Udo W. Lipeck Stepwise specification of dynamic database behaviour , 1986, SIGMOD '86.

[2]  Udo W. Lipeck,et al.  Transformation of Dynamic Integrity Constraints into Transaction Specifications , 1990, Theor. Comput. Sci..

[3]  Naser S. Barghouti,et al.  Supporting cooperation in the Marvel process-centered SDE , 1992, SDE 5.

[4]  Ahmed K. Elmagarmid,et al.  Introduction to Advanced Transaction Models , 1992, Database Transaction Models for Advanced Applications.

[5]  Andreas Reuter,et al.  Transaction Processing: Concepts and Techniques , 1992 .

[6]  Paul W. P. J. Grefen,et al.  Integrity Control in Relational Database Systems - An Overview , 1993, Data Knowl. Eng..

[7]  Hala Skaf-Molli,et al.  Maintaining Consistency of Cooperative Software Development Activities , 1996, FMLDO.

[8]  Hala Skaf-Molli,et al.  Designing and implementing COO: design process, architectural style, lessons learned , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[9]  J. Davenport Editor , 1960 .

[10]  Claude Godart,et al.  Cooperation Models in Co-Design , 1998 .

[11]  Jacky Estublier,et al.  ADELE-TEMPO: an environment to support process modelling and enaction , 1994 .

[12]  Hala Skaf Une approche hybride pour gérer la cohérence dans les environnements de développement coopératif , 1997 .

[13]  Wilhelm Schäfer,et al.  MERLIN: supporting cooperation in software development through a knowledge-based environment , 1994 .

[14]  Panos K. Chrysanthis,et al.  A taxonomy of correctness criteria in database applications , 1996, The VLDB Journal.

[15]  Claude Godart COO: A Transaction Model to Support COOperating Software Developers COOrdination , 1993, ESEC.