<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://jimcarey.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Jim Carey</title>
 <link>http://jimcarey.sys-con.com/</link>
 <description>Latest News from Jim Carey</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 07 Dec 2009 11:24:53 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Discovering and Documenting Business Application Patterns</title>
 <link>http://jimcarey.sys-con.com/node/43359</link>
 <description>Over the past two months, we&#039;ve looked at the process of extracting a business application pattern from a series of business requirements. You&#039;ve seen this pattern take shape, from its original form as a design meeting the specific needs of a particular business application (configurable product balance information) through an initial abstraction that was modified by other business requirements to reach its final form.&lt;p&gt;&lt;a href=&quot;http://jimcarey.sys-con.com/node/43359&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 15 Apr 2003 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://jimcarey.sys-con.com/node/43359</guid>
 <comments>http://jimcarey.sys-con.com/node/43359#feedback</comments>
</item>
<item>
 <title>Discovering and Documenting Business Application Patterns</title>
 <link>http://jimcarey.sys-con.com/node/43322</link>
 <description>This month we&#039;ll look at pattern discovery in more detail by continuing to examine a business application pattern we discovered and documented. Our focus isn&#039;t on creating formal patterns, but on capturing, refining, and sharing the knowledge gained during development. We&#039;ll discuss the steps we went through as we discovered and captured our pattern. As we progress through the steps, we&#039;ll show you not only what we learned as we captured this pattern, but also things we learned as we captured other patterns.&lt;p&gt;&lt;a href=&quot;http://jimcarey.sys-con.com/node/43322&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 21 Mar 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jimcarey.sys-con.com/node/43322</guid>
 <comments>http://jimcarey.sys-con.com/node/43322#feedback</comments>
</item>
<item>
 <title>Discovering and Documenting Business Application Patterns</title>
 <link>http://jimcarey.sys-con.com/node/43310</link>
 <description>You&#039;re probably saying to yourself, &#039;Oh, no! Not another patterns article!&#039; Technically, that&#039;s what this is. However, instead of simply showing you a finished pattern, we&#039;re going to look at pattern discovery. And, while what we&#039;ll talk about can help you capture fundamental patterns (that is, if there are any fundamental patterns left to be defined) we&#039;re going to focus on the capture of more workaday patterns. These are patterns that may be useful to only you and your team and might never be made into formal patterns or even shared outside of your group. In fact a pattern purist might say they aren&#039;t even patterns.&lt;p&gt;&lt;a href=&quot;http://jimcarey.sys-con.com/node/43310&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 03 Feb 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://jimcarey.sys-con.com/node/43310</guid>
 <comments>http://jimcarey.sys-con.com/node/43310#feedback</comments>
</item>
</channel>
</rss>
