#Open closed antnotes software

If we create the right abstractions, we can depend mostly on well-defined and stable behaviors. We want modules to be closed for modifications, as every change has the potential to have negative side effects. We want the ability to extend the behavior of our application so that we can adapt to our customer's needs. If requirements change and we get requests for new features, we'd like to accommodate them in our code. We want modules that embody the two definitions: This assumes that the module has been given a well-defined, stable description (the interface in the sense of information hiding) For example, it should be possible to add fields to the data structures it contains, or new elements to the set of functions it performs.ДЄ module will be said to be closed if it's available for use by other modules.

#Open closed antnotes software

On the book Object-Oriented Software Construction(1988), by Bertrand Meyer, the following two definitions appear:ДЄ module will be said to be open if it is still available for extension. The principle has a single goal: to make the system easy to extend without impacting the code that already exists. A small change in requirements should be accomplished without too much effort, while bigger features should still be possible to implement. It's related to one of the main goals of software architecture: the proportion of changes in requirements and changes in the code. It seems like an incredibly simple principle, but it's behind most of the best practices we use when designing software. ) should be open for extension but closed for modification Software entities (classes, modules, functions. Originally coined by Bertrand Meyer, it states that:

The Open Closed Principle is responsible for the 'O' of the S.O.L.I.D principles.