The impact of software evolution and reuse on software quality
โ Scribed by Taghi M. Khoshgoftaar; Edward B. Allen; Kalai S. Kalaichelvan; Nishith Goel
- Publisher
- Springer US
- Year
- 1996
- Tongue
- English
- Weight
- 941 KB
- Volume
- 1
- Category
- Article
- ISSN
- 1382-3256
No coin nor oath required. For personal study only.
โฆ Synopsis
This paper presents a case study of a software project in the maintenance phase. The case study was based on a sample of modules, representing about 1.3 million lines of code, from a very large telecommunications system. Software quality models were developed to predict the number of faults expected from the coding through operations phases. Since modules from the prior release were often reused to develop a new release, one model incorporated reuse data as additional independent variables. We compare this model's performance to a similar model without reuse data. Software quality models often have product metrics as the only input data for predicting quality. There is an implicit assumption that all the modules have had a similar development history, so that product attributes are the primary drivers of different quality levels. Reuse of software as components and software evolution do not fit this assumption very well, and consequently, traditional models for such environments may not have adequate accuracy.
Focusing on the software maintenance phase, this study demonstrated that reuse data can significantly improve the predictive accuracy of software quality models.
๐ SIMILAR VOLUMES
A homeless protocol is one in which all nodes are treated identically when they access common resources. By contrast, home-based protocols assign a home or manager to each resource. Use of the resource by the home incurs less overhead than use by other processors. The key to good performance in such
A major difficulty in evaluating the costs of reusing software is determining the amount of reused software artefacts in systems. Determining the amount of reuse in a system is important for software maintenance because reused software is likely to need less corrective maintenance than newly develop
Software analysis, evolution, and reengineering are important areas of the software life cycle. The quest to maintain and keep operational large mission critical systems has always been a challenge for software practitioners. This special issue presents a compilation of papers covering six major are
Preface to the special issue on software evolution, adaptability and variability Welcome to this special issue on Software Evolution, Adaptability and Variability. Software evolution is the term used in software engineering to refer to the process of developing an initial version of the software an
The paper suggests a two-level approach to describe visually software architectures and their evolution. One visual modeling formalism is used to describe the architecture level while another is used to model the behavior of each component (component specification level). Graph transformation is app