Diagnóstico del Uso de Técnicas de Revisión de Software en Uruguay
by Darío Macchi, Martín Solari
Darío Macchi, Martín Solari (2013) Diagnóstico del Uso de Técnicas de Revisión de Software en Uruguay. In XVI Ibero-American Conference on Software Engineering (CibSE 2013).
There are different fault detection static techniques, but the reviews are specials because they don't require the execution of the artifact to be evaluated. The objective of this research is to understand how different artifacts are being reviewed during the software development process. It performs a survey for software development professionals who do activities related to quality assurance and process definition. The survey results show that no formal review techniques are used, but different software artifacts are checked using less formal and systematic techniques (ad-hoc and peer review techniques). Regarding the artifacts, the most reviewed are those which are key to the development process, highly risky for project success and highly visible for the user. These are the requirements specifications and design documents, code and user interface respectively. Since the use of non-formal revisions are large, you can search for process quality improvements by the adoption of practices from more formal techniques such as the use of reading techniques and support tools through ongoing training.
There are different fault detection static techniques, but the reviews are specials because they don't require the execution of the artifact to be evaluated. The objective of this research is to understand how different artifacts are being reviewed during the software development process. It performs a survey for software development professionals who do activities related to quality assurance and process definition. The survey results show that no formal review techniques are used, but different software artifacts are checked using less formal and systematic techniques (ad-hoc and peer review techniques). Regarding the artifacts, the most reviewed are those which are key to the development process, highly risky for project success and highly visible for the user. These are the requirements specifications and design documents, code and user interface respectively. Since the use of non-formal revisions are large, you can search for process quality improvements by the adoption of practices from more formal techniques such as the use of reading techniques and support tools through ongoing training.
Spanish version
Existen distintas técnicas estáticas de detección de defectos entre las que se diferencian las revisiones por no requerir de la ejecución del artefacto a evaluar. El objetivo de esta investigación es conocer de qué manera están siendo revisados los distintos artefactos generados durante el proceso de desarrollo de software en Uruguay. Se realiza una encuesta online dirigida a profesionales en desarrollo de software, vinculados a actividades de aseguramiento de calidad o definición de procesos. Los resultados de la encuesta indican que no se utilizan técnicas formales de revisión aunque distintos artefactos de software son revisados mediante técnicas menos formales y sistemáticas (técnicas ad-hoc y revisiones de pares). Respecto a los artefactos, los más revisados son claves para el proceso de desarrollo, de alto riesgo para el éxito del proyecto y de alta visibilidad de cara al usuario. Estos son las especificaciones de requerimientos y documentos de diseño, el código y la interfaz de usuario respectivamente. Dado que el uso de revisiones no formales es amplio, se pueden buscar mejoras en la calidad de dichos procesos adoptando prácticas de técnicas más formales como el uso de técnicas de lectura y herramientas de apoyo a través de la capacitación permanente.
| Icon | File | Description |
|---|---|---|
|
diagnostico-del-uso-de-tecnicas-de-revision-de-software-en-uruguay.pdf | This is my self hosted version of the article. |
