Technical documentation explained

Technical documentation is a generic term for the classes of information created to describe (in technical language) the use, functionality or architecture of a product, system or service.

Classes of technical documentation

Classes of technical documentation may include:

Standardizing technical documentation

Historically, most classes of technical documentation lacked universal conformity (standards) for format, content and structure. Standards are being developed to redress this through bodies such as the International Organization for Standardization(ISO), which has published standards relating to rules for preparation of user guides, manuals, product specifications, etc. for technical product documentation. These standards are covered by ICS 01.110.[1] Technical product documentation not covered by ICS 01.110 are listed in the subsection below.

Discipline-specific

EU Medical Device Regulation

A technical documentation is also required for medical devices following EU medical device regulation.Annex II, Technical documentation, and Annex III, Technical documentation on post-market surveillance, of the regulation describe the content of a technical documentation for a medical device.This includes e.g. information on the device specification, labelling and instructions, design and manufacture, safety and performance requirements, risk management, and the validatain and verfification of the device, including the clinical evaluation; and also information from postmarketing surveillance.

Formats for source data

Documentation architecture and typing

Some documentation systems are concerned with the overall types or forms of documentation that constitute a documentation set, as well as (or rather than) how the documentation is produced, published or formatted.

For example, the Diátaxis framework (which is mostly used in the field of software documentation [8]) posits four distinct documentation forms, corresponding to four different user needs: tutorials, how-to guides, reference and explanation.[9] By contrast, DITA asserts five different "topic types": Task, Concept, Reference, Glossary Entry, and Troubleshooting, while RedHat's Modular Documentation system uses three "modules": Concept, Procedure and Reference.[10]

See also

Notes and References

  1. Web site: 01.110: Technical product documentation . . 10 June 2009 .
  2. Web site: ISO 15787:2001 Technical product documentation -- Heat-treated ferrous parts -- Presentation and indications . . 10 June 2009 .
  3. Web site: ISO 3098-0:1997 Technical product documentation -- Lettering -- Part 0: General requirements . . 10 June 2009 .
  4. Web site: ISO 10209-1:1992 Technical product documentation -- Vocabulary -- Part 1: Terms relating to technical drawings: general and types of drawings . . 10 June 2009 .
  5. Web site: ISO 2162-1:1993 Technical product documentation -- Springs -- Part 1: Simplified representation . . 10 June 2009 .
  6. Web site: ISO 5457:1999 Technical product documentation -- Sizes and layout of drawing sheets . . 10 June 2009 .
  7. ISO6433
  8. Web site: Partial list of Diátaxis documentation sets . 10 April 2021 .
  9. Web site: Outline of Diátaxis documentation forms . 10 April 2021 .
  10. Web site: RedHat Modular Documentation terms and definitions . 11 April 2021 .