Often a Class or Interface participates in more than one significant collaboration or Design Pattern. In that case it can be useful to only show those Operations and/or attribute Properties that participate in a specific collaboration.

Counterforces include:

UML: TIP: DO NOT overuse the display of selected attributes or operations in their containers, as the approach is fragile against the addition of new attributes and operations.

UML: TIP: avoid revealing operations and attributes of Classes (and Interfaces, if possible) in more than one diagram (UNLESS you do so to illustrate an explicit collaboration with another Class with revealed Features) !

Related notes
randomness