知识卡片
架构职责的三个范围
团队内架构关注本团队能构建、运行的设计;跨团队架构关注多个产品或程序中系统之间的协作;企业架构再把范围扩展到整个组织及采购系统。职位名称不能可靠说明范围。讨论谁应提供咨询时,应先说明涉及哪些团队和责任,再把本地职称映射进去。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Preface · 查看原书依据
First come those practicing architecture within (and for) multiple teams. They are commonly known as aligned4 software or solution architects if they work with multiple teams and team architects or even tech leads if they are permanent members of a single team. Both possibly even have the opportunity to write some code that
参考来源
- 位置:《Facilitating Software Architecture》第pf章《Preface》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/preface01.html)
- 结论依据:原文按within、across及整个组织划分职责,并说明标题各异,应按remit和accountability翻译到本组织。
- 原始内容:First come those practicing architecture within (and for) multiple teams. They are commonly known as aligned4 software or solution architects if they work with multiple teams and team architects or even tech leads if they are permanent members of a single team. Both possibly even have the opportunity to write some code that