3 quotes
If two classes express the same information, the most descriptive name should be kept. For example, although customer might describe a person taking an airline flight, Passenger is more descriptive.
Object-oriented modeling and design (1990)
Constructs extraneous to the real world should be eliminated from the analysis model. They may be needed later during design, but not now. For example, CPU subroutine, process, algorithm, and interrupt are implementation constructs for most applications [and should be excluded from the analysis model]...
Object-oriented modeling and design (1990)
The name of a class should reflect its intrinsic nature and not a role that it plays in an association. For example, Owner would be a poor name for a class in a car manufacturer's database. What if a list of drivers is added later? What about persons who lease cars? The proper class is Person (or possibly Customer), which assumes various different roles, such as owner, driver, and lessee.
Object-oriented modeling and design (1990)