Wikipedia: '"Don't repeat yourself" (DRY) is a principle of software development aimed at reducing repetition of information which is likely to change, replacing it with abstractions that are less likely to change, or using data normalization which avoids redundancy. The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system". The principle has been formulated by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. When the DRY principle is applied successfully, a modification of any single element of a system does not require a change in other logically unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, ...'
Many of the Webel best practice tips promote Single Source of Truth (SSOT) development that respects the Don't Repeat Yourself (DRY) principle (and helps avoid "WET" models and code). And UML® and SysML® tools are Single Source of Truth (SSOT) engines!
This site also leverages SSOT-based content macros via the Drupal Custom Tokens Plus module: for example, one can refer to this very page via this generated link: About the Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY) principles. And the following bit of linked text (that in fact links to this page) is also generated: Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY).
In all Webel IT Australia tutorial trails the Slide pages are linked to cross-referenced specification Snippet (extract) pages and Note pages with Webel Best Practice policies, tips on tool use, and issue tracking notes. We call this strategy "super relational".
One of the major aims of Model-Based Systems Engineering (MBSE) is to move away from older "disconnected" document-intensive systems engineering approaches to a centralised model shared by team members under stricter Single Source of Truth (SSOT) practices.