Law of Demeter

Law of Demeter, a design guideline for developing software.

The Law of Demeter states that an object should only interact with other objects near itself.

Law of Demeter, software development design guideline ("Only talk to your immediate friends").

Following the Law of Demeter can result in a lower RFC.

The advantage of following the Law of Demeter is that the resulting software tends to be more maintainable and adaptable.

Law of Demeter (also known as the "Principle of Least Knowledge")

A Multilayered architecture can be considered to be a systematic mechanism for implementing the Law of Demeter in a software system.

Basili et al. published experimental results in 1996 suggesting that the Law of Demeter was a valid way to reduce the probability of software faults.

The Law of Demeter (LoD) or principle of least knowledge is a design guideline for developing software, particularly object-oriented programs.

Phil Haack: "The Law of Demeter is not a Dot Counting Exercise"

Lieber: "Phil Holland's Law of Demeter"

According to Wirfs-Brock and Wilkerson, there is a conflict between the Law of Demeter and responsibility-driven design.

More formally, the Law of Demeter for functions requires that a method of an object may only invoke the methods of the following kinds of objects:

The Paperboy, The Wallet,and The Law Of Demeter (PDF)

Pressure to create an object orgy results from poor interface design, perhaps taking the form of a God object, not implementing true objects, or failing to heed the Law of Demeter.

When applied to object-oriented programs, the Law of Demeter can be more precisely called the "Law of Demeter for Functions/Methods" (LoD-F).