Evolution in software systems: foundations of the SPE classification scheme

Abstract

The SPE taxonomy of evolving software systems, first proposed by Lehman in 1980, is re-examined in this work. The primary concepts of software evolution are related to generic theories of evolution, particularly Dawkins' concept of a replicator, to the hermeneutic tradition in philosophy and to Kuhn's concept of paradigm. These concepts provide the foundations that are needed for understanding the phenomenon of software evolution and for refining the definitions of the SPE categories. In particular, this work argues that a software system should be defined as of type P if its controlling stakeholders have made a strategic decision that the system must comply with a single paradigm in its representation of domain knowledge. The proposed refinement of SPE is expected to provide a more productive basis for developing testable hypotheses and models about possible differences in the evolution of Eand P-type systems than is provided by the original scheme.

Causes of premature aging during software development

“…This study complements Cook and Lehman's description of software evolution [3]. Chaki's approach [15] defines the "how" of software evolution through planned processes, Cook and Lehman try to explain the "what".…”

“…The study of software evolution focuses on the mitigation and control of changes during the lifetime of software systems [3].While erosion is typically concerned with post-development deterioration, evolution is concerned with all changes, whether detrimental or beneficial, throughout the lifecycle of the software. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page.…”

“…It is generally admitted that the architecture of a software component degrades during maintenance activities [1][2][3][4]. Software maintenance introduces new requirements and technological advances [5] which contort existing design structures in unplanned ways.…”

A Process Model of Software Evolution Requirement Based on Feedback

“…Since the phenomenon of software evolution was found in 1960s, it has received great attention [1]. Lehman et al [2] define software evolution as an action of System Dynamics that makes software system continuously maintained and improved.…”

Creative Strategic Scenarios for preparation to requirements evolution

“…In this setting, Software Evolution is currently done under time pressure and some changes can be anticipated in order to better adapt Software Systems that support Organizational Information Systems (SSsOIS) [3]. We will focus on the Lehman's Laws of Software Evolution that relates the Continuing Change of E-systems to their Increasing Complexity, Continuing Growth and Declining Quality, mostly laws' numbers I, II, VI, VII and VIII [4] [5], as well as on the lack of accurate Predictive Models in Software Evolution [6].…”