Foundations of EA
Author: Eddie Wang
A principle is a general guideline for behavior in specific situations. The usefulness of principles is in their general orientation and perspective; they do not prescribe specific actions. A given principle applies in some contexts but not all contexts. Different principles may appear to conflict with each other, such as the principle of accessibility and the principle of security. Therefore, applying principles in the development of EA requires deliberation and often tradeoffs. The selection of principles to apply to a given EA is based on a combination of the general environment of the enterprise and the specifics of the goals and purpose of the EA. The application of appropriate principles facilitates grounding, balance, and positioning of an EA. Principles are sometimes given an order of primacy; when the application of two or more principles would result in conflicting decisions, the principle given primacy drives the decision.
Principles considered in developing an EA comprise several types. These may include Enterprise Principles, Architecture Principles, and Information Technology Principles, as well as Integrative Principles that tie these together. TOGAF provides another set of example Principle types that include: Business Principles, Data Principles, Application Principles, and Technology Principles. This topic area includes guidance and other references that will help the EA practitioner establish the proper principles upon which to develop a successful EA.
Regardless of what set of principles an organization settles on, the principles should act as a foundation of shared understanding that guides the use, management, and transformation of IT within your organization.
This topic area provides an EA practitioner access to guidance, case studies, and other references that demonstrate defining the scope of an EA, including appropriate level of detail.
- Architecture Principles: The Open Group Library.
- Douglass, C., (2014) Enterprise Architecture Principles, Plymouth University, UK.
EABOK® Knowledge Areas
Organizational Scope and Structure of EA
Developing an EA
- Business Requirements and Value Proposition
- Methodologies and Processes
- Architecture Frameworks
- Data and Information Management
- Project Management
- Change Management
- Testing and Evaluation
- Modeling and Simulation
- Role of Reference Architectures
- How to Build a Reference Architecture
- Coordinating the Creation of a Reference Architecture
Management of EA
EA in Practice
Perspectives on EA
EABOK is an evolving knowledge base and more information will be released as available.
In addition to the EABOK Board members, the content is also contributed by the following MITRE employees:
- Carla Kendrick
- Brenda Yu
- Eddie Wang
- Rose Tykinski
- Wakar Khan
- Mike Russell
This website is managed by the EABOK Consortium and hosted by MITRE to enable stakeholder collaboration within the EA community.
EABOK and the EABOK logo are trademarks of MITRE and are used by The EABOK Consortium with permission.
All other trademarks are the property of their respective owners. All rights reserved.