StateModelRev05f.ppt - RJL rev. 050918  3
StateModel Design – 3
Revert to Sparse Diagram Style
(1) Move full class name to a separate table or list of <TTabbrev, Entity Name> pairs (but keep it on the diagram).
(2) Remove all attributes (primary and foreign keys and non-key attributes) to a separate schema.sch text file.
(3) Hyperlink from diagram nodes to  #anchor points in the schema.sch file. (Here, we will link to later .ppt slides)
(4) Replace M:N relationship links with associative entities, for which UML. (Multiplicity almost always defaults to 1..1 to 0..* )
(5): External class and data member definitions would allow multi-line text in the ‘description’ field of StateModel.{sch,htm}. (Editing these into the schema.sch file is easy with an ASCII data format.)
The above diagram is far too cluttered to see the ‘big picture’ of inter-class relationship context, let alone add new nodes and links; this context is the main reason for graphics in the first place, and practically  demands a less cluttered diagram style.  Therefore: