Content deleted Content added
Repairing link to disambiguation page - You can help! |
m standard quote handling in WP;standard Apostrophe/quotation marks in WP; MOS general fixes |
||
| (11 intermediate revisions by 6 users not shown) | |||
Line 1:
[[File:TISAF Architectural View Relationships.jpg|thumb|360px|Relationships of the architectural views in TISAF.]]
The '''Treasury Information System Architecture Framework''' (TISAF) is
The TISAF was developed by the [[US Department of the Treasury]] in 1997, and let to the development of the [[Treasury Enterprise Architecture Framework]], released in 2000. The TEAF represents the second-generation framework for Treasury. TISAF was the first-generation framework.<ref name="TEAF00">
== Overview ==
The Treasury Information System Architecture Framework (TISAF) consists of a list of goals and objectives for planning [[Treasury]] [[information technology]] a set of architectural principles for developing information systems, an EISA model for describing distinct views of enterprise information systems, and a set of standards for guiding specific product selection.<ref name="Raines97"/>
The EISA model provides four [[view model|architectural view]]s to organize, plan, and build enterprise information systems, consisting of the Information, Functional, and Work architectures and the Infrastructure.<ref name="Raines97"/>
== History ==
TISAF incorporated elements from the C4ISR Architecture Framework, which was developed by the [[Mitre Corporation]] from 1994 on.<ref>Janis Putman (2001) ''Architecting With Rm-Odp''. p. 719</ref> In January 1997, [[US Department of the Treasury]] issued TISAF Version 1, consisting of three volumes:<ref name="TEAF00"/>
In January 1997, [[US Department of the Treasury]] issued TISAF Version 1, consisting of three volumes: the Treasury Information Systems Architecture Framework, Treasury Architecture Development Guidance, and the Treasury Architecture Development Process.<ref name="TEAF00"/> 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>▼
* the Treasury Information Systems Architecture Framework,
* Treasury Architecture Development Guidance, and
* the Treasury Architecture Development Process.
▲
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"/> == TISAF building blocks ==
=== Departmentwide architecture framework ===
According to TISAF, a complete architecture has the following four components, each representing a different [[Perspective (visual)|perspective]] or [[Opinion|view]] of the agency:<ref name=" GOA98"/>
* ''Functional'': A representation of what the organization does (i.e., its mission and business processes) and how the organization can use information systems to support its business operations.
* ''Work'': A description of where and by whom information systems are to be used throughout the agency.
* ''Information'': A description of what information is needed to support business operations.
* ''Infrastructure'': A description of the hardware and
=== Top-down approach ===
To develop and evolve systems that effectively support business functions, a top-down process must be followed. The logical architecture (e.g., business functions and information flows) is defined first and then used to specify supporting systems (e.g., interfaces, standards, and protocols).<ref name=" GOA98"/>
Treasury endorses this top-down approach. Treasury officials responsible for developing and implementing TISAF stated that development of the architecture begins with defining and describing the
specifications and standards) should be derived from the other three components. In addition, the guidance states that each element of the architecture must be integrated and traceable, and the relationships between them must be explicit.<ref name=" GOA98"/>
Line 35 ⟶ 42:
The Infrastructure is the "enabler" of information systems which describes the supporting services, computing platforms, and internal and external interfaces needed to provide technology environments within which information systems run.<ref name="Raines97"/>
To provide a context for discussing technical standards, a [[Technical Reference Model]] (TRM) is developed to organize and depict building blocks of an information system as a set of services categorized by functional areas.<ref name="Raines97"/>
== TISAF 1997 to TEAF 2000 ==
Line 50 ⟶ 57:
* Approaches for implementing an EA are now included and are documented as EA Accomplishment work products
* Alignments of the TEAF with the FEAF and the Zachman Framework are provided
== See also ==
* [[NIST Enterprise Architecture Model]]
* [[TAFIM|Technical Architecture Framework for Information Management]] (TAFIM)
== References ==
{{
{{reflist|2}}
[[Category:United States Office of Management and Budget]]
[[Category:Enterprise architecture frameworks]]
[[Category:Reference models]]
| |||