Abstract

Abstract

Abstract
General-purpose AI-assisted tools, such as ChatGPT, have recently gained much attention from the media and the general public. That raised questions about in which tasks we can apply such a tool. A good code design is essential for agile software development to keep it ready for change. In this context, identifying which design pattern can be appropriate for a given scenario can be considered an advanced skill that requires a high degree of abstraction and a good knowledge of object orientation. This paper aims to perform an exploratory study investigating the effectiveness of an AI-assisted tool in assisting developers in choosing a design pattern to solve design scenarios. To reach this goal, we gathered 56 existing questions used by teachers and public tenders that provide a concrete context and ask which design pattern would be suitable. We submitted these questions to ChatGPT and analyzed the answers. We found that 93% of the questions were answered correctly with a good level of detail, demonstrating the potential of such a tool as a valuable resource to help developers to apply design patterns and make design decisions.

Abstract
Software businesses are continuously increasing their presence in the cloud. While cloud computing is not a new research topic, designing software for the cloud is still challenging, requiring engineers to invest in research to become proficient at working with it. Design patterns can be used to facilitate cloud adoption, as they provide valuable design knowledge and implementation guidelines for recurrent engineering problems. This work introduces a pattern language for designing software for the cloud. We believe developers can significantly reduce their R&D time by adopting these patterns to bootstrap their cloud architecture. The language comprises 10 patterns, organized into four categories: Automated Infrastructure Management, Orchestration and Supervision, Monitoring, and Discovery and Communication. © The Author(s), under exclusive license to Springer-Verlag GmbH, DE, part of Springer Nature 2025.

Abstract
Throughout the Virtual Reality (VR) literature, we find different terms to define the same concepts as well as the same terms addressing different concepts. This issue can easily cause misinterpretations and difficulty in the analysis of papers from different authors. This work addresses this terminology confusion through a detailed analysis of current key concepts, how they have been employed, comparing them to other concepts, and proposing adaptations to their definitions to reduce conceptual overlap while preserving the original terms. In this work, we reviewed widely used terms in VR: Fidelity, Realism, Immersion, Presence, and Coherence. We also identified and discussed derivative terms, such as Place Illusion, Plausibility Illusion, Sensorimotor Contingencies, Multisensory, Virtual Content, Objective and Subjective Realism, and Objective and Subjective Internal Coherence. We proposed how these distinct concepts can be separated, merged, and linked, providing a clearer terminology for future use and discussing the implications of this terminology.

Abstract
We present CIDER, a novel framework for the collaborative editing of 3D augmented scenes. The framework allows multiple users to manipulate the virtual elements added to the real environment independently and without unexpected changes, comparing the different editing proposals and finalising a collaborative result. CIDER leverages the use of 'layers' encapsulating the state of the environment. Private layers can be edited independently by the different subjects, and a global one can be collaboratively updated with 'commit' operations. In this paper, we describe in detail the system architecture and the implementation as a prototype for the HoloLens 2 headsets, as well as the motivations behind the interaction design. The system has been validated with a user study on a realistic interior design task. The study not only evaluated the general usability but also compared two different approaches for the management of the atomic commit: forced (single-phase) and voting (requiring consensus), analyzing the effects of this choice on collaborative behaviour. According to the users' comments, we performed improvements to the interface and further tested their effectiveness.