知识卡片

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

领域驱动项目的共同特征是持续把领域理解写进软件

理解等级:高级

作者认为项目不必采用书中每项技术,但应持续把目标领域的理解融入软件。团队会打磨通用语言,不满足于当前模型,随着学习继续提炼,并认真对待能把模型表达成生产软件的设计能力。

这种态度允许遇到障碍后调整设计,同时维持领域理解这一目标。由“不必采用每项技术”可推:具体模式和组织形式应按项目条件选择;这是应用判断,不是作者给出的统一选型规则。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Epilogues · 查看原书依据

      No project will ever employ every technique in this book. Even so, any project committed to domain-driven design will be recognizable in a few ways. The defining characteristic is a priority on understanding the target domain and incorporating that understanding into the software. Everything else flows from that premise. Team members are conscious of the use of language on the project and cultivate its refinement. They are hard to satisfy with the quality of the domain model, because they keep learning more about the domain. They see continuous refinement as an opportunity and an ill-fitting model as a risk. They take design skill seriously because it isn't easy to develop production-quality software that clearly reflects the domain model. They stumble over obstacles, but they hold on to their principles as they pick themselves up and continue forward.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第141章《Epilogues》(源文件:_epub-src/0321125215_art01lev1sec1.html) - 结论依据:原文结尾列出领域优先、语言打磨、持续提炼和设计能力等可辨认特征。 - 原始内容:No project will ever employ every technique in this book. Even so, any project committed to domain-driven design will be recognizable in a few ways. The defining characteristic is a priority on understanding the target domain and incorporating that understanding into the software. Everything else flows from that premise. Team members are conscious of the use of language on the project and cultivate its refinement. They are hard to satisfy with the quality of the domain model, because they keep learning more about the domain. They see continuous refinement as an opportunity and an ill-fitting model as a risk. They take design skill seriously because it isn't easy to develop production-quality software that clearly reflects the domain model. They stumble over obstacles, but they hold on to their principles as they pick themselves up and continue forward.