Documentation

Last updated

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. [1] Documentation can be provided on paper, online, or on digital or analog media, such as audio tape or CDs. Examples are user guides, white papers, online help, and quick-reference guides. Paper or hard-copy documentation has become less common.[ citation needed ] Documentation is often distributed via websites, software products, and other online applications.

Contents

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 ISO standards are not easily available publicly, a guide from other sources for this topic may serve the purpose. [2] , [3] , [4] David Berger has provided several principles of document writing, including terminology, procedure numbering, and sentence length. [5]

Procedures and techniques

The procedures of documentation vary from one sector, or one type, to another. In general, these may involve document drafting, formatting, submitting, reviewing, approving, distributing, reposting and tracking, etc., and are convened by associated SOPs 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. [6] , [7] , [8] , [9]

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, or other types of clients to define and then create documentation that meets the user's needs. Corporate communications includes other types of written documentation that is required for most companies.

Specialized fields of documentation

Documentation in computer science

The following are typical software documentation types:

The following are typical hardware and service documentation types:

Tools for documenting software

There are many types of software and applications used to create documentation.

Software Documentation Folder (SDF)

A common type of software document written by software engineers 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 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 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. [11]

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. [12]

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" [13]

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. [13]

Pedagogical documentation, in terms of the teacher documentation, is the "teacher's story of the movement in children's understanding". [13] 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" [14]

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

  1. Documentation Panels (bulletin-board-like presentation with multiple pictures and descriptions about the project or event).
  2. Daily Log (a log kept every day that records the play and learning in the classroom)
  3. 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)
  4. Individual Portfolios (documentation used to track and highlight the development of each child)
  5. Electronic Documentation (using apps and devices to share documentation with families and collaborators)
  6. Transcripts or Recordings of Conversations (using recording in documentation can bring about deeper reflections for both the educator and the child)
  7. Learning Stories (a narrative used to "describe learning and help children see themselves as powerful learners" [13] )
  8. The Classroom as Documentation (reflections and documentation of the physical environment of a classroom). [13]

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:

See also

    Related Research Articles

    Acceptance testing Test to determine if the requirements of a specification or contract are met

    In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests.

    Information security, sometimes shortened to infosec, is the practice of protecting information by mitigating information risks. It is part of information risk management. It typically involves preventing or at least reducing the probability of unauthorized/inappropriate access to data, or the unlawful use, disclosure, disruption, deletion, corruption, modification, inspection, recording or devaluation of information. It also involves actions intended to reduce the adverse impacts of such incidents. Protected information may take any form, e.g. electronic or physical, tangible or intangible. Information security's primary focus is the balanced protection of the confidentiality, integrity and availability of data while maintaining a focus on efficient policy implementation, all without hampering organization productivity. This is largely achieved through a structured risk management process that involves:

    Software documentation is written text or illustration that accompanies computer software or is embedded in the source code. The documentation either explains how the software operates or how to use it, and may mean different things to people in different roles.

    Standard Generalized Markup Language Markup language

    The Standard Generalized Markup Language is a standard for defining generalized markup languages for documents. ISO 8879 Annex A.1 states that generalized markup is "based on two postulates":

    SQL is a domain-specific language used in programming and designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS). It is particularly useful in handling structured data, i.e. data incorporating relations among entities and variables.

    Configuration management process for maintaining consistency of a product attributes with its design

    Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. The CM process is widely used by military engineering organizations to manage changes throughout the system lifecycle of complex systems, such as weapon systems, military vehicles, and information systems. Outside the military, the CM process is also used with IT service management as defined by ITIL, and with other domain models in the civil engineering and other industrial engineering segments such as roads, bridges, canals, dams, and buildings.

    A document management system (DMS) is a system used to receive, track, manage and store documents and reduce paper. Most are capable of keeping a record of the various versions created and modified by different users. In the case of the management of digital documents such systems are based on computer programs. The term has some overlap with the concepts of content management systems. It is often viewed as a component of enterprise content management (ECM) systems and related to digital asset management, document imaging, workflow systems and records management systems.

    Business continuity planning Prevention and recovery from threats that might affect a company

    Business continuity planning is the process of creating systems of prevention and recovery to deal with potential threats to a company. In addition to prevention, the goal is to enable ongoing operations before and during execution of disaster recovery.

    An open standard is a standard that is publicly available and has various rights to use associated with it and may also have various properties of how it was designed. There is no single definition, and interpretations vary with usage.

    Computer accessibility refers to the accessibility of a computer system to all people, regardless of disability type or severity of impairment. The term accessibility is most often used in reference to specialized hardware or software, or a combination of both, designed to enable use of a computer by a person with a disability or impairment. Computer accessibility often has direct positive effects on people with disabilities.

    Change control within quality management systems (QMS) and information technology (IT) systems is a process—either formal or informal—used to ensure that changes to a product or system are introduced in a controlled and coordinated manner. It reduces the possibility that unnecessary changes will be introduced to a system without forethought, introducing faults into the system or undoing changes made by other users of software. The goals of a change control procedure usually include minimal disruption to services, reduction in back-out activities, and cost-effective utilization of resources involved in implementing change.

    Change management is an IT service management discipline. The objective of change management in this context is to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT infrastructure, in order to minimize the number and impact of any related incidents upon service. Changes in the IT infrastructure may arise reactively in response to problems or externally imposed requirements, e.g. legislative changes, or proactively from seeking improved efficiency and effectiveness or to enable or reflect business initiatives, or from programs, projects or service improvement initiatives. Change management can ensure standardized methods, processes and procedures which are used for all changes, facilitate efficient and prompt handling of all changes, and maintain the proper balance between the need for change and the potential detrimental impact of changes.

    Technical communication is a means to convey scientific, engineering, or other technical information. Individuals in a variety of contexts and with varied professional credentials engage in technical communication. Some individuals are designated as technical communicators or technical writers. These individuals use a set of methods to research, document, and present technical processes or products. Technical communicators may put the information they capture into paper documents, web pages, computer-based training, digitally stored text, audio, video, and other media. The Society for Technical Communication defines the field as any form of communication that focuses on technical or specialized topics, communicates specifically by using technology or provides instructions on how to do something. More succinctly, the Institute of Scientific and Technical Communicators defines technical communication as factual communication, usually about products and services. The European Association for Technical Communication briefly defines technical communication as "the process of defining, creating and delivering information products for the safe, efficient and effective use of products ".

    MIL-STD-498 (Military-Standard-498) was a United States military standard whose purpose was to "establish uniform requirements for software development and documentation." It was released Nov. 8, 1994, and replaced DOD-STD-2167A, DOD-STD-7935A, and DOD-STD-1703. It was meant as an interim standard, to be in effect for about two years until a commercial standard was developed.

    International standards in the ISO/IEC 19770 family of standards for IT asset management (ITAM) address both the processes and technology for managing software assets and related IT assets. Broadly speaking, the standard family belongs to the set of Software Asset Management standards and is integrated with other Management System Standards.

    A specification often refers to a set of documented requirements to be satisfied by a material, design, product, or service. A specification is often a type of technical standard.

    Metadata Data about data

    Metadata is "data that provides information about other data". In other words, it is "data about data." Many distinct types of metadata exist, including descriptive metadata, structural metadata, administrative metadata, reference metadata and statistical metadata.

    In engineering, technical documentation refers to any type of documentation that describes handling, functionality and architecture of a technical product or a product under development or use. The intended recipient for product technical documentation is both the (proficient) end user as well as the administrator / service or maintenance technician. In contrast to a mere "cookbook" manual, technical documentation aims at providing enough information for a user to understand inner and outer dependencies of the product at hand.

    Definitive Media Library

    A Definitive Media Library is a secure Information Technology repository in which an organisation's definitive, authorised versions of software media are stored and protected. Before an organisation releases any new or changed application software into its operational environment, any such software should be fully tested and quality assured. The Definitive Media Library provides the storage area for software objects ready for deployment and should only contain master copies of controlled software media configuration items (CIs) that have passed appropriate quality assurance checks, typically including both procured and bespoke application and gold build source code and executables. In the context of the ITIL best practice framework, the term Definitive Media Library supersedes the term definitive software library referred to prior to version ITIL v3.

    SNAP is the acronym for “Software Non-functional Assessment Process,” a measurement of non-functional software size. The SNAP sizing method complements ISO/IEC 20926:2009, which defines a method for the sizing of functional user requirements. SNAP is a product of the International Function Point Users Group (IFPUG), and is sized using the “Software Non-functional Assessment Practices Manual,” (APM) now in version 2.4. The SNAP methodology has the IEEE standard IEEE2430-2019.

    References

    1. "Documentation definition by The Linux Information Project". www.linfo.org. Retrieved 9 August 2020.
    2. N/A (2003). "Guide to Documentation" (PDF). Archived from the original (PDF) on 29 July 2007.
    3. CGRP. "A Guide to Documentation Styles" (PDF). Retrieved 12 June 2009.
    4. N/A. "A guide to MLA documentation" (PDF). Archived from the original (PDF) on 2 September 2006. Retrieved 12 June 2009.
    5. Berger, David. "Procedures and Documentation" (PDF). Archived from the original (PDF) on 27 July 2011. Retrieved 15 June 2009.
    6. Cropper, Mark; Tony Dibbens (2002). "GAIA-RVS Documentation Procedures" (PDF). Archived from the original (PDF) on 2 November 2005. Retrieved 15 June 2009.
    7. N/A. "GLNPO's Quality System Documentation Review Procedures and Tracking" (PDF). Archived from the original (PDF) on 4 December 2008. Retrieved 15 June 2009.
    8. UK Data Archive (2009). "Data Services Process Guides: Documentation Processing Procedures" (PDF). Archived from the original (PDF) on 13 June 2010. Retrieved 15 June 2009.
    9. UK Data Archive. "Data Services Process Guides: Documentation Processing Techniques" (PDF). Retrieved 15 June 2009.[ dead link ]
    10. Springhouse (2008). Complete Guide to Documentation. p. ix. ISBN   9781582555560 . Retrieved 12 June 2009.
    11. "XIA Configuration Network Documentation Tool" . Retrieved 8 August 2017.
    12. Rader Brown, Rebecca (2009). "The Gang's All Here: Evaluating the Need for a National Gang Database". Columbia Journal of Law and Social Problems. 42: 293–333.
    13. 1 2 3 4 5 Susan, Stacey (11 May 2015). Pedagogical documentation in early childhood : sharing children's learning and teachers' thinking. St. Paul, Minnesota. ISBN   9781605543925. OCLC   909907917.
    14. "Documentation: Transforming our Perspectives | Project Zero". www.pz.harvard.edu. Retrieved 26 October 2018.
    15. "ECRP. Vol 13 No 2". ecrp.uiuc.edu. Retrieved 26 October 2018.