知识卡片
非技术选择也影响架构
产品方向、人员分配及团队边界会改变系统承担的能力和组件归属。它们不必硬归为技术选择,但应按架构影响对待,邀请受影响者和相关专家,明确约束。否则技术团队可能在事后才发现结构已经被业务安排决定。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- To Practice Architecture Is to Decide · 查看原书依据
To keep this chapter focused, I’ve intentionally ignored two sources of influence on architectural decisions: Product management/the business Whoever decides on the alignment of teams to work It is unarguable that a product decision can have a direct impact on software architecture. The same can be said for a staffing or team-alignment decision. To
参考来源
- 位置:《Facilitating Software Architecture》第02章《To Practice Architecture Is to Decide》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch02.html)
- 结论依据:原文承认产品管理与团队对齐对架构的直接影响,主张as if architectural地使用同样的协作方法。
- 原始内容:To keep this chapter focused, I’ve intentionally ignored two sources of influence on architectural decisions: Product management/the business Whoever decides on the alignment of teams to work It is unarguable that a product decision can have a direct impact on software architecture. The same can be said for a staffing or team-alignment decision. To