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

Establishing a Service Inventory
To reuse something, first we need to establish the easily accessible inventory of reusable
entities and make sure that these entities are truly reusable. From Chapter 1 , SOA Ecosys-
tem - Interconnected Principles, Patterns, and Frameworks , you are aware of the eight
principles we must follow to achieve the four desirable characteristics. Simply put, it is
your (any) solution's evaluation spreadsheet that contains eight rows and four columns for
each component you are planning to evaluate. Surely, you can place your requirements at
the top, but bear in mind the tangibility of your criteria. Obviously, you will have to pay
some price for reusability as well. You need to balance your tactical and strategical goals
wisely, but what is obvious from the presented telecom example is that strategic targets
were sacrificed.
Initial analysis
Your first task as a lead architect is to meet the development team and review their design
of the new Order Management System service. You must evaluate the possibility of im-
proving the current Orchestration layer in order to reduce the operational costs (firstly by
minimization of service installations). Another obvious choice would be to scrap the Order-
oriented orchestration entirely and select a commercial product, Oracle Communications
Order and Service Management (OSM) , for instance.
Operations and Business System Support ( OSS / BSS ) form the core of the telecommu-
nication domain, handling custom relations management ( CRM ) and order management
and procurement among other functionalities.
TMForum ( www.tmforum.org ) is the main standardization authority in telecommunication.
Its eTOM specification was used for implementing the first release of the Pan-American
service layer, suitable for providing a unified order management.
Physical realizations presented by three tightly coupled Orchestrated services are as fol-
lows:
• COM : Commercial order management
• TOM : Technical order management
• SPC : Service provisioning
Obviously, the realization is on BPEL, as the development was initially carried out on the
previous Version 10 g and then migrated and refactored for 11 g .