The capability of services to be joined together on demand to create positive services, or disassembled just as easily into their functional components.  Loose coupling is a way of ensuring that technical details such as language, platform, and so on are decoupled from the service.

 

Loose coupling is the ultimate goal in the Service Oriented Architecture (SOA) between network applications and software.  In other words, we want to try to combine networks together in a way that is affordable, and offers the most benefits through minimal infracture changes within the system. 

 

 

NOTE:  Loose Coupling is one of the three technical concepts of Service Oriented Architecture (SOA).  If you would like to compare Loose Coupling with other technical concepts of SOA please refer to Services and Interoperability pages on the class BUS188sj support site.

 

Telephone system.  During the beginning stages of widespread phone useage, people using phones had first connect to an operator who would then physically plug a wire to create a semipermanent connection between the two parties.  Today, when customers pick upu a phone to call someone, there is no dial tone (disconnection).  After the person dials the phone number of the person they are trying to reach, thats when a dial tone - the connection - is made.  With millions of land and wireless phones in use everyday,  the phone systems need to use loose coupling to support this mass infracture.  Phone providers will support numerous live conversations at any given time rather than supporting both the live and dormant calls. 

 

 REFERENCES AND ADDITIONAL INFORMATION:

 

Wikipedia - Loose Coupling

 

Wikipedia - Service Oriented Architecture