Content deleted Content added
rm COI / citespam |
m →Open-source frameworks: Tag Bare URLs using AWB |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 32:
In 1987, John Zachman, who was a marketing specialist at IBM, published the paper, ''A Framework for Information Systems Architecture''.<ref name="JZ 1987">[[John A. Zachman]] (1987). '' A Framework for Information Systems Architecture''. In: IBM Systems Journal, vol 26, no 3. IBM Publication G321-5298.</ref> The paper provided a classification scheme for [[Enterprise architecture artifacts|artifacts]] that describe (at several levels of abstraction) the what, how, where, who, when and why of information systems. Given IBM already employed BSP, Zachman had no need to provide planning process. The paper did not mention enterprise architecture.
In 1989, the National Institute of Standards and Technology (NIST) published the [[NIST Enterprise Architecture Model]].<ref>W.B. Rigdon (1989). ''Architectures and Standards''. In Information Management Directions: The Integration Challenge (NIST Special Publication 500-167), E.N. Fong, A.H. Goldfine (Eds.), Gaithersburg, MD: National Institute of Standards and Technology (NIST), pp.135-150.</ref> This was a five-layer reference model that illustrates the interrelationship of business, information system, and technology domains. It was promoted within the U.S. federal government. It was not an EA framework as we see it now, but it helped to establish the notion of dividing EA into architecture domains or layers. The NIST Enterprise Architecture Model seemingly was the first publication that consistently used the term "Enterprise Architecture".
In 1990, the term "Enterprise Architecture" was formally defined for the first time as an architecture that "defines and interrelates data, hardware, software, and communications resources, as well as the supporting organization required to maintain the overall physical structure required by the architecture".
In 1992, a paper by Zachman and Sowa<ref name="JZ 1992">Zachman and Sowa (1992) ''Extending and formalising the framework of information systems architecture'' IBM Systems Journal, Vol 31, No 3</ref> started thus "John Zachman introduced a framework for information systems architecture (ISA) that has been widely adopted by systems analysts and database designers." The term enterprise architecture did not appear. The paper was about using the ISA framework to describe, “...the overall information system and how it relates to the enterprise and its surrounding environment.” The word enterprise was used as a synonym for business.
In 1993, Stephen Spewak's book [[Enterprise Architecture Planning]] (EAP) defined a process for defining architectures for the use of information in support of the business and the plan for implementing those architectures. The business mission is the primary driver. Then the data required to satisfy the mission. Then the applications built to store and provide that data. Finally the technology to implement the applications. Enterprise Architecture Planning is a data-centric approach to architecture planning. An aim is to improve data quality, access to data, adaptability to changing requirements, data interoperability and sharing, and cost containment. EAP has its roots in IBM's [[Business Systems Planning]] (BSP).
In 1994, the Open Group selected [[TAFIM]] from the US DoD as a basis for development of TOGAF, where architecture meant IT architecture. TOGAF started out taking a strategic and enterprise-wide, but technology-oriented, view. It emerged from the desire to rationalize a messy IT estate. Right up to version 7, TOGAF was still focused on defining and using a Technical Reference Model (or foundation architecture) to define the platform services required from the technologies that an entire enterprise uses to support business applications.<ref name="GB 2013"/>
Line 136:
== Types of enterprise architecture framework ==
[[File:Enterprise Architecture frameworks utilized 2011.jpg|thumb|240px|Just a few of the Enterprise Architecture frameworks utilized today, 2011<ref>[[Dennis E. Wisnosky]] (2011) ''[https://web.archive.org/web/20120921044933/http://dcmo.defense.gov/products-and-services/business-enterprise-architecture/8.1/products/BusOpsTransformation_EA_BI/7_cdq_issue9_january2011.pdf Engineering Enterprise Architecture: Call to Action]''. in: ''Common Defense Quarterly''. January 2011, p. 9</ref>]]
Nowadays there are now countless EA frameworks, many more than in the following listing.
Line 170:
Enterprise architecture frameworks that are released as [[Open Source Definition|open source]]:
* [[ArchiMate]]
* [[Lean Architecture Framework]] (LAF)<ref>https://lafinstitute.org/ {{Bare URL inline|date=August 2025}}</ref> is a collection of good practices thanks to which the IT environment will respond consistently and quickly to a changing business situation while maintaining its consistent form.
* MEGAF (Mega-modeling Architecture Framework)<ref>[http://megaf.di.univaq.it/ MEGAF]</ref> is an infrastructure for realizing architecture frameworks that conform to the definition of architecture framework provided in [[ISO/IEC 42010|ISO/IEC/IEEE 42010]].
* [[Praxeme]], an open enterprise methodology, contains an enterprise architecture framework called the Enterprise System Topology (EST)
| |||