Sep 2026· Zenodo (CERN European Organization for Nuclear Research)· 12 citations
Abstract
Normative OES-32 residual reference (ADR-001): a deterministic Python definition of the max-absolute residual between two 32-component vectors, with a strict > tolerance failure rule and executable contract tests. Contract. Input: two finite real-valued vectors of length 32 and a finite, non-negative tolerance. Component residual: abs(observed[i] - reference[i]). Aggregate residual: the maximum of the 32 component residuals. Failure occurs if and only if aggregate residual > tolerance. Invalid input is rejected with ValueError. This repository is the normative residual definition for Spark AI NLP under ADR-001 Option A (Residual-canonical); normative commit b77b61254f15778c6ae221843dceac7a8571158e. Downstream oes32_engine (Python) and oes32-hls (C++ HLS) are Profile A sidecars. The OES-512 weighted latch remains TARGET. Evidence tags. Contract-test vectors: SYNTHETIC (hand-written). Empirical, hardware, or field results: none claimed. Scope and limits. Research prototype. It is not an empirical study, a scientific theory, a physical or biological model, a diagnostic, or a claim about consciousness; it is not hardware, medical, or quantum-hardware software, and it does not justify decisions based on a pass/fail result. Evidence tags follow sparkainlp-x/.github (SYNTHETIC / REPORTED / TARGET / UNRUN).
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.