Comments on: BPMN Diagrams – Intermediate Multiple Events http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/comment-page-1/#comment-346147 Scott Sehlhorst Wed, 16 Apr 2008 02:41:23 +0000 http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/#comment-346147 Hey Mario, Thanks, and welcome to Tyner Blain! I hope this has been helpful for you and your team! If you see any mistakes or have any questions on any of the articles, please don't hesitate to ask. Hey Mario,

Thanks, and welcome to Tyner Blain! I hope this has been helpful for you and your team! If you see any mistakes or have any questions on any of the articles, please don’t hesitate to ask.

]]> By: Mario E. Cavieres http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/comment-page-1/#comment-344262 Mario E. Cavieres Fri, 11 Apr 2008 15:24:24 +0000 http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/#comment-344262 Thanks to everybody in Tynerblain for understand better BPMN mainly about the intermediate events with examples. I work as a project leader and my company is implemented BPMN. Also we are analizing the process of "the day trader" example, but finaly our target was the use of Multiple Intermediate event. Greetings from Chile. Thanks to everybody in Tynerblain for understand better BPMN mainly about the intermediate events with examples.

I work as a project leader and my company is implemented BPMN.

Also we are analizing the process of “the day trader” example, but finaly our target was the use of Multiple Intermediate event.

Greetings from Chile.

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/comment-page-1/#comment-171418 Scott Sehlhorst Wed, 31 Oct 2007 03:33:28 +0000 http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/#comment-171418 The following comment is from Mike, who emailed me offline. Sorry about the difficulties in posting a comment Mike, thanks VERY much for making the extra effort! Hi Scott, I tried to leave a comment on your Intermediate Multiple Events article, but got a wordpress error. This is what I tried to post: Thanks for your informative series of articles on BPMN. I do however have some problems with Day Trader diagram: * The "Watch Stock" task is duplicated and with different outcomes. Just an inconsistency which can be easily resolved. * The "Watch Stock" task(s) have multiple exit flows. Is this "legal" or should they go through some Gateway? * The Day Trader process can end, as it stands, directly from Watch Stock immediately, now, or never. I do not mean to be hyper-critical - just pointing out that is not always easy to get these things right. Maybe some tool to check diagrams for "syntax errors" would be useful. I offer my view - attached - of the Day Trader process which resolves the inconsistencies as I see them. (Thanks for the Visio template!) By the way, my view of the process allows Day Traders to short stocks too. BPMN is new to me, and I have probably made mistakes too! Anyway, thanks again, and feel free to use my diagram in any way you like. Mike [Scott again: Here's the link to Mike's improved version: http://sehlhorst.smugmug.com/photos/215288891-O.gif ] The following comment is from Mike, who emailed me offline. Sorry about the difficulties in posting a comment Mike, thanks VERY much for making the extra effort!

Hi Scott,

I tried to leave a comment on your Intermediate Multiple Events article, but got a wordpress error.

This is what I tried to post:

Thanks for your informative series of articles on BPMN.
I do however have some problems with Day Trader diagram:

* The “Watch Stock” task is duplicated and with different outcomes. Just an inconsistency which can be easily resolved.
* The “Watch Stock” task(s) have multiple exit flows. Is this “legal” or should they go through some Gateway?
* The Day Trader process can end, as it stands, directly from Watch Stock immediately, now, or never.

I do not mean to be hyper-critical – just pointing out that is not always easy to get these things right. Maybe some tool to check diagrams for “syntax errors” would be useful.

I offer my view – attached – of the Day Trader process which resolves the inconsistencies as I see them. (Thanks for the Visio template!)
By the way, my view of the process allows Day Traders to short stocks too.

BPMN is new to me, and I have probably made mistakes too!

Anyway, thanks again, and feel free to use my diagram in any way you like.

Mike

[Scott again: Here's the link to Mike's improved version: http://sehlhorst.smugmug.com/photos/215288891-O.gif ]

]]> By: Scott Sehlhorst http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/comment-page-1/#comment-55499 Scott Sehlhorst Fri, 13 Oct 2006 14:22:30 +0000 http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/#comment-55499 Soumya, Welcome to Tyner Blain, and thanks for reading and commenting! I actually posted an article about that last week - <a href="http://tynerblain.com/blog/2006/09/28/estimating-as-is/" title="Estimating process documentation" rel="nofollow">Estimating the documentation of an as-is process</a>. For a to-be process, I would quickly comment that it will take as much time as you allocate. Greater time = greater depth of analysis. Less time = shallow analysis. Depending on the goals of the migration project, you will lean towards one or the other. To-be process modeling/documentation can take anywhere from 50% of the as-is time to 500% or more. You have to reverse the approach for to-be, and budget an amount of time, then do as much optimization/invention as you can within that box. Soumya,

Welcome to Tyner Blain, and thanks for reading and commenting! I actually posted an article about that last week – Estimating the documentation of an as-is process.

For a to-be process, I would quickly comment that it will take as much time as you allocate. Greater time = greater depth of analysis. Less time = shallow analysis. Depending on the goals of the migration project, you will lean towards one or the other. To-be process modeling/documentation can take anywhere from 50% of the as-is time to 500% or more. You have to reverse the approach for to-be, and budget an amount of time, then do as much optimization/invention as you can within that box.

]]> By: Soumya http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/comment-page-1/#comment-55492 Soumya Fri, 13 Oct 2006 06:04:11 +0000 http://tynerblain.com/blog/2006/09/13/bpmn-intermediate-multiple/#comment-55492 Hi! I got the link to your blog from Sandy Kemsley's blog. I work as a Business Analyst and have managed to successfully use BPMN for modeling processes at a couple of client projects. Are you aware of any estimation model for estimating the efforts in a process modeling exercise? If not a formal model, can you please comment on some parameters (perhaps the process complexity, the analyst's familiarity of the domain,level of existing documentation etc.) that can be used to arrive at the efforts required in mapping processes? Hi!
I got the link to your blog from Sandy Kemsley’s blog. I work as a Business Analyst and have managed to successfully use BPMN for modeling processes at a couple of client projects. Are you aware of any estimation model for estimating the efforts in a process modeling exercise? If not a formal model, can you please comment on some parameters (perhaps the process complexity, the analyst’s familiarity of the domain,level of existing documentation etc.) that can be used to arrive at the efforts required in mapping processes?

]]>