Oversight of the Internal Revenue Service: Hearings Before the Committee on Governmental Affairs, United States Senate, One Hundred Fourth Congress, Second Session, March 26, 1996 ... September 10, 1996, Technical and Management Issues in IRS Modernization

Couverture
 

Avis des internautes - Rédiger un commentaire

Aucun commentaire n'a été trouvé aux emplacements habituels.

Autres éditions - Tout afficher

Expressions et termes fréquents

Fréquemment cités

Page 19 - Executive Guide: Improving Mission Performance Through Strategic Information Management and Technology (GAO/AIMD-94-115, May 1994), and our Strategic Information Management (SIM) Self-Assessment Toolkit (GAO/Version 1.0, October 28, 1994, exposure draft).
Page 127 - Its mission is to collect the proper amount of tax revenue at the least cost to the public, and in a manner that warrants the highest degree of public confidence in the Service's integrity, efficiency, and fairness.
Page 300 - IRS* pervasive management and technical weaknesses, (3) are small, represent low technical risk, and can be delivered in a relatively short time frame, and (4) involve deploying already developed systems...
Page 299 - Tax Systems Modernization: Management and Technical Weaknesses Must Be Corrected If Modernization Is To Succeed...
Page 456 - ... (4) involve deploying already developed systems that have been fully tested, are not premature given the lack of a complete systems architecture, and produce a proven, verifiable business value. The act providing IRS' fiscal year 1997 appropriations9 limited IRS' IT spending to efforts consistent with these categories.
Page 634 - Operations not later than 60 days after the date of the report and to the House and Senate Committees on Appropriations with the agency's first request for appropriations made more than 60 xiays after the date of the report.
Page 265 - I will be glad to answer any questions that you or the other Members of the Committee may have at this time.
Page 292 - A system architecture is an evolving description of an approach to achieving a desired mission. It describes (1) all functional activities to be performed to achieve the desired mission, (2) the system elements needed to perform the functions, (3) the designation of performance levels of those system elements, and (4) the technologies, interfaces, and location of functions. IRS agreed with these recommendations and said that it was identifying the necessary actions to define and enforce systems development...
Page 471 - Act provides the underpinning for identifying and correcting financial management weaknesses and reliably reporting on the results of IRS
Page 22 - IRS' current request for information services process, and for software quality assurance, software configuration management, and project planning and tracking; and define and implement a set of software development metrics to measure software attributes related to business goals. IRS agreed with these recommendations and said that it was committed to developing consistent procedures addressing requirements management, software quality assurance, software configuration management, and project planning...

Informations bibliographiques