Enterprise architecture is the organizing logic for
business processes and IT infrastructure reflecting the integration and
standardization requirements of the company's operating model. The operating
model is the desired state of business process integration and business process
standardization for delivering goods and services to customers.The
intent of an enterprise architecture is to determine how an organization can
most effectively achieve its current and future objectivesPurported advantages of having an enterprise architecture include improved decision making, improved adaptability to changing demands or market conditions, elimination of inefficient and redundant processes, optimization of the use of organizational assets, and minimization of employee turnover.
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. In short, is a prefabricated structure (i.e., a framework) that organizes the system architecture of an enterprise into complementary projections called Views or Viewpoints.
A View is a projection of the system architecture model of an enterprise that is meaningful to one or more system stakeholders. For example, a Business Analysis View might project business requirements and business process workflows that are vital to Business Analysts and Clients, but less meaningful to other system stakeholders (e.g., Hardware Engineers, Network Architects). Conversely, a System Design View might project software design details that are essential to Software Engineers, Hardware Engineers, and Network Architects, but less meaningful to Business Analysts and Clients.
An Enterprise Architecture (EA) framework is a repeatable, consistent methodology to classify the relationship between business and IT, (in simple terms). There are several “EA Frameworks” available depending on where you look, who you work for, and how you plan to apply them. Almost every large organization has attempted to create some form of Enterprise Architecture model, often aligning business services with a repeatable and consistent method of mapping IT-related characteristics to known business drivers.
The components of an architecture framework provide structured guidance that is divided into three main areas:
*Descriptions of architecture: how to document the enterprise as a system from several viewpoints. Each view describes one slice of the architecture; it includes those entities and relationships that address particular concerns of interest to particular stakeholders; it may take the form of a list, a table, a diagram, or a higher level of composite of such.
*Methods for designing architect: processes that architects follow. Usually, an overarching enterprise architecture process, composed of phases, breaks into lower-level processes composed of finer grained activities. A process is defined by its objectives, inputs, phases (steps or activities) and outputs. It may be supported by approaches, techniques, tools, principles, rules, and practices.
*Organization of architects: guidance on the team structure, the governance of the team, the skills, experience and training needed. ... More
The relationship between an enterprise Architecture Framework to its Views is analogous to the relationship between a building blueprint and its complementary
EA is a journey, not a project. It evolves over time and needs to maintain the flexibility required to adjust to changing market conditions, strategy shifts, and new innovations in technology. EA frameworks have emerged to manage the increasingly complexity of innovation and change.
EA frameworks were created to simplify the process and guide an architect through all areas of architecture development. An Enterprise Architecture framework provides a collection of best practices, standards, tools, processes, and templates to assist in the creation of the EA and architectures of various scopes.
Today’s most commonly used frameworks are:-
- The Zachman Framework for Enterprise Architectures
- The Open Group Architectural Framework (TOGAF)
- The Federal Enterprise Architecture
- The Gartner Methodology
•The Zachman Framework for Enterprise Architectures—Although self-described as a framework, is actually more accurately defined as a taxonomy. It can be used to align communication and ensure you consider all of the important perspectives and dimensions of an enterprise.
•The Open Group Architectural Framework (TOGAF)—Although called a framework, is actually more accurately defined as a process. It is a more complete framework consisting of both a classification structure and progress guidelines aimed at asking the right questions and creating an enterprise architecture.
•The Federal Enterprise Architecture—Can be viewed as either an implemented enterprise architecture or a proscriptive methodology for creating an enterprise architecture
•The Gartner Methodology—Can be best described as an enterprise architectural practice.
In alignment with the Enterprise Architecture definition and model, the TM Forum member community produced the standards for the communications industry. Now, with over 900 member companies, the Forum is the largest global trade association focused on bringing together the digital ecosystem, including communication service providers, digital service providers and enterprises, with the goal of enabling an open digital world. The Forum delivers a wealth of knowledge and practical tools for it's members, including unique research, best practices and standards.
They have produced the following standards.
1. Business Process Framework (eTOM - Enhanced Telecom Operations Map)
2. Information Framework (SID - Shared Information Model)
3. Application Framework (TAM)
4. Integration Framework Architecture & Governance
5. Business Metrics
A New Vision for Enterprise Architecture
http://www.ebizq.net/blogs/enterprise/2009/09/fixing_enterprise_architecture.php
