Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction
Discussion 4.1 Why Not Use Traditional Extractors?
Related Work
Conclusion and Future Work
References

TA-RE: An exchange language for mining software repositories

Profile image of Oscar NierstraszOscar Nierstrasz

2006

Abstract

Abstract Software repositories have been getting a lot of attention from researchers in recent years. In order to analyze software repositories, it is necessary to first extract raw data from the version control and problem tracking systems. This poses two challenges:(1) extraction requires a non-trivial effort, and (2) the results depend on the heuristics used during extraction.

References (25)

  1. <?xml version="1.0" encoding="utf-8" ?> <T:content xmlns:T="TA-RE:" id="c32" filename="src/edu/ucsc/Kenyon.java"> <T:corpus-version>0.1</T:corpus-version> <T:change-status value="modified"/> <T:reference kind="partof" level="transaction" transaction-id="t40"/> <T:reference kind="fixes" level="content" transaction-id="t29" content-id="c32"/> <T:reference kind="fixed-by" level="content" transaction-id="t45" content-id="c32"/> <T:reference kind="fixed-by" level="content" transaction-id="t99" content-id="c32"/> <T:count kind="accumulated-fix" value="2"/> <T:count kind="accumulated-fix-inducing" value="3"/> <T:count kind="accumulated-change" value="10"/> <T:entity level="class" id="class-foo" name="Foo" start-pos="20" end-pos="2564"> <T:entity level="method" id=" foo" name="foo" return-type="void" parameters="int I, char *var" start-pos="32" end-pos="95"> <T:reference kind="fixes" level="entity"> tansaction-id="t23" content-id="c32" entity-id="foo"/> </T:entity> <T:entity level="method" id=bar" name="bar" return-type="char" parameters="int i, char c" start-pos="103" end-pos="195"> </T:entity> ... </T:entity> </T:content>
  2. REFERENCES
  3. J. Bevan and E. J. Whitehead, Jr., "Identification of Software Instabilities," Proc. of 2003 Working Conference on Reverse Engineering (WCRE 2003), Victoria, Canada, 2003.
  4. J. Bevan, E. J. Whitehead, Jr., S. Kim, and M. Godfrey, "Facilitating Software Evolution with Kenyon," Proc. of the 2005 European Software Engineering Conference and 2005 Foundations of Software Engineering (ESEC/FSE 2005), Lisbon, Portugal, pp. 177-186, 2005.
  5. D. Beyer and A. Noack, "Clustering Software Artifacts Based on Frequent Common Changes," Proc. of the 13th IEEE International Workshop on Program Comprehension (IWPC 2005), St. Louis, Missouri, USA, pp. 259- 268, 2005.
  6. V. Dallmeier, P. Weißgerber, and T. Zimmermann, "APFEL: A Preprocessing Framework For Eclipse," 2005, http://www.st.cs.uni- sb.de/softevo/apfel/.
  7. S. G. Eick, T. L. Graves, A. F. Karr, J. S. Marron, and A. Mockus, "Does Code Decay? Assessing the Evidence from Change Management Data," IEEE Transactions on Software Engineering, vol. 27, pp. 1-12., 2001.
  8. M. Fischer, M. Pinzger, and H. Gall, "Populating a Release History Database from Version Control and Bug Tracking Systems," Proc. of 2003 Int'l Conference on Software Maintenance (ICSM'03), pp. 23-32, 2003.
  9. M. W. Godfrey and L. Zou, "Using Origin Analysis to Detect Merging and Splitting of Source Code Entities," IEEE Trans. on Software Engineering, vol. 31, pp. 166-181, 2005.
  10. T. L. Graves, A. F. Karr, J. S. Marron, and H. Siy, "Predicting Fault Incidence Using Software Change History," IEEE Transactions on Software Engineering, vol. 26, pp. 653-661, 2000.
  11. T. L. Graves and A. Mockus, "Inferring Change Effort from Configuration Management Data," Proc. of In Metrics 98: Fifth International Symposium on Software Metrics, Bethesda, Maryland, pp. 267-273, 1998.
  12. M. Kim, V. Sazawal, D. Notkin, and G. Murphy, "An Empirical Study of Code Clone Genealogies," Proc. of the 2005 European Software Engineering Conference and 2005 Foundations of Software Engineering (ESEC/FSE 2005), Lisbon, Portugal, pp. 187-196, 2005.
  13. S. Kim, K. Pan, and E. J. Whitehead, Jr., "When Functions Change Their Names: Automatic Detection of Origin Relationships," Proc. of 12th Working Conference on Reverse Engineering (WCRE 2005), Pennsylvania, USA, 2005.
  14. S. Kim, E. J. Whitehead, Jr., and J. Bevan, "Analysis of Signature Change Patterns," Proc. of Int'l Workshop on Mining Software Repositories (MSR 2005), Saint Louis, Missouri, USA, pp. 64-68, 2005.
  15. D. Lewis, Y. Yang, T. Rose, and F. Li, "RCV1: A New Benchmark Collection for Text Categorization Research " Journal of Machine Learning Research, vol. 5, pp. 361-397, 2004.
  16. A. Mockus, R. F. Fielding, and J. Herbsleb, "A Case Study of Open Source Development: The Apache Server," Proc. of 22nd Int'l Conference on Software Engineering (ICSE 2000), Limerick, Ireland, pp. 263-272 2000.
  17. A. Mockus and J. Herbsleb, "Expertise Browser: A Quantitative Approach to Identifying Expertise," Proc. of 24rd Int'l Conference on Software Engineering (ICSE 2002), Orlando, Florida, pp. 503-512, 2002.
  18. A. Mockus and L. G. Votta, "Identifying Reasons for Software Changes Using Historic Databases," Proc. of International Conference on Software Maintenance (ICSM 2000), San Jose, California, USA, pp. 120-130, 2000.
  19. A. Mockus and D. M. Weiss, "Globalization by Chunking: a Quantitative Approach," IEEE Software, vol. 18, pp. 30-37, 2001.
  20. A. Mockus, P. Zhang, and P. Li, "Drivers for Customer Perceived Software Quality," Proc. of 2005 Int'l Conference on Software Engineering (ICSE 2005), Saint Louis, Missouri, USA, 2005.
  21. D. J. Newman, S. Hettich, C. L. Blake, and C. J. Merz, "UCI Repository of machine learning databases," 1988, http://www.ics.uci.edu/~mlearn/MLRepository.html.
  22. J. Sayyad Shirabad and T. J. Menzies, "The PROMISE Repository of Software Engineering Databases," 2005, http://promise.site.uottawa.ca/SERepository.
  23. J. Sliwerski, T. Zimmermann, and A. Zeller, "When Do Changes Induce Fixes?" Proc. of Int'l Workshop on Mining Software Repositories (MSR 2005), Saint Louis, Missouri, USA, pp. 24-28, 2005.
  24. T. Zimmermann and P. Weißgerber, "Preprocessing CVS Data for Fine- Grained Analysis," Proc. of Int'l Workshop on Mining Software Repositories (MSR 2004), Edinburgh, Scotland, pp. 2-6, 2004.
  25. T. Zimmermann, P. Weißgerber, S. Diehl, and A. Zeller, "Mining Version Histories to Guide Software Changes," IEEE Trans. Software Engineering, vol. 31, pp. 429-445, 2005.

Related papers

The road ahead for Mining Software Repositories
Ahmed Hassan

2008 Frontiers of Software Maintenance, 2008

Source control repositories, bug repositories, archived communications, deployment logs, and code repositories are examples of software repositories that are commonly available for most software projects. The Mining Software Repositories (MSR) field analyzes and cross-links the rich data available in these repositories to uncover interesting and actionable information about software systems. By transforming these repositories from static record-keeping ones into active repositories, we can guide decision processes in modern software projects. For example, data in source control repositories, traditionally used to archive code, could be linked with data in bug repositories to help practitioners propagate complex changes and to warn them about risky code based on prior changes and bugs. In this paper, we present a brief history of the MSR field and discuss several recent achievements and results of using MSR techniques to support software research and practice. We then discuss the various opportunities and challenges that lie in the road ahead for this important and emerging field.

View PDFchevron_right
Guest editors introduction: special issue on mining software repositories
Stephan Diehl

Empirical Software Engineering, 2009

The Mining Software Repositories (MSR) field analyzes and cross-links the rich data available in software repositories to uncover interesting and actionable information about software systems and projects. Examples of software repositories are:

View PDFchevron_right
Report on MSR 2004: International workshop on mining software repositories
ahmed Hassan

Acm Sigsoft Software Engineering Notes, 2005

A one-day workshop was held on the topic of mining software repositories at ICSE 2004 in Edinburgh, Scotland. The workshop brought together researchers and practitioners in order to consider methods that use data stored in software repositories (such as source control systems, defect tracking systems, and archived project communications) to further understanding of software development practices. We divided submissions into six sessions, each devoted to a particular topic: 1) Infrastructure and Extraction, 2) Integration and Presentation, 3) System Understanding and Change Patterns, 4) Defect Analysis, 5) Process and Community Analysis, and 6) Software Reuse. To maximize interaction and discussion, we limited each session to a survey of the topic area, followed by the presentation of one or two papers, then an open discussion. We also allocated a demo hour to give interested parties the opportunity to learn more about other accepted papers.

View PDFchevron_right
Introduction to the special issue on software repository mining in 2009
Jim Whitehead

2012

This special issue of Empirical Software Engineering consists of revised and extended versions of four selected papers originally presented at the 6th IEEE Working Conference on Mining Software Repositories (MSR 2009). The conference was held in Vancouver, Canada on May 16���17, and was co-located with the 2009 ACM/IEEE International Conference on Software Engineering (ICSE 2009).

View PDFchevron_right
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved