2009 IEEE International Conference on Industrial Engineering and Engineering Management 2009
DOI: 10.1109/ieem.2009.5373367
|View full text |Cite
|
Sign up to set email alerts
|

A model of open source software maintenance activities

Abstract: The development of computer networks, especially the internet, has largely facilitated the communications among software developers and it resulted a thriving of open source software systems (OSS). As more and more open source software systems are deployed by individuals and enterprises, it is vital to study such systems separately from traditional software systems since their development and maintenance processes are fairly different. In this paper, we investigate a type of behaviors of software maintenance o… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(1 citation statement)
references
References 17 publications
0
1
0
Order By: Relevance
“…However, maintenance activities have never been a straightforward task, it is considered as the most time/effort-consuming and complex task throughout the life cycle of software development [7]. The maintenance practices for traditional software systems have been extensively studied [8,9,10,11,7,12,13,14,15]. These studies focus on a broad range of areas, including examining source-code complexity and software enhancement effort [16], estimating the reliability in the maintenance phase [17], studying the distributions and evolution of technical debts [18,19,20,21], and predicting the prevalence of bugs using anti-patterns [22,23,24] among others.…”
Section: Introductionmentioning
confidence: 99%
“…However, maintenance activities have never been a straightforward task, it is considered as the most time/effort-consuming and complex task throughout the life cycle of software development [7]. The maintenance practices for traditional software systems have been extensively studied [8,9,10,11,7,12,13,14,15]. These studies focus on a broad range of areas, including examining source-code complexity and software enhancement effort [16], estimating the reliability in the maintenance phase [17], studying the distributions and evolution of technical debts [18,19,20,21], and predicting the prevalence of bugs using anti-patterns [22,23,24] among others.…”
Section: Introductionmentioning
confidence: 99%