Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Corrective evidence for Training adequacy and evaluation populations in remaining useful life benchmarks: 96 primary fits, two numerical-scale diagnostics and nine additional budget checks. All original prediction prefixes were reproduced exactly and every extended fit stopped by validation patience before the threefold cap. Target-comparison preferences and model-winning sets were unchanged under the budget extension. Separate sensor checks on six fixed predictors provide 72 perturbed test-prediction tables and 600 inference timings; the FD004 reference winner changes under prescribed range-scaled noise or bias. This is an exploratory assessment of one simulated benchmark, not a claim of global convergence or maintenance benefits. This software version supplies frozen corrective training/analysis code, full aggregate tables, figures, literature coding, specifications and reproduction instructions. A local materializer restores the required two-directory layout using the companion generated-artifact dataset. The historical root-level code and tables are retained and explicitly identified as historical. The corrective study supersedes architectural interpretations of a nearly constant baseline, same-task improvement claims based on different native truths, and inference treating deterministic tree repetitions as independent fits. Raw NASA sensor files, literature full texts, manuscript/submission files and credentials are excluded. Historical DOI versions do not contain these corrective experiments.
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 2, 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.