知识卡片

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

航运项目待需求清楚后才实现时区

理解等级:高级

原书的实际航运调度项目必须跨国协调当地时间。团队先用已有时间类和占位数据推进核心域;发现类库不足、需求已更清楚后,才寻找现成方案。没有可用方案,于是由临时合同程序员参考 BSD Unix 公有领域实现,移植时区数据库逻辑。问题比预想难,但代码最终集成,产品交付。

这不是“时区不重要”的案例:它是必要的支撑功能,只是应在需求具体、核心模型已有进展后投入,并让适合的人员处理。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第119章《Generic Subdomains》(源文件:_epub-src/0321125215_ch15lev1sec3.html;单元03) - 结论依据:原文叙述航运项目确实需要复杂转换、先推进核心模型、后寻找并改造 BSD Unix 方案,最终集成和交付。 - 原始内容:Having clearly established their need for this functionality, the team proceeded with development of the CORE DOMAIN and some early iterations of the application using the available time classes and some dummy data. [...] With their requirements by now even clearer, they searched for an off-theshelf solution, but found none. They had no option but to build it themselves. [...] But the task did not require any special knowledge of shipping and would not cultivate that knowledge, so they chose a programmer who was on the project on a temporary contract. This programmer did not start from scratch. He researched several existing implementations of time zones, most of which did not meet requirements, and decided to adapt the public-domain solution from BSD Unix, which had an elaborate database and an implementation in C. He reverse-engineered the logic and wrote an import routine for the database. The problem turned out to be even harder than expected (involving, for example, the import of databases of special cases), but the code got written and integrated with the CORE and the product was delivered. - 转录说明:两处 `[...]` 分别标明需求变清楚的中间说明,以及选用临时合同程序员前的工程精度与人选句;保留原 EPUB 的 `off-theshelf` 拼写。