Anil Kumar
What is SOLID principles in class designing ?
Posted by Anil Kumar in Design Patterns & Practices on Nov 23, 2012
  • 0
  • 6
  • 2371
Do you know the answer for this question? Post it below.
Posted by Shivam Shukla on Feb 10, 2015
  • 1

The five design principles the SOLID acronym stands for are, using Andras' brief description:

Single Responsibility Principle states that every object should only have one reason to change, i.e. every object should perform one thing only.
Open-Closed Principle states that classes should be open for extension and closed for modification.
Liskov Substitution Principle states that you should be able to use a derived class in place of a parent class and it must behave in the same manner.
Interface Segregation Principle states that clients should not be forced to depend on interfaces they do not use.
Dependency Inversion Principle helps to decouple your code by ensuring that you depend on abstractions rather than concrete implementations.

Posted by Shivam Shukla on Feb 10, 2015
  • 1

Posted by Anurag Agarwal on Aug 07, 2013
  • 1

S-Single responsibility principle.
(A class should have only a single responsibility.)

O-Open/closed principle
(software entities … should be open for extension, but closed for modification.)

L-Liskov substitution principle
(objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program.)

I-Interface segregation principle (many client-specific interfaces are better than one general-purpose interface)

D-Dependency inversion principle (one should Depend upon Abstractions. Do not depend upon concretions.Dependency injection is one method of following this principle.)

Posted by Naresh Avari on May 02, 2014
  • 0

I have recently found a very nice article on this topic at the below link:

Posted by Shweta Lodha on Apr 17, 2014
  • 0

Posted by Munesh Sharma on Apr 16, 2014
  • 0