The non-homogeneous maintenance periods: a case study of software modifications

Change profiles of a reused class framework vs. two of its applications

“…Gefen and Schneberger [14] examined an information system for 29 months and reported that in the first stage, the software was stabilized within the framework of its original specifications and changes were centered on corrective modifications. In the second period, the software was improved and new functions were added to the original framework.…”

“…No study listed in Table 2 performed analysis similar to that in [14,5], i.e. compared the changes of reused software and the software reusing it over time.…”

Comparison of software architecture reverse engineering methods

“…As a system evolves and goes through a number of maintenance releases [13], it naturally inherits functionality and characteristics from previous releases [25,26], and becomes a legacy system. As new functionality and features are added, there is a tendency towards increased complexity.…”

Two case studies in measuring software maintenance effort

“…An example of research on this level is Gefen and Schneberger [4], who look at the distribution of different types of software modifications during the life cycle of a software system. Micro level The costs of individual maintenance tasks.…”