Oct 2026· PoliEcoM Administration Review· 0 citations· 21 references
TL;DR
This study examines the extent to which scientific publications can support claims about algorithmic disaster governance in an information-limited setting and distinguishes among technological capability, functional compatibility, administrative embedding, and system integration.
Abstract
This study examines the extent to which scientific publications can support claims about algorithmic disaster governance in an information-limited setting. The empirical corpus consists of two purposively selected 2024 North Korean journal issues—Computer and Software Technology and Geologic and Geographic Science. All 48 scholarly or technical items listed in the two issues were screened, and 14 were retained for structured analysis. Using qualitative document analysis and evidence-bounded coding, the study distinguishes among technological capability, functional compatibility, administrative embedding, and system integration. Three inference rules constrain the escalation of claims: greater functional distance weakens evidentiary support; claims of embedding require connective institutional evidence; and module-level capabilities are non-additive for platform-level claims. The sampled literature documents disaster-risk assessment, remote sensing, terrain processing, deep-neural-network water-depth estimation, routing, sensing, robotics, optimization, and participatory-data workflows. Two qualitative robustness tests clarify the limits of inference. Excluding all transfer-hypothesis cases preserves the modular technical pattern; omitting the principal governance source, however, removes direct support for a full-cycle administrative architecture while leaving the technical-capability portfolio and inference framework intact. The article’s general contribution is therefore an evidence-bounded capability–compatibility–embedding protocol. Modular algorithmic disaster governance is the empirical pattern identified by applying that protocol to this bounded corpus, not a claim that an integrated nationwide system has been deployed.
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.