|
(1) In computer science, loose
coupling (or loosely coupled) is a type of coupling
that describes how multiple computer systems, even those using incompatible
technologies, can be joined together for transactions, regardless of
hardware, software and
other functional components. Loosely coupled systems describe those that work on
an exchange relationship where little input is needed from each of the
additional systems. In a loosely coupled system hardware and software may
interact but they are not dependant on each other to work. Computers in a
network are considered loose-coupled systems as a
client machine may request data from the
server, but the two systems also work independently of
each other.
(2) In software terminology, loosely coupled refers to software
where routines, modules,
functions, and similar components are
executed only as needed, and do not run at the launch
of the software application and while it is being used. Web services are a type of software application that uses loose coupling.
Also called light coupling.
See also coupling,
tight coupling, and decoupled.
|
 Design loosely coupled modules - object oriented systems
This article explains the coupling between the classes. It also explains the consequences of high coupling. The article then classifies coupling and explains each type of coupling along with the ways to eliminate the coupling.
Long-lived systems: decoupling
Systems that are clearly separated from each other live longer than systems that are coupled.
Towards a More Effective Coupling of Reflection and Runtime Metamodels for Middleware (PDF)
Reflection plays an important role in the flexibilisation of middleware platforms. Through dynamic inspection, middleware interfaces can be discovered and invoked at runtime, and through adaptation the structure and behavior of the platform can be modified on-the fly to meet new user or environment demands.
|
|
