Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Loose coupling


  
  The Loosely Coupled Enterprise: The Secret to Speed and Flexibility
Loose coupling can be applied at all levels of the enterprise, including the entire spectrum of the business process, data and technology architecture.
The absolute key to loose coupling is that the parts -- including the parts of the enterprise -- need to be designed in such a way that they are relatively autonomous.
Regardless of whether you believe that the concept of loose coupling will affect the structure of the enterprise itself, the organizations that embrace this concept in the design of core business processes and their supporting applications will gain flexibility and speed that may leave competitors in the dust.
www.computerworld.com /printthis/2005/0,4814,105574,00.html   (1109 words)

  
 Loose coupling - Wikipedia, the free encyclopedia
Loose coupling describes an approach where integration interfaces are developed with minimal assumptions between the sending/receiving parties, thus reducing the risk that a change in one application/module will force a change in another application/module.
The degree of loose coupling can be measured by noting the number of changes in data elements that could occur in the sending or receiving systems and determining if the computers would still continue communicating correctly.
Loose coupling of interfaces can be dramatically enhanced when publishers of data transmit messages using a flexible file format such as XML to enable subscribers to publish clear definitions of how they subsequently use this data.
en.wikipedia.org /wiki/Loose_coupling   (592 words)

  
 Organization structure from a loose coupling perspective: A multidimensional approach Decision Sciences - Find Articles
Loose coupling, however, is an abstract metaphor that is simultaneously fertile and ambiguous.
Loose coupling, however, is a metaphor that "has a rare combination of face validity, metaphorical salience, and cutting-edge mysticism, all of which encourage researchers to adopt the concept but do not help them to examine its underlying structure, themes, and implications" (Orton & Weick, p.
Second, the components of coupling are translated into network analysis terms to clarify and operationalize the theoretical definitions of loose coupling.
www.findarticles.com /p/articles/mi_qa3713/is_200104/ai_n8934463   (695 words)

  
 Jim Thomas's Home Page (http://www.soci.niu.edu/~jthomas)
Loose Coupling and the Judicial Process Loose coupling is a metaphor that allows for identification of contradictions between and within structural and interactional organizational processes (Weick, 1980; Manning, 1979a, 1980; Thomas, 1980).
Loose coupling refers to decisions, behaviors, policies, and the like, which are made in what Weick has described as the grey area between organizational interdependence and individual autonomy.
Loose coupling implies a lack of connections, or slippage, between organizational niches and the behaviors that are intended to bind organizational goals to organizational practices.
www.soci.niu.edu /~jthomas/papers/justinter.html   (7252 words)

  
 How loose is your coupling?
In fact, there's so much emphasis on loose coupling that many people jump to two natural, but false conclusions: first, that because loose coupling is so good, then tight coupling must be bad, and second, that there are only two levels of coupling, namely loose and tight.
Coupling is a term that describes the level of common knowledge necessary by a provider and a consumer in a distributed computing exchange.
In a very loosely coupled interaction, there may be no way for the consuming software to understand the contents of that fragment, but a human consumer may be able to recognize the fragment simply by looking at it and figuring out the context of the fragment.
searchwebservices.techtarget.com /tip/1,289483,sid26_gci1012724,00.html   (1612 words)

  
 Achieving Loose Coupling
In this paper David Orchard shows that loose coupling is a qualitative measure of the dependency between two systems and that a variety of constraints can be performed to achieve loose coupling.
One definition of coupling [1] defines coupling as the degree to which components depend on one another.
This article shows that loose coupling is a qualitative measure of the dependency between two systems and that a variety of constraints can be performed to achieve loose coupling.
dev2dev.bea.com /pub/a/2004/02/orchard.html   (2021 words)

  
 XML Magazine - Loosely Speaking   (Site not responding. Last check: 2007-08-07)
By loose coupling, I mean that you can be sure that changes to your implementation will not break other applications that are relying on it through the aegis of Web services.
Synchronous invocation is inherently fragile in the world of loosely coupled applications, which is why RPC breaks down.
Loose coupling is central to the nature of Web services-based application integration.
www.fawcette.com /xmlmag/2002_04/magazine/departments/endtag   (650 words)

  
 Coupling
One simple way to think about coupling is this: how easy is it to change something about web service A without having to change web service B. If many changes in A require something in B to be changed, they are tightly coupled.
Tightly coupled architectures are much harder to maintain and reuse, so loose coupling is a major goal in a service oriented architecture.
Semantic coupling occurs when two web services are so dependent on each other that it’s virtually impossible to use web service A without using web service B (or a nearly identical implementation of B).
www.serviceoriented.org /coupling.html   (339 words)

  
 Coupling (computer science) - Wikipedia, the free encyclopedia
In computer science, coupling or dependency is the degree to which each program module relies on each one of the other modules.
Low coupling means that one module does not have to be concerned with the internal implementation of another module, and interacts with another module with a stable interface (see Information hiding).
In modern computing systems, performance is often traded for lower coupling; the gains in the software development process are greater than the value of the running performance gain.
en.wikipedia.org /wiki/Dependency_(computer_science)   (783 words)

  
 DDJ | Departments | SOA, Web Services and XML | SOA Web Services Blog   (Site not responding. Last check: 2007-08-07)
Coupling is a pseudo-technical term used to measure the subjective inter-connectedness of two things.
I did not intend to discuss the loose coupling that's been around for decades and is well understood by OO practitioners, but rather the "Loose Coupling" that SOA is supposed to enable (or was that SOA 2.0?).
Loose coupling means the same thing in both words: namely, separating the interface from the implementation.
www.ddj.com /blog/webservicesblog/archives/2006/05/coupling_good_b.html   (1579 words)

  
 Loose coupling in service-oriented architecture (SOA) - HP Dev Resource Central
Then we'll discuss what loose coupling is and provide examples of loose coupling in practice, including one in HP IT's SOA environment.
Simply put, loosely coupled services can be joined together or disassembled on demand just as easily into their functional components.
Loose coupling helps to have an abstraction layer between the service producers and service consumers.
devresource.hp.com /drc/resources/dc0608/index.jsp   (1011 words)

  
 WebLogic Pro - Designing a Better SOA
The degree of coupling between two services mainly depends on two factors: the implementation and invocation of the service provider, and the consumer's knowledge of how to find and invoke the service.
Because location decoupling is not possible (between two known entities, but possible in an event-driven architecture), and tight coupling of location is inflexible, an intermediate loose coupling of location is desirable.
Loose coupling of location can be achieved by using service intermediaries such as service brokers or directory services.
www.ftponline.com /weblogicpro/2005_01/magazine/features/rramanathan   (532 words)

  
 Design Patterns for .Net
Some contend that services are inherently loosely coupled, and therefore make it easier than ever before to build complex applications by simply integrating their functions into a cohesive whole in order to achieve some larger objective.
Coupling is a computer science term that is used to describe the strength of a connection or the nature of the dependencies that exist between one thing and another.
Indeed, the efforts to achieve loose coupling can be taken to extremes resulting in overly complex designs that can be as hard to maintain as more tightly coupled approaches, so we really need to be pragmatic and consider the unique needs our systems.
www.designpatternsfor.net /default.aspx?pid=38   (2332 words)

  
 Understanding Service-Oriented Architecture
Coupling is increased when service consumers require a large amount of information about the service provider to use the service.
Since a service may be both a consumer and a provider of some services, the dependency on only the contract enforces the notion of loose coupling in service-oriented architecture.
Although coupling between service consumers and service producers is loose, implementation of the service can be tightly coupled with implementation of other services.
www.developer.com /java/web/print.php/10935_2207371_5   (1219 words)

  
 Loose coupling
Loose coupling is often a notion that is mentioned when we talk about SOA.
This is (as I understand it, a cheap version of) dynamic coupling, one step beyond beyond loose coupling.
Loose coupling is not necessarily an end in itself, it is a way to achieve dynamic coupling.
www.ebpml.org /loose_coupling.htm   (544 words)

  
 Adobe - Developer Center : Loose coupling in Flex applications
Loose coupling is a technique you can use to write better Flex code.
When using loose coupling, you write components for your applications in a reusable way that reduces interdependencies between the components.
This article shows a short example of the loose coupling technique and some of the pitfalls when the technique is not used, which lead to higher development costs.
www.adobe.com /devnet/flex/articles/loose_coupling.html   (1032 words)

  
 Enterprise Java Community: TSS Featured Entry
Loose coupling has more up front costs than tight coupling.
In essence, the component was designed with loose coupling in mind (the plug) but the instantiation (or the use) of the component allowed the engineer to bypass the plug by directly connecting to the wire lead.
The level of investment that was placed on enabling a component to be loosely coupled (e.g., it comes with a plug attached).
www.theserverside.com /blogs/showblog.tss?id=DynamicCoupling   (805 words)

  
 John Hagel: Viewpoint- Loosely Coupled - A Term Worth Understanding :: strategy @ the intersection of business & ...
Loosely coupled - if you’re a technology person, chances are pretty good that you are familiar with the term.
Even technology people, when asked for a definition of “loosely coupled”, seem to have a hard time offering a concise and rigorous definition, even though the term is widely used in discussions of computing and software architectures.
Loosely coupled systems reduce this risk by enforcing standards for behavior at the interfaces of modules while providing a great deal of freedom to modify activity within the module.
www.johnhagel.com /view20021009.shtml   (2002 words)

  
 Soa And Loose Coupling
Use of XML is sometimes mentioned as being a key ingredient in achieving loose coupling in an SOA.
When we talk about systems being loosely coupled, we mean that there are few dependencies between them, and/or the dependencies are arranged in their technical details such that certain kinds of changes to the subsystem that implements an interface can be tolerated by clients without requiring changes to the latter.
The only technical aspect of XML-based interaction that seems to promote loose coupling is the fact that information can be added to the output of interfaces, which will be ignored by unmodified clients, and perhaps conversely, that additional inputs accepted by the serving system can be defaulted if not supplied by the client.
c2.com /cgi/wiki?SoaAndLooseCoupling   (1008 words)

  
 Coupling And Cohesion
Coupling between modules/components is their degree of mutual interdependence; lower coupling is better.
Patterns such as AbstractInteractions increase coupling at one level (the interactions are now required maintenance for the dependent class), but expose less dependence upon other spaces because they deliberately allow the substitution of the object previously required for its execution.
In ObjectOrientedProgramming, the main vehicle of Coupling is Polymorphism, and the main vehicle of Cohesion is Encapsulation.
c2.com /cgi/wiki?CouplingAndCohesion   (6264 words)

  
 RE: [soa-rm] Loose Coupling
If the coupling remains inside the SOA Fabric and does not directly touch a service and/or a service consumer, this kind of coupling is not a "coupling" in the context of SOA.
For example, when you talk about "policy requirements" and things alike, these concepts are actually handled by the SOA Fabric and not directly by a service and/or a service consumer in the sense that the implementation of it may have to change or accommodate in a certain way to ensure interoperability.
Loose coupling is a design attribute, and therefore a concrete not an
www.oasis-open.org /archives/soa-rm/200505/msg00552.html   (1459 words)

  
 CISE Seminar - Cross-Layer Design for Multi-hop Wireless Networks: A Loose-Coupling Perspective
The idea is that by jointly optimizing the control over two or more layers, cross-layer solutions can yield significantly improved performance by exploiting the tight coupling between the layers in wireless systems.
In this talk, we develop a "loose -coupling" approach to address this tradeoff.
By loose -coupling, we mean that the cross-layer solution only requires a minimal amount of interaction between the layers, and is robust to imperfect decisions made at each layer.
www.bu.edu /systems/seminars/archive/spring05/classes/class15.htm   (486 words)

  
 java.net: Loosely Coupled Communication and Coordination in Next-Generation Java Middleware
A lot of effort is spent trying to reduce the number of systems and their complexity, as well as spare time, money and resources, by the consolidation and synchronization of the existing data.
Asynchronous middleware offers loose coupling, which enables the use of architectures that cope with those issues in a better way (see [Goff03]).
Besides flexible communication, loose coupling facilitates the composition of large applications by letting the programmer easily add components without redesigning the entire application.
today.java.net /pub/a/today/2005/06/03/loose.html   (4728 words)

  
 Interfaces and Loose Coupling in Java by Charlie Calvert
The term "loose coupling" probably cannot be defined in a definitive manner.
In this sense, they are "loosely" coupled to the other objects in their program.
This relationship will be so loosely coupled that almost any class can quickly learn to consume any object that conforms to the contract defined by this interface.
bdn.borland.com /article/30372   (2202 words)

  
 Information Systems Theory
The five voices are used to review the loose coupling information and then the authors go on to suggest more useful ways of using the concepts.
Causes of loose coupling-leads to types of loose coupling-leads to direct effects of loose coupling-leads to compensations for loose coupling and they all are attached to Organizational Outcomes of Loose Coupling.
This article said to me that there is a common definition of loose coupling that we all use, but there a different branches off that common definition.
oak.cats.ohiou.edu /~kc722196/kcis.htm   (683 words)

  
 LCblog | Wanton coupling | Jun 14th 2004 10:10pm
The paradox of loose coupling is that it's never context-free.
He makes the very important observation that an architecture that has coupling designed into it can be coupled either at assembly time or at runtime, and that these two alternatives have different implications for the looseness of the configuration:
What Jeff is aiming to do here is to reconcile his desire for greatest-common-factor interactions with the ability to maintain the lowest-common-denominator requirement of interoperable loose coupling.
www.looselycoupled.com /blog/lc00aa00039.html   (368 words)

  
 Choosing among JCA, JMS, and Web services for EAI
They can be tightly coupled, and their deployment can be based on the use of invocation frameworks.
Tight coupling means that there is a nailed-down, predetermined client-server or consumer-publisher relationship that is not so easy to change.
Dynamic binding implies loose coupling: the requester discovers at runtime the implementation to be used for the service called; it might even determine at runtime the interface that should be called.
www-106.ibm.com /developerworks/webservices/library/ws-jcajms.html   (3348 words)

  
 Loose Coupling   (Site not responding. Last check: 2007-08-07)
But natural systems perspectives point out that it's hard to observe these tight couplings in real organizations, and find that employees resist close supervision.
Some rational mechanisms like decentralization, delegation, professionalization are methods to build some looseness and flexibility into organizational structures (Scott p.
Meyer and Rowan (1977) take this further and argue that often the peripheral activities are sometimes ceremonialized for external legitimacy purposes and are loosely coupled to the technical core, because they do not offer consistent guidelines to manage it.
faculty.babson.edu /krollag/org_site/encyclop/loose_coupling.html   (285 words)

  
 Connecting with Web services | InfoWorld | Insight | 2002-06-07 | By Jon Udell
For a while, loose coupling will mean abstract interfaces and asynchronous messaging, and there is much important work to be done according to these definitions.
At the Emerging Technology Conference, KnowNow's Rohit Khare sketched out a model he calls "application-layer internetworking," in which SOAP routers enable the composition of systems that are loosely coupled in the broadest sense.
Developers newly converted to Web services may feel that loose coupling is a bait and switch -- that the rules are shifting before the game has really started.
www.infoworld.com /article/02/06/07/020610feappdevtci_1.html   (1884 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.