Sep 2026· Frontiers in Bioengineering and Biotechnology· Vol 14· 24 references
Abstract
Background Deep squats are required for basic activities of daily life, such as toileting and floor work, but the Lewinnek acetabular safe zone was based on static supine radiographs and did not account for dynamic pelvic positioning during functional activities. Consequently, quantitative positioning targets that integrate walking with deep-squat biomechanics remain poorly defined. Methods Simulations were performed in the AnyBody Modeling System using a generic adult musculoskeletal model. Angular Impingement Distance and Angular Edge-loading Distance (AED) were computed at 1° increments across 10,201 acetabular component positions during walking and deep squat. A dual-activity feasible zone was defined as component positions simultaneously satisfying AID- and AED-based criteria for both activities. Sensitivity to femoral head diameter (28, 32, and 36 mm) was evaluated. Results In the normal spinal-mobility scenario, the dual-activity feasible zone contained 231 positions, with a target position at radiographic anteversion (RA) 24° and radiographic inclination (RI) 46°. Only 21.6% of these feasible positions fell within the Lewinnek zone; most required higher anteversion or inclination than the Lewinnek target. In the reduced lumbopelvic-mobility scenario, the feasible zone contained 209 positions with a target position shifted toward higher anteversion and inclination (RA 36°, RI 56°) and no overlap with the Lewinnek zone. Sensitivity to femoral head diameter was substantial: compared with the 28-mm head, the 36-mm head increased the feasible zone 4.2-fold (375 vs. 89 positions), with the 32-mm default yielding 231 positions. Conclusion We present a computational framework for deriving activity-specific acetabular positioning targets from dynamic musculoskeletal simulations of walking and deep squat. The resulting targets are biomechanically grounded but remain simulation-derived hypotheses pending clinical validation.
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 perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.