Background/Objectives: Local mesh density characterizes the polygonal representation of digital surface models; however, reference values and clinically relevant thresholds for posterior occlusal meshes generated through intraoral scanning and subsequent software processing have not been established. This study aimed to characterize the occlusal mesh density of maxillary first molars using V/A as the primary descriptor and F/A as a topology-derived secondary descriptor, and to evaluate mean bilateral differences between teeth 16 and 26. Methods: Twenty participants with intact bilateral maxillary first molars were included in this prospective within-subject observational study. Full-arch scans were acquired with a Medit i900 intraoral scanner and exported as STL files. Occlusal regions of interest were isolated in Medit Design, exported as PLY files, and analyzed for surface area, vertex count, face count, vertices per unit area (V/A), and faces per unit area (F/A). Bilateral differences were evaluated using paired-sample t-tests. Results: Mean participant-level occlusal mesh density was 37.62 ± 2.13 vertices/mm2 and 73.13 ± 4.22 faces/mm2. No significant bilateral differences were found for surface area, vertex or face counts, V/A, or F/A (all p > 0.05). For V/A, the mean right–left difference was 0.48 vertices/mm2, with Bland–Altman 95% limits of agreement from −3.87 to 4.82 vertices/mm2. In a descriptive cross-study comparison involving independent participant samples, the occlusal mesh-density values observed in the present study were higher than the buccal-surface values reported previously. Conclusions: Under the specified Medit i900 acquisition and Medit Design ROI-processing workflow, no statistically significant mean right–left differences in local mesh density were detected. The reported V/A and F/A values provide workflow-specific baseline descriptors of the final exported PLY mesh structure and should not be interpreted as measures of scanning accuracy. Their relationship to downstream CAD, AI-based design, or clinical outcomes requires direct investigation.
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.