知识卡片

普通读书笔记卡 · 1971.o.1.b.1.b.1.a

业务规则冲突需澄清

理解等级:中级

领域专家处理业务时,常凭经验在多条规则间补空缺、化解矛盾;软件不能照搬这份未说出的常识。建模讨论应把规则逐条说清,并对冲突作出明确取舍:

  • 补全条件不明的规则,确认何时适用。
  • 协调相互矛盾的规则,明确优先关系。
  • 暂不处理的例外说明范围,避免代码暗中作决定。

这些取舍需要领域专家与开发者共同完成,不能仅从实体名称或字段推出来。参见 [[反馈与抽象缺一不可]]。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第01章|Knowledge-Rich Design · 查看原书依据

      Domain experts are usually not aware of how complex their mental processes are as, in the course of their work, they navigate all these rules, reconcile contradictions, and fill in gaps with common sense. Software can't do this. It is through knowledge crunching in close collaboration with software experts that the rules are clarified, fleshed out, reconciled, or placed out of scope.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第14章《原书第01章|Knowledge-Rich Design》(源文件:_epub-src/0321125215_ch01lev1sec4.html) - 结论依据:原文指出专家在工作中会凭常识处理规则矛盾和缺口,但软件做不到;因此要求在与软件人员密切协作的知识消化中澄清、补全、调和规则或划出范围。列表中的“优先关系”是对调和冲突的一种说明,不代表原书给了固定优先级算法。 - 原始内容:Domain experts are usually not aware of how complex their mental processes are as, in the course of their work, they navigate all these rules, reconcile contradictions, and fill in gaps with common sense. Software can't do this. It is through knowledge crunching in close collaboration with software experts that the rules are clarified, fleshed out, reconciled, or placed out of scope.