An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules
The importance of the relationship between size and defect proneness of software modules is well recognized. Understanding the nature of that relationship can facilitate various development decisions related to prioritization of quality assurance activities. Overall, the previous research only drew...
Gespeichert in:
Veröffentlicht in: | IEEE transactions on software engineering 2009-03, Vol.35 (2), p.293-304 |
---|---|
Hauptverfasser: | , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 304 |
---|---|
container_issue | 2 |
container_start_page | 293 |
container_title | IEEE transactions on software engineering |
container_volume | 35 |
creator | Koru, A.G. Dongsong Zhang El Emam, K. Hongfang Liu |
description | The importance of the relationship between size and defect proneness of software modules is well recognized. Understanding the nature of that relationship can facilitate various development decisions related to prioritization of quality assurance activities. Overall, the previous research only drew a general conclusion that there was a monotonically increasing relationship between module size and defect proneness. In this study, we analyzed class-level size and defect data in order to increase our understanding of this crucial relationship. In order to obtain validated and more generalizable results, we studied four large-scale object-oriented products, Mozilla, Cn3d, JBoss, and Eclipse. Our results consistently revealed a significant effect of size on defect proneness; however, contrary to common intuition, the size-defect relationship took a logarithmic form, indicating that smaller classes were proportionally more problematic than larger classes. Therefore, practitioners should consider giving higher priority to smaller modules when planning focused quality assurance activities with limited resources. For example, in Mozilla and Eclipse, an inspection strategy investing 80% of available resources on 100-LOC classes and the rest on 1,000-LOC classes would be more than twice as cost effective as the opposite strategy. These results should be immediately useful to guide focused quality assurance activities in large-scale software projects. |
doi_str_mv | 10.1109/TSE.2008.90 |
format | Article |
fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_proquest_miscellaneous_903636533</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>4693715</ieee_id><sourcerecordid>34441000</sourcerecordid><originalsourceid>FETCH-LOGICAL-c375t-cefc7749c6bd0d49f3d4076bbc88f528df8b633c4347c5ef55bacf52b340e10e3</originalsourceid><addsrcrecordid>eNqF0cFPwyAUBnBiNHFOTx69EA96MJ2PAS0czXRqojFxerVp6UNrujKh1ehfL3PGgwc9kTx-EPg-QnYZjBgDfXw3OxuNAdRIwxoZMM11wuUY1skAQKtESqU3yVYIzwAgs0wOyMNJSy_bVwxd_Vh0tWtp3XaOdk9Ip31rlpOioVPn59TZr_Gs_sDkFC2ajt5i83UoPNULap2nM2e7t8IjvXZV32DYJhu2aALufK9Dcj89u5tcJFc355eTk6vE8Ex2iUFrskxok5YVVEJbXgnI0rI0Slk5VpVVZcq5EVxkRqKVsixM3Ci5AGSAfEgOV_cuvHvp42_yeR0MNk3RoutDroGnPJWc_ytVqpWUYqyjPPhTciEEi0FGuP8LPrvex9xCznTMHASIiI5WyHgXgkebL3w9L_x7ziBflpfH8vJlecvHDsneSteI-CNFqnnGJP8Elc6Uxg</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>195580404</pqid></control><display><type>article</type><title>An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules</title><source>IEEE Electronic Library (IEL)</source><creator>Koru, A.G. ; Dongsong Zhang ; El Emam, K. ; Hongfang Liu</creator><creatorcontrib>Koru, A.G. ; Dongsong Zhang ; El Emam, K. ; Hongfang Liu</creatorcontrib><description>The importance of the relationship between size and defect proneness of software modules is well recognized. Understanding the nature of that relationship can facilitate various development decisions related to prioritization of quality assurance activities. Overall, the previous research only drew a general conclusion that there was a monotonically increasing relationship between module size and defect proneness. In this study, we analyzed class-level size and defect data in order to increase our understanding of this crucial relationship. In order to obtain validated and more generalizable results, we studied four large-scale object-oriented products, Mozilla, Cn3d, JBoss, and Eclipse. Our results consistently revealed a significant effect of size on defect proneness; however, contrary to common intuition, the size-defect relationship took a logarithmic form, indicating that smaller classes were proportionally more problematic than larger classes. Therefore, practitioners should consider giving higher priority to smaller modules when planning focused quality assurance activities with limited resources. For example, in Mozilla and Eclipse, an inspection strategy investing 80% of available resources on 100-LOC classes and the rest on 1,000-LOC classes would be more than twice as cost effective as the opposite strategy. These results should be immediately useful to guide focused quality assurance activities in large-scale software projects.</description><identifier>ISSN: 0098-5589</identifier><identifier>EISSN: 1939-3520</identifier><identifier>DOI: 10.1109/TSE.2008.90</identifier><identifier>CODEN: IESEDJ</identifier><language>eng</language><publisher>New York: IEEE</publisher><subject>Computer programs ; Cost analysis ; Defects ; Density measurement ; Digital Object Identifier ; Eclipses ; Inspection ; Large-scale systems ; Literature reviews ; Modules ; Object oriented modeling ; Open source software ; Planning for SQA and Measurement applied to SQA and Software Quality/SQA ; Predictive models ; Product metrics ; Quality assurance ; Quality control ; Regression analysis ; Research methodology ; Size measurement ; Software ; Software Engineering ; Software measurement ; Software quality ; Software science ; Software/Software Engin ; Strategy</subject><ispartof>IEEE transactions on software engineering, 2009-03, Vol.35 (2), p.293-304</ispartof><rights>Copyright IEEE Computer Society Mar/Apr 2009</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c375t-cefc7749c6bd0d49f3d4076bbc88f528df8b633c4347c5ef55bacf52b340e10e3</citedby><cites>FETCH-LOGICAL-c375t-cefc7749c6bd0d49f3d4076bbc88f528df8b633c4347c5ef55bacf52b340e10e3</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/4693715$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,776,780,792,27901,27902,54733</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/4693715$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Koru, A.G.</creatorcontrib><creatorcontrib>Dongsong Zhang</creatorcontrib><creatorcontrib>El Emam, K.</creatorcontrib><creatorcontrib>Hongfang Liu</creatorcontrib><title>An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules</title><title>IEEE transactions on software engineering</title><addtitle>TSE</addtitle><description>The importance of the relationship between size and defect proneness of software modules is well recognized. Understanding the nature of that relationship can facilitate various development decisions related to prioritization of quality assurance activities. Overall, the previous research only drew a general conclusion that there was a monotonically increasing relationship between module size and defect proneness. In this study, we analyzed class-level size and defect data in order to increase our understanding of this crucial relationship. In order to obtain validated and more generalizable results, we studied four large-scale object-oriented products, Mozilla, Cn3d, JBoss, and Eclipse. Our results consistently revealed a significant effect of size on defect proneness; however, contrary to common intuition, the size-defect relationship took a logarithmic form, indicating that smaller classes were proportionally more problematic than larger classes. Therefore, practitioners should consider giving higher priority to smaller modules when planning focused quality assurance activities with limited resources. For example, in Mozilla and Eclipse, an inspection strategy investing 80% of available resources on 100-LOC classes and the rest on 1,000-LOC classes would be more than twice as cost effective as the opposite strategy. These results should be immediately useful to guide focused quality assurance activities in large-scale software projects.</description><subject>Computer programs</subject><subject>Cost analysis</subject><subject>Defects</subject><subject>Density measurement</subject><subject>Digital Object Identifier</subject><subject>Eclipses</subject><subject>Inspection</subject><subject>Large-scale systems</subject><subject>Literature reviews</subject><subject>Modules</subject><subject>Object oriented modeling</subject><subject>Open source software</subject><subject>Planning for SQA and Measurement applied to SQA and Software Quality/SQA</subject><subject>Predictive models</subject><subject>Product metrics</subject><subject>Quality assurance</subject><subject>Quality control</subject><subject>Regression analysis</subject><subject>Research methodology</subject><subject>Size measurement</subject><subject>Software</subject><subject>Software Engineering</subject><subject>Software measurement</subject><subject>Software quality</subject><subject>Software science</subject><subject>Software/Software Engin</subject><subject>Strategy</subject><issn>0098-5589</issn><issn>1939-3520</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2009</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><sourceid>8G5</sourceid><sourceid>BENPR</sourceid><sourceid>GUQSH</sourceid><sourceid>M2O</sourceid><recordid>eNqF0cFPwyAUBnBiNHFOTx69EA96MJ2PAS0czXRqojFxerVp6UNrujKh1ehfL3PGgwc9kTx-EPg-QnYZjBgDfXw3OxuNAdRIwxoZMM11wuUY1skAQKtESqU3yVYIzwAgs0wOyMNJSy_bVwxd_Vh0tWtp3XaOdk9Ip31rlpOioVPn59TZr_Gs_sDkFC2ajt5i83UoPNULap2nM2e7t8IjvXZV32DYJhu2aALufK9Dcj89u5tcJFc355eTk6vE8Ex2iUFrskxok5YVVEJbXgnI0rI0Slk5VpVVZcq5EVxkRqKVsixM3Ci5AGSAfEgOV_cuvHvp42_yeR0MNk3RoutDroGnPJWc_ytVqpWUYqyjPPhTciEEi0FGuP8LPrvex9xCznTMHASIiI5WyHgXgkebL3w9L_x7ziBflpfH8vJlecvHDsneSteI-CNFqnnGJP8Elc6Uxg</recordid><startdate>20090301</startdate><enddate>20090301</enddate><creator>Koru, A.G.</creator><creator>Dongsong Zhang</creator><creator>El Emam, K.</creator><creator>Hongfang Liu</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>97E</scope><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7X7</scope><scope>7XB</scope><scope>87Z</scope><scope>88E</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FI</scope><scope>8FJ</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>FYUFA</scope><scope>F~G</scope><scope>GHDGH</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>K9.</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M0S</scope><scope>M1P</scope><scope>M1Q</scope><scope>M2O</scope><scope>M2P</scope><scope>M2T</scope><scope>M7S</scope><scope>MBDVC</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>7SP</scope><scope>8FD</scope><scope>F28</scope><scope>FR3</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>20090301</creationdate><title>An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules</title><author>Koru, A.G. ; Dongsong Zhang ; El Emam, K. ; Hongfang Liu</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c375t-cefc7749c6bd0d49f3d4076bbc88f528df8b633c4347c5ef55bacf52b340e10e3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2009</creationdate><topic>Computer programs</topic><topic>Cost analysis</topic><topic>Defects</topic><topic>Density measurement</topic><topic>Digital Object Identifier</topic><topic>Eclipses</topic><topic>Inspection</topic><topic>Large-scale systems</topic><topic>Literature reviews</topic><topic>Modules</topic><topic>Object oriented modeling</topic><topic>Open source software</topic><topic>Planning for SQA and Measurement applied to SQA and Software Quality/SQA</topic><topic>Predictive models</topic><topic>Product metrics</topic><topic>Quality assurance</topic><topic>Quality control</topic><topic>Regression analysis</topic><topic>Research methodology</topic><topic>Size measurement</topic><topic>Software</topic><topic>Software Engineering</topic><topic>Software measurement</topic><topic>Software quality</topic><topic>Software science</topic><topic>Software/Software Engin</topic><topic>Strategy</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Koru, A.G.</creatorcontrib><creatorcontrib>Dongsong Zhang</creatorcontrib><creatorcontrib>El Emam, K.</creatorcontrib><creatorcontrib>Hongfang Liu</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 2005-present</collection><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>ABI/INFORM Collection</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>Health & Medical Collection</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (Alumni Edition)</collection><collection>Medical Database (Alumni Edition)</collection><collection>Military Database (Alumni Edition)</collection><collection>Science Database (Alumni Edition)</collection><collection>Telecommunications (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Hospital Premium Collection</collection><collection>Hospital Premium Collection (Alumni Edition)</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies & Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>Business Premium Collection (Alumni)</collection><collection>Health Research Premium Collection</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>Health Research Premium Collection (Alumni)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer Science Database</collection><collection>ProQuest Health & Medical Complete (Alumni)</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing Database</collection><collection>Health & Medical Collection (Alumni Edition)</collection><collection>Medical Database</collection><collection>Military Database</collection><collection>Research Library</collection><collection>Science Database</collection><collection>Telecommunications Database</collection><collection>Engineering Database</collection><collection>Research Library (Corporate)</collection><collection>Advanced Technologies & Aerospace Database</collection><collection>ProQuest Advanced Technologies & Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Electronics & Communications Abstracts</collection><collection>Technology Research Database</collection><collection>ANTE: Abstracts in New Technology & Engineering</collection><collection>Engineering Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>IEEE transactions on software engineering</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Koru, A.G.</au><au>Dongsong Zhang</au><au>El Emam, K.</au><au>Hongfang Liu</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules</atitle><jtitle>IEEE transactions on software engineering</jtitle><stitle>TSE</stitle><date>2009-03-01</date><risdate>2009</risdate><volume>35</volume><issue>2</issue><spage>293</spage><epage>304</epage><pages>293-304</pages><issn>0098-5589</issn><eissn>1939-3520</eissn><coden>IESEDJ</coden><abstract>The importance of the relationship between size and defect proneness of software modules is well recognized. Understanding the nature of that relationship can facilitate various development decisions related to prioritization of quality assurance activities. Overall, the previous research only drew a general conclusion that there was a monotonically increasing relationship between module size and defect proneness. In this study, we analyzed class-level size and defect data in order to increase our understanding of this crucial relationship. In order to obtain validated and more generalizable results, we studied four large-scale object-oriented products, Mozilla, Cn3d, JBoss, and Eclipse. Our results consistently revealed a significant effect of size on defect proneness; however, contrary to common intuition, the size-defect relationship took a logarithmic form, indicating that smaller classes were proportionally more problematic than larger classes. Therefore, practitioners should consider giving higher priority to smaller modules when planning focused quality assurance activities with limited resources. For example, in Mozilla and Eclipse, an inspection strategy investing 80% of available resources on 100-LOC classes and the rest on 1,000-LOC classes would be more than twice as cost effective as the opposite strategy. These results should be immediately useful to guide focused quality assurance activities in large-scale software projects.</abstract><cop>New York</cop><pub>IEEE</pub><doi>10.1109/TSE.2008.90</doi><tpages>12</tpages></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | ISSN: 0098-5589 |
ispartof | IEEE transactions on software engineering, 2009-03, Vol.35 (2), p.293-304 |
issn | 0098-5589 1939-3520 |
language | eng |
recordid | cdi_proquest_miscellaneous_903636533 |
source | IEEE Electronic Library (IEL) |
subjects | Computer programs Cost analysis Defects Density measurement Digital Object Identifier Eclipses Inspection Large-scale systems Literature reviews Modules Object oriented modeling Open source software Planning for SQA and Measurement applied to SQA and Software Quality/SQA Predictive models Product metrics Quality assurance Quality control Regression analysis Research methodology Size measurement Software Software Engineering Software measurement Software quality Software science Software/Software Engin Strategy |
title | An Investigation into the Functional Form of the Size-Defect Relationship for Software Modules |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-02T03%3A03%3A41IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=An%20Investigation%20into%20the%20Functional%20Form%20of%20the%20Size-Defect%20Relationship%20for%20Software%20Modules&rft.jtitle=IEEE%20transactions%20on%20software%20engineering&rft.au=Koru,%20A.G.&rft.date=2009-03-01&rft.volume=35&rft.issue=2&rft.spage=293&rft.epage=304&rft.pages=293-304&rft.issn=0098-5589&rft.eissn=1939-3520&rft.coden=IESEDJ&rft_id=info:doi/10.1109/TSE.2008.90&rft_dat=%3Cproquest_RIE%3E34441000%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=195580404&rft_id=info:pmid/&rft_ieee_id=4693715&rfr_iscdi=true |