Abstract

Abstract
As atividades assíncronas no ensino online requerem um acompanhamento regular por parte dos docentes. Esse acompanhamento acompanha duas dimensões: a de grupo, atendendo às dinâmicas globais da turma; e a individual, atendendo às ações de cada estudante. Estando habitualmente estruturadas em tópicos com duração limitada no tempo, a preponderância destas dimensões altera-se nas necessidades de dedicação e intervenção docente. Neste trabalho apresenta-se uma estratégia de apoio à planificação e desenvolvimento da atividade docente, que decompõe essas atividades de acompanhamento e intervenção em cinco marcos temporais. Pretende esta estratégia permitir ao docente identificar os aspetos mais prementes para recolha, de forma praticável, de elementos que possam informar a sua decisão de intervenção pedagógica.

Abstract
Vulnerability scanning tools are essential in detecting systems weaknesses caused by vulnerabilities in their components or wrong configurations. Corporations may use these tools to assess a system in advance and fix its vulnerabilities, thus preventing or mitigating the impact of real attacks. A set of these tools are organized by plugins, each intended to check a specific vulnerability, such as the case of the Tsunami Security Scanner tool released in 2020 by Google. Multiple plugins for this tool were proposed in a community-based approach and thus, it is important for the users and research community to have these plugins in a framework consistently categorized across multiple sources and types. This paper proposes a comprehensive taxonomy for all the 61 plugins available, hierarchically sorted into 2 main categories, 4 categories, 4 subcategories, and 7 types. An analysis and a discussion on statistics by categories and types over time are also provided. The analysis shows that, so far, there are 4 main contributors, being Google, Community, Facebook, and Govtech. The Google source is still the top contributor counting 39 out of 61 plugins and the highest number of plugins available are in the RCE subcategory. The plugins available are mainly focused on critical and high vulnerabilities.

Abstract
We present DIO, a generic tool for observing inefficient and erroneous I/O interactions between applications and in-kernel storage backends that lead to performance, dependability, and correctness issues. DIO eases the analysis and enables near real-time visualization of complex I/O patterns for data-intensive applications generating millions of storage requests. This is achieved by non-intrusively intercepting system calls, enriching collected data with relevant context, and providing timely analysis and visualization for traced events. We demonstrate its usefulness by analyzing four production-level applications. Results show that DIO enables diagnosing inefficient I/O patterns that lead to poor application performance, unexpected and redundant I/O calls caused by high-level libraries, resource contention in multithreaded I/O that leads to high tail latency, and erroneous file accesses that cause data loss. Moreover, through a detailed evaluation, we show that, when comparing DIO's inline diagnosis pipeline with a similar state-of-the-art solution, our system captures up to 28x more events while keeping tracing performance overhead between 14% and 51%.

Abstract
Service-based architecture is an approach that emerged to overcome software development challenges such as difficulty to scale, low productivity, and strong dependence between elements. Microservice, an architectural style that follows this approach, offers advantages such as scalability, agility, resilience, and reuse. This architectural style has been well accepted and used in industry and has been the target of several academic studies. However, analyzing the state-of-the-art and -practice, we can notice a fuzzy limit when trying to classify and characterize the architecture of service-based systems. Furthermore, it is possible to realize that it is difficult to analyze the trade-offs to make decisions regarding the design and evolution of this kind of system. Some concrete examples of these decisions are related to how big the services should be, how they communicate, and how the data should be divided/shared. Based on this context, we developed the CharM, a model for characterizing the architecture of service-based systems that adopts microservices guidelines. To achieve this goal, we followed the guidelines of the Design Science Research in five iterations, composed of an ad-hoc literature review, discussions with experts, two case studies, and a survey. As a contribution, the CharM is an easily understandable model that helps professionals with different profiles to understand, document, and maintain the architecture of service-based systems.& COPY; 2023 Elsevier Inc. All rights reserved.

Abstract