DEPROVAL: herramienta para la definición del proceso de validación en pequeñas organizaciones de software

En el presesente artículo se presenta una herramienta para la definnición de los procesos de validación de software. La herramienta está implementada en base a un metamodelo de validación de software basado en el modelo CMMI. La herramienta facilita que las pequeñas organizaciones de software que presentan diferentes dificultades como es aplicar los modelos de mejora a su organización y falta de personal con conocimiento en pruebas, puedan establecer los procesos de validacion de sus productos a través de la herramienta

Benefits of TSPi in a software project under a small settings enviroment

This article presents a case study about the TSPi benefits in a software project under a Small Settings environment. An adapted process based on the TSPi was defined. The pilot project had a schedule and budget restricted. The process began collecting historical projects data in order to get a measure repository. The project was launched defining the following goals: increase the productivity, reduce the test time and improve the product quality. Finally, the results were analysed and the goals were verified

Análisis de la calidad y productividad en el desarrollo de un proyecto software en una microempresa con TSPi

Este artículo presenta el análisis de los resultados obtenidos al aplicar TSPi en el desarrollo de un proyecto software en una microempresa desde el punto de vista de la calidad y la productividad. La organización en estudio necesitaba mejorar la calidad de sus procesos pero no contaba con los recursos económicos que requieren modelos como CMMI-DEV. Por esta razón, se decidió utilizar un proceso adaptado a la organización basado en TSPi, observándose una reducción en la desviación de las estimaciones, un incremento en la productividad, y una mejora en la calidad.---ABSTRACT---This article shows the benefits of developing a software project using TSPi in a “Very Small Enterprise” based in quality and productivity measures. An adapted process from the current process based on the TSPi was defined and the team was trained in it. The workaround began by gathering historical data from previous projects in order to get a measurement repository, and then the project metrics were collected. Finally, the process, product and quality improvements were verified

A small settings case study using TSPi in a software project

This article introduces a small setting case study about the benefits of using TSPi in a software project. An adapted process from the current process based on the TSPi was defined. The pilot project had schedule and budget constraints. The process began by gathering historical data from previous projects in order to get a measurement repository. The project was launched with the following goals: increase the productivity, reduce the test time and improve the product quality. Finally, the results were analysed and the goals were verifie

Quality and productivity analysis in a very small enterprise using TSPi

This article shows the benefits of developing a software project using TSPi in a "Very Small Enterprise" based in quality and productivity measures. An adapted process from the current process based on the TSPi was defined and the team was trained in it. The pilot project had schedule and budget constraints. The workaround began by gathering historical data from previous projects in order to get a measurement repository, and then the project metrics were collected. Finally, the process, product and quality improvements were verifie

A Process Asset Library to support Software Process Improvement in Small Settings

A main factor to the success of any organization process improvement effort is the Process Asset Library implementation that provides a central database accessible by anyone at the organization. This repository includes any process support materials to help process deployment. Those materials are composed of organization's standard software process, software process related documentation, descriptions of the software life cycles, guidelines, examples, templates, and any artefacts that the organization considers useful to help the process improvement. This paper describe the structure and contents of the Web-based Process Asset Library for Small businesses and small groups within large organizations. This library is structured using CMMI as reference model in order to implement those Process Areas described by this model

A review of software project testing

In this article a review of software projects based on a taxonomy project is established, allowing the development team or testing personnel to identify the tests to which the project must be subjected for validation. The taxonomy is focused on identifying software projects according to their technology. To establish the taxonomy, a development method comprised of 5 phases was applied

Expected requirements in support tool for software process improvement in SMEs

Nowadays being competitive is an important challenge for software development organizations. In order to achieve this, since last years, software process improvement has been an obvious and logical way. Unfortunately, even when many organizations are motivated to implement software process initiatives, not all know how best to do so, especially in Small and Medium Enterprises (SMEs) where due to its especial features, they have to be carefully in how to manage its resources to assure their market survival, Besides, even wen there has been developed models which pretend to help SMEs in the implementation of software process improvements, one of the main barrier that stopping SME's to implement software process improvements are the lack of knowledge and support of software process improvement. This paper presents and analysis of software process improvement at SMEs focusing on identifying on the once hand, SMEs features and success factors in the implementation of SPI initiatives. On the other hand, the expected requirements in a software tool focus on providing support for SMEs in the implementation of SPI initiatives

A Taxonomy for software testing projects

This article establishes taxonomy for software testing projects, allowing the development team or testing personnel to identify the tests to which the project must be subjected for validation. The taxonomy is focused on identifying software projects according to their technology. To establish the taxonomy, a development method comprised of 5 phases was applied. The developed taxonomy is comprised of 9 categories and 27 subcategories and was validated by a group of information technology (IT) managers and professionals in the field of IT through the use of a survey. The results obtained from the survey are subjected to the Mann-Whitney U test, which indicates that the taxonomy is validated. The taxonomy can be implemented in development organizations with or without a testing team that provides a classification for technology projects

Characterization of tests focused on validation of software project

In this paper, a method is applied to identify and characterize what software testing should be applied to a software project for technological validation. The method was applied to a Web project and resulted in a characterization of the tests to which a project must be subjected to verify its functional and non-functional requirements. The characterization determined which tests should be applied to the project. Furthermore, the results of the characterization define a test plan that presents the validation tests for a specific project, and the problem of applying specific and appropriate tests to the project is thus resolved