Oct 2026· Dental journal· 0 citations· 30 references
TL;DR
Within the constraints of a single-group pilot design, the training program was associated with increases in students’ self-reported perceptions across all five dimensions and may inform, but do not by themselves justify, decisions on the curricular integration of IOS training.
Abstract
Background/Objectives: Intraoral scanners (IOS) are increasingly integrated into dental curricula, yet evidence on how brief structured training affects novice students remains limited, particularly in resource-constrained settings. This pilot quasi-experimental study evaluated the effect of a structured IOS training program on the self-reported perceptions of undergraduate dental students with no prior IOS experience. Methods: Twenty first- and third-semester students at the School of Dentistry, Universidad de Especialidades Espíritu Santo (Ecuador), completed a 5-item Likert-type questionnaire (1–9 scale) before and after a training program comprising theoretical instruction and typodont-based practical sessions using a TRIOS 3 scanner (3Shape, Copenhagen, Denmark). Paired Student’s t-tests and Wilcoxon signed-rank tests were used to compare pre- and post-training scores, and effect sizes (Cohen’s dz for paired samples) were calculated for each dimension. Results: Significant improvements were observed in all five perception dimensions (all p < 0.001): familiarity (mean difference: +3.45; dz = 1.50), comfort (+3.25; dz = 1.40), confidence (+3.70; dz = 1.54), perceived scan accuracy (+3.30; dz = 1.41), and software competence (+3.55; dz = 1.30). Conclusions: Within the constraints of a single-group pilot design, the training program was associated with increases in students’ self-reported perceptions across all five dimensions. These preliminary findings may inform, but do not by themselves justify, decisions on the curricular integration of IOS training. Controlled studies with objective performance outcomes, validated instruments and follow-up assessment are required.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.