With Great thanks to Roger Sessions - ObjectWatch, Inc.
Through the mid 1980s and 90s, businesses realized that IT systems were becoming more and more complex, and more and more expensive. Vendors used differing standards, integration was difficult at best, and impossible most of the time.
To add gas to the fire, by the time these IT systems were built, they no longer aligned with Business Requirements.
Out of this requirement for aligning Business Needs to IT Architecture and implementation, while keeping costs in line, came the field of Enterprise Architecture.
"Issues that we are faced withManagement and users often express their dissatisfaction with the IT systems and we feel the need of addressing their concern. The common refrain that we hear is as follows:
i) IT systems have become unmanageably complex and increasingly costly to maintain.ii) IT systems are hindering the organization’s ability to respond to current, and future, market conditions in a timely and cost-effective manner.iii) Mission-critical information (provided by IT) is consistently out-of-date and/ or just plain wrong.iv) A culture of distrust is developing between the business and technology sides of the organization."
Definition of terms as per IEEE 1471-2000 Recommended Practice for Architectural Description of Software-Intensive Systems
- architect—One whose responsibility is the design of an architecture and the creation of an architectural description
- architectural artifact—A specific document, report, analysis, model, or other tangible that contributes to an architectural description
- architectural description—A collection of products (artifacts) to document an architecture
- architectural framework—A skeletal structure that defines suggested architectural artifacts, describes how those artifacts are related to each other, and provides generic definitions for what those artifacts might look like
- architectural methodology—A generic term that can describe any structured approach to solving some or all of the problems related to architecture
- architectural process—A defined series of actions directed to the goal of producing either an architecture or an architectural description
- architectural taxonomy—A methodology for organizing and categorizing architectural artifacts
- architecture—The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution
- enterprise architecture—An architecture in which the system in question is the whole enterprise, especially the business processes, technologies, and information systems of the enterprise
Understanding and applying the Open Group Architecture Framework - TOGAF
Microsoft MSDN: A Comparison of the Top Four Enterprise-Architecture Methodologies
Objectwatch: Comparison of the Top Four Enterprise Architecture Methodologies
Welcome to TOGAF® Version 9.1 "Enterprise Edition"
TOGAF 9.1 Online Book
Canadian Department of National Defence (DNDAF)
The Best Enterprise Architecture: “Less is More”