Abstract The practices proposed in agile methods to speed up software development, although they are beneficial to the organization, can affect the way in which requirements engineering activities are conducted as these practices are not explicit. These activities, when not carried out properly, can result in poorly understood, omitted and poorly specified requirements, leading to requirements debt and can compromise other stages of software development. However, requirements debts are little explored and, on many occasions, are unknown, not monitored or managed efficiently, which causes high maintenance costs over time. The objective of this article is to propose an Ontology focused on requirements debt in the agile context. The research was conducted through an investigation of the state of practice supported by \textit{grounded theory}, unifying the result with information obtained in two systematic studies of the literature: a systematic mapping of the literature that consists of identifying the causes, consequences and practices aimed at debts of requirements and a tertiary study focused on debt management, supporting the knowledge obtained about requirements debt and serving as input for the construction of an ontology, called “OntoReD”.

With the constant development of new solutions that process personal data and the approval of privacy regulations such as GDPR and LGPD, the demand for development teams to be prepared, engaged, and responsible for implementing software that guarantees users’ data protection has increased. The privacy concern must be present from the conception of the solution. Therefore, the Requirements Engineering area must incorporate processes, methods, techniques, and tools that address data protection aspects, especially in line with current regulations. In this context, the present study investigates which approaches to Requirements Engineering currently proposed in the literature support personal data protection. This objective was achieved through a systematic mapping that identified 11 approaches, 4 tools, 3 methods, 2 processes, 1 technique, and 1 language. The results point to solutions addressing distinct sets of input artifacts but with a predominance of privacy requirements as a resultant artifact. In addition, the results show the need to apply the solutions in actual contexts of use.

[Context] Awareness is a well-known but still not fully reached concept in collaborative environments. At this point, two main potential issues remain open: First, the understanding of what awareness is and how to face it in collaborative applications; Second, the establishment of a solid basis for the assessment focusing on awareness aspects. [Goal] We elaborated an awareness taxonomy that contemplates a broad set of awareness elements and collaboration aspects necessary for cooperative work. We developed our awareness taxonomy through a systematic mapping study over the last-10-years CSCW publications regarding the design, development, and evaluation of groupware systems that addressed awareness and collaboration aspects. [Result] We developed a comprehensive multidimensional taxonomy, represented in three main awareness dimensions, namely, collaboration, workspace, and contextual, which encompass, in a simplified way, the awareness literature presented by other models.

Context] Awareness has been a valuable concept in Computer-Supported Cooperative Work – CSCW – since its formation, and it is an essential part of collaborative systems. The awareness research followed side by side the evolution of the CSCW field over the last decades, and we can see the progress both in a mutual understanding of awareness and in developing concepts and technology of awareness support. [Goal] Using the awareness and collaboration concepts as a starting point, we performed a systematic mapping study to identify the state-of-the-art of approaches, models, methodologies, or processes adopted in the design, development, and evaluation of collaborative applications. We figured out our research through the six most relevant databases/search engines combined with snowballing techniques, and selected 42 papers from 4320 analyzed, considering publications in the last ten years. [Result] We established a conceptual awareness framework composed of five broad dimensions necessary in collaborative applications: contextual, collaboration, situational, workspace, and historical awareness. This framework constitutes a reasonable set of 17 design categories and 92 awareness elements that assists in providing awareness and collaboration aspects in collaborative systems.

Background: Agile development was an important initiative that changed the traditional way of developing software into an agile development process.Action is more important than the process in the agile world, and requirements and documentation do more harm than good.However, when developing requirement engineering activities inadequately, they motivate the emergence of problems that directly affect the development, which can incur requirements debt.Aim: This study investigates the causes of requirements debt that incur requirements debt and actions that can minimize and or avoid them inside the context of agile software development.Method: To fulfill the objective, we performed qualitative research, supported by data analysis suggested by Grounded Theory, with 19 subjects in 13 agile organizations at a national and international level in different segments.Results: At the end of this study, we proposed a theoretical model containing the requirements debt causes and their effects and practices that might mitigate them, and the relation between these three factors.

Abstract Context: Interest in global software development (GSD) has led to the publication of numerous studies. Over time, these studies should be updated to verify if their findings and conclusions remain valid. Objective: To update a tertiary study, published in 2014, focused on investigating risks and risk mitigation advice in the context of GSD. Method: We conducted a systematic literature study based on forward snowballing, out of which we identified and selected 25 unique studies. Results: We extracted: (a) 118 risks (75 of which already identified in the original work), and (b) 167 mitigation advice (44 of which were identified in the original work). Out of 43 new risks identified, just 10 are specific to GSD settings; the others are risks of the software process described in the context of GSD. The evidence supporting these risks and mitigation were extracted from 619 and 389 primary sources, respectively. Given the amount of evidence found, we have reported only those with higher empirical support. The raw data is available online as complementary material. Conclusions: Interest in GSD, its potential risks, and mitigation strategies, remains high. This update has allowed increasing the level of empirical support provided by the findings of the original work.

Systematic Literature Review (SLR) is a key tool for evidence-based practice as it combines results from multiple studies of a specific topic of research. Due its characteristics, it is a time consuming, hard process that requires a properly documented protocol for scientific acknowledgment. In this context, this paper presents the SESRA -- a web-based automated tool to support all phases of the SLR process, contributing to its productivity and reliability. We also present a use case on the software engineering field, applying specific knowledge to set the process in the discipline. Further, we discuss how to use the tool to establish a more formal and controlled process and to reduce effort on its repetitive activities. The outcomes and feedback obtained in early use have shown that SESRA could support the SLR process, automating some of its key activities.

Green IT and computing are key areas to contribute with the environment sustainability. Recent researches have been exploring tools, practices, process, frameworks, reference models in Green IT, as well as they are mitigating the impact of the technology on the user of raw materials, electrical energy costs, greenhouse gas emissions or generation e-waste. Sizing up earnings and costs of green practices and processes will allow that software organizations can invest more in environment actions. This paper presents a systematic mapping study about green metrics, with objective to discover the state-of-the art drived by software engineering.