← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 2285.m.12

联合模型避免翻译损耗

理解等级:高级

操作层应共享一个内容完整的逻辑模型,而不是业务模型交给IT翻译成另一个技术模型。不同工具、仓库和环境可以有物理副本与版本,但含义与内容不应经过转换。高层战略图仅像电影预告,不能当作真实运行模型。副本合并需要约定,可以指定开发仓库为权威模型,切勿过早陷入自动往返同步争论。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 业务与IT协作 · 查看原书依据

      On the operational level it’s important to have a single, comprehensive model. Of course, this model could have different versions, and may even live in different environments. For example, the business analyst might work on MightyProcess in their collaborative BPMN modeler, while the developer works on mighty_process.bpmn in their Git repository and the operations person

    参考来源

    - 位置:《Practical Process Automation》第10章《业务与IT协作》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch10.xhtml) - 结论依据:原文给出的机制、实例与边界支持本卡的解释。 - 原始内容:On the operational level it’s important to have a single, comprehensive model. Of course, this model could have different versions, and may even live in different environments. For example, the business analyst might work on MightyProcess in their collaborative BPMN modeler, while the developer works on mighty_process.bpmn in their Git repository and the operations person