知识卡片

普通读书笔记卡 · 1762.f.3

痛点与枢纽事件

理解等级:高级

时间线形成后,把瓶颈、人工步骤、缺文档或未知业务知识标为粉色菱形痛点,后续随时补记。再找表示业务阶段或语境改变的枢纽事件,用竖线分隔前后阶段。枢纽是限界上下文的候选线索,不能只凭出现一个显著事件就认定技术边界。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 事件风暴 · 查看原书依据

      Once you have the events organized in a timeline, use this broad view to identify points in the process that require attention. These can be bottlenecks, manual steps that require automation, missing documentation, or missing domain knowledge. It’s important to make these inefficiencies explicit so that it will be easy to return to them as

    参考来源

    - 位置:《Learning Domain-Driven Design》第12章《事件风暴》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Learning Domain-Driven Design/_epub-src/OEBPS/ch12.html) - 结论依据:原文步骤3至4分别引入痛点与枢纽事件,并将枢纽称为潜在上下文边界指示。 - 原始内容:Once you have the events organized in a timeline, use this broad view to identify points in the process that require attention. These can be bottlenecks, manual steps that require automation, missing documentation, or missing domain knowledge. It’s important to make these inefficiencies explicit so that it will be easy to return to them as