Predicting fault-prone modules based on metrics transitions

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Predicting fault-prone modules based on metrics transitions

Full text

Pdf (586 KB)

Source

International Symposium on Software Testing and Analysis archive
Proceedings of the 2008 workshop on Defects in large software systems table of contents

Seattle, Washington

SESSION: Technical papers table of contents

Pages 6-10

Year of Publication: 2008

ISBN:978-1-60558-051-7

Authors

Yoshiki Higo	Osaka University
Kenji Murao	Osaka University
Shinji Kusumoto	Osaka University
Katsuro Inoue	Osaka University

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 7, Downloads (12 Months): 51, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1390817.1390820 What is a DOI?

ABSTRACT

This paper describe a method for identifying fault-prone modules. The method utilizes metrics transitions rather than raw metrics values. Metrics transitions are measured from the source code of consecutive versions, which is archived in software repositories. Metrics transitions should be an good indicator of software quality because they reflect how the software system has evolved. This paper exhibits a case study, which is a comparison between metrics transitions and CK metrics suite. In the case study, the metrics transitions could precisely identify fault-prone modules.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	CVS. http://ximbiot.com/cvs/wiki/.
	2	FreeMind. http://freemind.sourceforge.net/wiki/index.php/Main_Page.
	3	Subversion, http://subversion.tigris.org/.
	4	Victor R. Basili , Lionel C. Briand , Walcélio L. Melo, A Validation of Object-Oriented Design Metrics as Quality Indicators, IEEE Transactions on Software Engineering, v.22 n.10, p.751-761, October 1996 [doi>10.1109/32.544352]
	5	S. R. Chidamber , C. F. Kemerer, A Metrics Suite for Object Oriented Design, IEEE Transactions on Software Engineering, v.20 n.6, p.476-493, June 1994 [doi>10.1109/32.295895]
	6	Thomas J. Ostrand , Elaine J. Weyuker , Robert M. Bell, Predicting the Location and Number of Faults in Large Software Systems, IEEE Transactions on Software Engineering, v.31 n.4, p.340-355, April 2005 [doi>10.1109/TSE.2005.49]
	7	C. E. Shannon. A mathematical theory of communication. The Bell System Technical Journal, 27:379--423, 623--656, 1948.
	8	Ramanath Subramanyam , M. S. Krishnan, Empirical Analysis of CK Metrics for Object-Oriented Design Complexity: Implications for Software Defects, IEEE Transactions on Software Engineering, v.29 n.4, p.297-310, April 2003 [doi>10.1109/TSE.2003.1191795]
	9	Chadd C. Williams , Jeffrey K. Hollingsworth, Automatic Mining of Source Code Repositories to Improve Bug Finding Techniques, IEEE Transactions on Software Engineering, v.31 n.6, p.466-480, June 2005 [doi>10.1109/TSE.2005.63]