返回主题:风险驱动的架构设计

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

知识卡片

普通读书笔记卡 · 1958.a.27.e

每次迭代都分析是否足够

理解等级:高级

迭代结束应核对部分设计是否真的满足目标,最好请有不同经验与假设的人共同检查,再判断本轮设计目的是否达到。时间不足时,用风险指导停止:优先驱动至少要被充分处理,未解决点应明确保留。画完图或做了选择不等于有证据表明质量已满足。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 设计架构 · 查看原书依据

      What are the criteria for evaluating if more design iterations are necessary? Let risk be your guide. You should at least have addressed the drivers with the highest priority. Ideally, you should have certainty that critical drivers are satisfied or, at least, that the design is “good enough” to satisfy them.

    参考来源

    - 位置:《Software Architecture in Practice, 4th Edition》第20章《设计架构》(来源项目:book-sources;源文件:extracted/Software Architecture in Practice, 4th Edition/_epub-src/ch20.html) - 结论依据:原文解释迭代结束应核对部分设计是否真的满足目标,最好请有不同经验与假设的人共同检查,再判断本轮设计目的是否达到;本章后续机制、例子与条件共同限定本卡,原书经验数字和前景不视为当前实测或现状。 - 原始内容:What are the criteria for evaluating if more design iterations are necessary? Let risk be your guide. You should at least have addressed the drivers with the highest priority. Ideally, you should have certainty that critical drivers are satisfied or, at least, that the design is “good enough” to satisfy them.