ReMo: A recommendation model for software process improvement (original) (raw)

Combining quantitative and qualitative assessment methods in software process improvement

Proceedings of the Sixth European Conference on Information Systems, 1998

Since the Software Engineering Institute (SEI) in Pittsburgh developed the Capability Maturity Model for Software (CMM) the idea of using assessments to determine the state of an organisation's current software processes has gained increasing momentum. However, the assessment process itself has not received nearly the same attention as the maturity models used in the assessments. This paper argues that a useful assessment process is one which combines quantitative and qualitative methods of studying an ...

Proposed Metrics for Process Capability Analysis in Improving Software Quality: An Empirical Study

International Journal of Software Engineering and Technologies (IJSET), 2016

A software project faces its top expense on defect removal; thereby delaying the schedules. There has been increasing demand for high quality software. Here, high quality software means, delivering defect free software and meeting the predictable results within time and cost constraints. Software defect prediction strives to improve software quality and testing efficiency. The research work presented here is an empirical study and analyzes importance of different metrics used in the organization. The paper examines the impact of LSL and USL, known as organization baselines, on various projects and proposes four metrics for capability analysis metrics. These can prove beneficial for categorizing the process of software development. These metrics aim to improve the ongoing software development process and are helpful in determining the quality of these processes in terms of their specification limits. Also, the paper attempts to justify the probability of the values related to the dat...

A model for the implementation of software process improvement: A pilot study

2003

Advances have been made in the development of software process improvement (SPI) standards and models, i.e. Capability Maturity Model (CMM), more recently CMMI, and ISO’s SPICE. However, these advances have not been matched by equal advances in the adoption of these standards and models in software development which has resulted in limited success for many SPI efforts. The current problem with SPI is not a lack of a standard or model, but rather a lack of an effective strategy to successfully implement these standards or models. In the literature, much attention has been paid to “what activities to implement” rather than “how to implement” these activities. We believe that identification of only “what activities to implement” is not sufficient and that knowledge of “how to implement” is also required for successful implementation of SPI programmes. The aim of this research paper is to empirically explore the viewpoints and experiences of practitioners regarding SPI implementation and based on the findings to develop a model in order to guide practitioners in effectively implementing SPI programmes. This SPI implementation model has six phases and provides a very practical structure within which to implement SPI programmes in organizations.

Modelling the Likelihood of Software Process Improvement: An Exploratory Study

Empirical Software Engineering, 2001

Software process assessments have become big business worldwide. They can be a powerful tool for initiating and sustaining software process improvement (SPI). However, SPI programs sometimes fail. Moreover there still are very few systematic empirical investigations about the conditions under which SPI initiatives vary in their outcomes. In this paper we present the results of a study of factors that influence the success of SPI. The data come from a sample survey of organizations that have performed assessments based on the capability maturity model for software, and was conducted from 1 to 3 years after the assessments (sufficient time had passed for changes to have taken place). The results consist of a multivariate model of the conditions (e.g., how the improvement efforts are organized and funded) that can explain the successes and failures of SPI efforts. The model is constructed using a classification tree algorithm. It identifies the most important factors that affect the outcome of SPI efforts, and describes how those factors interact with each other to influence success or failure.

Supporting Software Process Improvement with Project Assessments

Seminar in Scandinavia (IRIS …, 1999

One of the most popular ways to improve the software development capability in organizations is to embark upon a Software Process Improvement (SPI) program based on one of the existing capability maturity models. Some of the challenges in norm-based SPI ...

Reference Model for Software Process Improvement: A Brazilian Experience

2005

Recent research efforts about quality in the software area demonstrate that a concentrated effort is necessary to improve software process. Mainly in Brazil, there is an urge to enhance software processes performance aiming to improve the quality of software products and to increase Brazilian organizations competitive advantages both in the national and international markets. This work describes an approach developed to establish the base for Brazilian organizations to improve software processes. The focus of this work is to increase the software development capability of small and medium size companies in a fast pace. The presented approach consists of the development of a Reference Model for software process improvement and an appraisal method for the Brazilian software industry. This model has been deployed in several Brazilian companies thorough the support of Software Development Environments. The pilot experience and empirical validation results of application of the presented approach are also described in this paper.

Software Process Self-Assessment Methodology

2012

Controlling and improving the process used to develop and maintain a software product has been widely proposed as a primary answer to the poor quality and non-conforming software products. The ultimate goal of those efforts is to create a continuous SPI (Software Process Improvement) space. Once the organization is committed to begin the SPI effort, the first step is an assessment of the current process and the current capability of the organization to develop and maintain quality software. In this paper, the author presents a methodology for continuous software process self-assessment, developed, tested and successfully applied in several companies in Macedonia. The methodology, using the SW-CMM (Software Capability Maturity Model) as a referentmodel, is unique in: Development of a suitably structured Database of Documents covering nearly every practice used by the actual software process. The documents are grouped according to aspects of development, quality assurance, configuration management and project management. The database provides software input to the referent model. Formalization of the complex structure of the referent model SW-CMM, enabling statistical evaluation of the practices used versus baselines of the model, starting from the bottom up to the Levels of Maturity. For that purpose a software tool has been created and applied.There are very few methodologies and techniques, which include processes, modeling and documentation in a single package (Curtis et al. 1992). The main finding of this study is that an efficient, easy to use, sustainable and objective self-assessment and consequently self-improvement process should involve significant, well-designed initial efforts. This paper presents the methodology itself and reports our experiences in developing and conducting a self-assessment process that follows such a systematic approach.