<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="P0b002ee18039cab8">
<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">2000-08-01</dateIssued>
 <issuance>monographic</issuance>
</originInfo>
<physicalDescription>
 <note type="source content type">deposited</note>
 <digitalOrigin>born digital</digitalOrigin>
 <extent>24 p.</extent>
</physicalDescription>
<classification authority="sudocs">GA 1.13:AIMD-00-212</classification>
<identifier type="uri">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-212</identifier>
<identifier type="local">P0b002ee18039cab8</identifier>
<identifier type="former package identifier">f:ai00212</identifier>
<recordInfo>
 <recordContentSource authority="marcorg">DGPO</recordContentSource>
 <recordCreationDate encoding="w3cdtf">2010-08-12</recordCreationDate>
 <recordChangeDate encoding="w3cdtf">2011-03-24</recordChangeDate>
 <recordIdentifier source="DGPO">GAOREPORTS-AIMD-00-212</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-212</accessId>
 <reportNumber>AIMD-00-212</reportNumber>
 <subject>Systems design</subject>
 <subject>Information resources management</subject>
 <subject>Systems development life cycle</subject>
 <subject>ADP procurement</subject>
 <subject>Information technology</subject>
 <subject>Strategic information systems planning</subject>
 <identifier>DOJ Information Technology Architecture</identifier>
 <identifier>INS Computer Linked Application Information Management</identifier>
 <identifier>System</identifier>
 <type>Letter Report</type>
 <seriesAbbrev>AIMD</seriesAbbrev>
 <law congress="104" isPrivate="false" number="106"></law>
</extension>
<titleInfo>
 <title>Information Technology: INS Needs to Better Manage the</title>
</titleInfo>
<abstract>GAO reviewed the Immigration and Naturalization Service&apos;s (INS)
development of an enterprise architecture focusing on the: (1) status of
INS&apos; efforts and; (2) effectiveness of INS&apos; structures and processes for
managing this development effort.&lt;p/&gt;GAO noted that: (1) INS recognizes that it does not have an enterprise
architecture and has taken some limited steps to develop one; (2)
however, it has considerable work left to accomplish before it will have
a complete, and thus useful, enterprise architecture; (3) moreover, its
approach to managing the development of its architecture lacks
fundamental controls; (4) specifically, INS&apos; Office of Information
Resources Management (OIRM), which is the organization responsible for
managing INS&apos; information technology (IT) functions and assets, has, in
isolation from INS business owners, put together a bottom-up description
of INS&apos; IT environment and it has mapped its software applications to
INS&apos; three major business areas; (5) this is a reasonable start to
describing INS&apos; architectural environment; (6) however, important steps
still need to be accomplished, such as linking the systems environment
description to a decomposed view of INS&apos; business areas, including each
area&apos;s component business functions and subfunctions, and information
needs and flows among functions and subfunctions; (7) doing this with
any degree of reliability, however, requires business owners to validate
the resultant linkages; (8) also, INS has not begun developing either a
target architecture or a plan for sequencing between its current
architecture and a target architecture; (9) in lieu of the target
architecture, OIRM is developing what it calls an &quot;initial&quot; target
architecture that, according to the architecture team leader, is a
2-year plan for correcting known system-level problems; (10) this plan
will basically describe near-term system maintenance efforts and will
not provide a definition of the business and systems environments needed
to optimize INS&apos; mission performance; (11) INS&apos; limited steps to date to
develop an enterprise architecture are due to the absence of certain
fundamental management structures and processes associated with
successful architecture development; (12) INS has focused on the
technology layers of enterprise architecture, rather than on an agency
wide effort that includes participation by INS business owners; (13)
INS&apos; architecture development efforts are not being managed as a formal
program; (14) also, these efforts do not include performance measures
and progress reporting requirements to ensure that the effort is
progressing satisfactorily; and (15) without these management controls,
it is unlikely that INS will produce a complete and useful enterprise
architecture.</abstract>
<location>
 <url displayLabel="HTML rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-212/html/GAOREPORTS-AIMD-00-212.htm</url>
 <url displayLabel="PDF rendition" access="raw object">https://www.govinfo.gov/content/pkg/GAOREPORTS-AIMD-00-212/pdf/GAOREPORTS-AIMD-00-212.pdf</url>
</location>
<identifier type="preferred citation">GAO/AIMD-00-212</identifier>
<location>
 <url displayLabel="Content Detail" access="object in context">https://www.govinfo.gov/app/details/GAOREPORTS-AIMD-00-212</url>
</location>
<note>Letter Report</note>
<extension>
 <searchTitle>GAO/AIMD-00-212; Information Technology: INS Needs to Better Manage the;
            </searchTitle>
</extension>
<subject>
 <topic>Systems design</topic>
 <topic>Information resources management</topic>
 <topic>Systems development life cycle</topic>
 <topic>ADP procurement</topic>
 <topic>Information technology</topic>
 <topic>Strategic information systems planning</topic>
 <topic>DOJ Information Technology Architecture</topic>
 <topic>INS Computer Linked Application Information Management</topic>
 <topic>System</topic>
</subject>
<relatedItem type="isReferencedBy">
 <titleInfo>
  <title>United States Public Law 106 (104th Congress)</title>
</titleInfo>
 <identifier type="public law citation">Public Law 104-106</identifier>
</relatedItem>
</mods>