Software Process Improvement Methods Research Articles

Improving requirements-test alignment by prescribing practices that mitigate communication gaps

The communication of requirements within software development is vital for project success. Requirements engineering and testing are two processes that when aligned can enable the discovery of issues and misunderstandings earlier, rather than later, and avoid costly and time-consuming rework and delays. There are a number of practices that support requirements-test alignment. However, each organisation and project is different and there is no one-fits-all set of practices. The software process improvement method called Gap Finder is designed to increase requirements-test alignment. The method contains two parts: an assessment part and a prescriptive part. It detects potential communication gaps between people and between artefacts (the assessment part), and identifies practices for mitigating these gaps (the prescriptive part). This paper presents the design and formative evaluation of the prescriptive part; an evaluation of the assessment part was published previously. The Gap Finder method was constructed using a design science research approach and is built on the Theory of Distances for Software Engineering, which in turn is grounded in empirical evidence from five case companies. The formative evaluation was performed through a case study in which Gap Finder was applied to an on-going development project. A qualitative and mixed-method approach was taken in the evaluation, including ethnographically-informed observations. The results show that Gap Finder can detect relevant communication gaps and seven of the nine prescribed practices were deemed practically relevant for mitigating these gaps. The project team found the method to be useful and supported joint reflection and improvement of their requirements communication. Our findings demonstrate that an empirically-based theory can be used to improve software development practices and provide a foundation for further research on factors that affect requirements communication.

Process mining support for Capability Maturity Model Integration‐based software process assessment, in principle and in practice

ABSTRACTCurrently used software process improvement methods such as the Capability Maturity Model Integration (CMMI) rely in their process assessments on information, which is gathered during interviews, in oral audit sessions, and from quality manuals and process standard reviews. Although valuable information about software processes can be gained in these assessments, the resulting data quality can be improved upon. This paper investigates the potential of process mining to support current software process assessment and improvement approaches. Based on an analysis of CMMI from a process mining perspective, particular CMMI model components are identified for which it is in principle possible to apply process mining techniques. Subsequently, criteria have been defined to select, with respect to these particular CMMI components, software processes for which process mining has an added value. These criteria have been applied in the selection of a particular ‘minable’ software process, that is, a change control process. Subsequently, the results of a case study from industrial practice, on the process mining of a change control board process, are used to illustrate that process mining can provide CMMI assessors with relevant information. This information reflects the actual or ‘real’ software processes in practice, and as such, it offers an excellent basis to support assessors in understanding the ‘actual’ software processes. Copyright © 2014 John Wiley & Sons, Ltd.

Software process improvement through the Lean Measurement (SPI-LEAM) method

Software process improvement methods help to continuously refine and adjust the software process to improve its performance (e.g., in terms of lead-time, quality of the software product, reduction of change requests, and so forth). Lean software development propagates two important principles that help process improvement, namely identification of waste in the process and considering interactions between the individual parts of the software process from an end-to-end perspective. A large shift of thinking about the own way of working is often required to adopt lean. One of the potential main sources of failure is to try to make a too large shift about the ways of working at once. Therefore, the change to lean has to be done in a continuous and incremental way. In response to this we propose a novel approach to bring together the quality improvement paradigm and lean software development practices, the approach being called Software Process Improvement through the Lean Measurement (SPI-LEAM) Method. The method allows to assess the performance of the development process and take continuous actions to arrive at a more lean software process over time. The method is under implementation in industry and an initial evaluation of the method has been performed.

The impacts of quality and productivity perceptions on the use of software process improvement innovations

Numerous software process improvement (SPI) innovations have been proposed to improve software development productivity and system quality; however, their diffusion in practice has been disappointing. This research investigates the adoption of the Personal Software Process on industrial software projects. Quantitative and qualitative analyses reveal that perceived increases in software quality and development productivity, project management benefits, and innovation fit to development tasks, enhance the usefulness of the innovation to developers. Results underscore the need to enrich current technology acceptance models with these constructs, and serve to encourage project managers to adopt formal SPI methods if developers perceive the methods will have positive impacts on their productivity and system quality.

Experiences in the Application of Software Process Improvement in SMES

During the last few years, many Software Process Improvement methods (SPI) have been presented to increase the quality of products and services provided by a software organization. Current Software Process Improvement (SPI) methods (i.e. ISO 15504, CBA-IPI, …), are difficult to apply to Small and Medium-sized Enterprises (SMES) due to the costs (financial, time, and resource) associated with their application. Also, these methods are principally focused on the assessment stage. This paper presents a new SPI method, called MESOPYME, which main focus is to reduce effort and time on the SPI implementation. This method focuses on the improvement implementation stage, which is based on a concept called Action Package, whose components are described (in Section 2.1.). The results obtained in the application of a Requirements Engineering Action Package in three organizations are also presented.

A case study of software process improvement during development

We present a case study of the use of a software process improvement method which is based on the analysis of defect data. The first step of the method is the classification of software defects using attributes which relate defects to specific process activities. Such classification captures the semantics of the defects in a fashion which is useful for process correction. The second step utilizes a machine-assisted approach to data exploration which allows a project team to discover such knowledge from defect data as is useful for process correction. We show that such analysis of defect data can readily lead a project team to improve their process during development. >