Uso de revisiones sistemáticas como estrategia de generación de conocimientos para mejora continua

En el presente trabajo se describe cómo las Revisiones Sistemáticas (una estrategia científica que apunta a generar piezas de conocimiento de alto nivel) pueden ayudar al proceso de “mejora continua” que propone CMMI a las empresas que desean certificar los más altos niveles de madurez.Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

Uso de revisiones sistemáticas como estrategia de generación de conocimientos para mejora continua

En el presente trabajo se describe cómo las Revisiones Sistemáticas (una estrategia científica que apunta a generar piezas de conocimiento de alto nivel) pueden ayudar al proceso de “mejora continua” que propone CMMI a las empresas que desean certificar los más altos niveles de madurez.Workshop de Ingeniería de Software y Bases de Datos (WISBD)Red de Universidades con Carreras en Informática (RedUNCI

An approach to estimate the saving from negotiation based on cost- benefit anaylsis model

This paper presents an approach to estimate the savings from implementing negotiation in requirements elicitation process. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements defects. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net-gain and the return-oninvestment show positive value which suggest that negotiation activities worth an investment. Based on the return-oninvestment of 197 percent in average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the creation of requirements

Analysis of inspection technique performance

Inspection techniques are strategies for analysing software artefacts. These techniques provide guidelines for examining the software documentation and identifying defects. These guidelines consist of a series of heuristics to help reviewers to read and understand the artefact that they are analysing. A number of researchers have now developed experimental studies to compare the performance of the different techniques in an attempt to find out what is the best strategy to adopt in which cases. In this work, we conduct a systematic review of the effectiveness and efficiency of inspection techniques following Kitchenham’s recommendations.VI Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

Requirements Negotiation: Does Consensus Reduce Software Development Cost?

The requirements engineering activities within a software project are known to be critical to the successful production of a correctly functioning system. This is particularly so when considering the varying views of multiple stakeholders. One promising approach for improving the outcome is to introduce formal negotiation. Negotiation is beneficial to identify and to resolve conflicts between stakeholders. Consensus achieved through negotiation represents all key stakeholders’ perspectives and perceptions regarding the system to be developed. The aim of implementing negotiation is to minimize the possibility of introducing defects during the creation of requirements and to decrease later effort required to fix requirements’ defects. This paper answers the question of whether consensus gives positive significant impact to the software project as a whole or not. It presents an approach to estimate the savings from implementing negotiation in the requirements elicitation process. An empirical evaluation study is adopted through a role play experiment to evaluate the benefit of exercising negotiation. The net gain and the return on investment show positive values which suggest that negotiation activities are worth an investment. Based on a return on investment of 197 percent on average, this paper suggests that negotiation is a useful prevention activity to inhibit defects from occurring during the requirements creation process

Analysis of inspection technique performance

Inspection techniques are strategies for analysing software artefacts. These techniques provide guidelines for examining the software documentation and identifying defects. These guidelines consist of a series of heuristics to help reviewers to read and understand the artefact that they are analysing. A number of researchers have now developed experimental studies to compare the performance of the different techniques in an attempt to find out what is the best strategy to adopt in which cases. In this work, we conduct a systematic review of the effectiveness and efficiency of inspection techniques following Kitchenham’s recommendations.VI Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI