| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What is the future for WebSphere MQ Workflow? |
« View previous topic :: View next topic » |
| Author |
Message
|
| ucbus1 |
 Posted: Thu May 26, 2005 7:46 am Post subject: What is the future for WebSphere MQ Workflow? |
 |
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
The otherday my manager was saying BPM would deliver much more than Workflow. We are using MQ Workflow and bit perplexed.
Hence my question, What is the future for WebSphere MQ Workflow?
Is BPM going to take over Workflow? Is IBM going to have a BPM suite that encompasses MQ Workflow?
Has any one got any idea about any of the BPM tools? If so ,could you please share?
My interest is basically, Do I have to start learning BPM and get out from Workflow? |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu May 26, 2005 8:13 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I think we need to know what it is that you mean by BPM.
It is my opinion that workflow will never go away. It will evolve of course, but the technology is too valuable to just stop using it.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Thu May 26, 2005 8:41 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
BPM stands for Buisness Process Management.
Here is what I have seen on one of the documents by softwarefutures.com
| Quote: |
1) What is the difference between workflow and BPM?
While often treated synonymously, BPM and workflow are,
in fact, two distinct and separate entities whose differences
are more than academic.
Workflow is concerned with the application-specific
sequencing of activities via predefined instruction sets,
involving either or both automated procedures (softwarebased)
and manual activities (people work). Business
Process Management is concerned with the definition,
execution and management of business processes defined
independently of any single application. BPM is a superset
of workflow, further differentiated by the ability to
coordinate activities across multiple applications with
fine grain control.
Workflow, in the context of BPM, will be seen as a common
feature and component of most BPM solutions. It is used
as a sub-component of BPM and is commonly used to
deliver BPM solutions. Workflow can be defined quite
simply as a term used to describe the tasks and procedural
steps that organizations or the people involved require to
input, process, and output information. Workflow provides
the tools needed for each step in the business process.
The scope of BPM is also much broader than that of
traditional workflow tools. Handling workflow paths is
only one component of a robust BPM solution – other
components include real-time process monitoring, capturing
of process and business data for analysis, process modeling
and simulation. In addition, the architecture of a strong
BPM solution is very service and orchestration oriented
such that it is very easy to leverage web services, .NET,
and Java components and execute these services within
the context and control of a business process. |
|
|
| Back to top |
|
|
| jmac |
| Posted: Thu May 26, 2005 8:57 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The way I would sum up the definition you provide is that BPM is the analysis part and Workflow is the engine that provides for the automation of the process.
Given this definition, I would say that a business analyst only has a need to know BPM and a Workflow specialist needs to understand BPM and the particular engine for which they are implementing.
Bottom line, I do not disagree with the statement that BPM will deliver more than Workflow.
It is my opinion that when implemented properly you have a well developed Business Process developed using the BPM tool of your choice, that is combined with properly architected workflow solution in the Workflow engine of your choice.
It is my opinion that any good Workflow developer has to have a fairly deep understanding of the process model. They will care about different things in the model than the Business Anaylst would. To use IBM's Modeler 4.2.4 as an example. As a Workflow specialist I do not really care much about the costs that are assigned to all of the resources, and the simulation really does not do much for me from an MQWF point of view. However, I care deeply about the data mappings, and all of the underlying settings in the activities, where the Business Analyst would probably not care about those things at all.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
