These issues wouldn't arise.

The reason there are so frequently documentation/code synchronization issues is that the User Manual should be completed and proofread well before the objective spec is written, since it is dependent on the User Manual. The Objective spec must be complete and fully compliant with the User Manual before the first line of code is written. Without that, there's nothing against which the code can be tested. The code must be entirely and completely compliant with the objective specification prior to release. If the code doesn't, in every way, meet the objective spec, which has to be etched in concrete, so to speak, before design and coding begins, then the code will never meet the spec.

Software types always want to leap into the coding task because it's much easier to do that ad-hoc rather than adhering to a well designed specification. That's why many of us choke when trying to say the words "software" and "engineering" in the same context. If only coders would apply common and sound engineering principles to software design and construction.

RE