Summary

Review

Some key points in this chapter are listed below:

• Analyzing problem requirements in an object-oriented context
• How to draw Unified Modeling Language (UML) diagrams to communicate how the system works
• Discussing object-oriented systems using the correct terminology and jargon
• Understanding the distinction between class, object, attribute, and behavior
• Some OOD techniques are used more than others. In our case study example, we focused on a few:
  • Encapsulating features into classes
  • Inheritance to extend a class with new features
  • Composition to build a class from component objects

Synopsis

In this chapter, we took a whirlwind tour through the terminology of the object-oriented paradigm, focusing on object-oriented design. We learned that we can separate different objects into a taxonomy of different classes and describe the attributes and behaviors of those objects via the class interface. Abstraction, encapsulation, and information hiding are highly related concepts. There are many different kinds of relationships between objects, including association, composition, and inheritance. UML syntax can be useful for fun and communication.