Yes. Though the schematic is the driving document in both cases. I.e., it wins all arguments ("Oh, I thought RESET was on pin 23..." "No, it's not.")
The biggest consumer of the document is the end user. He needs to be able to quickly understand what the design is trying to do and how it is trying to do it. To that end, you have to balance "information" with "clutter".
Ouch! Your schematics must be very "dark" :>
I only name things that *need* names. E.g., if I have an RC snubber across a switching diode, I don't name the signal
*between* the R and the C. Chances are, I will never have to refer to it in my written commentary. And, if I actually *do* need to refer to it (e.g., to tell a technician to probe the signal there), I would simply say "the junction of Rx and Cy".Yes, but everything you put on a document is one more thing that has to be maintained. It's like putting comments on each line of code in a program. Or, using "FirstArrayIndex" and "SecondArrayIndex" (as in array[FirstArrayIndex][SecondArrayIndex]) instead of array[i][j]). I.e., it's just more than you need.
YMMV. The whole point of this was to elicit
*preferences* as none of these things are cast in stone...