"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 ..."

“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 , which assumes various different roles, such as owner, driver, and lessee.”

“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.”

“The is a general-purpose visual that is used to specify, visualize, construct, and document the artifacts of a software system. It captures decisions and understanding about systems that must be constructed. It is used to understand, design, browse, configure, maintain, and control information about such systems. It is intended for use with all development methods, lifecycle stages, application domains, and media. The modeling language is intended to unify past experience about modeling techniques and to incorporate current software best practices into a standard approach. UML includes semantic concepts, notation, and guidelines. It has static, dynamic, environmental, and organizational parts. It is intended to be supported by interactive visual modeling tools that have code generators and report writers. The UML specification does not define a standard process but is intended to be useful with an iterative development process. It is intended to support most existing object-oriented development processes.”