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

知识卡片

普通读书笔记卡 · 1931.d

以约束验证替代技术传教

理解等级:高级

技术成功经验通常有情境边界。架构师应要求倡导者同时列出收益与代价,并用当前业务场景验证,避免被迫替另一阵营辩护。仓库策略案例中,团队尝试单仓库,同时用适应度函数防止项目因位置相邻而意外形成依赖。这样把争论变为可观察约束:允许实验,也明确什么负面结果不能发生;经验提供假设,测量决定其在本环境是否成立。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 构建自己的权衡分析 · 查看原书依据

      For example, one of the damaging anti-patterns they wanted to avoid was accidental coupling between two projects because of repository proximity, so the architect and team built a series of fitness functions to ensure that, while technically possible to create a coupling point, the fitness function prevented it.

    参考来源

    - 位置:《Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)》第15章《Chapter 15. Build Your Own Trade-Off Analysis》(来源项目:book-sources;源文件:extracted/Software Architecture The Hard Parts Modern Trade-Off Analyses for Distributed Architectures (Neal Ford, Mark Richards, Pramod Sadalage etc.)/_epub-src/OEBPS/ch15.xhtml) - 结论依据:原文的定义、示例或失败路径支持以下归纳:技术成功经验通常有情境边界。 其他条件结合本章同小节说明;不将模式目标当成已有运行保证。 - 原始内容:For example, one of the damaging anti-patterns they wanted to avoid was accidental coupling between two projects because of repository proximity, so the architect and team built a series of fitness functions to ensure that, while technically possible to create a coupling point, the fitness function prevented it.