Database Reference
In-Depth Information
capabilities that is desirable for the expected level of reuse. What is inside the component,
that is, its technical implementation, is completely out of discussion, and it's up to the
technical lead to decide which way to go.
Thus, various technical platforms can leverage their best sides where it's needed (or where
it's inevitable due to specific skill sets in place of physical implementation) by staying in-
terconnected without affecting each other's premises and project deadlines. Finally, the
federated approach gives the opportunity to choose the best products from various
vendors and assemble them in the business flows, abstracted and architected in the previ-
ous steps. Of course, these products must stay in compliance with the interface specifica-
tions and the operational requirements that we put in place. The opposite is also true, that
is, setting standards from our business standpoint will help vendors to adjust their
products and offerings in such a way that integration efforts will be minimal.
So, it's all about money, as the logical sequence mentioned earlier demonstrates. Have you
noticed that in that logical exercise, we didn't use the abbreviation SOA at all? So far, we
are just trying to convert the previously presented list of intentions derived from various
project-design documents, such as
request for informations
(
RFIs
) and
request for pro-
posals
(
RFPs
), into a concise list of benefits. Our next step will be to assess how attain-
able they are. Although that will be the purpose of the entire topic, the key criterion will
be defined here shortly. Before proceeding with this, we would like to stress again that the
basic terminology around business benefits and design characteristics is based on the
widely accepted structure presented by Thomas Erl as mentioned earlier. Also, we do not
want to reinvent the wheel for the thousandth time and then participate in terminology
wars, which will lead us nowhere. Thomas Erl has described the obvious benefits that we
would like to achieve in a logical sequence, and you can see the proposed sequence for
implementing the listed-out goals in the following table:
Goals and benefits
Common solutions' requirements
Increased ROI
1, 8
Reduced IT burden (low TCO)
1, 3
Increased organizational agility (shorter time to market)
4, 8, 10
Increased intrinsic interoperability (reduce integration efforts) 2, 4, 6
Search WWH ::
Custom Search