On Class Visibility and Division of Responsibilities

The case study described in Listings 14.6-14.16 presents a good opportunity for a discussion of relationships among classes.

One of the important ideas discussed in the first part of the book was the idea of dividing responsibilities among functions to avoid excessive communication between the functions (and excessive coordination and cooperation among developers). This excessive communication often results from tearing apart what should belong together and from pushing responsibility up to client functions rather than down to server functions.

In this part of the book, this idea takes the form of dividing responsibilities among classes to avoid excessive communication between the classes ...

Get Core C++ A Software Engineering Approach now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.