A minimal test practice framework for emerging software organizations

Karlström, Daniel; Runeson, Per; Nordén, Sara

doi:10.1002/stvr.317

Cited by 24 publications

(50 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…However, the validity of this strategy, in terms [120], [122], [124], [125], [128], [129], [133], [135], [138], [139], [142], [144], [145], [147], [150], [152], [154]- [156], [160], [165], [168]- [170], [173], [179], [180], [182], [183], [185], [187], [188], [190]- [192], [195]- [197], [200], [201], [204], [209], [210], [215], [216], [219], [221], [225], [226], [228]- [230], [237]- [241], …”

Section: Analysis and Discussionmentioning

confidence: 99%

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

BACKGROUND-Software Process Improvement (SPI) is a systematic approach to increase the efficiency and effectiveness of a software development organization and to enhance software products. OBJECTIVE-This paper aims to identify and characterize evaluation strategies and measurements used to assess the impact of different SPI initiatives. METHOD-The systematic literature review includes 148 papers published between 1991 and 2008. The selected papers were classified according to SPI initiative, applied evaluation strategies and measurement perspectives. Potential confounding factors interfering with the evaluation of the improvement effort were assessed. RESULTS-Seven distinct evaluation strategies were identified, whereas the most common one, "Pre-Post Comparison", was applied in 49% of the inspected papers. Quality was the most measured attribute (62%), followed by Cost (41%) and Schedule (18%). Looking at measurement perspectives, "Project" represents the majority with 66%. CONCLUSION-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. Measurements to assess the short and mid-term impact of SPI initiatives prevail, whereas long-term measurements in terms of customer satisfaction and return on investment tend to be less used.

show abstract

Section: Analysis and Discussionmentioning

confidence: 99%

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Unterkalmsteiner

Gorschek

Islam

et al. 2012

IIEEE Trans. Software Eng.

244

147

View full text Add to dashboard Cite

show abstract

“…• Procesos de Mejora de Pruebas: TMMI [17], TPI [18], Propuesta para el testeo de PyMEs [19], y Minimal Test Practice Framework [20].…”

Section: Trabajos Relacionadosunclassified

“…Fuentes para la definición del proceso de pruebas [12,[20][21][22][23][24] El proceso de pruebas propuesto describe 6 fases: i) Inicio, ii) Planeación, iii) Diseño, iv) Ejecución, v)…”

Section: Figunclassified

Proceso de pruebas para pequeñas organizaciones desarrolladoras de software

Rojas-Montes

Pino-Correa

Martínez³

2015

Fac. Ing.

View full text Add to dashboard Cite

Define a testing process in an organization can be valuable to the extent that it allows to: (i) increase product quality, (ii) facilitate the understanding and communication between team members, (iii) support the process improvement in a manner continous, (iv) and support the tasks' automatic execution. In this sense, this paper proposes a light weight process defined to guide and support the test process in small software development organizations. The proposed process incorporates functional testing techniques in order to setting the activities required to evaluate the software product's functionality from an organized and systematic manner, especially those having to do with the design and execution of tests. This process has been defined from the analysis of: (i) few existing testing process reference models, and (ii) different studies reviewed of the literature. This process has been successful used in a small software development company answer have observed that it can be useful and practical to perform tests of software product in this type of companies.

show abstract

“…[20] propose a test practice framework useful for small emerging organizations, and emphazises the availability of the test environment when it is needed. The paper draws from a number of case-studies that shows the importance of test environment handling.…”

Section: Related Workmentioning

confidence: 99%

Technical Debt in Test Automation

Wiklund

Eldh

Sundmark

et al. 2012

2012 IEEE Fifth International Conference on Software Testing, Verification and Validation

View full text Add to dashboard Cite

Abstract-Automated test execution is one of the more popular and available strategies to minimize the cost for software testing, and is also becoming one of the central concepts in modern software development as methods such as test-driven development gain popularity. Published studies on test automation indicate that the maintenance and development of test automation tools commonly encounter problems due to unforeseen issues. To further investigate this, we performed a case study on a telecommunication subsystem to seek factors that contribute to inefficiencies in use, maintenance, and development of the automated testing performed within the scope of responsibility of a software design team. A qualitative evaluation of the findings indicates that the main areas of improvement in this case are in the fields of interaction design and general software design principles, as applied to test execution system development.

show abstract

A minimal test practice framework for emerging software organizations

Cited by 24 publications

References 10 publications

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review

Proceso de pruebas para pequeñas organizaciones desarrolladoras de software

Technical Debt in Test Automation

Contact Info

Product

Resources

About