Timetrave: Created page with "{{Short description|Set of documents providing knowledge to explain a system}} {{Merge from|Documentary evidence|discuss=Talk:Documentation#Proposed merge of Documentary evide..."

2021-07-31T16:15:25Z

Created page with "{{Short description|Set of documents providing knowledge to explain a system}} {{Merge from|Documentary evidence|discuss=Talk:Documentation#Proposed merge of Documentary evide..."

Neue Seite

{{Short description|Set of documents providing knowledge to explain a system}}
{{Merge from|Documentary evidence|discuss=Talk:Documentation#Proposed merge of Documentary evidence into Documentation|date=May 2021}}
{{Self reference|For a guide on using the documentation in Wikipedia templates, see {{tl|documentation}}}}
{{Use dmy dates|date=March 2020}}

'''Documentation''' is any communicable material that is used to describe, explain or instruct regarding some attributes of an object, system or procedure, such as its parts, assembly, installation, maintenance and use.<ref>{{cite web |title=Documentation definition by The Linux Information Project |url=http://www.linfo.org/documentation.html |website=www.linfo.org |access-date=9 August 2020}}</ref> Documentation can be provided on paper, [[online]], or on [[Digital media|digital]] or [[analog media]], such as [[Tape recorder|audio tape]] or [[Compact disc|CDs]]. Examples are user guides, white papers, online help, and quick-reference guides. Paper or hard-copy documentation has become less common.{{Citation needed|date=August 2020}} Documentation is often distributed via websites, software products, and other online applications.

Documentation as a set of instructional materials shouldn't be confused with [[documentation science]], the study of the recording and retrieval of information.

== Principles for producing documentation ==

While associated [[International Organization for Standardization|ISO]] standards are not easily available publicly, a guide from other sources for this topic may serve the purpose.<ref name=agd>{{cite web|last=N/A |title=Guide to Documentation |year=2003 |url=http://www.somers.k12.ct.us/common/guide_to_doc.pdf |url-status=dead |archive-url=https://web.archive.org/web/20070729135707/http://www.somers.k12.ct.us/common/guide_to_doc.pdf |archive-date=29 July 2007 }}</ref>,<ref name=agds>{{cite web
| last = CGRP
| title = A Guide to Documentation Styles
| url = http://www.sfsu.edu/~carp1/pdf/A%20Guide%20to%20Documentation%20Styles.pdf
| access-date = 12 June 2009
}}</ref>,<ref name=agmd>{{cite web|last=N/A |title=A guide to MLA documentation |url=http://www.sunyjcc.edu/jamestown/library/pdf/mla.pdf |access-date=12 June 2009 |url-status=dead |archive-url=https://web.archive.org/web/20060902180310/http://www.sunyjcc.edu/jamestown/library/pdf/mla.pdf |archive-date=2 September 2006 }}</ref><ref name=pad>{{cite web
|last = Berger
|first = David
|title = Procedures and Documentation
|url = http://www.maintenanceonline.org/maintenanceonline/content_images/p11%20Trans%20View-20080410-222135.pdf
|access-date = 15 June 2009
|archive-url = https://web.archive.org/web/20110727055502/http://www.maintenanceonline.org/maintenanceonline/content_images/p11%20Trans%20View-20080410-222135.pdf
|archive-date = 27 July 2011
|url-status = dead}}</ref>

Documentation development may involve document drafting, formatting, submitting, reviewing, approving, distributing, reposting and tracking, etc., and are convened by associated [[Standing operating procedure|SOP]]s in a regulatory industry. It could also involve creating content from scratch. Documentation should be easy to read and understand. If it's too long and too wordy, it may be misunderstood or ignored. Clear, concise words should be used, and sentences should be limited to a maximum of 15 words. Documentation intended for a general audience should avoid gender-specific terms and cultural biases. In a series of procedures, steps should be clearly numbered.<ref name=grdp>{{cite web
| last = Cropper
| first = Mark
| author2 = Tony Dibbens
| title = GAIA-RVS Documentation Procedures
| year = 2002
| url = http://www.mssl.ucl.ac.uk/gaia-rvs/document_repository/MSSL_GAIA-RVS_AD_001.01.pdf
| access-date = 15 June 2009
| url-status = dead
| archive-url = https://web.archive.org/web/20051102091330/http://www.mssl.ucl.ac.uk/gaia-rvs/document_repository/MSSL_GAIA-RVS_AD_001.01.pdf
| archive-date = 2 November 2005 }}</ref>,<ref name=gqsd>{{cite web|last=N/A |title=GLNPO's Quality System Documentation Review Procedures and Tracking |url=http://www.epa.gov/glnpo/qmp/Appendix%20S/Quality_Doc_Review_Procedures.pdf |archive-url=https://wayback.archive-it.org/all/20081204090246/http://epa.gov/glnpo/qmp/Appendix%20S/Quality_Doc_Review_Procedures.pdf |url-status=dead |archive-date=4 December 2008 |access-date=15 June 2009 }}</ref>,<ref name=dspg>{{cite web| last =UK Data Archive| title =Data Services Process Guides: Documentation Processing Procedures| year =2009| url =http://www.esds.ac.uk/news/publications/UKDA_DSS_DocumentationProcessingProcedures.pdf| access-date =15 June 2009| url-status =dead| archive-url =https://web.archive.org/web/20100613042612/http://www.esds.ac.uk/news/publications/UKDA_DSS_DocumentationProcessingProcedures.pdf| archive-date =13 June 2010}}</ref>,<ref name=dspg2>{{cite web|last=UK Data Archive |title=Data Services Process Guides: Documentation Processing Techniques |url=http://www.esds.ac.uk/news/publications/UKDADocProcessingTechniques.pdf |access-date=15 June 2009 }}{{dead link|date=May 2016|bot=medic}}{{cbignore|bot=medic}}</ref>

== Producing documentation ==
[[Technical writers]] and corporate communicators are professionals whose field and work is documentation. Ideally, technical writers have a background in both the subject matter and also in writing, managing content, and information architecture. Technical writers more commonly collaborate with subject matter experts (SMEs), such as engineers, technical experts, medical professionals, etc. to define and then create documentation to meet the user's needs. [[Corporate communication]]s includes other types of written documentation, for example:
* [[Market communications]] (MarCom): MarCom writers endeavor to convey the company's value proposition through a variety of print, electronic, and social media. This area of corporate writing is often engaged in responding to proposals.
* [[Technical communication]] (TechCom): Technical writers document a company's product or service. Technical publications can include user guides, installation and configuration manuals, and troubleshooting and repair procedures.
* [[Legal writing]]: This type of documentation is often prepared by attorneys or paralegals.
* Compliance documentation: This type of documentation codifies [[Standard Operating Procedures]] (SOPs), for any regulatory compliance needs, as for safety approval, taxation, financing, technical approval, and all
* Healthcare documentation: This field of documentation encompasses the timely recording and validation of events that have occurred during the course of providing health care.<ref name=cgd2>{{cite book |last=Springhouse |title=Complete Guide to Documentation |url=https://books.google.com/books?id=m1fPFVJIi6gC&q=intitle:documentation&pg=PA87 |access-date=12 June 2009|isbn=9781582555560 |year=2008 |page=ix}}</ref>

== Documentation in computer science ==
{{main|Software documentation}}
=== Types ===
The following are typical software documentation types:
* Request for Proposal ([[RFP]])
* Requirements/ [[Statement of work]]/ Scope of Work (SOW)
* Software Design and Functional Specification
* System Design and Functional Specifications
* Change Management, Error and Enhancement Tracking
* [[User Acceptance Testing]]
* [[Man page|Manpages]]

The following are typical hardware and service documentation types:
* [[Computer network diagram|Network diagrams]]
* Network maps
* [[Datasheet]] for IT systems (Server, Switch, e.g.)
* Service Catalog and Service Portfolio ([[ITIL]])

=== Software Documentation Folder (SDF) tool ===
A common type of software document written in the simulation industry is the SDF. When developing software for a simulator, which can range from embedded avionics devices to 3D terrain databases by way of full motion control systems, the engineer keeps a notebook detailing the development "the build" of the project or module. The document can be a wiki page, MS word document or other environment. They should contain a ''requirements'' section, an ''interface'' section to detail the communication interface of the software. Often a ''notes'' section is used to detail the proof of concept, and then track errors and enhancements. Finally, a ''testing'' section to document how the software was tested. This documents conformance to the client's requirements. The result is a detailed description of how the software is designed, how to build and install the software on the target device, and any known defects and work-arounds. This build document enables future developers and maintainers to come up to speed on the software in a timely manner, and also provides a roadmap to modifying code or searching for bugs.

=== Software tools for Network Inventory and Configuration ===
These software tools can automatically collect data of your network equipment. The data could be for inventory and for configuration information. The [[ITIL|ITIL Library]] requests to create such a database as a basis for all information for the IT responsible. It's also the basis for IT documentation. Examples include XIA Configuration.<ref>{{cite web|url=https://www.centrel-solutions.com/xiaconfiguration/|title=XIA Configuration Network Documentation Tool|access-date=8 August 2017}}</ref>

== Documentation in criminal justice ==

"Documentation" is the preferred term for the process of populating criminal databases. Examples include the [[National Counter-terrorism Center]]'s [[Terrorist Identities Datamart Environment]] ("TIDE"), [[sex offender registries]], and gang databases.<ref>{{cite journal|last=Rader Brown|first=Rebecca|title=The Gang's All Here: Evaluating the Need for a National Gang Database|journal=Columbia Journal of Law and Social Problems|year=2009|volume=42|pages=293–333}}</ref>

== Documentation in early childhood education ==
Documentation, as it pertains to the early childhood education field, is "when we notice and value children's ideas, thinking, questions, and theories about the world and then collect traces of their work (drawings, photographs of the children in action, and transcripts of their words) to share with a wider community"<ref name=":0">{{Cite book|title=Pedagogical documentation in early childhood : sharing children's learning and teachers' thinking|last=Susan|first=Stacey|isbn=9781605543925|location=St. Paul, Minnesota|oclc=909907917|date = 2015-05-11}}</ref>

Thus, documentation is a process, used to link the educator's knowledge and learning of the child/children with the families, other collaborators, and even to the children themselves.

Documentation is an integral part of the cycle of inquiry - observing, reflecting, documenting, sharing and responding.<ref name=":0" />

Pedagogical documentation, in terms of the teacher documentation, is the "teacher's story of the movement in children's understanding".<ref name=":0" /> According to Stephanie Cox Suarez in 'Documentation - Transforming our Perspectives', "teachers are considered researchers, and documentation is a research tool to support knowledge building among children and adults"<ref name=":1">{{Cite web|url=http://www.pz.harvard.edu/resources/documentation-transforming-our-perspectives|title=Documentation: Transforming our Perspectives {{!}} Project Zero|website=www.pz.harvard.edu|language=en|access-date=2018-10-26}}</ref>

Documentation can take many different styles in the classroom. The following exemplifies ways in which documentation can make the 'research', or learning, visible:

# Documentation Panels (bulletin-board-like presentation with multiple pictures and descriptions about the project or event).
# Daily Log (a log kept every day that records the play and learning in the classroom)
# Documentation developed by or with the children (when observing children during documentation, the child's lens of the observation is used in the actual documentation)
# Individual Portfolios (documentation used to track and highlight the development of each child)
# Electronic Documentation (using apps and devices to share documentation with families and collaborators)
# Transcripts or Recordings of Conversations (using recording in documentation can bring about deeper reflections for both the educator and the child)
# Learning Stories (a narrative used to "describe learning and help children see themselves as powerful learners"<ref name=":0" />)
# The Classroom as Documentation (reflections and documentation of the physical environment of a classroom).<ref name=":0" />

Documentation is certainly a process in and of itself, and it is also a process within the educator. The following is the development of documentation as it progresses for and in the educator themselves:

* Develop(s) habits of documentation
* Become(s) comfortable with going public with recounting of activities
* Develop(s) visual literacy skills
* Conceptualize(s) the purpose of documentation as making learning styles visible, and
* Share(s) visible theories for interpretation purposes and further design of curriculum.<ref name=":2">{{Cite web|url=http://ecrp.uiuc.edu/v13n2/index.html|title=ECRP. Vol 13 No 2|website=ecrp.uiuc.edu|access-date=2018-10-26}}</ref>

==See also==

{{Div col|colwidth=20em|small=yes}}
* [[Author]]ing
* [[Bibliographic control]]
* [[Change control]]
* [[Citation|Citation Index]]
* [[Copyright]]
* [[Description]]
* [[Document]]
* [[Documentation (field)]]
* [[Documentation science]]
* [[Digital object identifier|Document identifier]]
* [[Document management system]]
* [[Documentary film|Documentary]]
* [[Freedom of information]]
* [[Glossary]]
* [[Historical document]]
* [[Index (publishing)]]
* [[ISO 2384:1977]]
* [[ISO 259:1984]]
* [[ISO 5123:1984]]
* [[ISO 3602:1989]]
* [[ISO 6357:1985]]
* [[ISO 690]]
* [[ISO 5964]]
* [[ISO 9001]]
* [[IEC 61355]]
* [[International Standard Bibliographic Description]]
* [[Journal of Documentation]]
* [[Licensing]]
* [[Letterhead]]
* [[Table of contents|List of Contents]]
* [[Technical documentation]]
* [[User guide]]
* [[Medical certificate]]
* [[Publishing]]
* [[Records management]]
* [[Software documentation]]
* [[Style guide]]
* [[Technical communication]]
{{div col end}}


<references group="https://dissertationpapers.co.uk" />

==References==
{{Reflist}}

==External links==

{{Wiktionary}}
* [http://ewh.ieee.org/soc/pcs/ IEEE Professional Communication Society]
* [http://www.linfo.org/documentation.html Documentation Definition] by The Linux Information Project (LINFO)
* [http://www.problemistics.org/tools/references/information.html Information & Documentation] List of selected tools
* Library of articles on documentation: [http://www.hci.com.au/hcisite5/library/default.htm Technical writing and documentation articles]

{{Authority control}}

[[Category:Technical communication]]
[[Category:Information science]]

Documentation - Versionsgeschichte

Timetrave: Created page with "{{Short description|Set of documents providing knowledge to explain a system}} {{Merge from|Documentary evidence|discuss=Talk:Documentation#Proposed merge of Documentary evide..."