Design Patterns Java Workbook - Final Part

Couple of Days back i started reading Design Patterns Java™ Workbook By Steven John Metsker.

Nice book written by Steven John Metsker.

I wanted to share few quotations found the book from the remaining chapters.

This chapter talks about UML

1) In UML we can show a class name or a method name in italics to indicate that the class or method is abstract.

2) Use a closed, hollow arrowhead to point to a class's superclass.

3) Use a line between classes to indicate that instances of the classes are connected. Most commonly, a line on a class diagram means that one class has an instance variable that refers to the other class.

4) An open arrowhead indicates navigability. Use it to emphasize that one class has a reference to another and that the pointed-to class does not have a back reference.

5) A multiplicity indicator, such as 0..1, indicates how many connections may appear between objects. Use an asterisk (*) to indicate that zero or more instances of an object of a class may be connected to objects of an associated class.

6) To show that a method may throw an exception, use a dashed arrow pointing from the method to the exception class. Label the arrow with a «throws» stereotype.