Unwanted Modeling Language

UnwantedModelingLanguage is how MartinFowler is characterising UnifiedModelingLanguage (UML). See http://martinfowler.com/bliki/UnwantedModelingLanguage.html

UML was supposed to have been created for ObjectOrientedAnalysis? and ObjectOrientedDesign, but:

  1. UseCases are FunctionalSpecifications? in disguise. UserStories are the same thing. No, <<using>>, <<including>> and <<extending>> UseCases doesn't cut it.
  2. ClassDiagrams relate classes because they are included inside another, they know each other or they extend another. Those relationships are not very well represented by cardinality, because it is not the same having a dictionary, a set or a list of objects, but all of them are represented using the same cardinality. ClassHierarchies? are not well represented in a diagram in which cardinalities are also represented.
  3. The TemplateMethod DesignPattern is not directly representable in ClassDiagrams, or any other UML diagram.
  4. PolyMorphism can't be represented in ClassDiagrams or SequenceDiagrams.
  5. SequenceDiagrams violate encapsulation.
  6. SequenceDiagrams are PolyMorphism oblivious.
  7. SequenceDiagrams do not stay at one AbstractionLevel, so they are useless for modeling abstractions.
  8. SequenceDiagrams can't model complex behavior.

UML is the antithesis of ObjectOrientation. On the other hand, CrcCards are a useful abstraction for modeling ObjectOriented software.
"UMLís segregation of the system model into multiple views is a major source of difficulty in capturing the system as a whole, understanding its parts, and being able to coherently follow the functionality it performs." See UmlControversies.

EditText of this page (last edited January 18, 2005) or FindPage with title or text search