知识卡片

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

卫星仿真项目用通信层次找回整体叙事

理解等级:高级

原书的实际卫星通信仿真项目已有许多小而内聚的模块,却难判断功能该放哪里、模块如何连成整体。开发者先能讲出数据经通信基础设施传输、保证路由与完整性的故事,却在模型中看不到其整体结构。

团队遂用通信系统的概念层次组织设计:底层表示节点间比特传输,上层处理数据包路由等关注点。随后重定义跨层模块及对象职责,并在实践中反过来修正层次定义。原书报告的结果是功能位置更易判断、独立工作决策更一致;没有提供性能或交付速度的量化指标。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Chapter Sixteen. Large-Scale Structure · 查看原书依据

      After the developers mulled over the problem for a week or two, the idea began to jell. They would impose a structure on the design. The entire simulator would be viewed as a series of layers related to aspects of the communications system. The bottom layer would represent the physical infrastructure, the basic ability to transmit bits from one node to another. Then there would be a packet-routing layer that brought together the concerns of how a particular data stream would be directed. Other layers would identify other conceptual levels of the problem. These layers would outline their story of the system. They set out to refactor the code to conform to the new structure. MODULES had to be redefined so as not to span layers. In some cases, object responsibilities were refactored so that each object would clearly belong to one layer.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第127章《Chapter Sixteen. Large-Scale Structure》(源文件:_epub-src/0321125215_ch16.html;单元01–02) - 结论依据:原文叙述卫星仿真项目从模块过多到形成通信层次,再经模块与对象重构让结构、模型共同演进。 - 原始内容:After the developers mulled over the problem for a week or two, the idea began to jell. They would impose a structure on the design. The entire simulator would be viewed as a series of layers related to aspects of the communications system. The bottom layer would represent the physical infrastructure, the basic ability to transmit bits from one node to another. Then there would be a packet-routing layer that brought together the concerns of how a particular data stream would be directed. Other layers would identify other conceptual levels of the problem. These layers would outline their story of the system. They set out to refactor the code to conform to the new structure. MODULES had to be redefined so as not to span layers. In some cases, object responsibilities were refactored so that each object would clearly belong to one layer. - 转录说明:原书两句相邻,未省去正文;`M ODULES` 是 EPUB 首字母与强调标签边界造成的断词,此处按完整术语转录。原书仅报告设计决策更易协调,未提供量化绩效数据。