Design Principles [closed]

Answer 1

As mentioned above, some of the fundamental Object Oriented Design principles are OCP, LSP, DIP and ISP.

An excellent overview of these by Robert C. Martin (of Object Mentor) is available here: OOD Principles and Patterns

Answer 2

The S.O.L.I.D. principles.
Or at least I try not to steer away too much from them.

Answer 3

I usually try to fit the class into one of the oo design patterns.

Answer 4

loosely coupled, highly cohesive.

Composition over inheritance.

Answer 5

The "Resource Acquisition Is Initialization" paradigm is handy, particularly when writing in C++ and dealing with operating system resources (file handles, ports, etc.).

A key benefit of this approach is that an object, once created, is "complete" - there is no need for two-phase initialization and no possibility of partially-initialized objects.

Answer 6

A thing which I would like to add to all this is layering, Define layers in your application, the overall responsibility of a layer, they way two layers will interact. Only classes which have the same responsibility as that of the layer should be allowed in that layer. Doing this resolves a lot of chaos, ensures exceptions are handled appropriately, and it makes sure that new developers know where to place their code.

Another way to design is by designing your class to be configurable creating a mechanism where the configuration can be plugged in your class, rather than overriding methods in sub classes, identify what changes, see if that can be made configurable and ensures that this functionality is derived from configurations