知识卡片

普通读书笔记卡 · 2285.h.15

图形模型的开发治理

理解等级:中级

图形模型仍是开发团队负责的源码,进入版本库和CI/CD。XML差异合并可采用与代码相同的纪律:只改必要元素,避免无关重排布局。模型让业务可理解,并不转移技术设计的最终责任;团队需解释设计选择,使共同讨论和交付责任兼容。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 工作流引擎与BPMN的取舍 · 查看原书依据

      An executable process model is also source code. It is part of the solution design and thus under the responsibility of the people who build the solution (i.e., the development team). They need to have the last call on the design choices, and if there are good technical reasons to change a model they need to be empowered to do this.

    参考来源

    - 位置:《Practical Process Automation》第5章《工作流引擎与BPMN的取舍》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/ch05.xhtml) - 结论依据:原文中的定义、机制和适用条件支持上述解释,正文未将产品示例推广为所有引擎的保证。 - 原始内容:An executable process model is also source code. It is part of the solution design and thus under the responsibility of the people who build the solution (i.e., the development team). They need to have the last call on the design choices, and if there are good technical reasons to change a model they need to be empowered to do this.