Last update: Sun Aug 5 02:03:07 MDT 2018
@Article{Mamone:2000:DT,
author = "Salvatore Mamone",
title = "Documentation testing",
journal = j-SIGSOFT,
volume = "25",
number = "2",
pages = "26--29",
month = mar,
year = "2000",
CODEN = "SFENDP",
DOI = "https://doi.org/10.1145/346057.346066",
ISSN = "0163-5948 (print), 1943-5843 (electronic)",
ISSN-L = "0163-5948",
bibdate = "Wed Aug 1 17:13:56 MDT 2018",
bibsource = "http://www.math.utah.edu/pub/tex/bib/sigsoft2000.bib",
abstract = "One definition of documentation is 'Any written or
pictorial information describing, defining, specifying,
reporting, or certifying activities, requirements,
procedures, or results.' (1). Documentation is as
important to a product's success as the product itself.
If the documentation is poor, non-existent, or wrong,
it reflects on the quality of the product and the
vendor. At the Bell Atlantic Systems Integration \&
Testing Center documentation testing is an important
function that receives as much attention as the testing
of software and hardware. Because the Bell Atlantic
Systems Integration \& Testing Center is ISO9001
certified, an enormous effort was undertaken to ensure
quality assurance of all products including
documentation. Both a test procedure and test plan for
documentation has been implemented to ensure this
quality. This article will describe what documentation
is, why document testing is important, and how document
testing is performed at the Bell Atlantic Systems
Integration \& Testing Center. Other information
pertaining to documentation, such as human factors, how
to achieve document comprehensiveness, and
comprehensibility, although important, are beyond the
reach of this report.",
acknowledgement = ack-nhfb,
fjournal = "ACM SIGSOFT Software Engineering Notes",
journal-URL = "https://dl.acm.org/citation.cfm?id=J728",
}