Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
140 Chapter 7 Work<strong>in</strong>g from <strong>Your</strong> Processes to the <strong>Cloud</strong>s<br />
Us<strong>in</strong>g these assumptions, we could def<strong>in</strong>e “Cut parts” as a process that is<br />
kicked off by a sales event from the sales system that is posted to the manufactur<strong>in</strong>g<br />
system. We can then decompose that “Cut parts” process down to<br />
additional subprocesses if needed (we are not go<strong>in</strong>g to do that here). After<br />
the parts are cut, we let manufactur<strong>in</strong>g know that the process is complete,<br />
<strong>and</strong> it <strong>in</strong> turn kicks off the process to assemble the parts. Once that is complete,<br />
we return <strong>in</strong>formation to the manufactur<strong>in</strong>g system, <strong>and</strong> it kicks off<br />
the f<strong>in</strong>ish<strong>in</strong>g process<strong>in</strong>g. Once that occurs, the <strong>in</strong>ventory system is updated<br />
with the <strong>in</strong>formation on the completed product, <strong>and</strong> the sales system is updated<br />
with the fact that the product is complete <strong>and</strong> ready for shipment.<br />
The key idea is that the higher-level processes, the meta-application <strong>in</strong> a<br />
sense, drive the processes <strong>and</strong> coord<strong>in</strong>ate the exchange of <strong>in</strong>formation between<br />
the source <strong>and</strong> target systems. These processes leverage service <strong>in</strong>terfaces<br />
<strong>and</strong> abstract the encapsulated processes up to a higher-level set of<br />
processes <strong>in</strong> support of this bus<strong>in</strong>ess event.<br />
Although this is a very simplistic example, it is nonetheless a good depiction<br />
of the higher-level activities <strong>and</strong> concepts of BPM.<br />
BPM is the science <strong>and</strong> mechanism of manag<strong>in</strong>g the movement of data<br />
<strong>and</strong> the <strong>in</strong>vocation of services <strong>in</strong> the correct <strong>and</strong> proper order to support the<br />
management <strong>and</strong> execution of common processes that exist <strong>in</strong> <strong>and</strong> between<br />
organizations <strong>and</strong> <strong>in</strong>ternal applications. BPM provides another layer of easily<br />
def<strong>in</strong>ed <strong>and</strong> centrally managed processes that exist on top of an exist<strong>in</strong>g set<br />
of processes, application services, <strong>and</strong> data with<strong>in</strong> any set of applications.<br />
The goal of our discussion is to def<strong>in</strong>e a mechanism to b<strong>in</strong>d relevant processes<br />
that exist between <strong>in</strong>ternal <strong>and</strong> external systems <strong>in</strong> order to support<br />
the flow of <strong>in</strong>formation <strong>and</strong> logic between them, thus maximiz<strong>in</strong>g their mutual<br />
value. Moreover, we are look<strong>in</strong>g to def<strong>in</strong>e a common, agreed-upon process<br />
that exists between many organizations, has visibility <strong>in</strong>to any number<br />
of <strong>in</strong>tegrated systems, <strong>and</strong> is visible to any system that needs to leverage the<br />
common process model.<br />
Underst<strong>and</strong><strong>in</strong>g the Semantics<br />
As we move <strong>in</strong>to the world of BPM, we f<strong>in</strong>d that the names for particular types<br />
of technologies <strong>and</strong> approaches can be somewhat confus<strong>in</strong>g. As we mentioned