Use UML Class Diagrams for Skeleton Code, Not Perfect Documentation
Class diagrams rot when they try to document everything. Use them for code-bound scaffolding of domain boundaries, with explicit visibility, multiplicity and composition, and accept partial round-trip engineering.