<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-6008447801024190541</id><updated>2011-11-28T01:01:01.629+01:00</updated><category term='mdd java mod4j'/><category term='agile'/><category term='architecture'/><title type='text'>What's new on the Developer's Front?</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>8</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-6864542797734707818</id><published>2011-09-25T21:11:00.003+02:00</published><updated>2011-09-25T21:11:25.823+02:00</updated><title type='text'>The daily team development checklist</title><summary type='text'>Have you ever seen software development team members around five in the afternoon commit their changes for the day into the source code management system and go home, happily whistling, just before the Continuous Integration build finishes with errors that they introduced? And you had to stay and correct their errors before you could commit your own changes and go home yourself? I have seen this </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/6864542797734707818/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=6864542797734707818' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/6864542797734707818'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/6864542797734707818'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2011/09/daily-team-development-checklist.html' title='The daily team development checklist'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-9091616529139081527</id><published>2011-02-28T13:23:00.000+01:00</published><updated>2011-02-28T13:23:25.537+01:00</updated><title type='text'>Question: how to do acceptance testing in Scrum?</title><summary type='text'>When starting to use Scrum for software development, many teams approach acceptance testing in a more or less traditional way. Developers focus on implementing the spring backlog items within the sprint. At the end of the sprint a new release of the system is delivered and declared ready for acceptance testing.

There are is a problem with this approach. When a Product Backlog Item is not tested </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/9091616529139081527/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=9091616529139081527' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/9091616529139081527'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/9091616529139081527'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2011/02/question-how-to-do-acceptance-testing.html' title='Question: how to do acceptance testing in Scrum?'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-6421160362748335307</id><published>2011-02-10T23:29:00.001+01:00</published><updated>2011-02-11T08:40:03.028+01:00</updated><title type='text'>There's no such thing as platform-independence.</title><summary type='text'>The central model in the Model-Driven Architecture (MDA) is the Platform-independent Model (PIM). The functionality of a system is specified it in a way that is independent of the platform used to implement it. To realize this implementation, the PIM is transformed into one or more platform-specific Models (PSM), from which source code is generated in a programming language like C, Java or .Net. </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/6421160362748335307/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=6421160362748335307' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/6421160362748335307'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/6421160362748335307'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2011/02/theres-no-such-thing-as-platform.html' title='There&apos;s no such thing as platform-independence.'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-5608289044214434012</id><published>2010-11-10T16:20:00.002+01:00</published><updated>2010-11-10T16:34:29.515+01:00</updated><title type='text'>A false claim about loose coupling</title><summary type='text'>Sometimes when loose coupling between modules is described as a desirable property (which it is of course), an somewhat exaggerated claim is made about its benefits. See for example the section "The Benefits" in OSGi – The Business Drivers:
As long as the module boundaries don’t change, one can change the functionality of the module freely, without concern for breaking the wider system; i.e. the </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/5608289044214434012/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=5608289044214434012' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/5608289044214434012'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/5608289044214434012'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2010/11/false-claim-about-loose-coupling.html' title='A false claim about loose coupling'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-3846982544895760900</id><published>2010-09-04T20:35:00.000+02:00</published><updated>2010-09-04T20:35:09.893+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='architecture'/><title type='text'>The value of software architecture</title><summary type='text'>A favorite hobby of IT architects is to discuss the purpose of IT architecture and what value it contributes to an organisation. See for example The Three C's of Architecture, or the motto of the last Nationaal Architectuur Congres in the Netherlands: Architecture múst contribute (as if that were not obvious!).

The goal of information technology is to improve business processes using computers. </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/3846982544895760900/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=3846982544895760900' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/3846982544895760900'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/3846982544895760900'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2010/08/value-of-software-architecture.html' title='The value of software architecture'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-4276197974786858119</id><published>2009-08-21T22:15:00.006+02:00</published><updated>2009-08-21T22:32:46.242+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='mdd java mod4j'/><title type='text'>Model Driven Development with Mod4J</title><summary type='text'>My article "Model Driven Development met Mod4J" (in Dutch) appeared in the June 2009 issue of Java Magazine. Actually my first published article!</summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/4276197974786858119/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=4276197974786858119' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/4276197974786858119'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/4276197974786858119'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2009/08/model-driven-development-with-mod4j.html' title='Model Driven Development with Mod4J'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-3173874023061655632</id><published>2009-03-20T09:38:00.019+01:00</published><updated>2009-03-20T17:03:26.927+01:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='agile'/><category scheme='http://www.blogger.com/atom/ns#' term='architecture'/><title type='text'>How agile is architecture?</title><summary type='text'>Ever since software is being developed, one of the greatest challenges is how to build exactly what the customer needs. How do you stay close to your customer in the face of forces that drive you away from him? Many methods and programming languages have promised a solution to this problem.Take COBOL, one of the oldest programming languages. COBOL means COmmon Business Oriented Languages. The </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/3173874023061655632/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=3173874023061655632' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/3173874023061655632'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/3173874023061655632'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2009/03/how-agile-is-architecture.html' title='How agile is architecture?'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-6008447801024190541.post-5632408770843081757</id><published>2009-02-11T21:50:00.011+01:00</published><updated>2009-02-16T10:53:43.165+01:00</updated><title type='text'>What's new about Model-Driven Development?</title><summary type='text'>The introduction of the Model Driven Architecture (MDA) by the Object Management Group (OMG) in 2001 caused a surge of optimism among the relatively few people still interested in code-generation. Finally a standard modelling language (UML) as a basis for code-generation, and consequently the possibility to exchange models between tools of different vendors! Since then the initial enthusiasm for </summary><link rel='replies' type='application/atom+xml' href='http://emalotau.blogspot.com/feeds/5632408770843081757/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=6008447801024190541&amp;postID=5632408770843081757' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/5632408770843081757'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/6008447801024190541/posts/default/5632408770843081757'/><link rel='alternate' type='text/html' href='http://emalotau.blogspot.com/2009/02/whats-new-about-model-driven.html' title='What&apos;s new about Model-Driven Development?'/><author><name>Eric Jan Malotaux</name><uri>http://www.blogger.com/profile/11146058582748543970</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='24' height='32' src='http://3.bp.blogspot.com/_H_pJZMfc4uU/SW2srWEi-FI/AAAAAAAAAAM/IWHiV6fgsaY/S220/EricJanMalotaux-100-140.gif'/></author><thr:total>0</thr:total></entry></feed>
