Software Evolution

We use 810 versions of the Linux kernel, released over a period of 14 years, to characterize the system's evolution, using Lehman's laws of software evolution as a basis. We investigate different possible interpretations of these laws, as reflected by different metrics that can be used to quantify them. For example, system growth has traditionally been quantified using lines of code or number of functions, but functional growth of an operating system like Linux can also be quantified using the number of system calls. In addition we use the availability of the source code to track metrics, such as McCabe's cyclomatic complexity, that have not been tracked across so many versions previously. We find that the data supports several of Lehman's laws, mainly those concerned with growth and with the stability of the process. We also make some novel observations, e.g. that the average complexity of functions is decreasing with time, but this is mainly due to the addition of many small functions.

show abstract

“…The laws and their implications are as follows, using the phrasing in [27]. The numbering reflects the order in which they were formulated.…”

Section: Lehman's Laws Of Software Evolutionmentioning

confidence: 99%

The Linux kernel as a case study in software evolution

Israeli

Feitelson

2010

Journal of Systems and Software

112

View full text Add to dashboard Cite

show abstract

“…Lehman and Ramil [2004] provide an appropriate definition for software evolution. In the definition that follows, an attempt has been made to address properties applicable in a general sense.…”

Section: Evolution Models and Theoriesmentioning

confidence: 99%

Understanding Open Source Software Evolution 181

Scacchi

2006

Software Evolution and Feedback

View full text Add to dashboard Cite

“…The software in our lives is increasingly complex; its interaction with the real world means that its requirements are in a state of constant change [6]. Many complex systems, from medical systems to transport and telecommunication control infrastructures, depend on reliable, high-quality software.…”

Section: Introductionmentioning

confidence: 99%

Evolving Critical Systems: A Research Agenda for Computer-Based Systems

Hinchey

Coyle

2010

2010 17th IEEE International Conference and Workshops on Engineering of Computer Based Systems

View full text Add to dashboard Cite

Increasingly software can be considered to be critical, due to the business or other functionality which it supports. Upgrades or changes to such software are expensive and risky, primarily because the software has not been designed and built for ease of change. Expertise, tools and methodologies which support the design and implementation of software systems that evolve without risk (of failure or loss of quality) are essential. We address a research agenda for building software in computer-based systems that (a) is highly reliable and (b) retains this reliability as it evolves, either over time or at run-time.

show abstract

Software Evolution

Cited by 28 publications

References 0 publications

The Linux kernel as a case study in software evolution

The Linux kernel as a case study in software evolution

Understanding Open Source Software Evolution 181

Evolving Critical Systems: A Research Agenda for Computer-Based Systems

Contact Info

Product

Resources

About