知识卡片

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

知识级与架构反射对应但双向依赖

理解等级:高级

原书将领域知识级/操作级类比架构反射中的元级/基础级:操作级负责日常行为,知识级保存决定这些行为如何成立的类型和规则。两级之间可能双向依赖,因此作者特意不用“知识层”一词。

知识级由普通领域对象实现。Java 等语言的反射机制描述的是类和方法,并不能直接充当员工类型、退休政策等领域规则。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第16章|Knowledge Level · 查看原书依据

      This is done by splitting the software into a "base level," which carries the operational responsibility for the application, and a "meta level," which represents knowledge of the structure and behavior of the software.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第131章《Knowledge Level》(源文件:_epub-src/0321125215_ch16lev1sec4.html) - 结论依据:原文明确映射两组术语,解释双向依赖,并排除将编程语言反射元对象直接用作领域知识级。 - 原始内容:K NOWLEDGE LEVEL is an application to the domain layer of the REFLECTION pattern, used in many software architectures and technical infrastructures and described well in Buschmann et al. 1996 . R EFLECTION accommodates changing needs by making the software "self-aware," and making selected aspects of its structure and behavior accessible for adaptation and change. This is done by splitting the software into a "base level," which carries the operational responsibility for the application, and a "meta level," which represents knowledge of the structure and behavior of the software. [...] Significantly, the pattern is not called a knowledge "layer." As much as it resembles layering, REFLECTION involves mutual dependencies running in both directions. [...] Just to be clear, the reflection tools of the programming language are not for use in implementing the KNOWLEDGE LEVEL of a domain model. Those meta-objects describe the structure and behavior of the language constructs themselves. Instead, the KNOWLEDGE LEVEL must be built of ordinary objects. - 转录说明:原 EPUB 以普通首字母加后续强调标签拼出 `KNOWLEDGE` 与 `REFLECTION`;上行纯文本抽取后的 `K NOWLEDGE`、`R EFLECTION` 是标签边界。`[...]` 标出非连续段落的省略。