Diagram Stereotypes

[Paolo F Cantoni]

I'm starting to Stereotype my diagrams.  For example, I have a diagram that shows how all the classes in a namespace interact.  I've stereotyped this as «namespace».  
For diagrams with «namespace» stereotype, the following rules apply:

• Show ONLY classes in the namespace
  
• Classes expose public features ONLY!
  
  Another is «classDefinition» (typically created when you make the class "composite"):
  
• Central class has "everything" showing.
  
• Show all elements within one level of relation to the central class, these show no elements, unless useful for this class.
  
  The idea is that an automaton would investigate the stereotype and apply the defined rules.  Initially, the automaton would be ME!  (No jokes please!)
  
  Do you have a favourite diagram layout (or algorithm) you use?  Please describe it in your reply and assign a stereotype.
  
  Cheerz,
  Paolo

[thomaskilian]

I'd just populate the diagrams according the rules, call AutoLayout and do the rest manually.

[Paolo F Cantoni]

I'd just populate the diagrams according the rules, call AutoLayout and do the rest manually.

Sorry, Thomas, I didn't explain myself well enough.  I might have a number of Class (Structure) diagrams - each one show some specific aspect of a class (or classes).  They are all the same type of diagram, bu they have different content (almost behaviour) - hence the stereotype.

Typically for each class I have a number of standard diagrams:
classDefinition
classSubtypes
classPolicies

(I won't enumerate the different rules that apply to these three).

I'm after the "extra" rules people use within the confines of the diagram type (that I think) you were meaning.

Cheerz,
Paolo