2026-09-19T01:25:43Zhttps://dspace.mit.edu/server/oai/request

oai:dspace.mit.edu:1721.1/765662026-06-06T01:05:01Zcom_1721.1_7582com_1721.1_7581col_1721.1_131023

Alan D. MacCormack. Almossawi, Ali Massachusetts Institute of Technology. Engineering Systems Division. System Design and Management Program. Massachusetts Institute of Technology. Engineering Systems Division 2013-01-23T20:22:54Z 2013-01-23T20:22:54Z 2012 2012 http://hdl.handle.net/1721.1/76566 822586716 Thesis (S.M. in Engineering and Management)--Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2012. Cataloged from PDF version of thesis. Includes bibliographical references (p. 64-67). In major software systems that are developed by competent software engineers, the existence of defects in production is unlikely to be an acceptable situation. And yet, we find that in several such systems, defects remain a reality. Furthermore, the number of changes that are fixed only to then be reopened is noticeable. The implications of having defects in a system can be frustrating for all stakeholders, and when they require constant rework, they can lead to the problematic code-test-code-test mode of development. For management, such conditions can result in slipped schedules and an increase in development costs and for upper management and users, they can result in losing confidence in the product. This study looks at the drivers of defects in the mature open-source project GNOME and explores the relationship between the various drivers of these defects and software quality. Using defect-activity and source-code data for 32 systems over a period of eight years, the work presents a multiple regression model capable of explaining 16.2% of defects and a logistic regression model capable of explaining between 13.6% and 18.1% of reopened defects. The study also shows that although defects in general and reopened defects appear to move together, defects in general correlate with a measure of complexity that captures how components connect to each other whereas reopened defects correlate with a measure that captures the inner complexities of components, thereby suggesting that different types of defects are correlated with different forms of complexity. by Ali Almossawi. S.M. in Engineering and Management viii, 6-76 p. eng Massachusetts Institute of Technology M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission. http://dspace.mit.edu/handle/1721.1/7582 System Design and Management Program. Engineering Systems Division. Investigating the architectural drivers of defects in open-source software systems : an empirical study of defects and reopened defects in GNOME Investigating the sources of defects in distributed open source software systems Thesis application/pdf false Publication unknown unknown <Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="222429b0-ca50-4f77-bf02-bb8d4b60e7dc"> <Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843</Type> <Language>eng</Language> <Title>Investigating the architectural drivers of defects in open-source software systems : an empirical study of defects and reopened defects in GNOME</Title> <Subtitle>Investigating the sources of defects in distributed open source software systems</Subtitle> <PublishedIn> <Publication> </Publication> </PublishedIn> <PublicationDate>2012</PublicationDate> <Authors> <Author> <DisplayName>Almossawi, Ali</DisplayName> <Affiliation> <OrgUnit> </OrgUnit> </Affiliation> </Author> </Authors> <Editors> </Editors> <Publishers> <Publisher> <DisplayName>Massachusetts Institute of Technology</DisplayName> <OrgUnit /> </Publisher> </Publishers> <License>http://dspace.mit.edu/handle/1721.1/7582</License> <Keyword>System Design and Management Program.</Keyword> <Keyword>Engineering Systems Division.</Keyword> <Abstract>In major software systems that are developed by competent software engineers, the existence of defects in production is unlikely to be an acceptable situation. And yet, we find that in several such systems, defects remain a reality. Furthermore, the number of changes that are fixed only to then be reopened is noticeable. The implications of having defects in a system can be frustrating for all stakeholders, and when they require constant rework, they can lead to the problematic code-test-code-test mode of development. For management, such conditions can result in slipped schedules and an increase in development costs and for upper management and users, they can result in losing confidence in the product. This study looks at the drivers of defects in the mature open-source project GNOME and explores the relationship between the various drivers of these defects and software quality. Using defect-activity and source-code data for 32 systems over a period of eight years, the work presents a multiple regression model capable of explaining 16.2% of defects and a logistic regression model capable of explaining between 13.6% and 18.1% of reopened defects. The study also shows that although defects in general and reopened defects appear to move together, defects in general correlate with a measure of complexity that captures how components connect to each other whereas reopened defects correlate with a measure that captures the inner complexities of components, thereby suggesting that different types of defects are correlated with different forms of complexity.</Abstract> <Access xmlns="http://purl.org/coar/access_right" > </Access> </Publication>