Any two open system interacting with each other are naturally going to have some kind of cause and effect relation between each other.
Organizations are getting more and more aware of the impact or damage that dependencies between multiple components of their system can cause on their business. Organizations are now trying to get themselves trained on analyzing the impact and potential risk of mutual dependencies between their components, for example putting too much responsibility on one personal can create a bottleneck in the whole delivery process of their organization if the personal decides to leave the organization without transferring the knowledge and experience he has gained over the years.
Experience of facing problems of inter dependencies has led to the concept of Common Maturity Model in IT companies. A common maturity models enforce and ensure that there is less scope of heroism and everything is process oriented, thereby eliminating any chance of a personal becoming bottleneck.
Now the question is, how do you detect an interdependency in a system? You need to understand the roles of different components of a system. It includes analyzing all the components to see if other components of the systems uses this system as a tool. Multiple components in the system can play the roles of both goal and tool.
So, all you need to do is find out if the component A is providing service A to the component B, and vice versa. It is also observed that if the multiple companies have inter dependencies, just recovering only your company is not enough, you also need to plan and assist other companies recover as well.
