Sep 2026· Modelling and Data Analysis· 7 references
Abstract
Context and relevance. Modern trends in technology development are moving towards the transfer of computing from cloud platforms to embedded devices. In this regard, there is a growing need to determine the optimal stack of hardware and software technologies for solving computer vision problems. Goal. Determine the optimal hardware configuration for real-time computer vision tasks based on the criteria of bandwidth, latency, accuracy, and ease of integration. Methods and materials. The paper provides a direct experimental comparison of two embedded platforms for executing the YOLO11n object detection model: a single-board Orange Pi 5 computer with a built-in Rockchip RK3588S neuroprocessor (6 TOPS, INT8) and a Raspberry Pi 4B bundle with an external Google Coral Edge TPU USB accelerator (4 TOPS, INT8). The YOLO11n model was converted from a single PyTorch source file to the target formats RKNN and TensorFlow Lite (full integer quantization) using the tool chains recommended by the manufacturers. The measurements were performed under identical pretreatment conditions. Results. The Orange Pi 5 achieved a steady frame rate of 43-54 FPS (640×640 resolution) with an end-to-end delay of 19-23 ms; accuracy mAP@0.5:0.95 with INT8 quantization, it remains at ~39%. On a Raspberry Pi 4B with Edge TPU at a resolution of 448×448, the delay was 121.5 ms (~8.2 FPS), while 45% of operations are performed on the CPU, which limits scaling. Conclusions. The Orange Pi's gain in speed reaches 6-7 times at a higher resolution, the NPU demonstrates a significant load margin, and the single-board implementation eliminates the overhead of the external interface. The totality of the results allows us to recommend Orange Pi 5 as the preferred platform for building productive edge solutions with real-time object detection.
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 perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.