# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1570609814 -7200
# Node ID 7a27e64cee67da63b7b16b7f3e04fee3136f2289
# Parent  204f6466c03b7e7bb73b27bc086e48e071b36d48
link to the Modularity Manifesto (NetBeans)

diff -r 204f6466c03b -r 7a27e64cee67 text/ssm.en.xml
--- a/text/ssm.en.xml	Tue Oct 08 17:21:13 2019 +0200
+++ b/text/ssm.en.xml	Wed Oct 09 10:30:14 2019 +0200
@@ -264,6 +264,13 @@
 			<id>e50424e8-94f3-48aa-bf01-0ba984eb2349</id>
 			<type>requirement</type>
 			<text>Larger and multi-purpose software must be divided into smaller modules.</text>
+			<link>
+				<url>http://wiki.apidesign.org/wiki/NetBeans_Runtime_Container#Modularity_Manifesto</url>
+				<type>compatible</type>
+				<title>Modularity Manifesto</title>
+				<quotation>Splitting application into modules can greatly improve the design. It is not hard to guess that a monolithic piece of code where every line in any source code can access any other source file is much more interconnected and unreadable than a code which introduces many modules and allows such uncontrolled calls to happen just inside the module.</quotation>
+				<quotation>Modularity would give systems clearer design, control of dependencies between modules and give developers more flexibility in maintanence. Think about it when starting any new project - nevertheless big it is, do it in modular way. It is going to be big plus for the architecture of the whole application as it grows from its child days.</quotation>
+			</link>
 		</item>
 		<item>
 			<id>e752efae-75c9-4620-aa14-65c4949a3609</id>