ICMM—a maturity model for software inspections

Kollanus, Sami

doi:10.1002/smr.456

Cited by 10 publications

(3 citation statements)

References 52 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Sami Kollanus proposed a model named inspection capability maturity model. He claimed that his model provides support for assessment and improvement of inspection practices in a software organisation.…”

Section: Validation Of the Modelmentioning

confidence: 99%

A simplified model for software inspection

Misra

Fernández

Colomo‐Palacios

2014

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

Software inspection is considered a cost‐effective quality assurance technique in software process improvement. Although inspections detect the majority of defects in the early stages of the development process, this technique is not a common practice in the software industry, especially in small and medium enterprises. In this paper, we propose a model for the inspection process intended to be applicable and acceptable to both small and medium enterprises and large software organisations. The model was implemented in two organisations: one in a medium‐scale company and the other one in a department of a big company where its feasibility and benefits were confirmed. A comparison with recent alternative inspection models has also been performed showing the practicality of the proposal and ease of adoption and cost‐effectiveness. Copyright © 2014 John Wiley & Sons, Ltd.

show abstract

Section: Validation Of the Modelmentioning

confidence: 99%

A simplified model for software inspection

Misra

Fernández

Colomo‐Palacios

2014

J. Softw. Evol. and Proc.

View full text Add to dashboard Cite

show abstract

“…Researchers who have widely studied software inspections agree that they are an effective method of identifying faults and improving software quality (Aurum et al 2002;Fagan 1986;Kollanus and Koskinen 2009). One researcher has even developed a maturity model for software inspections (Kollanus 2009(Kollanus , 2011. In other cases, faculty members are including requirements inspections as part of their software engineering courses (e.g.…”

Section: Introductionmentioning

confidence: 99%

Investigation of individual factors impacting the effectiveness of requirements inspections: a replicated experiment

Albayrak

Carver

2012

Empir Software Eng

View full text Add to dashboard Cite

Cataloged from PDF version of article.This paper presents a replication of an empirical study regarding the impact of\ud individual factors on the effectiveness of requirements inspections. Experimental replications\ud are important for verifying results and investigating the generality of empirical studies.\ud We utilized the lab package and procedures from the original study, with some changes and\ud additions, to conduct the replication with 69 professional developers in three different\ud companies in Turkey. In general the results of the replication were consistent with those of\ud the original study. The main result from the original study, which is supported in the\ud replication, was that inspectors whose degree is in a field related to software engineering\ud are less effective during a requirements inspection than inspectors whose degrees are in other\ud fields. In addition, we found that Company, Experience, and English Proficiency impacted\ud inspection effectiveness

show abstract

“…También se asegura que existen otros beneficios menos cuantificables como permitir la identificación y priorización de áreas de código que requieren una actualización continua, promover el trabajo en equipo e identificar las causas raíces de ciertos defectos a través del análisis causal de los mismos. Otro beneficio es el de ser un medio excelente de transferencia tecnológica y de entrenamiento en estándares, material técnico, cultura y en el propio proceso de inspección [10] [11].…”

Section: Introductionunclassified

Software inspection adoption: A mapping study

Macchi

Solari

2012

2012 XXXVIII Conferencia Latinoamericana en Informatica (CLEI)

View full text Add to dashboard Cite

In Software Engineering technical literature the references about the benefits of software inspections are abundant. In contrast, some authors raise the problem of low adoption of this process. From this issue a literature review is made to produce a map on most researched topics in the area, factors causing low adoption and possible solutions. Results showed a list of 64 articles selected using a search protocol, which were classified according to a defined taxonomy. The founded factors were codified and a list of solutions founded in the reviewed papers was made. The main conclusion was that most of the factors causing low adoption are related to developers perceptions about the process, lack of training and some characteristics of the process as the rigidity, complexity and the difficulty of connecting the effort made with the final product quality. These factors should be studied in future works. I. INTRODUCCIÓNSe estima que entre el 50% y el 60% del esfuerzo total de producir software se invierte en tareas de aseguramiento de calidad [1]. Por otra parte, de acuerdo a un estudio realizado en el 2002 por el NIST (National Institute of Standards and Technology) la entrega de software defectuoso le cuesta a los Estados Unidos $59.5 miles de millones por año, de los cuales $22.2 miles de millones podrían ahorrarse mejorando la infraestructura de testing, revisiones e inspecciones [2]. Humphrey dijo que la calidad de los productos de software depende directamente de la calidad del proceso que los genera [3]. Dentro de estos procesos, los de verificación y validación permiten evaluar si un software cumple con los requerimientos y con el uso previsto. También permiten detectar defectos en los artefactos de software lo que contribuye a aumentar la productividad y reducir el esfuerzo de retrabajo. Estos conceptos no solamente son aplicables al código, sino también a todo artefacto elaborado durante el proceso de desarrollo.Normalmente cuando se utiliza el término inspección de software se hace en referencia al método introducido por Michael Fagan [4], el cual puede verse en la Figura 1. Esto se debe a que la mayor parte de los métodos de inspección existentes son variantes del método de Fagan. Por ejemplo se quitan o agregan elementos del proceso como en el método de Gilb y Graham [5], se modifica la cantidad de participantes, como en el caso del método limited logging meeting, o la distribución en distintas locaciones físicas (virtual logging meeting) [6]. Figura 1. Proceso de inspección según IEEE-1028 2008.Existen distintos métodos manuales (o semi-automáticos) de detectar anomalías que complementan el testing, estandarizados por IEEE [7]. La inspección de software es el método más formal en cuanto a sus procedimientos y se realiza con el objetivo de producir resultados más repetibles [4]. Consiste en un proceso de revisión utilizado para mejorar la calidad del software, documentos relacionados y de todo artefacto que sea generado durante el proceso de desarrollo de software. Un método menos formal es el de las rev...

show abstract

ICMM—a maturity model for software inspections

Cited by 10 publications

References 52 publications

A simplified model for software inspection

A simplified model for software inspection

Investigation of individual factors impacting the effectiveness of requirements inspections: a replicated experiment

Software inspection adoption: A mapping study

Contact Info

Product

Resources

About