The Object-Oriented Design Principles are the core of OOP programming, but I have seen most of the Java programmers chasing design patterns like Singleton pattern, Decorator pattern, or Observer pattern, and not putting enough attention on learning Object-oriented analysis and design. It's essential to learn the basics of Object-oriented programming like Abstraction, Encapsulation, Polymorphism, and Inheritance. But, at the same time, it's equally important to know object-oriented design principles. They will help you to create a clean and modular design, which would be easy to test, debug, and maintain in the future.
I have regularly seen Java programmers and developers of various experience level, who have either never heard about these OOP and SOLID design principle, or simply doesn't know what benefits a particular design principle offers and how to apply these design principle in coding.
I have regularly seen Java programmers and developers of various experience level, who have either never heard about these OOP and SOLID design principle, or simply doesn't know what benefits a particular design principle offers and how to apply these design principle in coding.
To do my part, I have jotted down all important object-oriented design principles and putting them here for quick reference. These will at least give you some idea about what they are and what benefits they offer.
I have not put examples, just to keep the article short, but you can find a lot of examples of these design principles in my blog; just use the search bar at the top of the page.
If you are not able to understand a design principle, you should try to do more than one example because sometimes we connect to another example or author better, but you must understand these design principles and learn how to use them in your code.
Another thing you can do is to join a comprehensive object-oriented design course like SOLID Principles: Introducing Software Architecture & Design by Sujith George on Udemy. It has helped me a lot in my understanding and application of these principles.
I personally think each of these OOP and SOLID design principle needs an article to explain them clearly, and I will definitely try to do that here, but for now, just get yourself ready for a quick bike ride on design principle town :)
I have not put examples, just to keep the article short, but you can find a lot of examples of these design principles in my blog; just use the search bar at the top of the page.
If you are not able to understand a design principle, you should try to do more than one example because sometimes we connect to another example or author better, but you must understand these design principles and learn how to use them in your code.
Another thing you can do is to join a comprehensive object-oriented design course like SOLID Principles: Introducing Software Architecture & Design by Sujith George on Udemy. It has helped me a lot in my understanding and application of these principles.
10 Object-Oriented and SOLID Design Principles for Java Programmers
Though the best way of learning any design principle or pattern is a real-world example and understanding the consequences of violating that design principle, the subject of this article is Introducing Object-oriented design principles for Java Programmers, who are either not exposed to it or in the learning phase.
I personally think each of these OOP and SOLID design principle needs an article to explain them clearly, and I will definitely try to do that here, but for now, just get yourself ready for a quick bike ride on design principle town :)
1. DRY (Don't repeat yourself)
Our first object-oriented design principle is DRY, as the name suggests DRY (don't repeat yourself) means don't write duplicate code, instead use Abstraction to abstract common things in one place.
If you have a block of code in more than two places, consider making it a separate method, or if you use a hard-coded value more than one time, make them public final constant.
The benefit of this Object-oriented design principle is in maintenance. It's important not to abuse it, duplication is not for code, but for functionality. It means if you used standard code to validate OrderID and SSN, it doesn’t mean they are the same, or they will remain the same in the future.
The benefit of this Object-oriented design principle is in maintenance. It's important not to abuse it, duplication is not for code, but for functionality. It means if you used standard code to validate OrderID and SSN, it doesn’t mean they are the same, or they will remain the same in the future.
By using standard code for two different functionality or thing, you tightly couple them forever, and when your OrderId changes its format, your SSN validation code will break.
So beware of such coupling and just don’t combine anything which uses similar code but is not related. You can further check out the Basics of Software Architecture & Design Patterns in Java course on Udemy to learn more about writing the right code and best practices to follow while designing a system.
So beware of such coupling and just don’t combine anything which uses similar code but is not related. You can further check out the Basics of Software Architecture & Design Patterns in Java course on Udemy to learn more about writing the right code and best practices to follow while designing a system.
2. Encapsulate What Changes
Only one thing is constant in the software field, and that is "Change," So encapsulate the code you expect or suspect to be changed in the future. The benefit of this OOP Design principle is that It's easy to test and maintain proper encapsulated code.
If you are coding in Java, then follow the principle of making variables and methods private by default and increasing access step by step, like from private to protected and not public.
If you are coding in Java, then follow the principle of making variables and methods private by default and increasing access step by step, like from private to protected and not public.
Several of the design patterns in Java uses Encapsulation, the Factory design pattern is one example of Encapsulation that encapsulates object creation code and provides flexibility to introduce a new product later with no impact on existing code.
Btw, if you are interested in learning more about design patterns in Java and Object-Oriented Programming, then you must check this Design Pattern Library course Pluralsight. It's one of the best collections of design patterns and advice on how to use them in the real world.
Btw, if you are interested in learning more about design patterns in Java and Object-Oriented Programming, then you must check this Design Pattern Library course Pluralsight. It's one of the best collections of design patterns and advice on how to use them in the real world.
3. Open Closed Design Principle
Classes, methods, or functions should be Open for extension (new functionality) and Closed for modification. This is another beautiful SOLID design principle, which prevents someone from changing already tried and tested code.
Ideally, if you are adding new functionality only, then your code should be tested, and that's the goal of the Open Closed Design principle. By the way, the Open-Closed principle is "O" from the SOLID acronym.
4. Single Responsibility Principle (SRP)
Single Responsibility Principle is another SOLID design principle, and represent "S" on the SOLID acronym. As per SRP, there should not be more than one reason for a class to change, or a class should always handle single functionality.
If you put more than one functionality in one Class in Java, it introduces coupling between two functionality, and even if you change one feature, there is a chance you broke coupled functionality, which requires another round of testing to avoid any surprise on the production environment.
You can further see the SOLID Principles of Object-Oriented Design and Architecture course on Udemy for more real-world examples and to learn about patterns that are based on this principle.
You can further see the SOLID Principles of Object-Oriented Design and Architecture course on Udemy for more real-world examples and to learn about patterns that are based on this principle.
5. Dependency Injection or Inversion principle
Don't ask for dependency; it will be provided to you by the framework. This has been very well implemented in the Spring framework, the beauty of this design principle is that any class which is injected by the DI framework is easy to test with the mock object and more comfortable to maintain because object creation code is centralized in the framework and the client code is not littered with that.
There are multiple ways to implemented Dependency injection like using bytecode instrumentation, which some AOP (Aspect Oriented Programming) framework like AspectJ does, or by using proxies just like used in Spring. See this example of the IOC and DI design pattern to learn more about this SOLID design principle. It represents "D" on the SOLID acronym.
There are multiple ways to implemented Dependency injection like using bytecode instrumentation, which some AOP (Aspect Oriented Programming) framework like AspectJ does, or by using proxies just like used in Spring. See this example of the IOC and DI design pattern to learn more about this SOLID design principle. It represents "D" on the SOLID acronym.
6. Favor Composition over Inheritance
Always favor composition over inheritance, if possible. Some of you may argue this, but I found that Composition is a lot more flexible than Inheritance.
Composition allows changing the behavior of a class at run-time by setting property during run-time, and by using Interfaces to compose a class, we use polymorphism, which provides flexibility to replace with better implementation at any time.
Even the classic book Effective Java advises favoring composition over inheritance. See here to learn more about why your Composition is better than Inheritance for reusing code and functionality.
Composition allows changing the behavior of a class at run-time by setting property during run-time, and by using Interfaces to compose a class, we use polymorphism, which provides flexibility to replace with better implementation at any time.
Even the classic book Effective Java advises favoring composition over inheritance. See here to learn more about why your Composition is better than Inheritance for reusing code and functionality.
7. Liskov Substitution Principle (LSP)
According to the Liskov Substitution Principle, Subtypes must be substitutable for supertype, i.e. methods or functions which use superclass type must be able to work with the object of subclass without any issue".
LSP is closely related to the Single responsibility principle and Interface Segregation Principle. If a class has more functionality, then the subclass might not support some of the functionality and does violate LSP.
In order to follow LSP SOLID design principle, derived class or subclass must enhance functionality, but not reduce them. LSP represents "L" on the SOLID acronym. If you are interested in a more real-world example, then the SOLID Principles of Object-Oriented Design course on Pluralsight is an excellent course to start with.
LSP is closely related to the Single responsibility principle and Interface Segregation Principle. If a class has more functionality, then the subclass might not support some of the functionality and does violate LSP.
In order to follow LSP SOLID design principle, derived class or subclass must enhance functionality, but not reduce them. LSP represents "L" on the SOLID acronym. If you are interested in a more real-world example, then the SOLID Principles of Object-Oriented Design course on Pluralsight is an excellent course to start with.
Btw, you would need a Pluralsight membership to get access to this course, which costs around $29 per month or $299 annually (14% discount).
If you don't have Pluralsight membership, I encourage you to get one because it allows you to access their 5000+ online courses on all the latest topics like front-end and back-end development, machine learning, etc. It also includes interactive quizzes, exercises, and the most recent certification material.
It's more like Netflix for Software Developers, and Since learning is an integral part of our job, Pluralsight membership is a great way to stay ahead of your competition.
They also provide a 10-day free trial without any commitment, which is a great way to not just access this course for free but also to check the quality of courses before joining Pluralsight.
8. Interface Segregation Principle (ISP)
The Interface Segregation Principle states that a client should not implement an interface if it doesn't use that. This happens mostly when one interface contains more than one functionality, and the client only needs one functionality and no other.
Interface design is a tricky job because once you release your interface, you can not change it without breaking all implementation.
Another benefit of this design principle in Java is, the interface has the disadvantage of implementing all methods before any class can use it, so having single functionality means less method to implement. If you don't get the benefit of the interface in coding, then I suggest you read my blog post, the real usage of an interface in Java to learn more.
Interface design is a tricky job because once you release your interface, you can not change it without breaking all implementation.
Another benefit of this design principle in Java is, the interface has the disadvantage of implementing all methods before any class can use it, so having single functionality means less method to implement. If you don't get the benefit of the interface in coding, then I suggest you read my blog post, the real usage of an interface in Java to learn more.
9. Programming for Interface not implementation
Always program for the interface and not for application; this will lead to flexible code that can work with any new implementation of the interface.
So use interface type on variables, return types of method, or argument type of methods in Java.
This has been advised in many Java books, including in Effective Java and Head First design pattern book.
So use interface type on variables, return types of method, or argument type of methods in Java.
This has been advised in many Java books, including in Effective Java and Head First design pattern book.
10. Delegation principles
Don't do all stuff by yourself, delegate it to the respective class. Classical example of delegation design principle is equals() and hashCode() method in Java. In order to compare two objects for equality, we ask the class itself to make a comparison instead of the Client class doing that check.
The key benefit of this design principle is no duplication of code and pretty easy to modify behavior. Event delegation is another example of this principle, where an event is delegated to handlers for handling.
The key benefit of this design principle is no duplication of code and pretty easy to modify behavior. Event delegation is another example of this principle, where an event is delegated to handlers for handling.
Summary
All these object-oriented design principles help you write flexible and better code by striving for high cohesion and low coupling. The theory is the first step, but what is most important is to develop the ability to find out when to apply these design principles.Once you get hold of that, the next step is to learn Design patterns in Java, which uses these design patterns to solve common problems of application development and software engineering.
If you are looking for an excellent course to start with, I suggest you join the Software Design Patterns: Best Practices for Software Developers course on Educative, a text-based interactive online learning portal where you can practice patterns right on your browser.
Anyway, here is an excellent summary of all these OOP design principles.
Anyway, here is an excellent summary of all these OOP design principles.
Find out whether we are violating any design principle and compromising the flexibility of code, but again as nothing is perfect in this world, don't always try to solve the problem with design patterns and design principles. They are mostly for large enterprise projects which have a longer maintenance cycle.
The bottom line is, professionals programmers should always strive for a highly cohesive and loosely couple solution, code, or design. Looking at open source code from Apache and Google are some excellent ways of learning Java and OOP design principles.
They show us how design principles should be used in coding and Java programs. Java Development Kit follows many design principles like Factory Pattern in BorderFactory class, Singleton pattern in Runtime class, Decorator pattern on various java.io classes.
If you are interested in learning object-oriented principles and patterns, then you can look at my other personal favorite Head First Object-Oriented Analysis and Design, an excellent book and probably the best material available in object-oriented analysis and design.
Not many programmers know this book because it is often shadowed by its more famous cousin Head First Design Pattern by Eric Freeman, which is more about how these principles come together to create a pattern you can use directly to solve known problems.
These books help a lot to write better code, taking full advantage of various Object-oriented and SOLID design principles.
Btw, if you really interested more in Java coding practices, then read Effective Java 3rd Edition by Joshua Bloch, a gem by the guy who wrote Java Collection API.
Other Java and Programming Resources you may like
- 10 Things Every Java Programmer should learn
- 10 Books Every Programmer Must Read
- 10 Courses to learn DevOps in Depth
- The Step by Step Java Developer RoadMap
- My favorite courses to learn Software Architecture
- 10 Tips to Improve Your Programming skill
- 10 Tools Every Software Developer should know
- 21 Tech skills Java developers should learn
- 5 Courses to Learn Software Architecture in Depth
- 20 Libraries and APIS Java Programmer Should Know
- 7 Best books to learn about Design Patterns
- Top 10 Programming languages to Learn for Software Engineers
- 10 Articles Every Programmer Should Read
- 10 Framework and Library Java and Web Developer Should Learn
Thanks for reading this article. If you find these object-oriented design principles useful, then please share them with your friends and colleagues. If you have any questions or feedback, then please drop a note.
P. S. - If you are serious about improving your coding skills then as a next step you can also learn design patterns, they are the patterns that use these principles to solve common problems of software development. If you need resources, check out these Design Patterns in Java courses by Dmitri Nestruk on Udemy to learn more about the modern implementation of classic design patterns in Java.
28 comments :
Excellent Article.....!!!!!but these concepts can be learned by experience...Hopefully I am trying to applying the things which I learnt.
But I hope you are going to post few articles regarding the OOPS concept and design principles.
awesome blogs .. Hats of to you Javin....You are taking this to a whole new level..I was asked this question in a BNY /Mellon interview and i wish i could answer it this clearly!!!!
Very simple great impact !!!
Very great article.
But lets not forget the basic design principle:
KISS: Keep It Simple and Straightforward; simplicity should be a key goal in design and unnecessary complexity should be avoided
Some quick notes:
DRY is not exactly an object oriented principle, isn't it? Nor is it one of the SOLID principles.
Dependency injection and Inversion (of Control) are not equal. Moreover you do not need a framework to do dependency injection.
As its name suggests ISP is rather the other way round: Break up a single (big) interface into small ones. Maybe you meant the right thing and your definition is just confusing.
Equals() and hashCode() are good examples of encapsulation and information hiding rather than delegation.
"... design patterns and design principle ... are mostly for large enterprise project which has longer maintenance cycle"
That is like saying a healthy lifestyle is only important for athletes. You seem to confuse basic patterns and principles with sophisticated designs. Plus: The length of a maintenance cycle does not correlate with the size of a project.
It's good for less experienced developers, though, to see many important principles in one place. Keep on going.
@Anonymous, Thanks for your comment. DRY (Don't repeat yourself) is more of pattern derived from Experience, but its mostly referenced along with other SOLD design principles.
Regarding DI, isn't it an example of Inversion of Control where dependency is injected by external source like Spring framework instead of hard coded, though I agree that you can write your own framework to implement Dependency Injection but I still see better to use Spring framework than creating your own as you can never get same level of testing, quality and stability as front line open source project like Spring gains.
Regarding equals() and hashCode() indeed they better fit and example of encapsulation rather than delegation.
Anyway Thanks for your input and comment, keep it coming.
Sounds as if these examples were taken from " Head First Object-Oriented Analysis and Design". A great book BTW, worth mentioning here :-)
How about adding few more design principles :
KISS (Keep it Simple, Stupid)- KISS design principle says that that most software, program works well if they are made simple rather than complex.
YAGNI - You are not going to need it, is an extreme programming design principle which states that don't build any functionality until you need it. this is best to remove dead code or not utilized code from your project.
Superb stuff
Please don't confuse dependency inversion (DIP) and dependency injection - they are two totally different principles. See http://martinfowler.com/articles/dipInTheWild.html for explanation.
Hello there, what is difference between design principle and design patterns? Can you please describe?
Hi Pattision,
Basically design principles are the base on which design patterns get created to solve a problem.
More details can be found here-
http://techythought.wordpress.com/2013/01/21/design-principle-vs-ds-design-pattern-describing-oop-elements/
HI Javin, Please try to post an article Design Principles Vs Design Patterns? People often confusing about principles and patterns are same or not. Could be highly appreciate if you can post an article.
good theory but can you publish practical programs of above 10 points.it will be helpful also.
a great article, every java developer and designer must definitely read this.
Good list, though I know these principles and patterns and what problem they solve, having them in one place is great job. In real life there are more principle, rules than these though, for example I would like to share one design pattern, principle or rule, call it whatever you like, which has benefited me lot in past.
One of the keys to write robust and flexible software is to make sure that layers at the bottom that are reusable have no knowledge of the layers that use them.
For example, the Logger classes have no knowledge of any other class that uses them. This lets the class designers focus on the Logging functionality.
Excellent Article.....!!!! here i've seen most them taking hashCode() and equals(-) method into the criteria of encapsulatio rather than delegation so here we can also keep toString() method as the example of encapsulation design pattern .............. m i ri8 or wrong..........
Thanks for the article ,it made me realise the importance of design principles
Ganesh : Super se Uper...:)
Great post. Explaining all in simple words.
Thank you Neelesh and Deepak.
Please provide Best udemy courses name/link for learning object oriented design principles, patterns
Hello @Anonymous, I have shared some of the best online courses to learn Design patterns and Object oriented programming already. those list contains best courses from both Udemy and Pluralsight. You can see those links. Thanks
Nice piece of paper
why does is seem like people were replying to this post 5 years before it was posted?
Because these design principles are still valid and will remain valid for coming years. I have also update the post regularly.
I want to learn
1) Java project case studies
2) Low Level Design and High Level Design
3) Java Project Designing.
Please help me if any courses available on Udemy or any other site or url to learn.
Thanks for understanding
Hello JavaMuralee, I suggest you try some o the courses on Educative like Grokking the Object Oriented Design and Grokking the System Design Interview, it will help you with designing projects. You can find some more links on my Medium article My favorite courses to learn Object Oriented design
Post a Comment