Treasury Information System Architecture Framework: Difference between revisions

Revision as of 01:38, 19 July 2013

Revision as of 01:44, 19 July 2013

Line 16:

In July 1997, the Treasury issued additional guidance to complement Treasury Information System Architecture Framework (TISAF). This guidance, which was finalized in September 1997, provides “how to” processes for developing an information systems architecture in accordance with TISAF.<ref name=" GOA98"> United States General Accounting Office (US GOA) (1998). [http://www.gao.gov/archive/1998/ai98070.pdf CUSTOMS SERVICE MODERNIZATION : Architecture Must Be Complete and Enforced to Effectively Build and Maintain Systems] Report to Congressional Requesters.</ref> In 1989 US congress granted $200,000 for the department-wide implementation of the Treasury Information System Architecture Framework.<ref>US Congree (1998) ''Congressional Record, V. 144, Pt. 19, October 19, 1998 to December 19, 1998''. p. 27114</ref>

Further developments in the US Department of the Treasury let to the development of the [[Treasury Enterprise Architecture Framework]], first published in July 2000. The TEAF represents a revision to TISAF, basedand onincorporated elements of FEAF.<ref>Mark G. Mykityshyn (2007) ''Assessing the Maturity of Information Architectures for Complex Dynamic Enterprise Systems''. p. 77</ref>. It was the result of an evaluation of Department and bureau experiences in applying and using the TISAF, and emerging best practices from other government organizations and industry.

TEAF is intended to emphasize the broader scope of the architecture framework, which includes both business and technical vantage points within an enterprise-wide perspective. The TEAF includes descriptions of a common suite of work products for documenting and modeling EAs. These work products align with FEAF models and with Department of Defense Architecture Framework ([[DoDAF]]) products.<ref name="TEAF00"/>