http://www.agileweb.org/ http://www.agileweb.org/ http://1.asset.soup.io/asset/0129/4353_8c96.gif 128 128 Ross Lawleys tumblelog mainly on software and agile methods. {"tags":["architecture","article","component","work","patterns","python","theory"],"type":"link","title":"Zope 3 wiki ComponentArchitectureApproach","source":"http://wiki.zope.org/zope3/ComponentArchitectureApproach","body":"An article on the Zope Component Architecture describing the use of components, rather than multiple-inheritence for managing complexity.\n\nWith multiple inheritance object responsibilities are spread over many separate mix-in classes. Many of the mix-in classes require subclasses to provide specialized meta-data or methods to customize the behavior of the mix-in. Classes typically have a large number of base classes and many bits of meta-data and special methods that are unrelated to the object's core functionality. .\n\nAn alternative for managing complexity is to spread the complexity over multiple cooperating objects, which make individual classes are much simpler, and thus, easier to maintain and allow functionality to be added and changed without modifying existing classes."} <p>An article on the Zope Component Architecture describing the use of components, rather than multiple-inheritence for managing complexity. With multiple inheritance object responsibilities are spread over many separate mix-in classes. Many of the mix-in classes require subclasses to provide specialized meta-data or methods to customize the behavior of the mix-in. Classes typically have a large number of base classes and many bits of meta-data and special methods that are unrelated to the object's core functionality. . An alternative for managing complexity is to spread the complexity over multiple cooperating objects, which make individual classes are much simpler, and thus, easier to maintain and allow functionality to be added and changed without modifying existing classes.</p> <p><a href="http://wiki.zope.org/zope3/ComponentArchitectureApproach">http://wiki.zope.org/zope3/ComponentArchitectureApproach</a></p>Wed, 23 Sep 2009 07:39:04 GMThttp://agileweb.org/post/29325502/Zope-3-wiki-ComponentArchitectureApproachurn:www-soup-io:1:29325502linkarchitecturearticlecomponentworkpatternspythontheory {"tags":["work","webdev","webdesign","usability","scrum","agile","iteratative"],"type":"link","title":"Getting Real About Agile Design","source":"http://www.alistapart.com/articles/gettingrealaboutagiledesign","body":null} <p><a href="http://www.alistapart.com/articles/gettingrealaboutagiledesign">http://www.alistapart.com/articles/gettingrealaboutagiledesign</a></p>Wed, 03 Dec 2008 08:45:31 GMThttp://agileweb.org/post/8483808/Getting-Real-About-Agile-Designurn:www-soup-io:1:8483808linkworkwebdevwebdesignusabilityscrumagileiteratative