知识卡片
异步广泛收集真实生态
雷达扫描宜沿产品从构想到退役全生命周期取材,涵盖开发、运维、测试、安全与产品,而非只按部门边界。先收当前、未来、遗留及有意义的版本差异,保留不同团队的独立描述和来源。此时需要知道,不急于一致;原始分歧本身是经验。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Using a Technology Radar · 查看原书依据
To run a sweep, you first need to decide how much of your software engineering organization your sweep will cover. It works best to set this scope around one or more (or all) products along their entire lifecycle. Sweeps bounded by departmental, organizational, or role lines tend to miss important blips, such as testing
参考来源
- 位置:《Facilitating Software Architecture》第11章《Using a Technology Radar》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch11.html)
- 结论依据:原文明确product lifecycle边界、representativeness、source字段及description为最有价值输入。
- 原始内容:To run a sweep, you first need to decide how much of your software engineering organization your sweep will cover. It works best to set this scope around one or more (or all) products along their entire lifecycle. Sweeps bounded by departmental, organizational, or role lines tend to miss important blips, such as testing