Academia.eduAcademia.edu

Outline

Title
Abstract
Introduction
Fault Analysis
Conclusion
References

Text is software too

Profile image of Tim MenziesTim Menzies

2004

https://doi.org/10.1049/IC:20040470
visibility

…

description

5 pages

link

1 file

Abstract

Abstract Software compiles and therefore is characterized by a parseable grammar. Natural language text rarely conforms to prescriptive grammars and therefore is much harder to parse. Mining parseable structures is easier than mining less structured entities. Therefore, most work on mining repositories focuses on software, not natural language text.

Related papers

Incorporating Wikis into software repository mining
James Kiper

2007

Software engineering projects produce large volumes of information that are collected in specialized, decentralized repositories. Combining information from these sources may aid in gaining accurate knowledge about the arguments and alternatives (e.g. rationale) that factor into the decision making and design process. This information is captured in synchronized systems: version control systems (such as CVS or Subversion), defect tracking systems (such as Bugzilla or Trac), and Wikis and in unsynchronized systems: email discussion lists and Web-based discussion forums. Our proposed research path involves combining these synchronized and unsynchronized sources of information in order to advance the field of mining software repositories (MSR). In this paper we discuss plans for the integration of these five sources of information and how unsynchronized information might be used to reason about actions captured in the synchronized systems.

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
The need for software specific natural language techniques
Christopher Morrell

Empirical Software Engineering, 2017

For over two decades, software engineering (SE) researchers have been importing tools and techniques from information retrieval (IR). Initial results have been quite positive. For example, when applied to problems such as feature location or re-establishing traceability links, IR techniques work well on their own, and often even better in combination with more traditional source code analysis techniques such as static and dynamic analysis. However, recently there has been growing awareness among SE researchers that IR tools and techniques are designed to work under different assumptions than those that hold for a software system. Thus it may be beneficial to consider IR-inspired tools and techniques that are specifically designed to work with software. One aim of this work is to provide quantitative empirical evidence in support of this observation. To do so a new technique is introduced that captures the level of difficulty found in an information need, the true, often latent, information that a searcher desires to know. The new technique is used to compare two domains: Natural Language (NL) and SE. Analysis of the data leads to three significant findings. First, the variation in the distribution of difficulty of the SE information needs differs from that of the NL information needs; second, collection age plays a role in the differences between the NL collections; and finally, the retrieval model used has little impact on the results.

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
Introduction to the special issue on software repository mining in 2009
Olga Baysal

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

References (21)

  1. R. Baeza-Yates and B. Ribeiro-Neto. Modern Infor mation Retrieval. ACM Press, Addison-Wesley, 1999.
  2. B. Boehm. Software Engineering Economics. Prentice- Hall, Englewood Cliffs, NJ, 1981.
  3. P. Clark and T. Ng. The cn2 induction algorithm. Machine Learning, 3:261-283, 1989.
  4. S. Deerwester, S. T. Dumais, T. K. Landauer, G. W. Furnas, and R. A. Harshman. Indexing by latent se mantic analysis. Journal of the Society for Information Science, 41(6):391-407, 1990.
  5. G. Di Lucca, M. Di Penta, and S. Gradara. An ap proach to classify software maintenance requests. In Proc., International Conference on Software Mainte nance (ICSM), 2002.
  6. S. Easterbrook, R. R. Lutz, R. Covington, J. Kelly, Y. Ampo, and D. Hamilton. Experiences using lightweight formal methods for requirements modeling. IEEE Transactions on Software Engineering, pages 4- 14, 1998.
  7. M. Halstead. Elements of Software Science. Elsevier, 1977.
  8. J. Hayes. Risk reduction through requirements trac ing. In The Conference Proceedings of Software Quality Week, 1990.
  9. J. H. Hayes. Input validation testing: A system level, early lifecycle technique. In ICSE '97 Doctoral Con sortium, published in the Proceedings of the Seven teenth International Conference on Software Engineer ing Doctoral Consortium, May 1997.
  10. J. H. Hayes, A. Dekhtyar, and J. Osbourne. Improving requirements tracing via information retrieval. In In ternational Conference on Requirements Engineering, Monterey, California, pages 151-161, 2003.
  11. J. H. Hayes, A. Dekhtyar, S. Sundaram, and S. Howard. Helping analysts trace requirements: An objective look. In International Conference on Re quirements Engineering (RE'2004), 2004.
  12. J. H. Hayes and J. Offutt. Input validation testing: A requirements-driven, system level, early lifecycle tech nique. In Proceedings of the 11th International Con ference on Software Engineering and its Applications, October 1998.
  13. J. H. Hayes and J. Offutt. Increased software reliabil ity through input validation analysis and testing. In Proceedings of The Tenth IEEE International Sympo sium on Software Reliability Engineering, pages 199- 209, 1999.
  14. W. Hersh and P. Over. The trec-9 interactive track report. In Proc. Text Retrieval Conference (TREC-9), pages 41-50, 2000.
  15. G. Holzmann. The model checker SPIN. IEEE Trans actions on Software Engineering, 23(5):279-295, May 1997.
  16. T. Joachims. Text categorization with suport vector machines: Learning with many relevant features. In Proc. ECML, pages 137-142, 1998.
  17. B. Lee and B. Bryant. Contextual knowledge repre sentation for requirements documents in natural lan guage. In Proceedings of FLAIRS, the 15th Interna tional Florida Artificial Intelligence Research Sympo sium, 2002.
  18. T. McCabe. A complexity measure. IEEE Trans actions on Software Engineering, 2(4):308-320, Dec. 1976.
  19. T. Menzies, J. S. D. Stefano, C. Cunanan, and R. M. Chapman. Mining repositories to assist in project planning and resource allocation. In International Workshop on Mining Software Repositories (submit ted), 2004. Available from http://menzies.us/pdf/ 04msrdefects.pdf.
  20. T. Mundie and F. Hallsworth. Requirements analy sis using supertrace pc. In Proc. American Society of Mechanical Engineers (ASME) for Computers in Engi neering Symposium at the Energy and Environmental Expo, 1995.
  21. D. R. Smith. KIDS: A semiautomatic program devel opment system. IEEE Transactions on Software En gineering, 16(9):1024-1043, 1990.

Related papers

Natural language processing in mining unstructured data from software repositories: a review
som gupta

Sādhanā

With the increasing popularity of open-source platforms, software data is easily available from various open-source tools like GitHub, CVS, SVN, etc. More than 80 percent of the data present in them is unstructured. Mining data from these repositories helps project managers, developers and businesses, in getting interesting insights. Most of the software artefacts present in these repositories are in the natural language form, which makes natural language processing (NLP) an important part of mining to get the useful results. The paper reviews the application of NLP techniques in the field of Mining Software Repositories (MSR). The paper mainly focuses on sentiment analysis, summarization, traceability, norms mining and mobile analytics. The paper presents the major NLP works performed in this area by surveying the research papers from 2000 to 2018. The paper firstly describes the major artefacts present in the software repositories where the NLP techniques have been applied. Next, the paper presents some popular open-source NLP tools that have been used to perform NLP tasks. Later the paper discusses, in brief, the research state of NLP in MSR field. The paper also lists down the various challenges along with the pointers for future work in this field of research and finally the conclusion.

View PDFchevron_right
TA-RE: An exchange language for mining software repositories
Oscar Nierstrasz

2006

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.

View PDFchevron_right
Mining Software Repositories – A Comparative Analysis
Sunday Olatunji

Article CITATIONS 0 READS 554 5 authors, including:

View PDFchevron_right
Emerging topics in mining software repositories
Raúl Marticorena

Progress in Artificial Intelligence, 2018

A software process is a set of related activities that culminates in the production of a software package: specification, design, implementation, testing, evolution into new versions, and maintenance. There are also other supporting activities such as configuration and change management, quality assurance, project management, evaluation of user experience, etc. Software repositories are infrastructures to support all these activities. They can be composed with several systems that include code change management, bug tracking, code review, build system, release binaries, wikis, forums, etc. This position paper on mining software repositories presents a review and a discussion of research in this field over the past decade. We also identify applied machine learning strategies, current working topics, and future challenges for the improvement of company decision-making systems. Machine learning is defined as the process of discovering patterns in data. It can be applied to software repositories, since every change is recorded as data. Companies can then use these patterns as the basis for their decision-making systems and for knowledge discovery.

View PDFchevron_right
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
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved