Ticket #42 (new enhancement)

Opened 2 years ago

Last modified 2 years ago

Describe rules for good classes

Reported by: gvwilson Assigned to: gvwilson
Priority: minor Milestone: Someday
Component: lectures Version:
Keywords: OOP Cc:

Description

Borrow description from Spinellis' books of what makes a good class:

  • low coupling and high cohesion
  • simple interface
  • etc.

Also include guidelines such as Liskov Substition Principle, Law of Demeter, etc. (On the other hand, this is pretty advanced stuff for someone who's just seeing OO programming for the first time.)