返回主题:对象与关系的结构映射

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

知识卡片

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

建模需与实现相连

理解等级:高级

领域分析需要持续改变可运行的设计,否则模型讨论再认真,也未必能改善软件。原书第三个项目拥有工具和业务知识,却把建模人员与实现人员分开;设计没有体现深入分析,反复迭代也未改善代码。该项目还存在业务对象设计不严谨、开发者技能不均等因素,因此不能把失利全归因于角色划分。应用推断:检查模型的新认识是否进入代码,并经运行与修改反馈继续修正模型。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Contrasting Three Projects · 查看原书依据

      Repeated iteration produced no improvement in the code, due to uneven skill levels among developers, who had no awareness of the informal body of style and technique for creating model-based objects that also function as practical, running software.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第03章《Contrasting Three Projects》(源文件:_epub-src/0321125215_fm01lev1sec1.html) - 结论依据:第三个项目虽重视建模,但原文明确指出角色分离使设计没有反映领域分析,并补充业务对象设计和技能水平问题;卡片据此保留多重成因,末句是基于案例的工程检查建议。 - 原始内容:This upward trajectory was directly attributable to an incisive domain model, repeatedly refined and expressed in code. As the team gained new insight into the domain, the model deepened. [...] The team had good tools and a good understanding of the business, and it gave careful attention to modeling. But a poorly chosen separation of developer roles disconnected modeling from implementation, so that the design did not reflect the deep analysis that was going on. In any case, the design of detailed business objects was not rigorous enough to support combining them in elaborate applications. Repeated iteration produced no improvement in the code, due to uneven skill levels among developers, who had no awareness of the informal body of style and technique for creating model-based objects that also function as practical, running software. As months rolled by, development work became mired in complexity and the team lost its cohesive vision of the system. After years of effort, the project did produce modest, useful software, but the team had given up its early ambitions along with the model focus.