In the last year, my focus has primarily been on system integrations. Now, my usual domain is the development of long lived packaged software, and it is quite a different thinking hat which you need to wear when doing integrations. And the interesting thing regarding my new “Integration Thinking Hat”, is the unexpected complexity.

But why is that so unexpected you might ask. After all, integrating Java and dot NET and SOAP and SQL and Oracle and MQ and all of those 3 letter things are supposed to be complex.

And the answer to the above is that the source of the complexity is not (as I expected) technological, but of human origin.

When we integrate a mainframe based system with a Wintel system, traditionally it used to be a complex affair. Web services and SOA principles have pretty much brought this from a dark art form to the stage where it is a relatively easy and repeatable process. You publish a service definition which describes inputs, outputs and actions. In simple terms you know what to expect and very important, also what not to expect.

Contrasting that with the human communication element, you need quite a bit of human interactions in order to start understanding what both sides of the equation can expect from the planned integration. In theory it is possible to come to a 100% understanding (in classroom based exercises anyway), but you will probably get to a 70% mutual understanding, and from there onwards pure ignorance will provide the rest. Where the horrors starts haunting you is in the area where all parties involved need to understand what NOT to expect.

So, we need to come up with a WSDL type human communication around integrations. Which we all know will not work, as we are more intelligent than our silicon based friends (machines), and therefore we make our own interpretations. (Which is our advantages over the machines, but in this case, also somewhat of a disadvantage) We are in need of an ubiquitous language which all parties involved will understand to the point where we all interpret every single word, sentence and model in exactly the same way.

So, while evolution helps us out with the above (probably by all system integrators having a war and leaving only a nucleus group alive), I have found the TOGAF enterprise architecture framework to be a great help in providing the ability for the different parties and stakeholders to reach a reasonable level of shared understanding . The framework provides a relatively simple way to connect business activities the data and technology. In summary, the framework provides a way to connect the following levels

•Business Processes

•Information

•Data

•Applications

•Technology Infrastructure

This helps you understand what impact the intricate interrelationships here – iow, what will happen to the enterprise if the data field “Address” of a client now needs to have 600 characters instead of 100, what process, information flows, applications and infrastructure components will be involved

It is a framework, and hence you can adopt and adapt to suite your needs, and an entire Enterprise Architecture exercise is not needed before you can start with your integration exercise.. Check it out at Open Group