Productivity analysis of object‐oriented software developed in a commercial environment

@article{Potok1999ProductivityAO,
  title={Productivity analysis of object‐oriented software developed in a commercial environment},
  author={Thomas E. Potok and Mladen A. Vouk and Andrew J. Rindos},
  journal={Software: Practice and Experience},
  year={1999},
  volume={29},
  url={https://api.semanticscholar.org/CorpusID:7768178}
}
The introduction of object‐oriented technology does not appear to hinder overall productivity on new large commercial projects, but nor does it seem to improve it in the first two product generations… 
View on Wiley
zenodo.org
22 Citations
Highly Influential Citations
2
Background Citations
12
Methods Citations
3

22 Citations

An empirical study of software development productivity in C and C + + 1

Investigating whether C++ improved the productivity of software development did not find any empirical evidence of improved productivity, in line with previous studies that to date have found no convincing empirical support in favor of object-oriented development.

Safe Object-Oriented Software: The Verified Design-By-Contract Paradigm

The main issues affecting safety are reviewed and a paradigm — Verified Design-by-Contract — that uses formal methods to facilitate the safe use of inheritance, polymorphism, dynamic binding and other features of the object-oriented approach is proposed.

Applying Formal Concept Analysis to Extract Framework Reuse Interface Specifications from Source Code

The possibility of reverse engineering a reuse interface specification from the source code of a framework and its example applications is discussed, and it is possible to automatically extract a considerable portion of those specifications from source code to allow effective tool support for framework specialization.

Construction of Reliable Software in Resource‐Constrained Environments

It is interesting to note that there are experimental results showing that testing efficiency can be improved over longer periods of time through process improvement, and that software quality does appear to be positively correlated with an increase in the average testing efficiency that stems from process improvements.

Software Productivity in Practice: A Systematic Mapping Study

A systematic mapping study is developed here to investigate the existence of diverse empirical perceptions of productivity within the distinct business sectors and knowledge areas covered by the industrial practice of SE, also identifying the commonalities among them.

What Can Lean Do for Software? Welcoming Software into the Industrial Fold

Evidence is shown that Lean not only works for software, in some ways it works even better than it does for the classic industries, and an overview of one incarnation of a Lean software process is given.

The Quest for Productivity in Software Engineering: A Practitioners Systematic Literature Review

A systematic literature review is developed to confirm the existence of different empirical perceptions of productivity from the distinct business sectors and knowledge areas covered in practice by Software Engineering, identifying also commonalities that may exist.

From OOP to SOP : What Improved ?

It is predicted that SOP is a sound direction to improve programmers' productivity and it is worthwhile putting more efforts on this kind of research and practice.

An Effort Prediction Model Based on BPM Measures for Process Automation

This empirical research examines the effect of various measures for BPMN compliant business process models on the effort spent to automate those models and proposes a prediction model developed by multiple linear regression analysis.

Capability-based software project scheduling with system dynamics and heuristic search

A framework for scheduling and monitoring in software project management is proposed based on System Dynamics models to help project managers to assign human resources automatically and realistically based on personnel/team capability.

23 References

Measuring the Impact of Reuse on Quality and Productivity in Object-Oriented Systems

This study indicates significant benefits from reuse in terms of reduced defect density and rework as well as increased productivity in OO systems.

The Effects of the Business Model on Object-Oriented Software Development Productivity

This paper examines empirical data from several commercial products developed using object-oriented methods and model and simulate the impact of the software task-completion incentives and deadlines on the productivity that might be expected from a technology with high-performance potential.

Effectiveness of traditional software metrics for object-oriented systems

The results of this research indicate that traditional metrics are applicable to the measurement of the complexity of object-oriented systems.

Development productivity for commercial software using object-oriented methods

This study indicates that first generation object-oriented projects achieve the same productivity rates as follow-on releases of procedural projects, and scheduling effects, such as the Parkinson effect and the Deadline effect, may be responsible for this economy of scale.

An Approach to the Modeling and Analysis of Software Production Processes

An empirical study of the object-oriented paradigm and software reuse

The experiment concludes that the object-oriented paradigm substantially improves productivity, although a significant part of this improvement is due to the effect of reuse, and language differences are far more important when programmers reuse than when they do not.

The Effects of Layering and Encapsulation on Software Development Cost and Quality

The results support the contention that layering significantly reduces the effort required to build new components, and the quality of the components is at least as good using the layered approach.

Object Technology and Reuse: Lessons from Early Adopters

Four longitudinal case studies illustrate the costs and risks of early object-oriented technology adoption, including the difficulty of achieving systematic reuse in practice, and recommend general strategies and specific tactics for overcoming adoption barriers.

OBJECT TECHNOLOGY AND SOFTWARE REUSE: LESSONS FROM LONGITUDINAL CASE STUDIES OF EARLY ADOPTERS

The actual experiences of the case sites as they made the transition to OO development are described, and a set of four lessons learned are presented: invest in organizational learning, develop a complete technical and process architecture, treat reuse as a process innovation in its own right, and view adoption as a multi-year exercise in process technology R&D.

Sixteen questions about software reuse

Software reuse is the use of existing software knowledge or artifacts to build new software artifacts to be used in different systems to be distinguished from porting.

Related Papers

Showing 1 through 3 of 0 Related Papers