To determine whether 3D superimposition software (“Apps”) systematically affects 3D deviation outcomes derived from intraoral scanner (IOS) data, using two quantile‑range accuracy metrics (Q90_Q10_half and Q95_Q05_half). Two jaw‑sized reference models were digitized with a high‑resolution optical scanner (ATOS III) to generate reference STL meshes (REF_STL). Five IOS devices acquired ten scans per device and per jaw model, exported as STL meshes (IMP_STL): Emerald Green, iTero 5D, Medit i900, Primescan, and Trios 5. Each IMP_STL was trimmed (1 mm above gingival line) and superimposed to REF_STL in four Apps: commercial industrial software: Geomagic Control X and GOM Inspect, and open dentistry-focused software Medit Design (Compare) and Dentexion; resulting in total to N = 400 superimpositions. For each superimposition, Q90_Q10_half and Q95_Q05_half values were computed from point-wise signed surface distances. A linear mixed‑effects model tested factor App as fixed effect with random intercepts for factors Device and Jaw, followed by Bonferroni‑adjusted pairwise comparisons (α = 0.05). App significantly influenced Q90_Q10_half (p < 0.01) and Q95_Q05_half (p < 0.001). Control X yielded higher adjusted means than Dentexion and Compare for Q90_Q10_half (both p < 0.01), while Dentexion, GOM, and Compare did not differ. For Q95_Q05_half, Control X exceeded all other Apps (all p < 0.01). Notably, IOS rankings were stable across Apps, indicating that software altered magnitude but not relative ordering. Evaluation software is a significant source of variability in 3D deviation metrics; Control X produced consistently higher (more conservative) quantile‑range values, particularly for Q95_Q05_half. Inter‑study comparisons in digital accuracy research should report the evaluation software and settings. Dentistry‑focused Apps (e.g., with automated tooth segmentation) may reduce operator‑dependent effects and facilitate clinically applicable monitoring.
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.