<?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: BPMN and ITIL</title>
	<atom:link href="http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/</link>
	<description>Bruce Silver's blog on business process management</description>
	<pubDate>Wed, 07 Jan 2009 17:03:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: kewbss</title>
		<link>http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/comment-page-1/#comment-573</link>
		<dc:creator>kewbss</dc:creator>
		<pubDate>Tue, 20 Mar 2007 04:47:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/#comment-573</guid>
		<description>Bruce,

I came across this post (again) while thinking about Exercise 15 of the training ... I was planning to do an ITIL process.

FWIW I think your 'best practice' approach is an improvement on the diagram above. Labelling of the message activity clearly shows its purpose ... the flow to an End Message event is redundant and adds clutter.

For a novice at least, it takes a conscious effort to realise that this end event does not actually signal the end of the sub-process ... arrival of a message at the parallel intermediate message event is the 'critical path' as far as process completion is concerned.</description>
		<content:encoded><![CDATA[<p>Bruce,</p>
<p>I came across this post (again) while thinking about Exercise 15 of the training &#8230; I was planning to do an ITIL process.</p>
<p>FWIW I think your &#8216;best practice&#8217; approach is an improvement on the diagram above. Labelling of the message activity clearly shows its purpose &#8230; the flow to an End Message event is redundant and adds clutter.</p>
<p>For a novice at least, it takes a conscious effort to realise that this end event does not actually signal the end of the sub-process &#8230; arrival of a message at the parallel intermediate message event is the &#8216;critical path&#8217; as far as process completion is concerned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Integrity Management Solutions</title>
		<link>http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/comment-page-1/#comment-347</link>
		<dc:creator>Integrity Management Solutions</dc:creator>
		<pubDate>Mon, 18 Dec 2006 20:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/#comment-347</guid>
		<description>&lt;strong&gt;Process Standards and Technology...&lt;/strong&gt;

When implementing Service Support and Delivery processes it is very important to document the process with process diagrams and textual information. However, when creating the process diagrams the format of the diagram is at the discretion of the autho...</description>
		<content:encoded><![CDATA[<p><strong>Process Standards and Technology&#8230;</strong></p>
<p>When implementing Service Support and Delivery processes it is very important to document the process with process diagrams and textual information. However, when creating the process diagrams the format of the diagram is at the discretion of the autho&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bruce</title>
		<link>http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/comment-page-1/#comment-321</link>
		<dc:creator>bruce</dc:creator>
		<pubDate>Mon, 11 Dec 2006 05:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/#comment-321</guid>
		<description>Marlon,
I think I see the piece you are objecting to.  I tried to explain it in my post, but perhaps it is incorrect.  I could have used a message intermediate event to send the Technical RFC, but my convention is to reserve that symbol for a receiving event, and use a Task to indicate the "work" done to create the event and an end event to actually send it (e.g. attach a message flow in choreography diagram), so that the pairing of event labels would be obvious.  Maybe that implies that the event is sent twice?  That was not my intention.  Does the name of the task or the little mail icon on it mean an event is sent?  It sounds like my convention may not be best practice, but I don't think actually incorrect.</description>
		<content:encoded><![CDATA[<p>Marlon,<br />
I think I see the piece you are objecting to.  I tried to explain it in my post, but perhaps it is incorrect.  I could have used a message intermediate event to send the Technical RFC, but my convention is to reserve that symbol for a receiving event, and use a Task to indicate the &#8220;work&#8221; done to create the event and an end event to actually send it (e.g. attach a message flow in choreography diagram), so that the pairing of event labels would be obvious.  Maybe that implies that the event is sent twice?  That was not my intention.  Does the name of the task or the little mail icon on it mean an event is sent?  It sounds like my convention may not be best practice, but I don&#8217;t think actually incorrect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marlon_dumas</title>
		<link>http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/comment-page-1/#comment-317</link>
		<dc:creator>marlon_dumas</dc:creator>
		<pubDate>Mon, 11 Dec 2006 01:36:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.brsilver.com/wordpress/2006/12/07/bpmn-and-itil/#comment-317</guid>
		<description>Bruce,
You have a history of posting BPMN models with all sorts of mistakes. Well, I believe now it's your turn to step into the dock as there seems to be a bug in your model (although minor). Inside the muti-instance sub-process, after creating the technical RFC, the sub-process sends this technical RFC (to the change management process I assume). But after sending the technical RFC, the process then sends again an RFC (through the 'end message event' labelled "RFC"). So the (technical) RFC is sent twice!</description>
		<content:encoded><![CDATA[<p>Bruce,<br />
You have a history of posting BPMN models with all sorts of mistakes. Well, I believe now it&#8217;s your turn to step into the dock as there seems to be a bug in your model (although minor). Inside the muti-instance sub-process, after creating the technical RFC, the sub-process sends this technical RFC (to the change management process I assume). But after sending the technical RFC, the process then sends again an RFC (through the &#8216;end message event&#8217; labelled &#8220;RFC&#8221;). So the (technical) RFC is sent twice!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
