High. Note that emerging
standards such as BPEL4WS
and BPML are already more
expressive than most workflow
languages. |
Will ease application
integration, including
process integration (integration
of processes by processes).
Will ease extranet based
process developments and
deployement. Alltogether
may promote radically
use of process management
technologies through mutual
propagation. |
It has already been
massive. Many people see
WS Choreography as the
only real way to view
BPM/A now. I discagree,
I think over time people
will see WS as an enabling
piece of an overall effort
to a process oriented
approach to application
development. WS provide
a technical soution to
software integration.
Many BPM/A tools will
be heavily oriented toward
WS Choreography but there
is far more to successful
BPM strategy than WebServices. |
Web-services will play
a dramatic role in the
evolution of workflow
as organizations will
look towards the lower
cost adaptive nature of
workflow rather than the
more costly and rigid
framework of ERP to connect
inter-organizational processes.
Web-services has the potential
to bring workflow to the
forefront of IS strategy |
Web Services will reduce
the importance of locations.
This will further enable
distributed workflows. |
- Will force us to
redesign the modularity
and structure of business
processes.
- Integration will
become more essential
than flexibility as
software components
get more granular
and smaller
|
light-weight workflow
systems will emerge gluing
web services together
flexibly by the end user |
see above |
Minimal. The transparency
of the applications, and
the company's modus operandi
is the bigest stumbling
block. Web services based
in UIs will become more
important as companies
invest more in portals
and Web applications. |
Web Services will be
the standard technology
to invoke actions in distributed
scenarios. They will marginalise
remote object services. |
That the processes
will extend to parties
outside the company if
needed. |
As already indicated
above, web service technology
can be the basis for inter-organizational
workflow management (see
our recent IBM research
report that actually discusses
this topic). |
It will place higher
demands and more automation |
Process Automation
will survive with or without
Web Services - so I see
this question the other
way around - what will
Process Technology do
for web services - I see
the only way that Web
Services will flourish
and live up to its potential
outside of the fire wall
is to be part of a well
defined, well constructed
and controlled set of
business processes |
The main impact of
Web Services is market
hype. EDI was a perfectly
acceptable substitute
that has been around for
20 years. Web Services
is a far BETTER implementation,
and has features beyond
what EDI can offer, BUT
the difficult problems
to B2B and B2C interactions
is not solved by simply
saying that you "have
web services". |
Web services are really
inter-organizational workflows.
Workflow technology will
play an important role
in facilitating web services.
|
important as technical
infrastructure. |
No impact since to
date it is not picked
up. Once it will be picked
up, it goes through a
maturity cycle that will
cost a lot and take a
long time. Web services
are not a solution, but
a technology. |