Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Version 2.0.0 provides two separate collections of 8,600 persisted probability files each, covering historical and supplementary experiments on the same 43 binary tasks and five seeds. Each NPZ contains validation/test probabilities and aligned binary labels (p_val, p_test, y_val, y_test). No raw feature tables or model weights are included. The four original proba_part ZIPs are inherited unchanged and contain 8,600 historical files under results/proba/. The five additional supplement_part01.zip through supplement_part05.zip archives together contain 8,600 new probability files and 8,600 cell JSON records under revision/supplement/, 860 forty-trial parameter-search records, 215 split-index files, and the historical 60,200-row seven-workflow score table. All five supplementary ZIPs are required for the complete collection. Identically named historical and supplementary probabilities must not be merged into one directory. Cache paths in new cell metadata are normalized; both original and released JSON hashes are retained. The companion software version provides all analysis code, contrast tables, model/sampler provenance, and corrections to v1.x interpretations. In particular, this is a workflow-dependent empirical evaluation, not evidence of a universal failure of remedies for all TFMs. New TabDPT comparisons use seeded same-run baselines; the old fit-time PCA RNG cannot be recovered. Threshold/calibration, source-dependence and protocol limitations are documented in the code erratum. Original generated artifacts are CC BY 4.0. Upstream datasets and weights retain their separate terms. README-DATA.md explains the file layout; SHA256SUMS.txt records archive checksums. The code-side installer verifies archive and individual-file hashes before extraction.
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.