BLOW: A Systematic Approach to Behavior-Driven Development in a Layered Organization of Work-Centers

Engineering notes

Key topics: autonomous driving, end-to-end, deployment. See the paper for implementation details and experimental results.

Chinese explanation / 中文解读

中文解读待补充：本站会优先为端到端自动驾驶、BEV感知、3D目标检测、轨迹预测、路径规划、LiDAR感知等高价值论文补充中文说明。

Original abstract

Agile teams often struggle to translate business requirements into maintainable, high-quality software due to the persistent ambiguity in the roles and relationships of behavior-driven development (BDD), Acceptance Test-driven Development (ATDD), and Test-driven Development (TDD). These approaches are frequently misunderstood, inconsistently applied, and only loosely connected within a unified delivery lifecycle. This article introduces BLOW (Behavior-Driven Development in a Layered Organization of Work-Centers), a systematic approach that establishes BDD as the coordinating methodology between ATDD (business-focused) and TDD (technology-focused). BLOW structures scenario-driven development across layered domains of accountability with clearly defined roles and responsibilities, organizing delivery through nested work-centers that transform user stories into executable specifications and production code. This approach integrates two complementary collaboration practices: the Three Amigos for discovering and formulating business scenarios, and the proposed Technical Three Amigos for linking those scenarios to Technical Domain Contexts, identifying required Enablers, and deriving technical scenarios when additional architectural support is needed. The proposed operating model emphasizes observability through executable scenarios as first-class artifacts, introducing native, test-anchored metrics that support reasoning about progress, technical effort, and value delivery within scenario-driven development. An exploratory longitudinal case study, consisting of a single-sprint proof of concept followed by an 18-month production deployment, reports patterns in which technical enablement precedes business value delivery and reusable infrastructure supports sustained growth of business scenarios over time. The findings also indicate that changes in the applied operating model are associated with measurable shifts in scenario evolution and internal quality indicators. Overall, BLOW provides a governance-compatible, end-to-end approach for organizing scenario driven development and improving alignment between stakeholder intent and technical implementation in complex software systems.

Links and sources

• PDF from original source

Comments