You'll sometimes find in your designs that one object starts to acquire a lot of behavior while other objects become little more than place holders for data. This is a sign that your code is suffering from a god class and an anemic domain model. Code that's structured this way extracts the data from the domain objects, performs all the processing in one class, then writes the results back to the domain objects. This approach will become complex very quickly and becomes hard to change and breaks easily. Try distributing the functionality away from the god class and make the domain objects do more of the work. You'll find that your designs become simpler and much easier to manage.
Download