# Open/Closed Principle in Software Design

DevFeed: [Open/Closed Principle in Software Design](<https://devfeed.tech/articles/open-closed-principle-in-software-design-40728.md>)

Original publisher: [Read original article](<https://radek.io/posts/openclosed-principle-in-software-design/>)

Published: 2011-08-04T00:00:00Z

Content type: article

Language: en

Sources: [Radek Pazdera](<https://devfeed.tech/sources/radek-pazdera.md>)

Topics: [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Software](<https://devfeed.tech/topics/software.md>), [classes](<https://devfeed.tech/topics/classes.md>), [function](<https://devfeed.tech/topics/function.md>), [modules](<https://devfeed.tech/topics/modules.md>), [unit tests](<https://devfeed.tech/topics/unit-tests.md>)

Tags: [changes](<https://devfeed.tech/tags/changes.md>), [classes](<https://devfeed.tech/tags/classes.md>), [code](<https://devfeed.tech/tags/code.md>), [customer](<https://devfeed.tech/tags/customer.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [open-closed](<https://devfeed.tech/tags/open-closed.md>), [software](<https://devfeed.tech/tags/software.md>), [software-design](<https://devfeed.tech/tags/software-design.md>), [tests](<https://devfeed.tech/tags/tests.md>)

## AI overview

This article explains the Open/Closed Principle in software design: software entities such as classes, modules, and functions should be open for extension but closed for modification. It argues that designing for likely changes can reduce the need to alter existing code, while noting that the principle is a guideline rather than an unconditional rule.

## Source excerpt

I build software products and write on the Internet.