A Systematic Literature Review of Software Process Improvement in Small and Medium Web Companies

Sulayman, Muhammad; Mendes, Emilia

doi:10.1007/978-3-642-10619-4_1

Cited by 32 publications

(19 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The critical factors for SPI in small software firms have also been reviewed (Khokhar et al 2010). A methodical literature review has pointed out the SPI models and relevant techniques employed by Web development SMEs (Sulayman and Mendes 2009); the review found that SMEs face budget constraints and tight project completion deadlines in SPI and that they lack long-term strategies. An initial framework has been proposed to explore the factors important to SPI success in Web SMEs (Sulayman et al 2012).…”

Section: Spi In Software Smesmentioning

confidence: 99%

Software SMEs’ unofficial readiness for CMMI®-based software process improvement

et al. 2015

View full text Add to dashboard Cite

The goal of software process improvement (SPI) is to improve software processes and produce high-quality software, but the results of SPI efforts in small-and medium-sized enterprises (SMEs) that develop software have been unsatisfactory. The objective of this study is to support the prolific and successful CMMI-based implementation of SPI in SMEs by presenting the facts related to the unofficial adoption of CMMI level 2 process area-specific practices by software SMEs. Two questionnaire surveys were performed, and 42 questionnaires were selected for data analysis. The questionnaires were filled out by experts from 42 non-CMMI-certified software SMEs based in Malaysia and Pakistan. In the case of each process area of CMMI level 2, the respondents were asked to choose from three categories, namely 'below 50 %,' '50-75 %,' and 'above 75 %'. The percentages indicated the extent to which process area-specific practices are routinely followed in the respondents' respective organizations. To deal with differing standards for defining SMEs, the notion of the common range standard has been introduced. The results of the study show that a large segment of software development SMEs informally follows the specific practices of CMMI level 2 process areas and thus has true potential for rapid and effective CMMI-based SPI. The results further indicate that, in the case of four process areas of CMMI level 2, there are statistically significant differences between the readiness of small and medium software enterprises to adopt the specific practices of those process areas, and between trends on their part to do so unofficially. The findings, manifesting various degrees of unofficial readiness for CMMI-based SPI among SMEs, can be used to define criteria for the selection of SMEs that would be included in SPI initiatives funded by relevant authorities. In the interests of developing fruitful CMMI-based SPI and to enhance the success rate of CMMI-based SPI initiatives, the study suggests that 'ready' or 'potential' SMEs should be given priority for SPI initiatives.

show abstract

Section: Spi In Software Smesmentioning

confidence: 99%

Software SMEs’ unofficial readiness for CMMI®-based software process improvement

et al. 2015

View full text Add to dashboard Cite

show abstract

“…The work on software process improvement has spanned decades using various methodologies [Marino and Succi, 1989, Valerio et al, 1997, Vernazza et al, 2000, processes [Kivi et al, 2000, Petrinja et al, 2010, Rossi et al, 2012a, Corral et al, 2013b, Kovács et al, 2004, and devices [Corral et al, 2011, Corral et al, 2013a and there is a large corpus of scientific studies referring to it as it is evidenced by the recent literature reviews on the subject [Khan et al, 2017]. The discipline is now moving to acknowledge specific aspects of it, like SMEs working on web-based systems [Sulayman and Mendes, 2009], process and simulations [Ali et al, 2014], agile methods [Campanelli and Parreiras, 2015].…”

Section: Related Work 21 Software Process Improvementmentioning

confidence: 99%

Toward a Better Understanding of How to Develop Software Under Stress – Drafting the Lines for Future Research

Brown

Ivanov

Rogers

et al. 2018

Proceedings of the 13th International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

Software is often produced under significant time constraints. Our idea is to understand the effects of various software development practices on the performance of developers working in stressful environments, and identify the best operating conditions for software developed under stressful conditions collecting data through questionnaires, non-invasive software measurement tools that can collect measurable data about software engineers and the software they develop, without intervening their activities, and biophysical sensors and then try to recreated also in different processes or key development practices such conditions.

show abstract

“…In the field of SPI few number of Systematic reviews have been conducted in the domain of CMM [31], SPI for small & medium companies [32] [49], evaluation framework for SPI [33], Evaluation and measurement strategies for SPI [34]. These SLRs are limited not only domain specific but also for some defined interval of publications.…”

Section: A Related Workmentioning

confidence: 99%

Software Process Improvement: A systematic literature review

Zil-e-Huma

Bano

Ikram

2012

2012 15th International Multitopic Conference (INMIC)

View full text Add to dashboard Cite

CONTEXT -Software Process Improvement (SPI) initiatives create new and improve existing processes to increase productivity, customer satisfaction, quality of product while reducing cost, and time to market thus maximizing Return on investments. OBJECTIVE -The main focus of this paper is to know about the state of art in SPI and to find out the strength of evidence in empirical work reported within SPI literature. METHOD -Methodology of systematic literature review (SLR) is used. A protocol has been developed and executed. Search strings developed and mentioned in the protocol were applied to the databases to extract relevant papers. A set of papers were identified after reading abstracts of papers extracted after application of search string. A quality criterion was applied on this set to finally select the studies for data extraction. Currently, we are at the data extraction phase of SLR. EXPECTED OUTCOME -The anticipated outcome of this systematic review will be state of art in SPI including widely used tools, models, and techniques; reasons to initiate SPI; SPI challenges/Issues widely reported; the SPI areas which are under more consideration; the SPI areas that lack of attention; frequencies of empirical studies in each of the SPI sub-areas.

show abstract

A Systematic Literature Review of Software Process Improvement in Small and Medium Web Companies

Cited by 32 publications

References 15 publications

Software SMEs’ unofficial readiness for CMMI®-based software process improvement

Software SMEs’ unofficial readiness for CMMI®-based software process improvement

Toward a Better Understanding of How to Develop Software Under Stress – Drafting the Lines for Future Research

Software Process Improvement: A systematic literature review

Contact Info

Product

Resources

About