<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="P0b002ee1803a0759">
<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">1998-04-30</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>39 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-98-88</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-88</identifier>
<identifier type="local">P0b002ee1803a0759</identifier>
<identifier type="former package identifier">f:ai98088</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-23</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-98-88</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-98-88</accessId>
 <reportNumber>AIMD-98-88</reportNumber>
 <subject>Computer software</subject>
 <subject>Financial management systems</subject>
 <subject>Requirements definition</subject>
 <subject>Computer software verification and validation</subject>
 <subject>Strategic information systems planning</subject>
 <subject>Municipal governments</subject>
 <subject>Financial management systems</subject>
 <identifier>District of Columbia</identifier>
 <identifier>DC Financial Management System</identifier>
 <identifier>Software Capability Maturity Model</identifier>
 <identifier>CMM</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
</extension>
<titleInfo>
 <title>District of Columbia: Software Acquisition Processes for a New Financial Management System</title>
</titleInfo>
<abstract>Pursuant to a congressional request, GAO reviewed whether the District
of Columbia had implemented disciplined software acquisition processes
for its new financial management system (FMS).&lt;p/&gt;GAO noted that: (1) while the district has many strengths in its
acquisition processes for FMS, it also has many weaknesses; (2) when
compared to standards established by the Software Engineering Institute,
the District&apos;s processes for software acquisitions are not mature; (3)
of the six key process areas (KPA) evaluated for the repeatable level,
the District fully satisfied only one--solicitation; (4) severe
weaknesses were found in other critical key processes, including
requirements development and management and evaluation; (5) for example,
the District does not have a policy for establishing and managing
software-related requirements, does not at present have adequate
resources for requirements development, and has not formally designated
responsibility for requirements development and management; (6)
similarly, the District does not have an effective evaluation process,
and is currently unable to objectively determine if the acquired systems
will satisfy the contract requirement; (7) finally, the District has not
satisfied the one KPA evaluated for the defined level of maturity,
acquisition risk management; and (8) the FMS project does not have a
risk management plan and does not track project risk.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-88/html/GAOREPORTS-AIMD-98-88.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-98-88/pdf/GAOREPORTS-AIMD-98-88.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-98-88</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-98-88</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-98-88; District of Columbia: Software Acquisition Processes for a New Financial Management System;
            </searchTitle>
</extension>
<subject>
 <topic>Computer software</topic>
 <topic>Financial management systems</topic>
 <topic>Requirements definition</topic>
 <topic>Computer software verification and validation</topic>
 <topic>Strategic information systems planning</topic>
 <topic>Municipal governments</topic>
 <topic>Financial management systems</topic>
 <topic>District of Columbia</topic>
 <topic>DC Financial Management System</topic>
 <topic>Software Capability Maturity Model</topic>
 <topic>CMM</topic>
</subject>
</mods>