COMPLEMENTARY, NOT SUBSTITUTIVE: LOAD-DEPENDENT INTERACTION EFFECTS OF FIBRE-OPTIC INFRASTRUCTURE AND SOFTWARE-DEFINED NETWORKING ON ISP NETWORK PERFORMANCE IN A KENYAN RESEARCH-AND-EDUCATION NETWORK
Sep 2026· World Journal of Advanced Engineering Technology and Sciences· 0 citations
Software-Defined Networks and 5G
Abstract
Fibre-optic infrastructure and Software-Defined Networking (SDN) are each independently documented to improve network performance, yet whether their combined effect is simply additive or functionally interactive has not been empirically tested in an African ISP context. This paper reports that test, using KENET, Kenya's national research and education network, as the empirical case. Controlled network emulation (Mininet 2.3, NS-3.38) on a twelve-node, three-tier replica of KENET's backbone compared a static-routing baseline against an SDN-integrated condition across a graduated traffic-load range (40–95 percent), cross-validated against KENET's own monitoring data (mean divergence 9.8 percent) and corroborated through 23 practitioner interviews (76.7 percent response rate). SDN deployment scope, entered as a continuous predictor, explained 76 percent of the variance in latency (R² = 0.76, F(1, N) = 48.6, p < .001). Critically, the combined benefit was not additive: latency improvement rose from 54.8 percent at 40 percent load to 65.4 percent at 95 percent load, P95 throughput improvement rose from 18.3 to 51.1 percent over the same range, and modelled annual uptime rose from 99.72 to 99.95 percent under automated failover. This load-dependent pattern was robust under sensitivity analysis (48.9–66.2 percent) and independently corroborated by practitioner-reported estimates (50–60 percent). H₀₃ was rejected in favour of H₁₃: fibre-optic infrastructure and SDN function as complementary rather than substitute investments, with SDN's marginal value concentrated precisely where fibre capacity is under the greatest strain. The findings imply that ISPs should sequence SDN rollout to the most congested segments first, capturing disproportionately greater marginal benefit than uniform deployment.
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.