知识卡片
稳定契约让可运行原型打通并行开发
原书假设装箱服务案例中,应用团队和优化算法团队若互等完整实现,集成与用户反馈都会推迟。先以同一 Packer 接口和安全断言提供可运行的简单原型,两队便能并行:应用团队接通外部系统,专家试用后给算法团队反馈,双方及早发现契约变更。成熟实现随后替换原型;这一可替换性取决于接口和断言被持续维护,不保证复杂实现上线“毫无集成问题”。参见[[可运行原型须声明算法与回滚局限]]。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第09章|Clearing Development Logjams with Working Prototypes · 查看原书依据
One team has to wait for working code from another in order to move forward. Both teams have to wait for full integration to exercise their components or get feedback from users. This kind of congestion can often be eased by a MODEL-DRIVEN prototype of a key component, even if it does not satisfy all requirements. When implementation is decoupled from interface, then having any working implementation at all allows flexibility for project work to go in parallel.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第71章《Clearing Development Logjams with Working Prototypes》(源文件:_epub-src/0321125215_ch09lev1sec2_split_001.html)
- 结论依据:原书以装箱服务原型说明接口与实现分离后,应用、算法与专家反馈可以并行,后续按同一接口替换实现。
- 原始内容:One team has to wait for working code from another in order to move forward. Both teams have to wait for full integration to exercise their components or get feedback from users. This kind of congestion can often be eased by a MODEL-DRIVEN prototype of a key component, even if it does not satisfy all requirements. When implementation is decoupled from interface, then having any working implementation at all allows flexibility for project work to go in parallel.