SOLID Design Principles

SOLID is acronym introduced by Robert C Martin, which stands for five basic principles of object oriented programming/design.

Single Responsibility Principle:
Every class should have a single responsibility, and that responsibility should be entirely encapsulated by the class.

Open Closed Principle:
Software entities (classes, modules) should be open for extension, but closed for modification.

Liskov Substitution Principle:
If S is a subtype of T, then objects of type T in a program may be replaced with objects of type S without altering any of the desirable properties of that program.

Interface Segregation Principle:
Split interfaces which are very large into smaller and more specific ones so that clients will only have to know about the methods that are of interest to them.

Dependency Inversion Principle:
Decouple high-level components from low-level components such that reuse with different low-level component implementations becomes possible.

Advertisements

One thought on “SOLID Design Principles

  1. I like this weblog very much so much good info. It’s a poor sort of memory that only works backward. by Lewis Carroll.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s