2002
DOI: 10.1046/j.1365-2575.2002.00117.x
|View full text |Cite
|
Sign up to set email alerts
|

Code quality analysis in open source software development

Abstract: Proponents of open source style software development claim that better software is produced using this model compared with the traditional closed model. However, there is little empirical evidence in support of these claims. In this paper, we present the results of a pilot case study aiming: (a) to understand the implications of structural quality; and (b) to figure out the benefits of structural quality analysis of the code delivered by open source style development. To this end, we have measured quality char… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
129
0
5

Year Published

2006
2006
2022
2022

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 230 publications
(134 citation statements)
references
References 21 publications
0
129
0
5
Order By: Relevance
“…VerifySoft Technology suggest a threshold of 15 per function, and 100 per file [29]. The Logiscope tool also uses a threshold of 15 [27]. The STAN static analysis tool gives a warning at 15, and considers values above 20 as an error [17].…”
Section: Mccabe's Cyclomatic Complexitymentioning
confidence: 99%
See 1 more Smart Citation
“…VerifySoft Technology suggest a threshold of 15 per function, and 100 per file [29]. The Logiscope tool also uses a threshold of 15 [27]. The STAN static analysis tool gives a warning at 15, and considers values above 20 as an error [17].…”
Section: Mccabe's Cyclomatic Complexitymentioning
confidence: 99%
“…This metric essentially counts the number of linear paths through the code (the precise definition is given below in Section II). In the original paper, McCabe suggests that procedures with an MCC value higher than 10 should be rewritten or split in order to reduce their complexity, and other slightly higher thresholds have also been suggested by others [18], [26], [27], [29]. However, these are limited to about 50, and there appears to be some agreement that procedures with much higher values are extremely undesirable.…”
Section: Introductionmentioning
confidence: 99%
“…The literature has not reflected the variety observed in the OSS phenomenon, but rather has focused on large, successful, and community-driven OSS projects. Moreover, Capiluppi et al [40] provide evidence that the majority of OSS projects struggle to attract contributors, Noll [142] shows that OSS can also be developed inside commercial software development companies without any active communities, and Stamelos et al [177] show that the quality of OSS software is not always as good as expected. Finally, Fitzgerald [79] argues that the OSS phenomenon has evolved into a more commercially viable form where volunteers and commercial organizations collaboratively contribute to evolving the phenomenon.…”
Section: Open Source Softwarementioning
confidence: 99%
“…Stamelos et al [31] presented empirical results on the relationship between the size of application components and the delivered quality measured as user satisfaction. Quality characteristics of 100 applications written for GNU/Linux were compared to industrial standards.…”
Section: Related Workmentioning
confidence: 99%