Empirical Research in Software Process Modeling: A Systematic Literature Review (original) (raw)

Modelling the likelihood of software process improvement: An exploratory study

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.

A Model for the Implementation of Software Process Improvement: An Empirical Study

2004

Little attention has been paid in the literature on "how to implement" software process improvement (SPI) which has resulted in limited success for many SPI efforts. In this paper we report on our recent empirical study which explored the experiences and perceptions of practitioners about SPI implementation. We visited 11 companies and conducted 14 in-depth interviews. Using the different experiences and opinions of practitioners regarding SPI implementation, we have developed a model for the implementation of SPI programmes. This model has six phases -awareness, learning, pilot implementation, SPI implementation action plan, implementation across the organization and maintenance -and provides advice to practitioners in effectively implementing SPI programmes.

PIT-ProcessM: A Software Process Improvement Meta-Model

2010 Seventh International Conference on the Quality of Information and Communications Technology, 2010

Software Process Improvement (SPI) is one of the main actual software development challenges. Process metamodels allow capturing informational and behavioural aspects of software development processes. Unfortunately, standard process meta-modelling approaches, such as the Software Process Engineering Meta-model (SPEM), OPEN Process Framework (OPF) and Standard Meta-model for Software Development Methodologies (SMSDM), focus just on process description, providing different models for several versions of the same process. According to these metamodelling approaches, it is not possible to compare and identify improvements in an improved process. This lack of information recognizes that further research in SPI meta-model is needed to reflect the evolution/change on software processes. Considering this limitation in SPI meta-modelling, this paper presents a comparative study of the most recognized process meta-models approaches and introduces a new SPI based metamodel designed by ProjectIT-Process Meta-model (PIT-ProcessM). Our intention is to present observed problems in existing approaches and propose a process meta-model that addresses features related to process changes and evolution.

Software Process Models and Project Performance

Information Systems Frontiers

In this paper we review the progress in software process research and the role of process improvement in enhancing business outcomes of software projects. We first describe the process view of software development. Next, we review the literature on software process research and discuss some of the leading software process models. The business value of software process improvements and empirical evidence from the software industry are also discussed in this paper. We conclude with a discussion of current challenges in software process research and directions for future research. Peer Reviewed http://deepblue.lib.umich.edu/bitstream/2027.42/46018/1/10796\_2004\_Article\_242160.pdf

A COMPARATIVE ANALYSIS OF VARIOUS SOFTWARE PROCESS IMPROVEMENT MODELS

It is rightly said that the 'change is inevitable' and when the change has been witnessed in the positive direction it is termed as improvement. It can be either in terms of enhancement to the existing system or adaptability to cater the changing requirements of the users. Software Process Improvement is a process based approach to software development which lay stress on the techniques and tools for the improvement of software development processes. Software Process Improvement (SPI) consists of a set of activities that will lead to a better software process, and as a consequence, high quality software is delivered in a desired time span. Although it is an never ending process and is difficult to find any particular standardized model for all systems but SPI models provide a yardstick to access the existing processes and hence setting a path for designing the new models for development of new systems. The existing paper studies the various process models and explores the possibility of further improvement.

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

2003

Little attention has been paid in the literature on "how to implement" software process improvement (SPI) which has resulted in limited success for many SPI efforts. In this paper we report on our recent empirical study which explored the experiences and perceptions of practitioners about SPI implementation. We visited 11 companies and conducted 14 in-depth interviews. Using the different experiences and opinions of practitioners regarding SPI implementation, we have developed a model for the implementation of SPI programmes. This model has six phases -awareness, learning, pilot implementation, SPI implementation action plan, implementation across the organization and maintenance -and provides advice to practitioners in effectively implementing SPI programmes.

Design of Software Process Improvement Model

International Journal of Computer Applications, 2012

Software process improvement (SPI) approaches have been designed to produce changes at many levels, i.e. in the strategies, culture and working practices, of software development. Studies have shown that nearly two thirds of all SPI efforts have failed or fallen short of expectations. SPI Software process improvement (SPI) today is based mainly on a perception of software processes as artifacts and this perception has led SPI efforts to focus on perfecting such artifacts as a means to improve the practices of the people supposed to execute these software processes. Such SPI efforts thus tend to view the design of software processes as separate from their use. In this approach process designers are expected to provide process knowledge to software developers, and software developers are expected to provide experiences and problems to the process designers. This focus on software processes as artifacts implies an emphasis on formalization and externalization of process models possibly at the expense of the process knowledge in the heads of the process users.

Applying a framework for the improvement of software process maturity

Software: Practice and Experience, 2006

and maintenance of software for information systems. The aim of FMESP is to provide companies with a conceptual and technological framework for the management of their process models and measurement models in an integrated way. Modelling and measurement are two key factors to promote continuous process improvement. As a result, important benefits were obtained. The company improved the maturity of its processes which allowed it to obtain the ISO 9000 certification. From a research point of view, are Capability Maturity Model for Software (SW-CMM) [1], Capability Maturity Model Integration (CMMI) and Software Process Improvement and Capability Determination (SPICE), which has been standardized as ISO 15504 .

A modest but practical software process modeling technique for software process improvement

Software Process: Improvement and Practice, 2002

One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals.

Software process models: a review and analysis

International Journal of Engineering & Technology

Modeling of software process has been a very challenging problem and constantly debated in the software development community in the past 30+ years, largely due to the complex nature of the software development process that involves not only the technical knowledge and skills but also many other factors, such as human, management, quality assessment, and cost. Although the situations of creating software differ greatly from one case to another, there are some common themes shared by many of the situations, and hence various software process models have been emerged to address these common themes. In this paper, we present a review of the software process models commonly used in practice, from traditional to agile, and assessment of these models with metrics and case studies.