知识卡片

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

完全合并模型先合并协作能力

理解等级:高级

把不断扩大的共享内核推进为单一上下文,除了模型重构,还会改变团队分工与共同语言。原书建议先让两队分别具备持续集成过程,再统一集成方式、轮换成员;之后把核心域逐步并入共享内核,必要时用临时翻译层衔接未合并部分。

合并核心模型可选一方模型并改造另一方,也可造更深的新模型,但要保住各用户群体的特殊需求。共享范围变大后逐渐提高集成频率。此过程不能只凭“图上已合一”宣布完成。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第115章《Transformations》(源文件:_epub-src/0321125215_ch14lev1sec14.html;单元02) - 结论依据:原文指出完全合并会涉及团队结构和语言,并列出统一流程、成员流动、核心域合并与持续集成频率演进。 - 原始内容:This is not just a matter of resolving the model differences. You are going to be changing team structures and ultimately the language people speak. [...] Be sure that all the processes needed for CONTINUOUS INTEGRATION (shared code ownership, frequent integration, and so on) are in place on each team, separately. Harmonize integration procedures on the two teams so that everyone is doing things in the same way. Start circulating team members between teams. [...] At this point, confidence should be high enough to begin merging the core domain into the SHARED KERNEL. This can take several iterations, and sometimes temporary translation layers are needed between the newly shared parts and the not-yet-shared parts. [...] You can stick with one model and modify the other to be compatible with it, or you can create a new model of the subdomain and adapt both contexts to use it. Watch out if the two models have been tailored to address distinct user needs. You may need the specialized power of both original models. [...] Be careful that it doesn't come at the cost of your ability to address the specialized needs of your users. As the SHARED KERNEL grows, increase the integration frequency to daily and finally to CONTINUOUS INTEGRATION. - 转录说明:`[...]` 标明人员准备、独立提炼、合并期风险及更深统一模型论证等实际省文;原 EPUB 强调标签边界造成的术语前空格已规范转录,列表项重复抽取处只转录一次。