Navigating C++ and Object-Oriented Design

1.5. Putting It All Together

This section uses many topics from the chapter.

The Modeling Process

Suppose we are modeling a library checkout system. Objects (possible classes) include LibraryBooks, LibraryMembers, and a BookCatalog. Classes keep track of data. For example, a LibraryBook tracks its title, author, and ISBN number. Class data members have a type and value and are maintained by the class itself. The LibraryBook is responsible for maintaining its own title. It stores a title attribute (probably as a String) and has a function which returns its title when invoked.

Once we've identified candidate classes, we need to identify behaviors within the problem domain. In our Library System, possible behaviors include checking out a LibraryBook, ...