OOP – Page 6 – Sharp: NCLEX, Java & Python

Java: Object Responsibility

How can validation logic be misplaced in object design?

Why can exposing an object's internal list become a real problem?

Why should behavior be kept with the data it operates on?

How does responsibility-driven design prevent confused objects?

How would you explain the danger of a class with too many responsibilities in an interview?

What does it mean for a list to be unmodifiable?

Why should validation be part of the constructor in some cases?

Why should fields in a class be private?

Why does a constructor in maintaining class invariants matter in this design?

How can encapsulation help avoid anemic objects?