<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: BPM and SOA</title>
	<atom:link href="http://friends.praxeme.org/2009/09/bpm-and-soa/feed/" rel="self" type="application/rss+xml" />
	<link>http://friends.praxeme.org/2009/09/bpm-and-soa/</link>
	<description>We love cheesecake...</description>
	<lastBuildDate>Wed, 12 Oct 2011 11:57:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: DVAU</title>
		<link>http://friends.praxeme.org/2009/09/bpm-and-soa/comment-page-1/#comment-13</link>
		<dc:creator>DVAU</dc:creator>
		<pubDate>Sun, 27 Sep 2009 14:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://friends.praxeme.org/?p=337#comment-13</guid>
		<description>The dotted arrow from &quot;Logical Aspect&quot; to &quot;Pragmatic aspect&quot; allows and summarizes a dozen of derivation rules. Thanks to these rules, a portion of the logical architecture is populated almost automatically and with a guarantee of alignment.
In this diagram, the package symbol stands for an aspect of the Enterprise System. The picture is an extract from the Enterprise System Topology, the methodological framework which is at the core of the Praxeme method. Regarding SOA, this picture shows that:
* BPM is important as an input for an SOA design;
* it is not enough: we need another starting point which lays in the semantic aspect, the place of the Business Objects.
The semantic modeling approach greatly contributes to the success of the SOA appraoch, especially in case of an IT system overhaul.</description>
		<content:encoded><![CDATA[<p>The dotted arrow from &#8220;Logical Aspect&#8221; to &#8220;Pragmatic aspect&#8221; allows and summarizes a dozen of derivation rules. Thanks to these rules, a portion of the logical architecture is populated almost automatically and with a guarantee of alignment.<br />
In this diagram, the package symbol stands for an aspect of the Enterprise System. The picture is an extract from the Enterprise System Topology, the methodological framework which is at the core of the Praxeme method. Regarding SOA, this picture shows that:<br />
* BPM is important as an input for an SOA design;<br />
* it is not enough: we need another starting point which lays in the semantic aspect, the place of the Business Objects.<br />
The semantic modeling approach greatly contributes to the success of the SOA appraoch, especially in case of an IT system overhaul.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

