That's all for this article. In the next article on the topic, we'll examine the two Is of UML class diagrams: interfaces and inheritance. I will leave you with a quote from Jill Nicola, Mark Mayfield, and Mike Abney's new book, Streamlined Object Modeling2:
"For understanding a problem and modeling it in a form that supports software development, there is no better technique than object modeling. Object modeling, when done properly, extracts client knowledge and represents it in a format that is recognizable to the client and profoundly informative to the developer"