<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://ericmarks.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Eric Marks</title>
 <link>http://ericmarks.sys-con.com/</link>
 <description>Latest News from Eric Marks</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Fri, 04 Dec 2009 01:25:33 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>SOA Governance Best Practices – Architectural, Organizational, and SDLC Implications</title>
 <link>http://ericmarks.sys-con.com/node/175376</link>
 <description>The fact that you&#039;re reading this article means that you are probably planning a service-oriented architecture (SOA) initiative and recognize that some level of governance is required in order to be successful. If you are like most people in this position, you are also somewhat confused as to the meaning of SOA governance. Governance is the current buzzword, and combining governance with SOA creates a phrase that every independent software vendor (ISV) wants a piece of. How do you sort out what is marketing hype from what is truly valuable and relevant to your organization&#039;s SOA efforts?&lt;p&gt;&lt;a href=&quot;http://ericmarks.sys-con.com/node/175376&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 29 Jan 2006 10:00:00 EST</pubDate>
 <guid isPermaLink="true">http://ericmarks.sys-con.com/node/175376</guid>
 <comments>http://ericmarks.sys-con.com/node/175376#feedback</comments>
</item>
</channel>
</rss>
