Life is Hard. Life is Hard… Then You Die Life is Hard… Then You Die…
Interoperability is Hard
-
Upload
lacey-trebaol -
Category
Engineering
-
view
164 -
download
0
Transcript of Interoperability is Hard
Once upon a *me there was a guy named Joe.
Joe had 4 systems that worked together perfectly; they worked as 1 System of Systems.
One day, Joe decided that he needed to add a new capability to his System of Systems, and so Joe gave the components to a
system integrator, and with them, a simple request: Add the new capability to the exis*ng SOS.
The system integra*on team tackled the task, and when the effort was complete they delivered the
enhanced SOS to Joe.
Everything was going well un*l Joe added another capability and a few data types to the equa*on. The result: interoperability was lost.
So Joe called the system integrator, said a few choice words, and asked if he could fix it
The System Integrator was confident he could right the wrongs. He explained to Joe that there were 2
ways he could go about doing this.
Op*on 1. Yes, hire him again and for *me & $ he would make it work, yet again. Sort of.
Sort of? The fix only lasts un*l Joe wants to make another change to any element of his
system. Then we do this all over again.
Op*on 2. Joe could go online and search for a magic ball. The magic ball
would allow Joe to see into the future so he could determine all of the capabili*es he would ever require! Then it was just 1 final integra*on effort and Joe’s SOS would work forever. Perfectly.
Annoyed and confused, Joe decided he needed to think of a new approach.
Interoperability apparently wasn’t simple.
THE PROBLEM
Achieving interoperability is hard for so many reasons, but integra*on issues caused by a lack of interoperability being built into the system’s architectural framework, as well as the specifica*on of rigorously defined standards outlining methods and means for exploi*ng this, are usually to blame.