What does documentation mean to you?
Document Actions
As an information developer, when I think of "documentation," I tend to think first of software manuals. Other people think of the documentation needed to complete their jobs: receipts, contracts, schedules, and standard operating procedures. What about you?
My posts about documentation, so far, have been focussed on documenting how software works. I talk about printed manuals and online forms of documentation.
Ronald Bartels pointed me to a page on his blog about problem management. When I check his posts about documentation, I see that while he is interested in the documentation about products, he seems mostly concerned with the documentation created by an IT department that is relevant to problem management - internally created documentation about how servers and other areas managed by the IT department have been set up, and standard operating procedures.
What sort of documentation do you work with?
_____
tags:
What "documentation" means in the medical device world
Posted by
Milan Davidovic
at
2008-08-25 20:46
It's an interesting question in the medical device world. "Documentation" is really only used by insiders to refer to the stuff that's needed to get the job done and to satisfy regulators -- design history files, standard operating procedures, training files, and so on (and on and on... ). The stuff that users see is called "labeling" -- not only the labels applied to the device, but any information product that accompanies the device (including manuals and quick reference guides). It makes discussion a little tricky sometimes because you can have "label" (an individual item) and "labeling" (the whole category) turn up in the same conversation and you have to take care to keep the meanings straight.
Forgot your password?
New user?
