Difference between revisions of "Enterprise Architecture Framework"

Revision as of 20:42, 10 December 2019

Enterprise Architecture Framework (EA Framework) is a formal definition of the essential elements or components of Enterprise Architecture, and their inter-relationship

An Enterprise Architecture Framework is analogous to a mathematical equation or chemical formula in that it specifies the variables or elements, and their relationships required to solve the "practical model of enterprise" puzzle.
It differs from equations and formulas in the sense that it pertains to one solution - a particular way of solving the enterprise modeling puzzle - and is not universally applicable or accepted answer to the Enterprise Architecture problem. There can be many different frameworks for Enterprise Architecture each as applicable and effective as the other.
It identifies "essential" elements or components i.e. those that are absolutely necessary, and sufficient to define the concept or solution

An Enterprise Architecture Framework can define enterprise modeling concept(s) in general or relate to a specific Enterprise Architecture Planning solution.

An Enterprise Architecture framework (EA framework) defines how to create and use an Enterprise Architecture. An Architecture Framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers or views, and offers models - typically matrices and diagrams - for documenting each view.^[1]

History of Enterprise Architecture Frameworks (EAF)^[2]
A commonly held tenet is that enterprise architecture frameworks date to the mid-1980s, in accordance with the publication of the Zachman Framework, developed by then-IBMer John Zachman. But deeper historic inquiries indicate that enterprise architecture frameworks actually got their start two decades earlier, when IBM produced their business systems planning (BSP), an effort that Zachman helped found.

A researcher of 20th– and 21st-century technology, Svyatoslav Kotusev says that we can look at the history of EAFs in three smaller eras:

Pre-EA: Originating with IBM, the BSP formalized a methodology that indicates a theory for information systems architecture. It included both a top-down planning approach and an architecture planning process that was divided into a series of steps for a company to follow. The plan, with diagrams and matrices to illustrate its system, can be traced through all EAFs even today. The Method/1 process by Arthur Andersen as well as other BSP-like methodologies from consulting firms and tech experts also originated in this era. Overall, these approaches focused strictly on technical infrastructure, like how to deploy hardware and servers.
Early EA: This begins in the 1980s and runs into the 1990s, and this era codifies the term “enterprise architecture”. The initial wave of EAF theories include the PRISM, sponsored by IBM among others, released in 1986, the Zachman Framework in 1987, and the NIST EA in 1989. Later entries marked a newer approach in this era including Steven Spewak’s Enterprise Architecture Planning (EAP), which has direct roots to the original BSP, as well as the TAFIM. These later frameworks began including applications and data integration, as systems became more sophisticated.
Modern EA: Starting in the late 1990s, this era continues to present day. Newer frameworks include the FEAF, which is based on Spewak’s EAP, as well as the TOGAF, a well-known version today, with roots in the TAFIM. Today’s frameworks aim to provide tangible solutions beyond only IT, integrating all layers of an enterprise, including overall strategy, business needs, IT infrastructure, and applications.

Despite the differences in approaches that these eras indicate, all frameworks are generally based on the original BSP methodology, often advocating similar steps or phases for planning and implementing enterprise IT.

References

↑ What is Enterprise Architecture framework? Wikipedia
↑ History of Enterprise Architecture Frameworks (EAF) BMC

@@ Line 7: / Line 7: @@
 An Enterprise Architecture framework (EA framework) defines how to create and use an [[Enterprise Architecture]]. An Architecture Framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers or views, and offers models - typically matrices and diagrams - for documenting each view.<ref>What is Enterprise Architecture framework? [https://en.wikipedia.org/wiki/Enterprise_architecture_framework Wikipedia]</ref>
+'''History of Enterprise Architecture Frameworks (EAF)<ref>History of Enterprise Architecture Frameworks (EAF) [https://www.bmc.com/blogs/enterprise-architecture-frameworks/ BMC]</ref>'''<br />
+A commonly held tenet is that enterprise architecture frameworks date to the mid-1980s, in accordance with the publication of the [[Zachman Framework]], developed by then-IBMer John Zachman. But deeper historic inquiries indicate that enterprise architecture frameworks actually got their start two decades earlier, when IBM produced their [[Business Systems Planning (BSP)|business systems planning (BSP)]], an effort that Zachman helped found.
+A researcher of 20th– and 21st-century technology, Svyatoslav Kotusev says that we can look at the history of EAFs in three smaller eras:
+*Pre-EA: Originating with IBM, the BSP formalized a methodology that indicates a theory for information systems architecture. It included both a top-down planning approach and an architecture planning process that was divided into a series of steps for a company to follow. The plan, with diagrams and matrices to illustrate its system, can be traced through all EAFs even today. The Method/1 process by Arthur Andersen as well as other BSP-like methodologies from consulting firms and tech experts also originated in this era. Overall, these approaches focused strictly on technical infrastructure, like how to deploy hardware and servers.
+*Early EA: This begins in the 1980s and runs into the 1990s, and this era codifies the term “[[Enterprise Architecture|enterprise architecture]]”. The initial wave of EAF theories include the PRISM, sponsored by IBM among others, released in 1986, the Zachman Framework in 1987, and the [[NIST Enterprise Architecture Model (NIST EA Model)|NIST EA]] in 1989. Later entries marked a newer approach in this era including Steven Spewak’s Enterprise Architecture Planning (EAP), which has direct roots to the original BSP, as well as the [[Technical Architecture Framework for Information Management (TAFIM)|TAFIM]]. These later frameworks began including applications and [[Data Integration|data integration]], as systems became more sophisticated.
+*Modern EA: Starting in the late 1990s, this era continues to present day. Newer frameworks include the [[Federal Enterprise Architecture Framework (FEA)|FEAF]], which is based on Spewak’s EAP, as well as the [[The Open Group Architecture Framework (TOGAF)|TOGA]]F, a well-known version today, with roots in the TAFIM. Today’s frameworks aim to provide tangible solutions beyond only [[Information Technology (IT)|IT]], integrating all layers of an enterprise, including overall [[Strategy|strategy]], [[Business Requirements|business needs]], [[IT Infrastructure|IT infrastructure]], and applications.
+Despite the differences in approaches that these eras indicate, all frameworks are generally based on the original BSP methodology, often advocating similar steps or phases for planning and implementing enterprise IT.

Difference between revisions of "Enterprise Architecture Framework"

Revision as of 20:42, 10 December 2019

See Also

References

Further Reading