If I did that, I might add to its pre-existing responsibilities in an inconsistent way. Showing Model Responses Typical object collaboration diagrams look either deceptively simple or overly complex. They don't reflect the thought or effort that went into producing them. In order to understand their significance, it is necessary to know what are key objects and what level of detail the designer intended to model. To find this information, either we need to look at supporting documents such as emerging class designs, prior conversations, and other supporting evidence.
Designers can also help by walking others through their design.
Diagrams alone can't show the significance of key design decisions. This is hard to find in class specifications, too. That's why designers need to tell us what they thought important. For example, our CustomerDatabase object isn't a simple minded database interfacer. It doesn't just humbly reconstitute customer objects from stored information.