Open Closed Principle

...

Section

show-title	false
title	Description

Quote External

author	Bertrand Meyer
source-date	1988

software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification

Design your documentation in such a way that you do not need to add information to existing documents if a new document is added. This does not imply that every modification is bad. But if there are two solutions to a problem, prefer the one that does not touch existing documents.

Section

title	Example

Section

title	Context

...

Section

required-permissions	write-access
title	Notes

Section

title	References
intro-text	More information on this principle.

projectdoc-tour-macro

render-as-definition-list	true
marker-column-property-name	Title
replace-title-with-name	true

Title

Short Description

Open Closed Principle

The principle described as a pattern on wiki.c2.com.

projectdoc-information-system-generic-macro

file	/Open/closed_principle
system-id	wikipedia-en
system-type	generic
label	Open/closed principle - Wikipedia

The principle described on Wikipedia.

Section

title	Resources

Space shortcuts

Page tree

Docs

Support

Free Blueprints

Tooling for Blueprints

Free Extensions

Spaces

Plugins for Maven

Incubator

Libraries for Java

Incubator

Add-ons for Confluence

Tools

Support

Team

Legal

Versions Compared

Old Version 2

New Version 3

Key

About

Keep up-to-date!

Powered by