UML Gota a Gota

Fowler's approach keeps things practical, but I wonder what made him choose to omit certain details. Was it to streamline learning or based on common usage?

The book’s examples are clear, but I’m curious if readers have applied these ideas in complex, large-scale systems and how well they translated.

Given the complexity of UML, Fowler's choice to simplify must have come from a specific insight or experience. I’d love to know what motivated this approach.