What to consider and challenge (what I know): names
Str#70. "Embedded Value in an Attribute Name" Strategy
- Attribute name includes the name of another object?
- Add that object to your model. Let that object know its
own attribute(s).
- Note: an object connection, expressed in text rather than
with graphics, names another object (as it should).
Str#71. "Type Attribute" Strategy
- Attribute expressing type, kind, or category?
- If it's needed solely for display or report, that's
fine.
- If it's a redundant expression of what gen-spec already
portrays, get rid of it (it's not needed).
- If it's needed to decide what to do in a service, use
gen-spec so that each object can just do its thing--without
needing to determine "what kind am I?" before taking
appropriate action. Why: take advantage of an opportunity to
apply polymorphism--and, as a result, increase resiliency to
change.
Establishing responsibilities
/ what I know
Strategies for building object
models