Software complexity and software maintenance: A survey of empirical research

Kemerer, Chris F.

doi:10.1007/bf02249043

Cited by 93 publications

(55 citation statements)

References 46 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…SLOC controls for size and is used to assess overall comparability. SLOC is highly correlated with most other metrics (Kemerer 1995). Further, it is as effective a measure of software comparability as other measures (Munson and Khoshgoftaar 1989).…”

Section: Computer Programsmentioning

confidence: 90%

The Role of Cognitive Fit in the Relationship between Software Comprehension and Modification

Shaft¹,

Vessey²

2006

MIS Quarterly

148

110

View full text Add to dashboard Cite

show abstract

Section: Computer Programsmentioning

confidence: 90%

The Role of Cognitive Fit in the Relationship between Software Comprehension and Modification

Shaft¹,

Vessey²

2006

MIS Quarterly

148

110

View full text Add to dashboard Cite

show abstract

“…Both increased complexity and increased size have been shown in prior research to be significant in predicting the future occurrence of software faults (Kemerer 1995). As the size and complexity of the software grow the likelihood of making errors increases.…”

Section: Product Characteristics and Future Softwarementioning

confidence: 99%

Environmental Volatility, Development Decisions, and Software Volatility: A Longitudinal Analysis

2006

Self Cite

View full text Add to dashboard Cite

Although product development research often focuses on activities prior to product launch, for long-lived, adaptable products like software, development can continue over the entire product life cycle. For managers of these products a challenge is to predict when and how much the products will change, and to understand how their development decisions influence the timing and magnitude of future change activities. We develop a two-stage model that relates environmental volatility to product development decisions, and product development decisions to software volatility. The model is evaluated using a data archive that captures changes over twenty years to a firm's environment, its managers' development choices, and its software products. In stage one we find that higher environmental volatility leads to greater use of process technology and standard component designs, but less team member rotation. Earlier development decisions strongly influence current development choices, especially for product design and process technology. In stage two we find that increased use of standard component designs dampens future software volatility by decreasing the average rate and magnitude of change. Adding new team members increases product enhancements at a faster pace than more intense use of process technology, but adds repairs at almost the same rate as enhancements.

show abstract

“…Modularity, measured often as coupling and cohesion in software engineering, has much benefits, including more comprehensible design and as a consequence result in better developer performance [43,44], can boost the innovation rate at each module, and enable better system reconfigurability [38]. However, this comes with a cost: First, even software with well defined architecture and internal interfaces tend to degrade over time.…”

Section: Software Designsmentioning

confidence: 99%

Integrating Value and Utility Concepts into a Value Decomposition Model for Value-Based Software Engineering

Rönkkö¹,

Frühwirth²,

Biffl

2009

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract.Value-based software engineering (VBSE) is an emerging stream of research that addresses the value considerations of software and extends the traditional scope of software engineering from technical issues to businessrelevant decision problems. While the concept of value in VBSE relies on the well-established economic value concept, the exact definition for this key concept within VBSE domain is still not well defined or agreed upon. We argue the discourse on value can significantly benefit from drawing from research in management, particularly software business. In this paper, we present three aspects of software: as a technology, as a design, and as an artifact. Furthermore, we divide the value concept into three components that are relevant for software product development companies and their customers: intrinsic value, externalities and option value. Finally, we propose a value decomposition matrix based on technology views and value components.

show abstract

Software complexity and software maintenance: A survey of empirical research

Cited by 93 publications

References 46 publications

The Role of Cognitive Fit in the Relationship between Software Comprehension and Modification

The Role of Cognitive Fit in the Relationship between Software Comprehension and Modification

Environmental Volatility, Development Decisions, and Software Volatility: A Longitudinal Analysis

Integrating Value and Utility Concepts into a Value Decomposition Model for Value-Based Software Engineering

Contact Info

Product

Resources

About