3 ms·
I agree, there's obviously a trade-off involved. I think the real issue is trying to identify RW-B's "Roles, responsibilities and Collaborations" in a design. T
by raganwald 18y ago
I agree, there's obviously a trade-off involved. I think the real issue is trying to identify RW-B's "Roles, responsibilities and Collaborations" in a design. There's (a) a piece of knowledge that a customer is involved, (b) a piece of knowledge that an SSN is involved, and (c) a piece of knowledge that an SSN can be extracted from a customer.
I suspect the issue here is making good decisions about which entities/modules/functions/objects/thingummies should know a, which should know b, and which should know c.