Real software sees entities (Customer, File etc) involved in multiple interactions. Simple OO examples model behavior in entity classes directly, but this becomes tangled as behaviors & interactions increase; and results in broken inheritance structures.
Instead of modelling these all in the entity, a more advanced OO approach considers separating behavior from the entity. We’ll consider key principles in this multi-part series.
Articles in the Series
This series covers key principles & insights gleaned from over 20 years design & architecture experience.
- OO Design is more about ‘Doing‘ than ‘Being‘
- Inheritance vs Composition
- Interactions spanning Entities
As on ongoing series, articles will be published at irregular intervals.
Be sure to add your comments, and keep checking back as the series progresses!