Anderson Belgamo

TUCCA: improving the effectiveness of use case construction and requirement analysis

Most of the delivered software products are delivered with defects usually introduce in the communications and transformations among different levels of abstraction along the software development phases. Defects remain in the artifacts even though high quality, rigorous design, inspections and testing activities are carried out during software development. Therefore, every software development activity should be systematic and rigorous and whenever possible should embody the aim of finding defects. This paper presents results of a feasibility study that was carried out aiming at evaluating TUCCA

Using Information Visualization and Text Mining to Facilitate the Conduction of Systematic Literature Reviews

Technique for use case model construction and construction-based requirements document analysis. TUCCA is composed of two reading techniques: AGRT - actor goal reading technique whose objective is to determine the actors of the system and their goals and UCRT - use case reading technique whose objective is to determine the use case model. These techniques support the construction of the use case model and also embody a review of the requirements document. In this paper we show that TUCCA is effective in use case construction and defect detection; we detailed the results of TUCCASs contribution for finding defects, comparing this technique with Checklist and PBR-User (perspective based reading - user view). The results motivate to investigate the relationship of inspection techniques embodying construction steps with the construction techniques embodying inspection steps, such as TUCCA, aiming at reducing the overall cost and increasing the effectiveness of the software development.

Using the Dependence Level Among Requirements to Priorize the Regression Testing Set and Characterize the Complexity of Requirements Change

Systematic Literature Review (SLR or SR) and Systematic Mapping (SM) are scientific literature review techniques that follow well-defined stages, according to a protocol previously elaborated. Besides systematizing the search for relevant studies, the SR predicts the organization and the analysis of the obtained results. However, the SR application is laborious because there are many steps to be followed. Aiming to offer computational support to SR and SM, the StArt (State of the Art through Systematic Review) tool was developed. Besides helping the steps of SR or SM, the StArt tool has implemented visualization and text mining techniques to support the conduction and the reporting of the SR or SM. A comparative analysis was carried out in relation to StArt and other similar tools.

An Overview of Experimental Studies on Software Inspection Process

Background: When there are changes in software requirements, other phases of software development are impacted and frequently, extra effort is needed to adjust the previous developed artifacts to new features or changes. However, if the development team has the traceability of requirements, the extra effort could be not an issue. An example is the software quality team, which needs to define effective tests cycles in each software release. Goal: This papers aims to present an approach based on requirements dependence level to support the regression test prioritization and identify the real impact of requirement changes. Method: The designed approach is based on automatic definition of Requirements Traceability Matrix with three different dependence levels. Moreover, dependence between requirement and test case is also defined. A case study in a real software development industry environment was performed to assess the approach. Results: Identifying the dependence level among requirements have allowed the quality assurance team priorize regression tests and, by means of these tests, defects are early identified if compared with tests execution without priorization. Moreover, the requirements changes complexity is also identified with the approach support. Conclusion: Results shows that definition of dependence levels among requirements gives two contributions: (i) allowing test prioritization definition, which become regression test cycle more effective, (ii) allowing characterize impacts of requirements changes, which is commonly requested by stakeholders.

Managing Literature Reviews Information through Visualization.

Software inspection process is an effective activity to find defects on software artifacts as soon as they are introduced. The development of experimental knowledge on this area is useful to everyone who needs to make decisions about inspection activity. This paper aims to map the empirical studies conducted in the software inspection process area. The steps of the Systematic Mapping (SM) process was performed with the support of the StArt tool. Seventy nine papers were accepted in this SM and attributes related to inspection process, techniques, tools, inspected artifacts, research groups and universities were extracted. The results show different inspection processes, which have been experimentally investigated. Fagan’s process is the most investigated of them. In relation to inspected artifacts, requirements document and source code were the most used. Moreover, different tools and techniques have been used to support these processes.