知识卡片
业务目标可直接约束架构
业务目标有三种关系:转成质量要求、直接影响架构、或完全不涉及架构。竞争差异可能要求更低延迟;组织现有专长或岗位安排也可能直接限定采用数据库,而不出现在外部需求里;降低办公能耗则可能与软件无关。理解目标让架构师能有根据地协商苛刻要求,也避免把每个经营口号都硬转成系统质量。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 架构显著需求 · 查看原书依据
There are three possible relationships between business goals and an architecture: 1. Business goals often lead to quality attribute requirements. Every quality attribute requirement—such as user-visible response time or platform flexibility or iron-clad security or any of a dozen other needs—originates from some higher purpose that can be described in terms of added value.
参考来源
- 位置:《Software Architecture in Practice, 4th Edition》第19章《架构显著需求》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch19.html)
- 结论依据:原文解释业务目标有三种关系:转成质量要求、直接影响架构、或完全不涉及架构;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。
- 原始内容:There are three possible relationships between business goals and an architecture: 1. Business goals often lead to quality attribute requirements. Every quality attribute requirement—such as user-visible response time or platform flexibility or iron-clad security or any of a dozen other needs—originates from some higher purpose that can be described in terms of added value.