evelIo orks③ ibm. com/developerWorks While Business Modeler supports the definition of business rules to control the outcome of decisions, business rules that govern the dynamic selection of endpoints must be defined elsewhere, for example, in Business Services Fabric. For this reason, we propose that the rules for dynamic processing be documented within Business Modeler as annotations(shown in Figure 5) Figure 5. Abstract representation of process variability 8 proces order 5e processorder. ccemM] Amend order t Amend order wim Auharizaton te candd orde 自 Anson Eno bo Ex abstract wew of sAcrae G地msak eR来T ● We toco Vacate Order Ful Ordr d For Loop nd ode statusbgfieas o. erer Code. 222 Amend order we setuNotfxabon errorcode 999 Cancel Order Proposed process for end-to-end representation Because a high-level business process(one that contains other proce components) has flows that will dynamically vary, there isn't one single end-to-end view of the process. Such a view can, however, be depicted in an abstract way. We propose the representation pattern shown in Figure 5 to enable the visualisation of process variability In this diagram Validate Order, handle Exception and Fulfil Order constitute the ( trivial)end-to-end process, while Amend Order, Amend Order with Authorization and Cancel Orders are the possible implementations of hande Exception. The Model business processes for flexibility and re-use: A component-oriented approach Page 6 of 11 Copyright IBM Corporation 2009. All rights reservedWhile Business Modeler supports the definition of business rules to control the outcome of decisions, business rules that govern the dynamic selection of endpoints must be defined elsewhere, for example, in Business Services Fabric. For this reason, we propose that the rules for dynamic processing be documented within Business Modeler as annotations (shown in Figure 5). Figure 5. Abstract representation of process variability Proposed process for end-to-end representation Because a high-level business process (one that contains other process components) has flows that will dynamically vary, there isn’t one single end-to-end view of the process. Such a view can, however, be depicted in an abstract way. We propose the representation pattern shown in Figure 5 to enable the visualisation of process variability. In this diagram Validate Order, handleException and Fulfil Order constitute the (trivial) end-to-end process, while Amend Order, Amend Order with Authorization and Cancel Orders are the possible implementations of handleException. The developerWorks® ibm.com/developerWorks Model business processes for flexibility and re-use: A component-oriented approach Page 6 of 11 © Copyright IBM Corporation 2009. All rights reserved