2006•Unpublished venueRequires access

The Consequences of Variability in Software

I. Levendel

Open publisher page 0 citations

Abstract

Summary form only given. Contrary to many other industrial processes, software production is characterized by an unusually high variance. This directly results from the significant role of the human factor in all the phases of its realization, and this will likely remain the case for a long time to come. In order to set the record straight, this presentation first analyzes various aspects of software metrics that demonstrate the heterogeneous nature of software and the variance in the software production process. We propose a new software model susceptible to acknowledge software variance and take advantage of it for managing the software development process. This model allows the identification of areas of software instability that are caused by the concentration of software defects. Two major applications are derived from the model analysis. First, the model provides a method for evaluating the "goodness" of the software architecture. The model can also be used to balance the budgeting of the testing effort among the various software functionalities and their interactions. We also discuss potential applications of the recognition of software variability for developing reactive real-time methods for improving software dependability

About this research paper

What this paper is about

Summary form only given. Contrary to many other industrial processes, software production is characterized by an unusually high variance. This directly results from the significant role of the human factor in all the phases of its realization, and this will likely remain the case for a long time to come. In order to set the record straight, this presentation first analyzes various aspects of software metrics that demonstrate the heterogeneous nature of software and the variance in the software production process. We propose a new software model susceptible to acknowledge software variance and take advantage of it for managing the software development process. This model allows the identification of areas of software instability that are caused by the concentration of software defects. Two major applications are derived from the model analysis. First, the model provides a method for evaluating the "goodness" of the software architecture. The model can also be used to balance the budgeting of the testing effort among the various software functionalities and their interactions. We also discuss potential applications of the recognition of software variability for developing reactive real-time methods for improving software dependability

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Summary form only given. Contrary to many other industrial processes, software production is characterized by an unusually high variance. This directly results from the significant role of the human factor in all the phases of its realization, and this will likely remain the case for a long time to come. In order to set the record straight, this presentation first analyzes various aspects of software metrics that demonstrate the heterogeneous nature of software and the variance in the software production process. We propose a new software model susceptible to acknowledge software variance and take advantage of it for managing the software development process. This model allows the identification of areas of software instability that are caused by the concentration of software defects. Two major applications are derived from the model analysis. First, the model provides a method for evaluating the "goodness" of the software architecture. The model can also be used to balance the budgeting of the testing effort among the various software functionalities and their interactions. We also discuss potential applications of the recognition of software variability for developing reactive real-time methods for improving software dependability

Key concepts: Computer science, Software construction, Software sizing, Software development, Software engineering, Software metric, Verification and validation, Software

Related papers

Back to paper searchBrowse research topicsOriginal source
The Consequences of Variability in Software — Research Paper | ScholarLens