知识卡片
共同抽象促成需求协商
架构提供各方能理解的共同抽象:用户问响应和可用,出资方问预算期限,管理者问团队独立协作,架构师统筹取舍。运行图也可能让用户发现此前未厘清的行为问题。评审应允许这种需求—架构对话,而不把所有用户问题都视为越界;由此澄清需求和不合理预期。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 软件架构为何重要 · 查看原书依据
Architecture provides a common language in which different concerns can be expressed, negotiated, and resolved at a level that is intellectually manageable even for large, complex systems. Without such a language, it is difficult to understand large systems sufficiently to make the early decisions that influence both quality and usefulness.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第2章《软件架构为何重要》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch02.html)
- 结论依据:原文的定义、机制或比较支持“架构提供各方能理解的共同抽象:用户问响应和可用,出资方问预算期限,管理者问团队独立协作,架构师统筹取舍”;正文保留其条件与取舍。
- 原始内容:Architecture provides a common language in which different concerns can be expressed, negotiated, and resolved at a level that is intellectually manageable even for large, complex systems. Without such a language, it is difficult to understand large systems sufficiently to make the early decisions that influence both quality and usefulness.