Enterprise architecture framework: Difference between revisions

Revision as of 19:36, 23 December 2024

Revision as of 14:21, 9 February 2025

Line 16:

[[File:Evolution of Enterprise Architecture Frameworks.jpg|240px|thumb|Overview of Enterprise Architecture Frameworks evolution (1987–2003).<ref name="SM03"/><ref>[[Jaap Schekkerman]] (2004) ''How to Survive in the Jungle of Enterprise Architecture Frameworks''. p.89 gives a similar scheme.</ref> On the left: The [[Zachman Framework]] 1987, [[NIST Enterprise Architecture Model|NIST Enterprise Architecture]] 1989, [[Enterprise Architecture Planning|EAP]] 1992, [[TISAF]] 1997, [[Federal Enterprise Architecture|FEAF]] 1999 and [[Treasury Enterprise Architecture Framework|TEAF]] 2000. On the right: [[TAFIM]] influenced by [[POSIX]], JTA, JTAA, [[TOGAF]] 1995, DoD TRM<ref>US Department of Defense (2001) ''[http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.196.5206&rep=rep1&type=pdf Department of Defense Technical Reference Model]''. Version 2.0. 9 April 2001. p. 11, mentioned that also the DoD TRM is influenced by POSIX.</ref> and [[C4ISTAR|C4ISR]] 1996, and [[DoDAF]] 2003.]]

The earliest rudiments of the step-wise planning methodology currently advocated by [[The Open Group Architecture Framework]] (TOGAF) and other EA frameworks can be traced back to the article of Marshall K. Evans and Lou R. Hague titled "Master Plan for Information Systems"<ref>Evans, M. K. and Hague, L. R. (1962) ''Master Plan for Information Systems'', Harvard Business Review, Vol. 40, No. 1, pp. 92-103.</ref> published in 1962 in Harvard Business Review.<ref name="The_Practice_of_EA">Kotusev, Svyatoslav (2021) ''The Practice of Enterprise Architecture: A Modern Approach to Business and IT Alignment (2nd Edition)''. Melbourne, Australia: SK Publishing.</ref>

Since the 1970s people working in IS/IT have looked for ways to engage business people – to enable business roles and processes - and to influence investment in business information systems and technologies – with a view to the wide and long term benefits of the enterprise. Many of the aims, principles, concepts and methods now employed in EA frameworks were established in the 1980s, and can be found in IS and IT architecture frameworks published in that decade and the next.<ref name="GB 2013">Graham Berrisford (2008-13) "[http://grahamberrisford.com/A%20brief%20history%20of%20EA.htm A brief history of EA: what is in it and what is not] {{Webarchive|url=https://web.archive.org/web/20130918061630/http://grahamberrisford.com/A%20brief%20history%20of%20EA.htm |date=2013-09-18 }}" on ''grahamberrisford.com'', last update 16/07/2013. Accessed 16/07?2003</ref>

Line 28:

In 1982, when working for IBM and with BSP, John Zachman outlined his framework for enterprise-level "Information Systems Architecture". Then and in later papers, Zachman used the word enterprise as a synonym for business. "Although many popular information systems planning methodologies, design approaches, and various tools and techniques do not preclude or are not inconsistent with enterprise-level analysis, few of them explicitly address or attempt to define enterprise architectures."<ref name="JZ 1982">[[John Zachman]] (1982) ''Business Systems Planning and Business Information Control Study: A comparison'' in IBM Systems Journal 21(1). p32.</ref> However, in this article the term "Enterprise Architecture" was mentioned only once without any specific definition and all subsequent works of Zachman used the term "Information Systems Architecture".<ref name="JZ 1987" /><ref name="JZ 1992"/>

In 1986, the [[PRISM architecture framework]] was developed as a result of the research project sponsored by a group of companies, including IBM, which was seemingly the first published EA framework.<ref name="HISTORY">Svyatoslav Kotusev (2016). ''The History of Enterprise Architecture: An Evidence-Based Review''. In: Journal of Enterprise Architecture, vol. 12, no. 1, pp. 29-37.</ref>

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.