<mods xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" ID="P0b002ee180378fad">
<name type="corporate">
 <namePart>United States Government Publishing Office</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">publisher</roleTerm>
  <roleTerm authority="marcrelator" type="code">pbl</roleTerm>
</role>
 <role>
  <roleTerm authority="marcrelator" type="text">distributor</roleTerm>
  <roleTerm authority="marcrelator" type="code">dst</roleTerm>
</role>
</name>
<name type="corporate">
 <namePart>United States</namePart>
 <namePart>Government Accountability Office</namePart>
 <namePart>Accounting and Information Management Division</namePart>
 <role>
  <roleTerm authority="marcrelator" type="text">author</roleTerm>
  <roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
 <description>Government Organization</description>
</name>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">government publication</genre>
<language>
 <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<extension>
 <collectionCode>GAOREPORTS</collectionCode>
 <category>Legislative Agency Publications</category>
 <waisDatabaseName>gao</waisDatabaseName>
 <branch>legislative</branch>
 <dateIngested>2010-08-12</dateIngested>
</extension>
<originInfo>
 <publisher>U.S. Government Printing Office</publisher>
 <dateIssued encoding="w3cdtf">1999-10-18</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>58 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-00-12</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-12</identifier>
<identifier type="local">P0b002ee180378fad</identifier>
<identifier type="former package identifier">f:ai00012</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-28</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-00-12</recordIdentifier>
 <recordOrigin>machine generated</recordOrigin>
 <languageOfCataloging>
  <languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</languageOfCataloging>
</recordInfo>
<accessCondition type="GPO scope determination">fdlp</accessCondition>
<extension>
 <docClass>REPORT</docClass>
 <accessId>GAOREPORTS-AIMD-00-12</accessId>
 <reportNumber>AIMD-00-12</reportNumber>
 <subject>Y2K</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Systems conversions</subject>
 <subject>Data integrity</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Information resources management</subject>
 <subject>Systems compatibility</subject>
 <identifier>Y2K</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>Defense Computers: DOD Y2K Functional End-to-End Testing</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO provided information on the
effectiveness of the Department of Defense&apos;s efforts to perform year
2000-related end-to-end tests for its major business functions.&lt;p/&gt;GAO noted that: (1) because year 2000 conversions often involve numerous
large interconnecting systems with many external interfaces and
extensive supporting technology infrastructures, year 2000 testing
should be approached in a structured and disciplined fashion; (2) GAO&apos;s
year 2000 guidance recommends that in planning and managing end-to-end
tests, agencies define test boundaries, secure the commitment of data
exchange partners, prepare test procedures and data, define exit
criteria and document test results, among other steps; (3) each of the
individual test events GAO attended and reviewed within the four
functional areas generally satisfied the key processes that GAO&apos;s year
2000 test guide defines as necessary to effectively plan, conduct, and
report on end-to-end testing; (4) moreover, while the events&apos; respective
approaches to implementing the key processes varied, these differences
were appropriately based on consideration of the event&apos;s scope and
complexity; (5) in addition, overall end-to-end test efforts within
three of the four functional areas were reported to be largely on
schedule and expected to be completed by October 1999; (6) however, at
the time GAO briefed the Communications functional area on the results
of GAO&apos;s review, it could not provide complete progress information; and
(7) while information was subsequently provided by Communications, it
showed that the functional area had not yet developed plans to test 31
mission-critical systems.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-12/html/GAOREPORTS-AIMD-00-12.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-12/pdf/GAOREPORTS-AIMD-00-12.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-00-12</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-12</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-00-12; Defense Computers: DOD Y2K Functional End-to-End Testing;
            </searchTitle>
</extension>
<subject>
 <topic>Y2K</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Systems conversions</topic>
 <topic>Data integrity</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Information resources management</topic>
 <topic>Systems compatibility</topic>
 <topic>Y2K</topic>
</subject>
</mods>