The use of checklists is considered a best practice in software industry. An experiment was devel... more The use of checklists is considered a best practice in software industry. An experiment was developed by a software organization to evaluate the impact of using a checklist to inspect and perform basic testing of software. This article presents the methodology and the results achieved.313318Pressman, R.S., (2005) Engenharia de Software, , Pearson, 5a EdiçãoWiegers, K.E., (2003) SoftwareRequirements, , Microsoft Press, Second EditionFagan, M.E., Design and code inspections to reduce errors in program development (1976) IBM Systems Journal, 15 (3), pp. 258-287(2006) Capability Maturity Model Integration for Development, , Software Engineering Institute Version 1.2Hebert, J.S., Aprimorando a Qualidade de Software através do Teste Cooperativo (1999) X Conferência Internacional de Tecnologia de Software (CITS), , Curitiba(1998) IEEE Std 829: Standard for Software Test Documentation, , IEEE Computer SocietySilva, O.J., Crespo, A.N., Salviano, C., Borges, C.A., Jino, M., Uma metodologia para teste de software no contexto de melhoria do processo (2004) III Simpósio Brasileiro de Qualidade de Software (SBQS), , BrasíliaFowler, M., (2006) GUI Architectures, , http://www.martinfowler.com/eaaDev/uiArchs.html, Acesso em 13 de abril de 200
The study of software reliability has its origin in 1967 when the first experiments were performe... more The study of software reliability has its origin in 1967 when the first experiments were performed. Since then, diverse models that use as parameter the time of execution of software or the time between failures have been considered. Another approach indicates that the use of code coverage, instead of execution time, yields better estimates of the reliability of the software. This paper presents the results observed in an experiment carried out to compare the software reliability models Binomial Model based on Coverage (BMBC) and Infinite Failure Software Reliability Model Based on Code Coverage (IFMBC) with the following models based on time domain: Geometric (GEO), Littlewood-Linear Verral (LAV-L), Littlewood-Quadratic Verral (LAVQ), Musa Basic (MS-B), Musa Logarithmic (MS-L) and Non-Homogeneous Poisson Model (NHP). These models, in addition to being much quoted in the literature, are implemented by SMERFS^3, used to calculate its parameters and to estimate reliability. As a result, it has been observed that traditional models do not provide robustness when the profile was changed. On the other hand, code coverage-based models have produced good results for all operational profiles. In addition to the good fit, coverage-based models have generated better estimates of software reliability, as shown by the Kolmogorov-Smirnov test.
ABSTRACT The estimation of the operational profile is one of the key factors during the use of so... more ABSTRACT The estimation of the operational profile is one of the key factors during the use of software reliability growth models. However, the operational profile can be very difficult to estimate in particular applications such as software used for process control. In other cases, a single operational profile may not be sufficient to describe the use of the product by a number of different customers. An operational profile may also change during the development of software or during its operational usage. All these cases may lead to errors in the estimation of the operational profile. The paper describes an empirical evaluation of the sensitivity of reliability growth models to errors in the estimation of the operational profiles. Some reliability growth models are applied during the testing phase of a software system. The particular characteristics of the case study allow the measurement of the actual reliability growth of the software and its comparison with the estimations provided by the models. Measurement and comparison are repeated for different operational profiles giving information about the effect of a possible error in the estimation of the operational profile. Results show that errors in the operational profile estimation do not heavily affect reliability estimates and that their influence is strongly dependent on the accuracy with which the software system has been tested.
ISO/IEC 15504 defines base practices for software processes and presents a set of generic practic... more ISO/IEC 15504 defines base practices for software processes and presents a set of generic practices that characterize the quality with which base practices are performed. The Artifact Oriented Process Model for Testing ⎯ ArtProTest ⎯ is a generic software testing model defined at CenPRA by selecting software testing “best practices”; it evolved over the last years and has been published in specific forums. The ArtProTest, which defines a set of partially ordered activities and test artifacts, has been validated and improved based on the experience of its application at software development companies in Brazil. In this work we carried out an evaluation of ArtProTest under the perspective of ISO/IEC 15504 process improvement model. We evaluated essentially which aspects of ISO/IEC 15504 are taken into account by ArtProTest. We also evaluate how ArtProTest can be used to supplement software testing related aspects of ISO/IEC 15504 model. Our analysis results pointed to improvements in ArtProTest, and also identify testing task and artifacts not considered by ISO/IEC 15504, which can significantly improve an organization testing practices. Keywods: Software Process; Software Testing; ISO/IEC 15504; Process Improvement, ArtProTest
The CMMI model for Software Engineering provides guidance for improving an organization’s process... more The CMMI model for Software Engineering provides guidance for improving an organization’s processes and the ability to develop software systems. The CenPRA test process is a generic software testing model defined by selecting software testing “best practices”; it evolved over the last years and has been published in specific forums. The CenPRA test process, which defines a set of partially
Dada a importância do uso de computadores nos dias de hoje, a qualidade e a reducao de custos de ... more Dada a importância do uso de computadores nos dias de hoje, a qualidade e a reducao de custos de solucoes baseadas em computadores sao fatores criticos. O projeto de desenvolvimento de um produto de software e sua capacidade de ser "amigavel ao ser humano" diferenciam-no dos produtos concorrentes que tenham funcao identica em outros aspectos. O presente trabalho objetiva consolidar a ideia de orientar a especificacao e a documentacao dos requisitos de um sistema, apos o levantamento e o conhecimento do problema para o desenvolvimento do mesmo. Para tanto, apos apresentar os conceitos basicos da area de Engenharia de Requisitos e da tecnica de Casos de Uso, e proposto um modelo de especificacao e documentacao de requisitos utilizando a tecnica apresentada. Para a validacao do modelo, foi apresentado um estudo de caso. O modelo proposto pode ser utilizado para controlar a mudanca nos requisitos e prover documentacao com informacoes sempre atualizadas em um unico documento, facilitando o controle de versoes pelos analistas do sistema. Para isso, e necessario apenas a utilizacao de um editor de texto qualquer Abstract
The IEEE Std 829-1998 is a standard for software test documentation which can be very useful to h... more The IEEE Std 829-1998 is a standard for software test documentation which can be very useful to help software houses to structure their software test projects. However, its application on real projects is not straightforward and many companies face difficulties when trying to use it. These difficulties may be explained, at least in part, by the fact that the standard is somewhat vague and lacking many details about the contents of the sections comprising the proposed documents. Aiming to help alleviate this problem, the Software Test Group at CenPRA has developed two guides which constitute the basis for a method proposed for the deployment of the software testing processes based on the IEEE Std 8291998’s usage. In the first one, “Guideline for the Elaboration of Software Test Documents,” the information needed to produce the documents proposed by the standard and its flow is described. In the second, “Processes for the Elaboration of Software Test Documents,” the processes for the production of the IEEE-829’s documents are presented. An outline of those two guides is given in this paper.
Resumo—Estudos sobre a qualidade no setor de software brasileiro mostram a necessidade de um esfo... more Resumo—Estudos sobre a qualidade no setor de software brasileiro mostram a necessidade de um esforço significativo capaz de aumentar a maturidade dos processos de software das empresas. Este artigo descreve o Projeto mps Br–melhoria de processo do ...
O objetivo deste trabalho é avaliar a capabilidade no processo produtivo para aprovação de uma me... more O objetivo deste trabalho é avaliar a capabilidade no processo produtivo para aprovação de uma melhoria de processo em uma empresa fornecedora de transmissões mecânica para veículos automotores. A melhoria consiste em verificar se um equipamento de torno de controle numérico é capaz de executar o processo de torneamento duro de engrenagens com corte interrompido para substituir o processo de retífica que é utilizada no processo e não atende às normas de segurança, devendo ser substituída por um equipamento novo ou ser reformada para adequação, conforme a norma de segurança NR12. Segundo o manual dos fabricantes de autopeças, sempre que houver qualquer alteração na forma de processamento dos produtos, é necessário a aprovação do PPAP (Processo de Aprovação da Peça de Produção). Desta forma, o estudo foi feito de maneira exploratória em 3 testes com tipos de insertos de usinagem diferentes com objetivo de verificar qual situação teria o melhor resultado para aprovação dos índices de c...
Software testing must be well documented and based on up to date and consistent information to av... more Software testing must be well documented and based on up to date and consistent information to avoid troubles such as incomplete or inappropriate tests. This involves the definition of what must be recorded, beyond tracing the diverse links among the many information elements that compose the documents. Documenting and tracing involve the manipulation of a very huge amount of data, demanding automated support. This paper presents PROMETEU, a tool to support documents generation and traceability among artifacts that comprises the test process documents.
The use of checklists is considered a best practice in software industry. An experiment was devel... more The use of checklists is considered a best practice in software industry. An experiment was developed by a software organization to evaluate the impact of using a checklist to inspect and perform basic testing of software. This article presents the methodology and the results achieved.313318Pressman, R.S., (2005) Engenharia de Software, , Pearson, 5a EdiçãoWiegers, K.E., (2003) SoftwareRequirements, , Microsoft Press, Second EditionFagan, M.E., Design and code inspections to reduce errors in program development (1976) IBM Systems Journal, 15 (3), pp. 258-287(2006) Capability Maturity Model Integration for Development, , Software Engineering Institute Version 1.2Hebert, J.S., Aprimorando a Qualidade de Software através do Teste Cooperativo (1999) X Conferência Internacional de Tecnologia de Software (CITS), , Curitiba(1998) IEEE Std 829: Standard for Software Test Documentation, , IEEE Computer SocietySilva, O.J., Crespo, A.N., Salviano, C., Borges, C.A., Jino, M., Uma metodologia para teste de software no contexto de melhoria do processo (2004) III Simpósio Brasileiro de Qualidade de Software (SBQS), , BrasíliaFowler, M., (2006) GUI Architectures, , http://www.martinfowler.com/eaaDev/uiArchs.html, Acesso em 13 de abril de 200
The study of software reliability has its origin in 1967 when the first experiments were performe... more The study of software reliability has its origin in 1967 when the first experiments were performed. Since then, diverse models that use as parameter the time of execution of software or the time between failures have been considered. Another approach indicates that the use of code coverage, instead of execution time, yields better estimates of the reliability of the software. This paper presents the results observed in an experiment carried out to compare the software reliability models Binomial Model based on Coverage (BMBC) and Infinite Failure Software Reliability Model Based on Code Coverage (IFMBC) with the following models based on time domain: Geometric (GEO), Littlewood-Linear Verral (LAV-L), Littlewood-Quadratic Verral (LAVQ), Musa Basic (MS-B), Musa Logarithmic (MS-L) and Non-Homogeneous Poisson Model (NHP). These models, in addition to being much quoted in the literature, are implemented by SMERFS^3, used to calculate its parameters and to estimate reliability. As a result, it has been observed that traditional models do not provide robustness when the profile was changed. On the other hand, code coverage-based models have produced good results for all operational profiles. In addition to the good fit, coverage-based models have generated better estimates of software reliability, as shown by the Kolmogorov-Smirnov test.
ABSTRACT The estimation of the operational profile is one of the key factors during the use of so... more ABSTRACT The estimation of the operational profile is one of the key factors during the use of software reliability growth models. However, the operational profile can be very difficult to estimate in particular applications such as software used for process control. In other cases, a single operational profile may not be sufficient to describe the use of the product by a number of different customers. An operational profile may also change during the development of software or during its operational usage. All these cases may lead to errors in the estimation of the operational profile. The paper describes an empirical evaluation of the sensitivity of reliability growth models to errors in the estimation of the operational profiles. Some reliability growth models are applied during the testing phase of a software system. The particular characteristics of the case study allow the measurement of the actual reliability growth of the software and its comparison with the estimations provided by the models. Measurement and comparison are repeated for different operational profiles giving information about the effect of a possible error in the estimation of the operational profile. Results show that errors in the operational profile estimation do not heavily affect reliability estimates and that their influence is strongly dependent on the accuracy with which the software system has been tested.
ISO/IEC 15504 defines base practices for software processes and presents a set of generic practic... more ISO/IEC 15504 defines base practices for software processes and presents a set of generic practices that characterize the quality with which base practices are performed. The Artifact Oriented Process Model for Testing ⎯ ArtProTest ⎯ is a generic software testing model defined at CenPRA by selecting software testing “best practices”; it evolved over the last years and has been published in specific forums. The ArtProTest, which defines a set of partially ordered activities and test artifacts, has been validated and improved based on the experience of its application at software development companies in Brazil. In this work we carried out an evaluation of ArtProTest under the perspective of ISO/IEC 15504 process improvement model. We evaluated essentially which aspects of ISO/IEC 15504 are taken into account by ArtProTest. We also evaluate how ArtProTest can be used to supplement software testing related aspects of ISO/IEC 15504 model. Our analysis results pointed to improvements in ArtProTest, and also identify testing task and artifacts not considered by ISO/IEC 15504, which can significantly improve an organization testing practices. Keywods: Software Process; Software Testing; ISO/IEC 15504; Process Improvement, ArtProTest
The CMMI model for Software Engineering provides guidance for improving an organization’s process... more The CMMI model for Software Engineering provides guidance for improving an organization’s processes and the ability to develop software systems. The CenPRA test process is a generic software testing model defined by selecting software testing “best practices”; it evolved over the last years and has been published in specific forums. The CenPRA test process, which defines a set of partially
Dada a importância do uso de computadores nos dias de hoje, a qualidade e a reducao de custos de ... more Dada a importância do uso de computadores nos dias de hoje, a qualidade e a reducao de custos de solucoes baseadas em computadores sao fatores criticos. O projeto de desenvolvimento de um produto de software e sua capacidade de ser "amigavel ao ser humano" diferenciam-no dos produtos concorrentes que tenham funcao identica em outros aspectos. O presente trabalho objetiva consolidar a ideia de orientar a especificacao e a documentacao dos requisitos de um sistema, apos o levantamento e o conhecimento do problema para o desenvolvimento do mesmo. Para tanto, apos apresentar os conceitos basicos da area de Engenharia de Requisitos e da tecnica de Casos de Uso, e proposto um modelo de especificacao e documentacao de requisitos utilizando a tecnica apresentada. Para a validacao do modelo, foi apresentado um estudo de caso. O modelo proposto pode ser utilizado para controlar a mudanca nos requisitos e prover documentacao com informacoes sempre atualizadas em um unico documento, facilitando o controle de versoes pelos analistas do sistema. Para isso, e necessario apenas a utilizacao de um editor de texto qualquer Abstract
The IEEE Std 829-1998 is a standard for software test documentation which can be very useful to h... more The IEEE Std 829-1998 is a standard for software test documentation which can be very useful to help software houses to structure their software test projects. However, its application on real projects is not straightforward and many companies face difficulties when trying to use it. These difficulties may be explained, at least in part, by the fact that the standard is somewhat vague and lacking many details about the contents of the sections comprising the proposed documents. Aiming to help alleviate this problem, the Software Test Group at CenPRA has developed two guides which constitute the basis for a method proposed for the deployment of the software testing processes based on the IEEE Std 8291998’s usage. In the first one, “Guideline for the Elaboration of Software Test Documents,” the information needed to produce the documents proposed by the standard and its flow is described. In the second, “Processes for the Elaboration of Software Test Documents,” the processes for the production of the IEEE-829’s documents are presented. An outline of those two guides is given in this paper.
Resumo—Estudos sobre a qualidade no setor de software brasileiro mostram a necessidade de um esfo... more Resumo—Estudos sobre a qualidade no setor de software brasileiro mostram a necessidade de um esforço significativo capaz de aumentar a maturidade dos processos de software das empresas. Este artigo descreve o Projeto mps Br–melhoria de processo do ...
O objetivo deste trabalho é avaliar a capabilidade no processo produtivo para aprovação de uma me... more O objetivo deste trabalho é avaliar a capabilidade no processo produtivo para aprovação de uma melhoria de processo em uma empresa fornecedora de transmissões mecânica para veículos automotores. A melhoria consiste em verificar se um equipamento de torno de controle numérico é capaz de executar o processo de torneamento duro de engrenagens com corte interrompido para substituir o processo de retífica que é utilizada no processo e não atende às normas de segurança, devendo ser substituída por um equipamento novo ou ser reformada para adequação, conforme a norma de segurança NR12. Segundo o manual dos fabricantes de autopeças, sempre que houver qualquer alteração na forma de processamento dos produtos, é necessário a aprovação do PPAP (Processo de Aprovação da Peça de Produção). Desta forma, o estudo foi feito de maneira exploratória em 3 testes com tipos de insertos de usinagem diferentes com objetivo de verificar qual situação teria o melhor resultado para aprovação dos índices de c...
Software testing must be well documented and based on up to date and consistent information to av... more Software testing must be well documented and based on up to date and consistent information to avoid troubles such as incomplete or inappropriate tests. This involves the definition of what must be recorded, beyond tracing the diverse links among the many information elements that compose the documents. Documenting and tracing involve the manipulation of a very huge amount of data, demanding automated support. This paper presents PROMETEU, a tool to support documents generation and traceability among artifacts that comprises the test process documents.
Uploads
Papers by Adalberto N Crespo