TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Just to put a non-software spin on the validate/verify discussion.... Several
years ago, I worked for an aerospace company (United Technologies, Hamilton
Standard Division), and we also distinguished between validating and verifying
manuals. Darned if I can remember which was which, but the distinction was that
one involved testing a manual in our own shop, with our own equipment, and a
qualified Hamilton Standard employee; the other was a test at a customer's
site, with the customer's equipment and people. The two conditions were not
necessarily the same. Depending on how flight-critical a component was, its
manual might get one or both tests.