知识卡片

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

建模者与编码者共享模型

理解等级:中级

软件的编码细节也是设计,不能照搬制造业的设计/装配分层。模型驱动设计允许角色分工,但建模与编码需要双向参与:

  • 参与模型的技术人员要接触代码,及时发现性能、工具和细节约束。
  • 修改代码的人要懂得用代码表达模型,并参与模型讨论、接触领域专家。

原书项目把建模者隔在实现之外,模型意图在交接中流失,平台低效的反馈数月后才传回;开发者最终绕开模型。代码细节也会改变模型,因此两类人员需用共同语言持续交换设计认识。参见 [[模型设计代码协同迭代]]。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第03章|Hands-On Modelers · 查看原书依据

      Any technical person contributing to the model must spend some time touching the code, whatever primary role he or she plays on the project. Anyone responsible for changing code must learn to express a model through the code. Every developer must be involved in some level of discussion about the model and have contact with domain experts.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第27章《原书第03章|Hands-On Modelers》(源文件:_epub-src/0321125215_ch03lev1sec4.html) - 结论依据:原书案例说明隔离建模者造成意图传递与实现反馈失效;后文明确要求技术建模者触碰代码,改代码者学会表达模型并参与模型及专家讨论,同时允许专业分工。 - 原始内容:Any technical person contributing to the model must spend some time touching the code, whatever primary role he or she plays on the project. Anyone responsible for changing code must learn to express a model through the code. Every developer must be involved in some level of discussion about the model and have contact with domain experts.