As

described in American [Link] Standards [Link]/[Link] of Electrical and Electronics Engineers (ANSI/IEEE) Std 1471-2000, an architecture is "the fundamental [Link] of a system, embodied in its components, their [Link] to each other and the environment, and the principles governing its design and [Link]."

 The goal of enterprise architecture is to promote alignment, [Link], reuse of [Link] IT assets, and the sharing of common methods for project management and soLware development across the [Link]. The end result, [Link], is that the enterprise architecture will make IT cheaper, more strategic, and more responsive.

 The purpose of enterprise architecture is to create a map of IT assets and business processes and a set of governance principles that drive an ongoing discussion about business strategy and how it can be expressed through IT.

Frameworks contain four basic domains, as follows: Business architecture: [Link] that outlines the company's most important business processes; Informa=on architecture: [Link] where important blocks of [Link], such as a customer record, are kept and how one typically accesses them; Applica=on system architecture: a map of the [Link] of soLware [Link] to one another; and The infrastructure technology architecture: a blueprint for the gamut of hardware, storage systems, and networks. The business architecture is the most [Link], but also the most dicult to implement, according to industry prac..oners.

Enterprise Architecture (EA) Frameworks (par=al list) 1. 1. Zachman Enterprise Architecture Framework (ZIFA) 2. The Open Group Architecture Framework (TOGAF) ) 3. Extended Enterprise Architecture Framework (E2AF) ) 4. Enterprise Architecture Planning (EAP) ) 5. Federal Enterprise Architecture Framework (FEAF) ) 6. Treasury Enterprise Architecture Framework (TEAF) ) 7. Integrated Architecture Framework (IAF) ) 8. Joint Technical Architecture (JTA) ) 9. Command, Control, [Link], Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) and DoD Architecture Framework (DoDAF) ) 10. Department of Defense Technical Reference Model (DoD TRM) ) 11. Technical Architecture Framework for [Link] Management (TAFIM) ) 12. Computer Integrated Manufacturing Open System Architecture (CIMOSA) ) 13. Purdue Enterprise Reference Architecture (PERA) ) 14. Standards and Architecture for eGovernment [Link] (SAGA) ) 15. European Union-IDABC & European Interoperability Framework) 16. ISO/IEC 14252 (IEEE Std 1003.0) ) 17. IEEE Std 1471-2000 IEEE Recommended [Link] for Architectural [Link] Fundamentally, all models seek in some way to make use of the concept of a generic service/object- oriented architecture

Macro view of the environment and of enterprise architecture.

Maturity of enterprise architecture development at a rm.

Necessity of enterprise architecture as environment grows more complex.

Some basic events that trigger a refresh of an enterprise architecture.

 Any enterprise architecture must be seen (designed, delivered, and internally sold) as a deliverable product, something that can be "touched and used" not just an abstract conceptualiza=on. In the IT context, an architecture needs to be perceived (seen) by users and stakeholders almost like another IT system [Link]: it must have inputs, outputs, func=onality, built-in data, etc. A simple conceptualiza=on is dicult to be seen as adding value.

Enterprise architecture model, also showing architecture ar=facts.

Business Func=on: This is a [Link] of all business elements and structures that are covered by the enterprise. Business Architecture: An architectural [Link] of the Business [Link]. Informa=on Func=on: This is a comprehensive [Link] of the data, the data ows, and the data [Link] required to support the Business [Link]. The [Link], [Link], [Link], and inventory/storage of [Link] are always necessary to run a business, but these are [Link] if the data-handling [Link] are to be automated. Informa=on Architecture: An architectural [Link] of the [Link] [Link] via a data model. (Systems/Applica=on) Solu=on Func=on: This is the [Link] that aims at delivering/supplying computerized IT systems required to support the plethora of specic [Link] needed by the Business [Link]. (Systems/Applica=on) Solu=on Architecture: An architectural [Link] of the (Systems/ [Link]) [Link] [Link]. Technology Infrastructure Func=on: The complete technology environment required to support the [Link] [Link] and the (Systems/[Link]) [Link] [Link]. Technology Infrastructure Architecture: An architectural [Link] ([Link]) of the Technology Infrastructure [Link].

A layered model of the enterprise architecture.