I like the analogy of an eco-system because any healthy eco-system is well-integrated but loosely coupled. Healthy eco-systems are well-integrated in the sense of the various elements contributing to a sustainable outcome, but loosely coupled in that Individual elements can come and go without creating a ripple, and even whole species may be replaced without disruption. The older way of doing IT systems is where everything was tightly-coupled – remove one element and the system is damaged. This is too fragile a mode of operation for any business to tolerate long-term (although many businesses are still be in this vulnerable condition).

I think the high-level view needs to include:
- overall system-plan
- identification of quality components to fill the various roles
- definition of human job roles and processes
- data-exchange between the various components (this is the critical translation mechanism that enables disparate elements to contribute to a unified business outcome)
- security.

I have pulled security out as a distinct item, even though it is obviously part of assessing the components. My reasoning here is that data-security is the major challenge now that so many critical business functions are going online.

Businesses that embrace the power of connective technologies need to be sophisticated in credentialling the components and services, and in understanding how the elements connect to form a viable business eco-system. Naivete in this domain can be very harshly punished.