Software entities like classes, modules and functions should be open for extension but closed for modifications.
The Open Close Principle encourages software developers to design and write code in a fashion that adding new functionality would involve minimal changes to existing code. Most changes will be handled as new methods and new classes. Designs following this principle would result in resilient code which does not break on addition of new functionality. In this article, we will explore the the open closed principle via an example of a resource allocator.
View Entire Paper | Previous Page | White Papers Search
If you found this page useful, bookmark and share it on: