<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet href='http://feeds.feedsky.com/styles/temp01.xsl' type='text/xsl' ?><!--这是一个由Feedsy提供技术支持的Feed，为了提高读者阅读的体验，以及满足用户美化自己Feed的需要，我们设计了多种精美的Feed模板，提供给大家选择，所有最终呈现出来的样式，皆由用户自愿选择使用，未经许可，任何团体和个人，请不要擅自修改样式或者盗用，这是对于用户选择权的尊重。--><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:fs="http://www.feedsky.com/namespace/feed" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link href="http://feeds.feedsky.com/csdn.net/ijacobson" type="application/rss+xml" rel="self"></atom:link><fs:self_link href="http://feeds.feedsky.com/csdn.net/ijacobson" type="application/rss+xml"></fs:self_link><lastBuildDate>Wed, 23 Jun 2010 04:07:00 GMT</lastBuildDate><title>ijacobson的专栏</title><description>CSDN博客聚合服务</description><link>http://blog.csdn.net/blogrss.aspx?username=ijacobson</link><item><title>What Drives Me</title><link>http://blog.csdn.net/ijacobson/archive/2010/06/23/5688927.aspx</link><description>&lt;br /&gt;&lt;br /&gt;“The best way to predict the future is to invent it!“ (Alan 
Kay)&lt;br /&gt;&lt;br /&gt;A few days ago, a very simple but thought provoking question was raised to 
me: “what it is that drives me?” The simple truth is that I do not know. But I 
do know what it is that does not drive me. It is not about money. Actually, 
never has it been about money. Neither is it about power. I am happy to step 
aside and I am happy to delegate both up and down. It is not about popularity – 
but I do li&lt;img src=&quot;http://www1.feedsky.com/t1/382414986/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/06/23/5688927.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414986/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414986/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Wed, 23 Jun 2010 12:07:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/06/23/5688927.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/06/23/5688927.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414986/1321924</fs:itemid></item><item><title>Two complementary macro-trends in software engineering</title><link>http://blog.csdn.net/ijacobson/archive/2010/05/05/5559980.aspx</link><description>April 30th, 2010

From my horizon, I see two distinct and yet complementary macro-trends driving the way we become better at developing software. One could be called “Methods &amp; Tools” the other could be called “Professionalism &amp; Craftsmanship”. These two trends are not new, they have been around as long as we have built software. Both are based on the fact that it is people who develop programs, rather than methods and tools. But they take different approaches to the problem by focusing on dif&lt;img src=&quot;http://www1.feedsky.com/t1/382414987/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/05/05/5559980.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414987/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414987/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Wed, 05 May 2010 16:20:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/05/05/5559980.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/05/05/5559980.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414987/1321924</fs:itemid></item><item><title>Model Storming</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491300.aspx</link><description>&lt;br /&gt; March 28th, 2010&lt;br /&gt;&lt;br /&gt;    Last week, I attended a workshop of a new initiative in software 
engineering (SEMAT see www.semat.org). This was the first real f2f 
meeting we've had. 28 people attended the workshop and one session with 
around 12 people were working on developing more detailed objectives of 
the entire initiative.
&lt;br /&gt;&lt;br /&gt;    To develop the objectives we appointed a facilitator. He suggested 
that we make a usage model for the Semat initiative. But for this&lt;img src=&quot;http://www1.feedsky.com/t1/382414988/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491300.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414988/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414988/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:29:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491300.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491300.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414988/1321924</fs:itemid></item><item><title>How to stop thinking about business as “the customer” and IT as “the vendor”</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491292.aspx</link><description>&lt;br /&gt; March 23rd, 2010&lt;br /&gt;&lt;br /&gt;    In my last three blogs, I discussed how we can close the gap between 
the business and IT. I summed up the way forward with the advice to stop
 thinking about the business as the customer and IT as the provider. 
Instead, let them work together in teams (similar to members of a soccer
 team), responsible directly to management.
&lt;br /&gt;&lt;br /&gt;    It will not be an easy journey, but here are some steps along the 
way:&lt;br /&gt;Management needs to:Make IT an&lt;img src=&quot;http://www1.feedsky.com/t1/382414989/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491292.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414989/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414989/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:26:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491292.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491292.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414989/1321924</fs:itemid></item><item><title>How do we get business and IT to play on the same team?</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491285.aspx</link><description>&lt;br /&gt; February 8th, 2010&lt;br /&gt;&lt;br /&gt;    To close the gap between business and IT we need to get them to play 
on the same team, as said in my two previous blogs.  I compared this 
team with a soccer team in which the participants are not just 
specialists but also generalists – they can all kick the ball when 
called upon.
&lt;br /&gt;&lt;br /&gt;    The Business-IT “team” should work in a similar way.  Despite having 
specialized roles, all of the participants should contribute to achieve a
 comm&lt;img src=&quot;http://www1.feedsky.com/t1/382414990/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491285.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414990/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414990/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:24:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491285.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491285.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414990/1321924</fs:itemid></item><item><title>Let the Business and IT play on the same team</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491271.aspx</link><description>&lt;br /&gt; December 19th, 2009&lt;br /&gt;&lt;br /&gt;    In an earlier blog (Nov 2009: Closing the Gap between Business 
and IT) I described the gap between business and IT and suggested a way 
forward: we must speak the same language.  That language must be more 
than just a spoken language; some simple drawings or models are often 
useful.  However, beware of business models inspired by software models,
 which assume an underlying abstract computational machine. We must work
 together pursuing common&lt;img src=&quot;http://www1.feedsky.com/t1/382414991/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491271.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414991/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414991/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:21:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491271.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491271.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414991/1321924</fs:itemid></item><item><title>SEMAT (Software Engineering Method and Theory): A Call for Action</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491252.aspx</link><description>&lt;br /&gt;December 18th, 2009&lt;br /&gt;&lt;br /&gt;    We are some people who have observed software engineering theory and 
practice of the past decades and have realized that it is now time to 
revitalize this discipline. We have been quietly planning a 
“revolution”.&lt;br /&gt;&lt;br /&gt;    For those who have been following my columns may know that, for a 
very long time, I have been talking about that we need a theory of 
software engineering. See my two blog entries, “A problem to fix: We 
don’t understan&lt;img src=&quot;http://www1.feedsky.com/t1/382414992/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491252.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414992/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414992/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:18:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491252.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491252.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414992/1321924</fs:itemid></item><item><title>Closing the Gap between Business and IT</title><link>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491216.aspx</link><description>    From almost the dawn of the age of software more than 50 years ago, 
there has been a communication gap between business and IT. For almost 
as long we have sought solutions, but they always seem to elude us.  
Meanwhile, the gap has grown into a chasm that now needs a fairly 
substantial bridge.    From the business you may hear that ”we have no confidence in IT’s 
ability to deliver useful solutions”, or “we have limited visibility of 
progress, risks and problems”&lt;img src=&quot;http://www1.feedsky.com/t1/382414993/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2010/04/16/5491216.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414993/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414993/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 16 Apr 2010 00:05:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2010/04/16/5491216.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2010/04/16/5491216.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414993/1321924</fs:itemid></item><item><title>There are practices and then there are Practices</title><link>http://blog.csdn.net/ijacobson/archive/2009/12/01/4914448.aspx</link><description>&lt;br /&gt;&lt;br /&gt;November 10, 2009&lt;br /&gt;&lt;br /&gt;    The software development community
has been talking about practices in an informal way for a very long time – more than 50 years. In the way the
community talks, a “practice”
is just something that people do, a habit they have that may be good, or
perhaps not good. Talking about practices in this way makes for good
conversation, but it is hard to figure out how to combine good practices into
something meaningful.&lt;br /&gt;&lt;br /&gt;    I like to talk&lt;img src=&quot;http://www1.feedsky.com/t1/382414994/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2009/12/01/4914448.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414994/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414994/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Tue, 01 Dec 2009 14:18:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2009/12/01/4914448.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2009/12/01/4914448.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414994/1321924</fs:itemid></item><item><title>Taking the temperature of UML</title><link>http://blog.csdn.net/ijacobson/archive/2009/07/24/4377022.aspx</link><description>&lt;br /&gt;【征集志愿者翻译Ivar Jacobson的文章，感兴趣的朋友可以邮件联系】&lt;br /&gt;&lt;br /&gt;More than twelve years have passed since UML, the Unified Modeling Language, became a standard. During these years the perception of UML has ranged from the heights of the heavens to the depths of the earth.&lt;br /&gt;At the beginning of the 1990s there were 26 published methods on object-orientation, most methods with its own notation. It was to address at least the notation problem that UML was conceived. As most of you probably know, Grady B&lt;img src=&quot;http://www1.feedsky.com/t1/382414995/ijacobson/csdn.net/s.gif?r=http://blog.csdn.net/ijacobson/archive/2009/07/24/4377022.aspx&quot; border=&quot;0&quot; height=&quot;0&quot; width=&quot;0&quot; style=&quot;position:absolute&quot; /&gt;&lt;p class=&quot;fswww1&quot;&gt;&lt;a href=&quot;http://www1.feedsky.com/r/l/csdn.net/ijacobson/382414995/art01.html&quot; target=&quot;_blank&quot;&gt;&lt;img border=&quot;0&quot; ismap=&quot;ismap&quot; src=&quot;http://www1.feedsky.com/r/i/csdn.net/ijacobson/382414995/art01.gif&quot; onerror=&quot;this.style.display='none'&quot; /&gt;&lt;/a&gt;&lt;/p&gt;</description><pubDate>Fri, 24 Jul 2009 15:16:00 +0800</pubDate><author>ijacobson</author><guid isPermaLink="false">http://blog.csdn.net/ijacobson/archive/2009/07/24/4377022.aspx</guid><dc:creator>ijacobson</dc:creator><fs:srclink>http://blog.csdn.net/ijacobson/archive/2009/07/24/4377022.aspx</fs:srclink><fs:srcfeed>http://blog.csdn.net/ijacobson/rss.aspx</fs:srcfeed><fs:itemid>csdn.net/ijacobson/~1317487/382414995/1321924</fs:itemid></item></channel></rss>
