My things

After looking in detail at the Guest model, the next logical object in my C++ event-planning reconstruction is the Group . At first, a Group appears simpler than a Guest. And in terms of stored state, it genuinely is. The reconstructed Group contains only three pieces of group-specific state: a collection of Guests, a Group name and a separate object containing shared contact information. But the simplicity of those fields is deceptive. The Group sits at an important junction in the application. It connects individual Guests into meaningful units, provides shared contact information, contributes presentation and sorting behaviour, and even participates in seating-related calculations. The Group is not merely a label attached to several Guests. It is an independent domain object with its own identity, contact data, membership and behaviour. The Group is itself an Event Object Like the Guest, the Group derives from the common Event Object foundatio...