Document Driven Design is superior to other development methodologies. Here's why.
By starting with the documentation, a blueprint is laid out and kept in sync with the other dimensions of development.
Clear documentation keeps everyone focused and concise.
If the product is successful, the documentation will have to be developed anyway; It will be much easier and accurate if it is already done. As with TDD, the tests can be the stubs of the client code, and will need to be written anyway by at least one client.
A system of annotating within the documentation has been developed to unify the development and documentation lifecycle.
A system of linking and has been developed to unify the development and documentation lifecycle and .
Documentation can inherit and override or append to existing documentation.