知识卡片
遗留系统可按其提供的服务归入整体结构
原书航运示例中,遗留 Shipping Coordination 内部不符合新责任层结构,并不意味着必须放弃责任层。团队可先承认遗留系统的实际位置,判断它提供的服务落在哪几层;若通过外观访问,可让外观的每项服务尽量符合一层的职责。
图17.04保留遗留内部的未分化状态,图17.05展示新上下文内部也可按熟悉的层组织。这里是原书的建模示意,不表示遗留系统已经完成迁移。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第17章|Combining Large-Scale Structures and B OUNDED C ONTEXTS · 查看原书依据
Suppose you want to adopt RESPONSIBILITY LAYERS, but you have a legacy system whose organization is inconsistent with your desired large-scale structure. Do you have to give up your LAYERS? No, but you have to acknowledge the actual place the legacy has within the structure. In fact, it may help to characterize the legacy. The SERVICES the legacy provides may in fact be confined to only a few LAYERS. To be able to say that the legacy system fits within particular RESPONSIBILITY LAYERS concisely describes a key aspect of its scope and role.