An illustration to http://www.ebizq.net/blogs/ebizq_forum/2011/02/how-big-is-a-process.php
From my book "Improving enterprise business process management systems":
We recommend introducing control-oriented coordination using a step-by-step approach
via the “eclipse” pattern (see figure 5.6). At first, we “cover” only a tiny area of the whole process. Usually we start with the intra-application coordination, because this part of IT is considered as boring and not very rewarding. The first fragment of explicit coordination may be quite primitive; it is a duplication of some existing functionality which is just eclipsed by this process. Then we introduce more and more fragments. With time, we cover bigger and bigger areas by explicit coordination of existing fragments.
Figure 5.6 Use of the “eclipse” pattern for making coordination explicit
Thanks,
AS
From my book "Improving enterprise business process management systems":
We recommend introducing control-oriented coordination using a step-by-step approach
via the “eclipse” pattern (see figure 5.6). At first, we “cover” only a tiny area of the whole process. Usually we start with the intra-application coordination, because this part of IT is considered as boring and not very rewarding. The first fragment of explicit coordination may be quite primitive; it is a duplication of some existing functionality which is just eclipsed by this process. Then we introduce more and more fragments. With time, we cover bigger and bigger areas by explicit coordination of existing fragments.
Figure 5.6 Use of the “eclipse” pattern for making coordination explicit
Thanks,
AS
Posts
No comments:
Post a Comment