We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Enterprise Architecture Matters

Adrian Grigoriu

All you want to know about Enterprise Architecture

user-pic
Vote 0 Votes

Here are my answers to a few frequently asked questions that get 

wrong answers.


What is Enterprise Architecture (EA)?

EA is the Architecture i.e. the blueprint of the Enterprise. It describes its structure and the human and technology resources operating it. The EA structure and operation are embedded in the Enterprise.

Long definition: The EA is the Enterprise structure and operation blueprint, describing the current and future states of the Enterprise and its transformation roadmap in terms of process, information, technology and people architectures, all linked by an EA navigation framework.

 

Why EA?

Because EA is an asset in the Enterprise competitive race, characterised by the growing pace of change and a soaring amount of information and complexity.

 

What is the purpose of EA?

The EA, as a blueprint, is employed by each and every stakeholder for own work purposes. 

For instance, IT people document, analyse and roadmap the IT. Finance people document the budget and cost flows. HR associates people, skills and remuneration to business functions and operation. All these views would be linked and traversed on the EA representation.

Overall, EA enables the Enterprise simplification,  integration, operational improvements, resource saving, assets management, enhanced agility through modular services, coherent roadmapping... and in general enables a superior management of the Enterprise and its growing complexity.

 

Who does EA?

The Enterprise Architect specifies the EA framework and coordinates the EA work.

The Enterprise domain experts model and document their own concerns in the Enterprise, the Views. EA is a collective effort.

 

What should EA do?

EA should coordinate and document the many fragmented or loose coupled Enterprise developments such as  SOA, IT Architecture, Application Integration (EAI), ITIL efforts  and many independently performed activities such as Enterprise alignment to Business Strategy and Goals, Enterprise Simplification, Compliance to Regulation Frameworks, Business Process Improvement, Six/Lean Sigma, Business Performance Management, Mergers and Acquisitions and Outsourcing (such as BPO, SaaS...).

Ultimately, EA becomes the Enterprise Knowledge database. 

 

What does EA in practice?
In practice, EA is used for the discovery of IT systems landscape and its roadmapping. Once this done, many  business as usual EA efforts are reduced to Architecture Review Boards's solution architectures reviews which are seldom based on an existing EA since there is none.

 

Why an EA framework?

The EA framework links together in the EA whole the parts of the Enterprise modelled and designed independently by owners so that the EA can be navigated for process analysis, impacts on resources, strategy mapping and so on. The framework offers predictability, repeatability to EA developments. 

1 Comment

| Leave a comment

Hi,
This is a wonderful opinion.Now I can understand what the EA stands for and what are its advantages.
I am very pleased with the thought and don’t feel like adding anything in it.

Smith.

----------

Leave a comment

Adrian Grigoriu blogs about everything relating to enterprise and business architecture, SOA, frameworks, design, planning, execution, organization and related issues.

Adrian Grigoriu

Adrian is an executive consultant in enterprise architecture, former head of enterprise architecture at Ofcom, the spectrum and broadcasting U.K. regulatory agency and chief architect at TM Forum, an organization providing a reference integrated business architecture framework, best practices and standards for the telecommunications and digital media industries. He also was a high technology, enterprise architecture and strategy senior manager at Accenture and Vodafone, and a principal consultant and lead architect at Qantas, Logica, Lucent Bell Labs and Nokia. He is the author of two books on enterprise architecture development available on Kindle and published articles with BPTrends, the Microsoft Architecture Journal and the EI magazine. Shortlisted by Computer Weekly for the IT Industry blogger of the year 2011.

Recently Commented On

Monthly Archives

Blogs

ADVERTISEMENT