equal
deleted
inserted
replaced
262 <id>c56e7e86-e480-4a5d-8a47-ab155dcd59b1</id> |
262 <id>c56e7e86-e480-4a5d-8a47-ab155dcd59b1</id> |
263 <item> |
263 <item> |
264 <id>e50424e8-94f3-48aa-bf01-0ba984eb2349</id> |
264 <id>e50424e8-94f3-48aa-bf01-0ba984eb2349</id> |
265 <type>requirement</type> |
265 <type>requirement</type> |
266 <text>Larger and multi-purpose software must be divided into smaller modules.</text> |
266 <text>Larger and multi-purpose software must be divided into smaller modules.</text> |
|
267 <link> |
|
268 <url>http://wiki.apidesign.org/wiki/NetBeans_Runtime_Container#Modularity_Manifesto</url> |
|
269 <type>compatible</type> |
|
270 <title>Modularity Manifesto</title> |
|
271 <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> |
|
272 <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> |
|
273 </link> |
267 </item> |
274 </item> |
268 <item> |
275 <item> |
269 <id>e752efae-75c9-4620-aa14-65c4949a3609</id> |
276 <id>e752efae-75c9-4620-aa14-65c4949a3609</id> |
270 <type>requirement</type> |
277 <type>requirement</type> |
271 <text>The modules must have defined dependencies (less = better).</text> |
278 <text>The modules must have defined dependencies (less = better).</text> |