The theory that paper documentation makes high quality software. -- KeithSader

<sarcasm>Design documents with sections organized by UML diagram type makes the best documentation</sarcasm> - ND

Better yet, how about a document defining a system using C-style declarations and prototypes. (But it's too early to start writing code.)

On the other hand, it's awfully easy to look like a genius next to those who spend their time generating printouts rather than results. On the other hand, it's frustrating, depressing even, always to be pulling against being dragged through the paper. On the other hand, he who does the work makes the rules. But on the other hand, it's awful lonely at the top.