270
edits
(New page: == Legend == '''Elements used in Class Diagrams ''' * <b>Class</b> <p> With or without <<interface>> and <<active>> stereotypes; ** an interface class can be an XPCOM interface or an ab...) |
(→Legend) |
||
Line 26: | Line 26: | ||
* <b>Activation bar</b> <p> Depicted as a rectangle on top of lifeline or another activation bar. It corresponds to one of the class' methods being on the stack.</p> | * <b>Activation bar</b> <p> Depicted as a rectangle on top of lifeline or another activation bar. It corresponds to one of the class' methods being on the stack.</p> | ||
* <b>Message call</b> <p> Depicted as a solid arrow. Corresponds a method call on the given class.</p> | * <b>Message call</b> <p> Depicted as a solid arrow. Corresponds a method call on the given class.</p> | ||
''' Other Considerations ''' | |||
* I omit nsISupports interface in diagrams unless there is a good reason to show | |||
* I don't repeat dependencies carried from interface implementations | |||
* Almost all basic types are omitted (i.e. ACString, AString etc.) | |||
* I show only significant method calls in sequence diagrams |
edits