<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://hughtaylor.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Hugh Taylor</title>
 <link>http://hughtaylor.sys-con.com/</link>
 <description>Latest News from Hugh Taylor</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Fri, 04 Dec 2009 20:59:34 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>The Triumph of the Ho-Hum SOA</title>
 <link>http://hughtaylor.sys-con.com/node/1186160</link>
 <description>If you’ve followed the arc of the SOA revolution, you might have expected the current moment to be one of great fanfare and proclamations of success. SOA (was supposed to have) arrived! SOA (was supposed to be) an accepted standard for software development and enterprise architecture. Yet, as we have seen, the naysayers appear to have had their day. SOA is DOA, we are told again and again.&lt;p&gt;&lt;a href=&quot;http://hughtaylor.sys-con.com/node/1186160&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 13 Nov 2009 17:45:00 EST</pubDate>
 <guid isPermaLink="true">http://hughtaylor.sys-con.com/node/1186160</guid>
 <comments>http://hughtaylor.sys-con.com/node/1186160#feedback</comments>
</item>
<item>
 <title>Business Optimization Through SOA</title>
 <link>http://hughtaylor.sys-con.com/node/417752</link>
 <description>Governance is the tail that wags the SOA dog. An organization that deploys Web Services without a solid governance program is headed for serious trouble in terms of reliability, security, and cost. While governance is a necessity for any IT endeavor, the open and potentially chaotic nature of SOA makes governance either a showstopper or a magic bullet for success, depending on how it&#039;s approached. This article will look at SOA governance from both a technological and business perspective, highlighting the need for a complete governance model - a closed loop that spans design time to runtime, policy definition, enforcement, and audit.&lt;p&gt;&lt;a href=&quot;http://hughtaylor.sys-con.com/node/417752&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 27 Aug 2007 19:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://hughtaylor.sys-con.com/node/417752</guid>
 <comments>http://hughtaylor.sys-con.com/node/417752#feedback</comments>
</item>
<item>
 <title>Managing SOX in the Age of SOA</title>
 <link>http://hughtaylor.sys-con.com/node/250507</link>
 <description>Service Oriented Architecture (SOA) is at the heart of many major IT initiatives and vendor offerings. However, while SOA has the potential to deliver business value through streamlined application integration, as well as integration with partners and suppliers, the open nature of SOA has the potential to cause problems with Sarbanes-Oxley compliance. This article will look at compliance issues inherent in developing an SOA. Using a practical example, we&#039;ll examine COSO Control Objectives, Risks, and their supporting IT systems from the perspective of Sarbanes-Oxley compliance.&lt;p&gt;&lt;a href=&quot;http://hughtaylor.sys-con.com/node/250507&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 28 Jul 2006 09:45:00 EDT</pubDate>
 <guid isPermaLink="true">http://hughtaylor.sys-con.com/node/250507</guid>
 <comments>http://hughtaylor.sys-con.com/node/250507#feedback</comments>
</item>
</channel>
</rss>
