Skip to main content
SpringerLink
Log in

Software Support Tools and Experimental Work

  • Chapter
Empirical Software Engineering Issues. Critical Assessment and Future Directions

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 4336))

Abstract

Presently it is difficult to imagine a software project without version control and problem tracking systems. This may be partly attributed to the emergence of open source projects where participants never meet each other and increasingly popular commercial globally distributed projects where groups of developers are often separated by many time zones. Version control and problem tracking tools are a basic necessity in such communication-poor environments. However, their value is getting more and more recognized in small co-located projects because information stored in these tools represent most of the project’s decision making history.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Atkins, D., Ball, T., Graves, T., Mockus, A.: Using version control data to evaluate the impact of software tools: A case study of the version editor. IEEE Transactions on Software Engineering 28(7), 625–637 (2002)

    Article  Google Scholar 

  2. Atkins, D.L., Mockus, A., Siy, H.P.: Quantifying the Value of New Technologies for Software Development. In: Value Based Software Engineering, pp. 327–344. Springer, Heidelberg (2006)

    Chapter  Google Scholar 

  3. Cedeqvist, P., et al.: CVS Manual. May be found on: http://www.cvshome.org/CVS/

  4. Collins-Sussman, B., Fitzpatrick, B.W., Pilato, C.M.: Subversion Manual. May be found on: http://svnbook.red-bean.com/

  5. Cubranic, D., Murphy, G.C.: Hipikat: A project memory for software development. TSE 31(6) (2005)

    Google Scholar 

  6. Dinh-Trong, T., Bieman, J.M.: Open source software development: A case study of freebsd. IEEE Transactions of Software Engineering 31(6) (2005)

    Google Scholar 

  7. Geppert, B., Mockus, A., Rößler, F.: Refactoring for changeability: A way to go? In: Metrics 2005: 11th International Symposium on Software Metrics, Como, September 2005, IEEE Computer Society Press, Los Alamitos (2005)

    Google Scholar 

  8. German, D., Mockus, A.: Automating the measurement of open source projects. In: ICSE ’03 Workshop on Open Source Software Engineering, page Automating the Measurement of Open Source Projects, Portland, Oregon, May 3-10 (2003)

    Google Scholar 

  9. Graves, T.L., Karr, A.F., Marron, J.S., Siy, H.: Predicting fault incidence using software change history. IEEE Transactions on Software Engineering 26(2) (2000)

    Google Scholar 

  10. Graves, T.L., Mockus, A.: Inferring programmer effort from software databases. In: 22nd European Meeting of Statisticians and 7th Vilnius Conference on Probability Theory and Mathematical Statistics, Vilnius, Lithuania, August, p. 334 (1998)

    Google Scholar 

  11. Herbsleb, J., Mockus, A.: Formulation and preliminary test of an empirical theory of coordination in software engineering. In: 2003 International Conference on Foundations of Software Engineering, Helsinki, Finland, October 2003, ACM Press, New York (2003)

    Google Scholar 

  12. Herbsleb, J.D., Mockus, A., Finholt, T.A., Grinter, R.E.: An empirical study of global software development: Distance and speed. In: 23nd International Conference on Software Engineering, Toronto, Canada, May 12-19, pp. 81–90 (2001)

    Google Scholar 

  13. Kim, M., Notkin, D.: Using a clone genealogy extractor for understanding and supporting evolution of code clones. In: International Workshop on Mining Software Repositories (2005)

    Google Scholar 

  14. Midha, A.K.: Software configuration management for the 21st century. Bell Labs Technical Journal 2(1) (1997)

    Google Scholar 

  15. Mockus, A.: Description and roadmap for a system to measure open source projects. Link to roadmap off, http://sourcechange.sourceforge.net/

  16. Mockus, A.: Analogy based prediction of work item flow in software projects: a case study. In: 2003 International Symposium on Empirical Software Engineering, Rome, Italy, October 2003, pp. 110–119. ACM Press, New York (2003)

    Chapter  Google Scholar 

  17. Mockus, A.: Empirical estimates of software availability of deployed systems. In: 2006 International Symposium on Empirical Software Engineering, page to appear, Rio de Janeiro, Brazil, September 21-22, 2006, ACM Press, New York (2006)

    Google Scholar 

  18. Mockus, A., Fielding, R.T., Herbsleb, J.: Two case studies of open source software development: Apache and mozilla. ACM Transactions on Software Engineering and Methodology 11(3), 1–38 (2002)

    Article  Google Scholar 

  19. Mockus, A., Herbsleb, J.: Expertise browser: A quantitative approach to identifying expertise. In: 2002 International Conference on Software Engineering, Orlando, Florida, May 19-25, 2002, pp. 503–512. ACM Press, New York (2002)

    Google Scholar 

  20. Mockus, A., Votta, L.G.: Identifying reasons for software change using historic databases. In: International Conference on Software Maintenance, San Jose, California, October 11-14, pp. 120–130 (2000)

    Google Scholar 

  21. Mockus, A., Weiss, D.M.: Predicting risk of software changes. Bell Labs Technical Journal 5(2), 169–180 (2000)

    Article  Google Scholar 

  22. Mockus, A., Weiss, D.M.: Globalization by chunking: a quantitative approach. IEEE Software 18(2), 30–37 (2001)

    Article  Google Scholar 

  23. Mockus, A., Weiss, D.M., Zhang, P.: Understanding and predicting effort in software projects. In: 2003 International Conference on Software Engineering, Portland, Oregon, May 3-10, 2003, pp. 274–284. ACM Press, New York (2003)

    Chapter  Google Scholar 

  24. Mockus, A., Zhang, P., Li, P.: Drivers for customer perceived software quality. In: ICSE 2005, St Louis, Missouri, May 2005. ACM Press, New York (2005)

    Google Scholar 

  25. Rational Software Corporation. ClearCase Manual. May be found on: http://www.rational.com/

  26. Rochkind, M.J.: The source code control system. IEEE Trans. on Software Engineering 1(4), 364–370 (1975)

    Google Scholar 

  27. Ying, A., Murphy, G., Ng, R., Chu-Carroll, M.: Predicting source code changes by mining change history. IEEE Transactions of Software Engineering 30(9) (2004)

    Google Scholar 

Download references

Authors
  1. Audris Mockus
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Victor R. Basili Dieter Rombach Kurt Schneider Barbara Kitchenham Dietmar Pfahl Richard W. Selby

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Springer Berlin Heidelberg

About this chapter

Cite this chapter

Mockus, A. (2007). Software Support Tools and Experimental Work. In: Basili, V.R., Rombach, D., Schneider, K., Kitchenham, B., Pfahl, D., Selby, R.W. (eds) Empirical Software Engineering Issues. Critical Assessment and Future Directions. Lecture Notes in Computer Science, vol 4336. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-71301-2_25

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-71301-2_25

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-71300-5

  • Online ISBN: 978-3-540-71301-2

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation