When is a rigid pelvis–trunk approximation sufficient? An output-specific model-reduction protocol applied to lumbar mobility in multibody biomechanics
Oct 2026· Zenodo (CERN European Organization for Nuclear Research)· 1 references
Modeling and Simulation Systems
Abstract
This preprint presents an output-specific computational model-reduction protocol for evaluating when simplified lumbar mobility is sufficient in multibody biomechanics. The primary study compares mass-equivalent exact-lock, axial-yaw-only and three-coordinate lumbar architectures using the public ModelicaHumanBodyPArts v0.10.0 RC1 library. It preserves the six mirrored nominal cases, 45-case operating sweep, 20 passive-lumbar sensitivity simulations, 18 numerical-refinement runs and analytical two-inertia benchmark. This revision adds the verified rigid head and upper-limb inertia sensitivity campaign: an analytical known-answer check and 45 simulations across 15 conditions and three architectures. At the stated 10% locked-normalized criterion, primary pelvis/thorax yaw adequacy is 15/15 each. With restored upper-body inertia, pelvis yaw meets the criterion in 13/15 conditions and thorax yaw in 15/15. The two pelvis-yaw exceedances are 11.19% and 11.95%, and both satisfy 20%. Free-side and support/contact outputs are more sensitive. Adequacy is specific to the output and operating conditions. The manuscript is a preprint and has not undergone peer review. This is a computational model-reduction study and does not establish human or clinical validation. Complete reproduction data, source code, logs and portable tests are archived at https://doi.org/10.5281/zenodo.23175126. The unchanged public software release is archived at https://doi.org/10.5281/zenodo.22941517. This version preserves the collaborator review markers; the publication-field patch updates only the archive filename, SHA-256 and version-specific dataset/preprint DOIs.
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.