I googled for "Documentation Driven Development" and came up with a number of links (why the heck did I not do this sooner?).
- SpliceIt seem to be doing it, but don't cite tests. There is no mention of integration with use-case-level tests.
- Vincent Massol had the experience when writing books about frameworks - always improved the underlying code. The message is: you have to be serious about writing good docs. Otherwise the effect is lost.
- Korby Parnell just thinks about it, but some comments point to people with experience doing it.
- IEEE has an article about DDD for real time systems. Also seems to take it as far as code-generation. I haven't read it.
- Miguel dos Santos has little to add, but there is a nice comment by someone called "Tania" about applying the idea of documenting the "why" more generally.
- Ilja Preuss's take is a bit too limited for me. In my experience, good DDD docs focus on tasks, not classes and methods.
- Michele Simionato is spot on. Already did it in 2003, in Python. Which, incidentally, executes the DDD/Citing idea very nicely indeed.
- Phil Thomson, as a half-joke, prompts Dave Thomas to drive DDD of RubyGems with his book. Funnily, it seems that Andy Hunt and Dave Thomas have used a JCite-like approach for every one of their books. They have some home-grown macros to make compiling and checking the example code automatic.