Fellow Squeakers...

I'm currently building an object model for a banking domain that has 5
parallel projects utilizing it (you know the kind...100+ people, etc.). I
have grown this model over the past year using true object-oriented design
principles ("true OO" being defined by Alan Kay as messaging,
encapsulation, and extreme late binding). Even though this is a huge I/T
group (2000+) and they require models in UML, I've used Squeak as my
modeling language. I have major parts of the model running in Squeak
complete with Traits-like pluggable behaviors and SUnit tests.

But now the challenge...they want diagrams. Futhermore, they want them in UML.

For those that have ever dove deep into UML you know it does not support
true messaging or late binding. A message in UML is a function invocation.
This sequence diagrams have enough trouble handling superclass/subclass
behaviors, and pluggable traits are almost impossible to show accurately.

Does anyone know of a graphical modeling notation that supports a truly
object-oriented model? Or is Smalltalk a new calculus, as Alan Kay
suggests, and therefore it remains textual? When I explain to people that
the true power lies between the objects, ie, the messaging, they want me to
to draw them a picture.

Thanks,
Mark Mayfield