DEM (abbreviating Data/Event Modeling) is a simplified and streamlined
version of Demeter/C++.

@ARTICLE{DEM:houser,
AUTHOR = "Chris Houser",
TITLE = "Manual and compiler for a terse and modular language DEM",
JOURNAL = SIGPLAN Notices,
YEAR = 1996,
PAGES = "41-51",
MONTH = "December",
VOLUME = 31,
NUMBER = 12
}

It is refreshing to see the ideas explained in a very direct way.
The paper explains the ideas of adaptiveness very well.
The implementation is only 100 lines of 
Perl 5 source code

and can be easily modifed by a Perl 5 specialist.
DEM makes Demeter very accessible.

The implementation makes some errors which are explained in:
Efficient Implementation of Adaptive Software.
 
Specifically, the through specifications can lead to inconsistency.

Demeter has been improved recently using context relations.
For the concepts, see:

Evolution of Object Behavior using Context Relations.

For an implementation, see:
http://www.ccs.neu.edu/home/lieber/Demeter-and-Java.html.

There is one statement by the author I would like to comment on: "Writing DEM flow specifications potentially requires global knowledge of the graph, breaking encapsulation and hindering reuse." Object-oriented programs are much worse regarding the detailed knowledge about the graph information which has to be put into the programs. So if DEM hinders reuse, then ordinary oo programming hinders reuse even much more.