An empirical study of software design practices

Card, David N.; Church, Victor E.; Agresti, William W.

doi:10.1109/tse.1986.6312942

Cited by 67 publications

(23 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The preliminary analysis showed that several of the dependent variables, such as development effort per source line and faults per source line, were not normally distributed in this environment, which is consistent with earlier studies [30], [31]. Therefore, the primary method for further analysis was through nonparametric analysis of variance (ANOVA) models using ranked data [32].…”

Section: Data Analysis Approachsupporting

confidence: 83%

Enabling reuse-based software development of large-scale systems

Selby

2005

IIEEE Trans. Software Eng.

126

105

View full text Add to dashboard Cite

Abstract-Software reuse enables developers to leverage past accomplishments and facilitates significant improvements in software productivity and quality. Software reuse catalyzes improvements in productivity by avoiding redevelopment and improvements in quality by incorporating components whose reliability has already been established. This study addresses a pivotal research issue that underlies software reuse-what factors characterize successful software reuse in large-scale systems? The research approach is to investigate, analyze, and evaluate software reuse empirically by mining software repositories from a NASA software development environment that actively reuses software. This software environment successfully follows principles of reuse-based software development in order to achieve an average reuse of 32 percent per project, which is the average amount of software either reused or modified from previous systems. We examine the repositories for 25 software systems ranging from 3,000 to 112,000 source lines from this software environment. We analyze four classes of software modules: modules reused without revision, modules reused with slight revision (< 25 percent revision), modules reused with major revision ( 25 percent revision), and newly developed modules. We apply nonparametric statistical models to compare numerous development variables across the 2,954 software modules in the systems. We identify two categories of factors that characterize successful reuse-based software development of large-scale systems: module design factors and module implementation factors. We also evaluate the fault rates of the reused, modified, and newly developed modules. The module design factors that characterize module reuse without revision were (after normalization by size in source lines): few calls to other system modules, many calls to utility functions, few input-output parameters, few reads and writes, and many comments. The module implementation factors that characterize module reuse without revision were small size in source lines and (after normalization by size in source lines): low development effort and many assignment statements. The modules reused without revision had the fewest faults, fewest faults per source line, and lowest fault correction effort. The modules reused with major revision had the highest fault correction effort and highest fault isolation effort as well as the most changes, most changes per source line, and highest change correction effort. In conclusion, we outline future research directions that build on these software reuse ideas and strategies.

show abstract

Section: Data Analysis Approachsupporting

confidence: 83%

Enabling reuse-based software development of large-scale systems

Selby

2005

IIEEE Trans. Software Eng.

126

105

View full text Add to dashboard Cite

show abstract

“…A number of studies demonstrate the significant correlation of software quality metrics with errors in the software design (e.g. [3,5,16,33,34]). In the tradition of this work, there are some works in the 1990s that are mainly rooted in software quality measurement.…”

Section: Related Workmentioning

confidence: 99%

On a Quest for Good Process Models: The Cross-Connectivity Metric

Vanderfeesten

Reijers

Mendling

et al. 2008

Notes on Numerical Fluid Mechanics and Multidisciplinary Design

101

View full text Add to dashboard Cite

Abstract. Business process modeling is an important corporate activity, but the understanding of what constitutes good process models is still rather limited. In this paper, we turn to the cognitive dimensions framework and identify the understanding of the structural relationship between any pair of model elements as a hard mental operation. Based on the weakest-link metaphor, we introduce the cross-connectivity metric that measures the strength of the links between process model elements. The definition of this new metric builds on the hypothesis that process models are easier understood and contain less errors if they have a high cross-connectivity. We undertake a thorough empirical evaluation to test this hypothesis and present the findings. The good performance of this novel metric underlines the importance of cognitive research for advancing the field of process model measurement.

show abstract

“…The inheritance based coupling is ignored. They state that high value of CBO means that high coupling value which result in high maintenance effort and therefore should be avoided [15].…”

Section: Related Workmentioning

confidence: 99%

Measuring Maintenance Effort in Object Oriented Software with Indirect Coupling

Gupta¹,

Rohil²

2012

IJCA

View full text Add to dashboard Cite

Measurement of maintenance effort in object oriented software engineering is one of the major challenges. Coupling among classes is one of the major factors determining the maintenance effort. Coupling is measured as strength of interconnection or interdependence between different parts of the Classes in object oriented software. It is widely accepted that there is strong relationship between high coupling and poor maintainability. Indirect coupling which is transitive in nature manifests between two seemingly unrelated parts of the system through hidden connections plays a major role in determining maintenance effort. This research proposes a set of metrics which determines maintenance effort for software with Indirect Coupling.

show abstract

An empirical study of software design practices

Cited by 67 publications

References 0 publications

Enabling reuse-based software development of large-scale systems

Enabling reuse-based software development of large-scale systems

On a Quest for Good Process Models: The Cross-Connectivity Metric

Measuring Maintenance Effort in Object Oriented Software with Indirect Coupling

Contact Info

Product

Resources

About