Applying Agile Methodologies to Embedded Software Development: A Case Study
Bibliographic record
Abstract
For decades, the embedded systems industry has been dominated by rigorous, sequential development models, primarily the Waterfall and V-Models, which prioritize front-end requirement stability over iterative flexibility. However, the exponential increase in firmware complexity and the relentless pressure for shorter time-to-market have necessitated a paradigm shift toward iterative development. This article presents a comprehensive case study on the application of Agile methodologies—specifically Scrum and Extreme Programming (XP)—within a high-stakes embedded software environment. We analyze the unique friction points created by integrating Agile with hardware-dependent constraints, such as the unavailability of physical prototypes, the non-malleability of hardware after tape-out, and the necessity for cross-functional hardware-software synchronization. Our findings demonstrate that while Agile significantly improves software quality, team morale, and transparency, it requires specific technical adaptations in "Continuous Integration" and "Automated Testing" to accommodate hardware-in-the-loop (HIL) environments. Furthermore, the study explores how Agile can be reconciled with stringent safety standards, proposing a framework for "Agile Documentation" that satisfies regulatory audits without stifling velocity.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.008 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".