Product documentation with a purpose

Abstract

The author maintains that in many components, product specifications written by or for a single department fail to meet the overall company needs. He argues that all such documentation should be structured to allow easy traceability of important product information to the authorizing source, as well as early verification that the end product will be what was originally intended.

Journal
IEEE Transactions on Professional Communication
Published
1986-09-01
DOI
10.1109/tpc.1986.6448248
CompPile
Open Access
Closed
Export

Citation Context

Cited by in this index (0)

No articles in this index cite this work.

References (0)

No references on file for this article.