返回主题:软件质量属性的取舍

此卡片不在当前主题的阅读序列中,可返回主题继续阅读。

知识卡片

普通读书笔记卡 · 3352.c

架构权衡需反复评估

理解等级:高级

架构选择同时受多项变量约束,变量的取值又随场景变化;某方案解决一个问题,也可能增加另一项代价。因而一次确定团队默认做法,不能代替后续场景中的权衡分析。

原书举只用编舞式分布式工作流作统一默认值的尝试:有些场景适用,有些场景会失败。遇到新场景应重新比较收益与代价,并与[[架构假设需要持续重估]]相互校验。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Introduction · 查看原书依据

      Every decision a software architect makes must account for a large number of variables that take on different values depending on the circumstances. Trade-offs are the essence of software architecture decisions. If you think you’ve discovered something that isn’t a trade-off, more likely you just haven’t identified the trade-off…yet.

    参考来源

    - 位置:《Fundamentals of Software Architecture》第02章《Introduction》(源文件:`OEBPS/ch01.html`,Laws of Software Architecture) - 结论依据:第一定律及两条推论指出架构决策普遍含权衡,且不能只评估一次;编舞式工作流的默认方案是原书举例,结论不得扩展为“编舞总是错误”。 - 原始内容:Every decision a software architect makes must account for a large number of variables that take on different values depending on the circumstances. Trade-offs are the essence of software architecture decisions. If you think you’ve discovered something that isn’t a trade-off, more likely you just haven’t identified the trade-off…yet.