I wouldn't associate
KnowledgeLevel with
Reflection as you have. As you
know,
KnowledgeLevel is that fine pattern from Martin's first book while
Reflection can mean many things to the reader.
JoshuaKerievsky
You are probably right that it shouldn't be "AKA". Yet they are very
closely related. When most of us read the
POSA book, we are thinking
about technical architecture, languages, and so forth. However, if
you take a look at the
POSA discussion of
Reflection, and think about
the context of domain design, you'll see what I mean. They didn't
even write it in a way that was specifically technical. Their
examples are technical, and the context of the book as a whole is,
too, but
Reflection is more general than that.
What I may do is describe it as an application of
Reflection to non-
technical domains. I do want to draw on
POSA. The list of
consequences, and really most of the discussion there, is relevant
and well organized.
EricEvans
KnowledgeLevelAkaReflection is mentioned on: ThreadView
