This paper compares multi-layer perceptron (MLP) and Kolmogorov--Arnold Network (KAN) receivers using a multi-SNR Nyquist-rate BPSK dataset and shows that both MLP and KAN receivers reproduce the expected AWGN-BPSK detection trend, while a compact KAN configuration reaches a comparable operating region with substantially fewer trainable parameters.
Abstract
Classical coherent binary phase-shift keying (BPSK) reception over additive white Gaussian noise (AWGN) channels is analytically well understood, and the optimum hard-decision detector is known. Therefore, the aim of using neural receivers in this study is not to replace the classical AWGN-BPSK detector. Instead, the AWGN-BPSK setting is deliberately selected as a theoretically verifiable benchmark for analyzing how compactly neural receiver architectures can represent a known decision behavior. This paper compares multi-layer perceptron (MLP) and Kolmogorov--Arnold Network (KAN) receivers using a multi-SNR Nyquist-rate BPSK dataset. The models are evaluated using bit error rate (BER), mean squared error (MSE), and trainable parameter count. Beyond reporting accuracy alone, this work emphasizes a common-loss parameter-efficiency perspective: when two receivers reach a comparable practical BER or loss region, the receiver with fewer parameters is more attractive for real-time deployment. The results show that both MLP and KAN receivers reproduce the expected AWGN-BPSK detection trend, while a compact KAN configuration reaches a comparable operating region with substantially fewer trainable parameters. In particular, the KAN receiver with 3281 parameters achieves a test BER of 2.45 x 10^-4, while the MLP baseline with 8513 parameters achieves a test BER of 2.50 x 10^-4. This corresponds to approximately 61.5% fewer trainable parameters at a comparable BER operating point. This reduction is important for real-time neural receivers because it affects memory footprint, parameter access, inference latency, energy consumption, and hardware feasibility on embedded, software-defined radio, FPGA, ASIC, and edge communication platforms.
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.