Abstract
Code inspection is an important activity to identify defects in the source code and improve software quality. However, even when using techniques such as checklists, inspectors consider implicit decision-making knowledge. In this paper, we perform an exploratory study with groups of inspectors (Group1 and Group2) with two objectives: 1) to present findings on how (and if) auxiliary artifacts interfere in decision making during the code inspection activity, and 2) to show whether there is any influence on the number of defects identified by inspectors when using or not auxiliary artifacts. Both groups used the computational code inspection support of the CRISTA tool, but only Group1 used auxiliary artifacts (requirements, UML diagrams, software metrics). We identified 10 findings. All of them are related to the inspectors’ decision making and the influence of using artifacts on defects identification. The findings suggested that when inspectors use auxiliary artifacts, their effectiveness in identifying defects is improved. Besides, their decision making is more homogeneous than that of inspectors who do not use auxiliary artifacts. However, more investigations are necessary to make the results more generalizable. As future work, different strategies for code inspection techniques can be defined based on the findings.

Abstract
Requirement patterns represent an abstraction of an application's behaviors and services that, in turn, may be replicated in similar applications. However, there has been a lack of efforts exploiting the benefits of requirement patterns in other phases of the software development life cycle, besides the requirements engineering itself. To address this gap, we propose the Software Pattern MetaModel (SoPaMM) that bridges requirement patterns to groups of scenarios with similar behaviors in the form of test patterns. SoPaMM allows the description of the behavior of a requirement pattern through a time executable and easy-to-use language aiming at the automatic generation of test patterns. Using SoPaMM, we model and implement a behavior-driven functional requirement pattern for a web-based user authentication application. Our preliminary results point out that a requirement pattern can be an executable specification capable of generating automated tests.

Abstract
The grown adoption of mobile devices makes the development of applications a very attractive market. On top of it, run tests is a crucial activity and a big challenge due to the high fragmentation on Android ecosystem. In this paper, we discuss how a new platform based on Collaborative Economy could be used to create a new alternative to software testing. We present an analysis of using this platform and we confirm its advantages over existing cloud solutions, from a scalability and cost viewpoints. Our solution can provide an average cost reduction upper to 85% and a potential increasing in scalability.

Abstract
Many countries today are attempting to move into digital transformation to try to improve the efficiency of Government activities and reduce unnecessary costs. This is how the concept of the Digital Government has come to the fore. All agree on the need to guarantee the quality of digitalized services that are provided to the taxpayer. Based on this scenario, this work adapts a validation process for digitalized services, providing a systematic way for test case generation, to guarantee the quality of software products delivered to the public. Amongst the challenges met in this research work, we highlight the lack of requirements for the services analyzed and the impossibility of accessing their source code, which requires a black-box testing process. We observed, based on the results, that the adapted process allowed the validation activity to be done efficiently and systematically, given the peculiarities of the context involved. We report the experience gained after the use of the adapted test process when compared to the previous ad-hoc testing process. Moreover, based on our experience, we identified a subset of tours from exploratory testing more suitable to test web based services, considering the restrictions we have, for improving the quality in the process of digital transformation. Other lessons learned are also presented and we think the results can be useful for testing systems with similar constraints.

Abstract

Abstract