Knowledge Base

Welcome to our knowledge base, this is where you can find information on various topics like Togaf, Enterprise Architecture, EA tools, IT trends and more. This section is purely intended as a free information library. If there are specific topics you would like to see described please email these to info@whitecloudsoftware.ca

WIKIPEDIA: Enterprise architecture 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.

GARTNER: Enterprise architecture is the process of translating business vision and strategy into effective enterprise change by creating, communicating, and improving the key principles and models that describe the enterprise's future state and enable its evolution.

FORRESTER: Enterprise architecture consists of the vision, principles and standards that guide the purchase and deployment of technology within an enterprise.

THE OPEN GROUP: Enterprise architecture is a discipline that helps the enterprise define, develop and exploit the capabilities in order to achieve the enterprise’s strategic Intent. An ‘enterprise’ is any collection of organizations that has a common set of goals and/or a single bottom line.

Notification

Icon
Error

    Enterprise Architecture and Solution Architecture
Enterprise Architecture and Solution Architecture

In the last couple of years, there has been a lot of debate about Enterprise Architecture. What Enterprise Architects do, why it's important and how it is different from Solution Architecture (SA) are just some of the questions EA community became too familiar with.

The difficulties in defining EA are partly due to the fact that EA is dealing in abstractions. EA need to look at the big picture in order to find the solution for the entire enterprise. Enterprise architects need to fill in the gaps between business and IT perspectives. That being said, EA's work is always evolving and it never ends. On the other hand, SA's work has a beginning, middle, and end.

While Solution Architecture is often regarded as the practical and important for business development, EA remains misunderstood and depicted as an isolated part of the business with little contact with real problems and development opportunities.

However, it is not really hard to understand how and where EA can provide value. Standardization, innovation implementation, and reduction of IT costs with enterprise architecture software implementation can help the business grow. The question is - how to do it? Well, the "how" part is exactly where Solution Architecture steps in.

It is clear that EA and SA are supposed to work together in order to build effective architecture and maximize benefits. Big companies need the both roles if they are planning to get things done. Below is the explanation of the roles of SA and EA.

Solution Architecture
SA is used to guide the organization and design of the software solutions and ensure technical consistency and integrity of the solution in every stage of the process. SA usually spend most of their time coordinating technical aspects of the initiative - from concept definition, analysis of requirements and implementation, to regular maintenance. This implies that SA has to be able to contribute to all of these activities.

Enterprise Architecture
EA is used to connect business to IT. It has a broad knowledge about enterprise architecture software, platforms, methods and processes in business as well as IT. EA is mainly used to describe the relationships within the enterprise as well as relationships of enterprise and external environment. Besides that, EA is also responsible for choosing the best technology (which doesn't always mean the newest) that fits well to the team and provides the solution at the same time and making many other strategical decisions. For that reason, Enterprise Architect should be the right arm of the C-level officers when it comes to defining development strategy of the business.

We hope that the difference between EA and SA is a bit clearer now.

In short:

- EA: Sees how to fit the solution into the business.
- SA: Designs solution, chooses technology, platform, etc.

Conclusion
Enterprise Architects and Solution Architects have very different purposes. EA is there to find out how to leverage technology and SA governs the creation of the solution itself. They complement each other and should work together in order to provide the best possible results.


keywords: Enterprise Architecture, Solution Architecture, EA, SA, TOGAF

Complete Enterprise Architecture Tool

Why use EAComposer?

  • Manage your architecture portfolio, your enterprise architecture building blocks. Applications, platforms, data but also any business components.
  • A complete EA solution for all enterprise architecture activities with 80+ real-life templates ready for use.
  • Includes an advanced EA modeling feature to create professional, business friendly enterprise architecture models and diagrams, ready for presentations.
  • Apply architecture governance to ensure that projects are aligned with standards, reference architectures & technology strategies.
  • The Free Trial will give you instant and full access to the product & features, after 4 weeks the trial automatically expires. No catches!