What's the closest we can come to a definitive list of concepts and guiding principles in OO Software Design?

Question

I'm hoping to assemble a definitive and useful study guide. Please help!

I'll start:

• Program to an Interface not an Implementation
• Interface Separation Principle
• DRY Principle (Don't Repeat Yourself)
• Law of Demeter
• Liskov Substitution Principle
• Dependency Injection/Inversion of Control
• Separation of Concerns
• Loose Coupling
• Open Closed Principle
• Prefer Composition over Inheritance

Answer 1

Interface Separation Principle

DRY Principle (Don't Repeat Yourself)

Answer 2

Program to an Interface not an Implementation.

Answer 3

I'd just refer people to Uncle Bob Martin's writings and call it a day. I think context beats a simple list any day. There's lots to read there.

Know the rules; know when the rules don't apply; know when to break the rules.

Most of all, don't base all your knowledge on dogmatic lists of snippets.

Answer 4

My definitive list:

1. Find, read, and understand the original "Law of Demeter" papers.
2. Find an Object Friendly language that you like.
3. Determine the following: Given the intention of maintaining encapsulation, maintainability, parsimony and readability, and given the features of this language, how should I use this language?

3 is kind of a doozy, but at least you'll have a point of view from which to read other people's advice on how to use the language.

Answer 5

• Program mindfully
• Immutability is your friend
• So are state transition diagrams
• O/R frameworks are not all they are cracked up to be
• Program mindfully
• Patterns are a communication mechanism, not a mandate

Answer 6

General Responsibility Assignment Software Patterns (or Principles)