Journal ArticleDOI
Case studies of software-process-improvement measurement
D.J. Paulish,A.D. Carleton +1 more
Reads0
Chats0
TLDR
Basic measures for performance of a software-development organization are defined, limited ourselves to a small number of simple measures to reduce the complexity of collecting, analyzing, and maintaining the performance data.Abstract:
Describes an ongoing research project conducted jointly by Siemens and the Software Engineering Institute. Siemens software-development organizations in Germany and the United States are case-study sites at which we measure the effect of methods to improve the software-development process. To observe and quantify the impact of software-process improvement, we must measure the performance of a software-development organization over time. Comparison of performance across organizations is very difficult, since organizations define measures and collect performance data in different ways. However, we can separately track performance improvement in each organization if it defines measures consistently and develops similar products. We have defined basic measures for performance of a software-development organization. We limited ourselves to a small number of simple measures to reduce the complexity of collecting, analyzing, and maintaining the performance data. Improving the software-development process improves the quality of software products and the overall performance of the software-development organization. However, process is only one of several controllable factors in improving software quality and organization performance. Others include the skills and experience of the people developing the software, the technology used (e.g. CASE tools), product complexity, and environmental characteristics such as schedule pressure and communications. >read more
Citations
More filters
Journal ArticleDOI
Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review
Michael Unterkalmsteiner,Tony Gorschek,A. K. M. M. Islam,Chow Kian Cheng,Rahadian Bayu Permadi,Robert Feldt +5 more
TL;DR: The evaluation validity of SPI initiatives is challenged by the scarce consideration of potential confounding factors, particularly given that “Pre-Post Comparison” was identified as the most common evaluation strategy, and the inaccurate descriptions of the evaluation context.
Journal Article
A Maturity Model for the Implementation of Software Process Improvement
Mahmood Niazi,David Wilson +1 more
Journal ArticleDOI
A maturity model for the implementation of software process improvement: an empirical study
TL;DR: A CMMI approach is adopted and a maturity model for SPI implementation is developed in order to guide organizations in assessing and improving their SPI implementation processes and provides a very practical structure with which to assess and improve SPI Implementation processes.
Journal ArticleDOI
Success factors of organizational change in software process improvement
Dirk Stelzer,Werner Mellis +1 more
TL;DR: In this paper, the authors describe ten factors that affect organizational change in software process improvement initiatives based on the Capability Maturity Model or the ISO 9000 quality standards and assess the relative importance of these factors and compare the findings with the results of previous research into organizational change.
Journal ArticleDOI
An empirical analysis of the impact of software development problem factors on software maintainability
Jie-Cherng Chen,Sun-Jen Huang +1 more
TL;DR: Results suggest that SPI can help reduce the level of severity of the documentation quality and process management problems, and is only likely to enhance software maintainability to a medium level.
References
More filters
Book
Managing the Software Process
TL;DR: This work describes the development of a Software Maturity Framework and the Principles of Software Process Change, and describes the management of this framework.
ReportDOI
Capability Maturity Model for Software, Version 1.1
TL;DR: This paper serves as one of the best sources for understanding the CMM, and it should clear up some of the misconceptions associated with software process maturity as advocated by the SEI.
Journal ArticleDOI
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation
A.J. Albrecht,J.E. Gaffney +1 more
TL;DR: In this paper, the equivalence between Albrecht's external input/output data flow representative of a program (the function points" metric) and Halstead's [2] "software science" or "software linguistics" model of a programming program as well as the "soft content" variation of Halsteads model suggested by Gaffney [7] was demonstrated.
ReportDOI
Software Size Measurement: A Framework for Counting Source Statements
TL;DR: A general framework for constructing size definitions is proposed and used to derive operational methods can be applied to address the information needs of different users while maintaining a common definition of software size.
Benefits of CMM-Based Software Process Improvement: Initial Results
TL;DR: In this article, the authors report the cost and business value of software process improvement efforts, as well as the yearly improvement in productivity, early defect detection, time to market, and post-release defect reports.