<?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: BPEL for Process Modeling Sucks</title>
	<atom:link href="http://www.procper.com/bpel-for-process-modeling-sucks/feed" rel="self" type="application/rss+xml" />
	<link>http://www.procper.com/bpel-for-process-modeling-sucks</link>
	<description>processes visualization</description>
	<lastBuildDate>Tue, 17 Mar 2009 09:16:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Owens</title>
		<link>http://www.procper.com/bpel-for-process-modeling-sucks/comment-page-1#comment-9</link>
		<dc:creator>John Owens</dc:creator>
		<pubDate>Tue, 17 Mar 2009 09:16:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.procper.com/?p=124#comment-9</guid>
		<description>I totally agree with your hammer analogy.  Far too often new fads are adopted because they are seen as the panacea for all of the ills of the IT and the Process Modeling worlds and a &quot;one hammer fits all approach&quot; is taken.

These &quot;advanced&quot; are adopted because nobody knows how the existing mess has occurred nor has the will or the skills to fix it. So, if an automated approach comes along, Eureka! Technology replaces thinking!

Too often IT wants to claim processes as it own in order to have control over the business.  The business too often abdicates responsibility to IT and then blames them when they fail to deliver.

The emergence of &quot;process centric&quot; business modeling over recent years has compounded the problem with everybody modeling everything that happens in a business as a &quot;process&quot;.

&lt;p&gt;Not everything that happens in a business is a process!  STOP MODELING IT AS SUCH.  Process modeling misses out up to 30% of essential business activity.&lt;/p&gt;

&lt;p&gt;Most &quot;process&quot; modeling tools are only suitable for modeling procedure.  This is not recognized as a problem by analysts and business managers who do not know the difference, but it is a big one.  Procedure can alter significantly over time within a process, due to in changes in technology, organization, etc.

This is where approaches such as BPEL are seen as solutions.  Because procedure has been modeled in place of process, changes are happening all the time and so there is a need to update things all the time and so a need for something like BPEL.

BPMN will not solve the problem either.  It is only a notation and can be used to model a faulty process or a good process.

Stop modeling the wrong thing.  Stop modeling complexity an trying to control it.  Model simplicity by modeling the Core activities of the business – Business Functions.  This will not only bring simplicity, but power and elegance too.

The Integrated Modeling Method [sincere plug] enables this simplicity and power to be achieved with far less effort and greater speed.</description>
		<content:encoded><![CDATA[<p>I totally agree with your hammer analogy.  Far too often new fads are adopted because they are seen as the panacea for all of the ills of the IT and the Process Modeling worlds and a &#8220;one hammer fits all approach&#8221; is taken.</p>
<p>These &#8220;advanced&#8221; are adopted because nobody knows how the existing mess has occurred nor has the will or the skills to fix it. So, if an automated approach comes along, Eureka! Technology replaces thinking!</p>
<p>Too often IT wants to claim processes as it own in order to have control over the business.  The business too often abdicates responsibility to IT and then blames them when they fail to deliver.</p>
<p>The emergence of &#8220;process centric&#8221; business modeling over recent years has compounded the problem with everybody modeling everything that happens in a business as a &#8220;process&#8221;.</p>
<p>Not everything that happens in a business is a process!  STOP MODELING IT AS SUCH.  Process modeling misses out up to 30% of essential business activity.</p>
<p>Most &#8220;process&#8221; modeling tools are only suitable for modeling procedure.  This is not recognized as a problem by analysts and business managers who do not know the difference, but it is a big one.  Procedure can alter significantly over time within a process, due to in changes in technology, organization, etc.</p>
<p>This is where approaches such as BPEL are seen as solutions.  Because procedure has been modeled in place of process, changes are happening all the time and so there is a need to update things all the time and so a need for something like BPEL.</p>
<p>BPMN will not solve the problem either.  It is only a notation and can be used to model a faulty process or a good process.</p>
<p>Stop modeling the wrong thing.  Stop modeling complexity an trying to control it.  Model simplicity by modeling the Core activities of the business – Business Functions.  This will not only bring simplicity, but power and elegance too.</p>
<p>The Integrated Modeling Method [sincere plug] enables this simplicity and power to be achieved with far less effort and greater speed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
