Building the Core – Enterprise Business Flows - Applied SOA Patterns on the Oracle Platform - page 215

Building the decision table for Agnostic Composition Controller
The earlier table is similar to any table you can create for this purpose (in Excel, for in-
stance). There are two parts. In the first part, using basket LOVs, we define the conditions
provided by inbound parameters such as productType: VOIP ; businessEvent: Up-
dateOrderStatus ; country: BR (for Brazil); and affiliate: BraTello (for Brazil Telephon-
ic). In the second part, we define actions, which in our case is the filename of the Execu-
tion Plan. Needless to say that this file is stored in MDS, and we know the actual path; it's
part of the deployment profile and configuration plans. You do not have to describe the
whole complexity of business rules and conditions from the start; taking one small step at
a time is important, and we would really like you to repeat it. Obviously, the execution
plans and their names will emerge gradually (and not exactly slowly) along the way of the
functional decomposition process together with logic centralization and service refactor-
ing (all of them are SOA patterns, representing the common sense we mentioned many
times).
Apparently, the ultimate outcome of this practical exercise would be the establishment of
a concrete Service Inventory, which is currently maintained on MDS. We are not going to
discuss the pros and cons of this realization now; we're just jumping ahead, but we can as-