[ Have you...: ]
- understood the issues and opportunities with your current applications and technical architecture?
- developed a future state and migration path for the technology that supports your enterprise?
- provided your business executives with a direction and decision making framework for IT capex?
- provided Information System (IS) with a blueprint for development?
If you haven't done, you need immediately a method for analyzing and designing your organization’s Information architecture, with the above goals.
IT people call this as a Business System Planning (BSP) but is something more...
Do it, now, with the right way!
----------

[ The term Enterprise Architecture (EA) ]

An Enterprise Architecture (EA) framework defines how to create and use an Enterprise Architecture providing 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.

Enterprise architecture (EA) is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a holistic 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."

But  there are various perspectives in regards to the meaning of the term enterprise architecture:
- MIT Center for Information Systems Research defined enterprise architecture as the specific aspects of a business that are under examination:
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.
- IT analysis firm Gartner defines the term as a discipline where an enterprise is led through change:

Enterprise architecture (EA) is a discipline for proactively and holistically leading enterprise responses to disruptive forces by identifying and analyzing the execution of change toward desired business vision and outcomes. EA delivers value by presenting business and IT leaders with signature-ready recommendations for adjusting policies and projects to achieve target business outcomes that capitalize on relevant business disruptions. EA is used to steer decision making toward the evolution of the future state architecture.

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 durability.
----------

[ The scope of Enterprise Architecture ]

The three key aspects for the purpose of EA are:

- Enterprise IT design: is the greater alignment between IT and business concerns. The main purpose of enterprise architecture is to guide the process of planning and design the IT/IS capabilities of an enterprise in order to meet desired organizational objectives. Typically, architecture proposals and decisions are limited to the IT/IS aspects of the enterprise; other aspects only serve as inputs.

Enterprise integrating: is to achieve greater coherency between the various concerns of an enterprise (HR, IT, Operations, etc.) including the linking between strategy formulation and execution. Typically, architecture proposals and decisions encompass all the aspects of the enterprise.

Enterprise ecological adaptation: the purpose of EA is to foster and maintain the learning capabilities of enterprises so that they may be sustainable. Consequently, a great deal of emphasis is put on improving the capabilities of the enterprise to improve itself, to innovate and to coevolve with its environment. Typically, proposals and decisions encompass both the enterprise and its environment.
----------

[ Architectural description of an enterprise ]

Architecture Description called the product used to describe the architecture of an enterprise and contains a variety of lists, tables and diagrams. These are models known as views and describe:

- Logical business functions or capabilities,
- Business processes,
- Human roles and actors,
- The physical organization structure,
  - The data flows and data stores,
- Business applications and platform applications,
- Hardware and communications infrastructure

The architecture of an enterprise is described with a view to improving the manageability, effectiveness, efficiency or agility of the business, and ensuring that money spent on Information Technology (IT) is justified.
Changes considered by enterprise architects typically include:
- innovations in the structure or processes of an organization
- innovations in the use of information systems or technologies
- the integration and/or standardization of business processes,
- improving the quality and timeliness of business information.
----------

[ EA Framework ]
Enterprise Architecture Framework is a methodology for developing and using architecture to guide the transformation of a business  from a baseline state to a target state, sometimes through several transition states. Provides a structured collection of processes, techniques, artifact descriptions, reference models and guidance for the production and use of an enterprise-specific architecture description.
----------

[ EA Benefits ]
The benefits of enterprise architecture are achieved through its direct and indirect contributions to organizational goals. It has been found that the most notable benefits of enterprise architecture can be observed in the following areas:

Organizational design - Organizational processes and process standards
- Project Portfolio Management
- Project management
- Requirements Engineering
- System development
- IT management and decision making
- IT value
- IT complexity
- IT openness
- IT risk management
----------

[ Relations with other methods ]
An Enterprise Architecture practice collaborates with many inter-‐connected disciplines including:
- performance engineering and management,
- process engineering and management,
- IT and enterprise portfolio management,
- governance and compliance,
- IT strategic planning,
- risk analysis,
- information management,
- metadata management
----------

[ But ]
A key concern about EA has been the difficulty in arriving in metrics of success, because of the broad-brush and often opaque nature of EA projects.
But in our approach we know the way to measure the EA method we apply to our customers.
Because we have a well defined and approved suite of methodologies to do the agreed job in a successful way!
----------

[ EA Development Cycle ]
The ADM is our method for EA development, which is designed to deal with most system and organizational requirements. However, it will often be necessary to ensure if any modification or extention is needed to suit our customers' specific needs. One of the tasks before applying the ADM is to review its components for applicability, and then tailor them as appropriate to the circumstances of the individual enterprise. This activity may well produce an "enter prise-specific" ADM.

[ Content Metamodel overview ]
The content metamodel provides a definition of all the types of building blocks that may exist within an architecture, showing how these building blocks can be described and related to one another. For example, when creating an architecture, an architect will identify applications, "data entities" held within applications, and technologies that implement those applications. These applications will in turn suppor t par ticular groups of business user or actor, and will be used to fulfil "business services".
The content metamodel identifies all of these concerns (i.e., application, data entity, technology, actor, and business service), shows the relationships that are possible between them (e.g. actors consume business services), and finally identifies artifacts that can be used to represent them.

[ Metamodel ER example-1 ]
Shows the metamodel entities and relationships that are present within a core content metamodel.

[ Metamodel ER example-2 ]
Shows the metamodel entities and relationships that are present within a full content metamodel.