Abstract
Background: Approaches to documenting the software patterns of a system can support intentionally and manually documenting them or automatically extracting them from the source code. Some of the approaches that we review do not maintain proximity between code and documentation. Others do not update the documentation after the code is changed. All of them present a low level of liveness. Approach: This work proposes an approach to improve the understandability of a software system by documenting the design patterns it uses. We regard the creation and the documentation of software as part of the same process and attempt to streamline the two activities. We achieve this by increasing the feedback about the pattern instances present in the code, during development-i.e., by increasing liveness. Moreover, our approach maintains proximity between code and documentation and allows us to visualize the pattern instances under the same environment. We developed a prototype-DesignPatternDoc-for IntelliJ IDEA that continuously identifies pattern instances in the code, suggests them to the developer, generates the respective pattern-instance documentation, and enables live editing and visualization of that documentation. Results: To evaluate this approach, we conducted a controlled experiment with 21 novice developers. We asked participants to complete three tasks that involved understanding and evolving small software systems-up to six classes and 100 lines of code-and recorded the duration and the number of context switches. The results show that our approach helps developers spend less time understanding and documenting a software system when compared to using tools with a lower degree of liveness. Additionally, embedding documentation in the IDE and maintaining it close to the source code reduces context switching significantly.

Abstract
Domain-specific standards and documents heavily regulate safety-critical systems. One example is the DO-178C standard for aerospace, which guides organizations to achieve system safety and evidence for their certification. Under such regulated contexts, most organizations use traditional development processes, in contrast to the massive adoption of Agile in the software industry. Among other benefits, Agile methods promise faster delivery and better flexibility to address customer needs. Adopting Agile methods and practices are possible in aerospace because the DO-178C standard does not prescribe concrete software development methods. In spite of that, Agile development is not used in DO-178C contexts. To help change that, our research aims to understand whether and how organizations engineering safety-critical software systems for aerospace may benefit from Agile methods and practices. We analyzed the DO-178C standard and confirm that it is compatible with Agile methods. Then, we present a systematic literature mapping of adopting Agile in software development for aerospace, where we identified significant concerns, recurrent issues, and several challenges. Some real industry aerospace projects provided us with important data and the perspective of domain experts about the pros and cons of Agile methods in this context. We conclude by proposing an agenda of research opportunities to improve safety-critical software development towards agility that we consider worthy of further research, application and confirmation in wider contexts.

Abstract
This paper leverages the outcomes of the first workshop on HCI Engineering Education [4] to create an online repository where the community can share content relevant to HCI. The repository takes advantage of the functionalities of the Git file versioning system to support presenting and adding content. The paper describes the structure of the repository and the process for adding new content. In addition, we propose an adaptation of the framework for presenting teaching samples, supporting more flexibility in the application of educational material for different teaching objectives. The new presentation format starts with describing a design problem and emphasises the students' applied understanding of conceptual and theoretical knowledge. The presentation format is demonstrated and discussed by the example of an end-user design tool for mobile data collection.

Abstract

Abstract
For the past fourteen years, the Workshop on Automating Test Case Design, Selection and Evaluation (A-TEST)1 has provided a venue for researchers and industry members alike to exchange and discuss trending views, ideas, state-of-the-art, work-in-progress, and scientific results on automated testing. The previous thirteen editions of A-TEST were co-located with several conferences over time: CISTI2 (first two editions), FEDCSIS 3 (three editions), and ESEC/FSE4 (seven editions). The 14th edition took place on September 15, 2023, in Kirchberg, Luxembourg, co-located with ASE 2023 (38th IEEE/ACM International Conference on Automated Software Engineering5). The A-TEST 2023 program featured an enlightening keynote on quantum software testing, followed by three technical sessions in which the authors of 6 full papers and 4 short papers dived into various aspects of automated testing, from neuroevolution and fuzzing techniques to GUI-based software testing and test case recommendations. This short report summarizes the keynote and paper presentations at A-TEST 2023.

Abstract
Background: The role of mindful eating (ME) and intuitive eating (IE) in improving eating behavior, diet quality, and health is an area of increasing interest. Objective: The objective of this review was to identify the instruments used to assess ME and IE among higher education students and outcomes related to these dimensions. Methods: This review was carried out according to the PRISMA statement, through systematic searches in PubMed, Web of Science, PsycInfo, and Scopus. The inclusion criteria selected for higher education students, levels of ME and/or IE reported, and observational and clinical studies. The exclusion criteria selected against reviews, qualitative studies, and case studies. Quality was assessed using the Academy of Nutrition and Dietetics Quality Criteria Checklist. Results: A total of 516 initial records were identified, from which 75 were included. Cross-sectional studies were the most common research design (86.7%). Most studies were conducted with samples that were predominantly female (90.7%), White (76.0%), aged 18 to 22 years (88.4%), with BMI < 25 kg/m(2) (83.0%), and in the United States (61.3%). The Intuitive Eating Scale (IES), the Mindful Eating Questionnaire (MEQ), and their different versions were the most used instruments. The outcomes most studies included were eating behavior and disorders (77.3%), anthropometric assessments (47.8%), mental health (42.0%), and body image (40.6%). Regarding the quality of studies, 34.7% of studies were assigned a positive, 1.3% a negative, and 64.0% a neutral rate. Conclusions: IES and MEQ were the most used instruments. RCT and cohort studies are scarce, and future research with a higher level of quality is needed, especially on the topics of food consumption, diet quality, and biochemical markers.