Elixir is an emerging functional programming language that is gaining popularity in the industry. However, to the best of our knowledge, no study has yet presented a specialized catalog of refactoring strategies specifically tailored for this language. Therefore, this paper aims to address this research gap by conducting a systematic literature review to explore whether there are existing refactoring strategies, compatible with Elixir, that have been proposed for other functional languages or languages that served as inspiration for the development of Elixir. Our preliminary results indicate that there are 54 refactoring strategies compatible with Elixir code, thus forming a comprehensive catalog of refactoring techniques tailored specifically for this language. To illustrate the application of these refactoring strategies, we have provided code examples that show the transformations resulting from each refactoring. Additionally, these refactorings have been categorized into three distinct groups based on the specific programming features required for the respective code transformations.

Elixir is a new functional programming language whose popularity is rising in the industry. However, there are few works in the literature focused on studying the internal quality of systems implemented in this language. Particularly, to the best of our knowledge, there is currently no catalog of code smells for Elixir. Therefore, in this paper, through a grey literature review, we investigate whether Elixir developers discuss code smells. Our preliminary results indicate that 11 of the 22 traditional code smells cataloged by Fowler and Beck are discussed by Elixir developers. We also propose a list of 18 new smells specific for Elixir systems and investigate whether these smells are currently identified by Credo, a well-known static code analysis tool for Elixir. We conclude that only two traditional code smells and one Elixir-specific code smell are automatically detected by this tool. Thus, these early results represent an opportunity for extending tools such as Credo to detect code smells and then contribute to improving the internal quality of Elixir systems.

The increase in the life expectancy has led to a higher number of elderly people accessing technology and mobile devices (cell phones and tablets). However, in general, the elderly present difficulties in this interaction because, in addition to the physical limitations imposed by aging, many applications were not properly designed to consider such restrictions. This paper presents the results of a survey pointing out main difficulties that elderly people face when using mobile devices and proposes strategies to overcome these barriers. The research was carried out by applying questionnaires in the form of customized applications. Based on the answers, some alternatives were proposed to try to circumvent the reported difficulties and to make the elderly acquire autonomy and use their devices safely, efficiently, without frustration regardless of their physical limitations. In order to evaluate and validate the proposals, a framework was developed to make it easier for application developers to create interfaces that incorporate the proposed strategies.

Software patterns are computing artifacts used to document knowledge that may be reused during software development process.There are several types of patterns, such as analysis, design, and architectural, among others.Design patterns are the most well known by designers, but many of them are described in books and scientific papers, a recurring way of documenting patterns that limits their reuse potential.Aiming to not only minimize this limitation but also provide ways of recovering contextualized knowledge in these patterns, the present paper presents the architecture APRImora, an extension based on Semantic Web of the Analysis Patterns Reuse Infrastructure (APRI).In this architecture, the patterns are documented by metadata defined as application profiles of the Dublin Core standard and stored in the RDF format, allowing them to be discovered by search engines.The APRImora architecture helps designers discover and reuse software patterns based on semantic relations, which favors their dissemination and reuse.