Oct 2026· The Journal of Indian Prosthodontic Society· Vol 26 4, pp.
370-377
· 0 citations
Medicine
TL;DR
Copings fabricated from dies scanned using IOS demonstrated significantly lower vertical marginal discrepancies compared to those scanned using the laboratory scanner, however, the marginal gaps observed in both groups were within clinically acceptable limits.
Abstract
Aim
This study aimed to evaluate and compare the vertical marginal discrepancy of DMLS copings fabricated from stone dies scanned using an intraoral scanner (IOS) and a laboratory scanner.
SETTINGS AND
Design
An in vitro comparative study was conducted to evaluate the influence of intraoral and laboratory scanning systems on the vertical marginal discrepancy of DMLS copings.
Materials And Methods
A customised stainless-steel model simulating a prepared tooth with a shoulder finish line was fabricated. Impressions of the model were made using elastomeric impression material. Forty dies ( n =40) were poured using type IV dental stone and divided into two groups ( n =20). Group 1 dies were scanned using a 3Shape TRIOS IOS and Group 2 dies were scanned using a 3Shape extraoral laboratory scanner. Copings were fabricated using CAD/CAM software. Marginal gap between the die and the coping was measured at 4 predetermined points (buccal, lingual, mesial, and distal) using a stereomicroscope at ×40 magnification.
STATISTICAL ANALYSIS USED
Data were analysed using SPSS (version 21, IBM Corp., Armonk, NY, USA). Student's unpaired t-test was used to compare the tested groups. The collected data were analysed at a significance level set at P < 0.05.
Results
The mean marginal gap between the die and coping was 11.44 μm for Group 1 and 29.62 μm for Group 2. The difference between the groups was statistically significant ( P < 0.001).
Conclusion
Copings fabricated from dies scanned using IOS demonstrated significantly lower vertical marginal discrepancies compared to those scanned using the laboratory scanner. However, the marginal gaps observed in both groups were within clinically acceptable limits.
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.