Parallel changes in large scale software development: an observational case study

An essential characteristic of large scale software development is parallel development by teams of developers. How this parallel development is structured and supported has a profound effect on both the quality and timeliness of the product. We conduct an observational case study in which me collect and analyze the change and configuration management history of a legacy system to delineate the boundaries of, and to understand the nature of, the problems encountered in parallel development. The results of our studies are: 1) that the degree of parallelism is very high-higher than considered by tool builders; 2) there are multiple levels of parallelism and the data for some important aspects are uniform and consistent for all levels and 3) the tails of the distributions are long, indicating the tail, rather than the mean, must receive serious attention in providing solutions for these problems.

[1]  Rebecca E. Grinter.  Doing Software Development: Occasions for Automation and Formalisation , 1997, ECSCW.

[2]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[3]  Sidney Addelman,et al.  trans-Dimethanolbis(1,1,1-trifluoro-5,5-dimethylhexane-2,4-dionato)zinc(II) , 2008, Acta crystallographica. Section E, Structure reports online.

[4]  A. Strauss,et al.  The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .

[5]  Marc J. Rochkind,et al.  The source code control system , 1975, IEEE Transactions on Software Engineering.

[6]  Dewayne E. Perry,et al.  Implications of evolution metrics on software maintenance , 1998, Proceedings. International Conference on Software Maintenance (Cat. No. 98CB36272).

[7]  Walter F. Tichy,et al.  Implementation and evaluation of a revision control system , 1982 .

[8]  Thomas W. Reps,et al.  Integrating noninterfering versions of programs , 1989, TOPL.

[9]  Harvey P. Siy,et al.  Predicting Fault Incidence Using Software Change History , 2000, IEEE Trans. Software Eng..

[10]  Leon J. Osterweil,et al.  A mechanism for environment integration , 1990, TOPL.

[11]  Dewayne E. Perry,et al.  System Compositions and Shared Dependencies , 1996, SCM.

[12]  K. E. Martersteck,et al.  The 5ESS switching system: Introduction , 1985, AT&T Technical Journal.

[13]  Gail E. Kaiser,et al.  WORKSPACES AND EXPERIMENTAL DATABASES: AUTOMATED SUPPORT FOR SOFTWARE MAINTENANCE AND EVOLUTION. , 1987 .

[14]  Dewayne E. Perry.  The inscape environment , 1989, ICSE '89.

[15]  Axel Mahler,et al.  Variants: keeping things together and telling them apart , 1995 .

[16]  David B. Leblang.  The CM challenge: configuration management that works , 1995 .

[17]  R. Yin.  Case Study Research: Design and Methods , 1984 .

[18]  Eliot R. Smith,et al.  Research methods in social relations , 1962 .

[19]  Jacky Estublier,et al.  The Adele configuration manager , 1995 .

[20]  John M. Chambers,et al.  Graphical Methods for Data Analysis , 1983 .