← 返回刚才阅读的位置

知识卡片

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

航运教学例把运营与运力分为两层

理解等级:高级

原书的航运教学例把“正在做什么”与“能做什么”分开:Operations 包含 Cargo、Route Specification、Itinerary 等当前交付活动;Capability 包含独立存在的运输航段及资源,支持运营但不以某票货物为前提。

Customer 的归属要看业务:例中假设公司培养长期客户关系,故放在较稳定的能力/潜力层;若是一次性个人包裹服务,判断可能不同。图16.5–16.6还以 Cargo Repository 查询代替跨层反向关联。以上是原书教学建模选择,不是实际航运系统的上线证据。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第130章《Responsibility Layers》(源文件:_epub-src/0321125215_ch16lev1sec3.html;单元02–03) - 结论依据:原文说明Operations与Capability的概念依赖,并根据假设企业的长期客户关系决定Customer归属,图16.5–16.6展示关系调整。 - 原始内容:A trickier decision is where to place Customer. In some businesses, customers tend to be transient: they're interesting while a package is being delivered and then mostly forgotten until next time. This quality would make customers only an operational concern for a parcel delivery service aimed at individual consumers. But our hypothetical shipping company tends to cultivate long-term relationships with customers, and most work comes from repeat business. Given these intentions of the business users, the Customer belongs in the potential layer. As you can see, this was not a technical decision. It was an attempt to capture and communicate knowledge of the domain. [...] Because the association between Cargo and Customer can be traversed in only one direction, the Cargo REPOSITORY will need a query that finds all Cargoes for a particular Customer. - 转录说明:原 EPUB 强调标签边界产生的术语前空格已规范转录;`[...]` 标明段落间省略。