Enterprise Architecture

[anitsh]

Prerequisite

176

Enterprise Architecture

It is a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes.

Practitioners of enterprise architecture, enterprise architects, are responsible for performing the analysis of business structure and processes and are often called upon to draw conclusions from the information collected to address the goals of enterprise architecture: effectiveness, efficiency, agility, and continuity of complex business operations.

• [ ] https://en.wikipedia.org/wiki/Enterprise_architecture
• [ ] https://en.wikipedia.org/wiki/Enterprise_architecture_planning
• [ ] https://en.wikipedia.org/wiki/Enterprise_architecture_artifacts
• [ ] Tools for Enterprise Architecture - The Open Group Conference.pdf
• [ ] https://medium.com/capital-one-tech/a-manifesto-for-effective-enterprise-architecture-7e887185f587
• [ ] http://www3.cis.gsu.edu/dtruex/courses/CIS8090/2013Articles/A%20Comparison%20of%20the%20Top%20Four%20Enterprise-Architecture%20Methodologies.html
• [ ] https://www.cio.com/article/3313657/what-is-enterprise-architecture-a-framework-for-transformation.html
• [ ] https://www.oracle.com/technical-resources/articles/enterprise-architecture/ricca-bridging-ea-sa.html
• [x] https://www.contino.io/insights/how-to-make-enterprise-container-strategies-that-last-part-one
• [ ] https://www.opengroup.org/what-we-do-technology-standards
• [ ] https://en.m.wikipedia.org/wiki/NIST_Enterprise_Architecture_Model
• [ ] https://ingine.wordpress.com/2013/07/16/for-who-the-heck-is-enterprise-architecture-not
• [ ] https://orey.github.io/papers/articles/mbse-vs-ea

[anitsh]

The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture today that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

TOGAF was developed starting 1995 by The Open Group, based on United States Department of Defense's TAFIM and Capgemini's Integrated Architecture Framework (IAF). As of 2016, The Open Group claims that TOGAF is employed by 80% of Global 50 companies and 60% of Fortune 500 companies

https://en.wikipedia.org/wiki/The_Open_Group_Architecture_Framework

[anitsh]

The Zachman Framework is an enterprise ontology and is a fundamental structure for Enterprise Architecture which provides a formal and structured way of viewing and defining an enterprise. The ontology is a two dimensional classification schema that reflects the intersection between two historical classifications. The first are primitive interrogatives: What, How, When, Who, Where, and Why. The second is derived from the philosophical concept of reification, the transformation of an abstract idea into an instantiation. The Zachman Framework reification transformations are: Identification, Definition, Representation, Specification, Configuration and Instantiation. The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes.; rather, it is an ontology whereby a schema for organizing architectural artifacts (in other words, design documents, specifications, and models) is used to take into account both who the artifact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed. The framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since. https://en.wikipedia.org/wiki/Zachman_Framework