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

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.



    EA Modeling Tips by EAComposer

A big part of what enterprise architects do is creating visual models. This is also known as EA modeling. We use EA modeling to deliver certain insights. The visual model is often how this insight is delivered.

We will now discuss two aspect of this. First we will share what the most common EA models are. Secondly we will discuss some basic tips & hints on basic modeling techniques and styles.

Now often creating visual models is done using EA tools. So when you are looking at the remainder of this article consider this almost a set of functional requirements for EA tools like EAComposer.

First we will look at what the most common EA models are produced:

With TOGAF 9.1 a strong focus on Capability Based Planning was introduced. From this, as you might have guessed, a business capability model for your organization is a very common visual model. A capability model show “what” your organization does. This “what” is usually very stable over time and therefor an ideal structure to share insights against. In TOGAF lingo this model is actually called a Functional Decomposition artifact. Consider it a cornerstone. The business capability model resides in the business architecture domain. Other models in this domain include process models (the “how”) and organizational models (the “who”).

A second popular model is inside the Application Architecture domain. Most often the related visual model is a model that shows applications and their relationship to capabilities (see above) that they enable. So you would visual map showing capabilities and the applications that are supporting/enabling these capabilities. A second benefits coming from developing this view is that you often also end up with an initial Application Inventory or in TOGAF lingo an Application Catalog.

The third popular model is a Data Architecture domain model. It is an Enterprise Data Model. Now as you might know a data model can mean a lot of things. Within the context of EA we usually define it as a pretty high level / conceptual / logical data model. Showing the core entities that are existing within your architecture landscape and the relationship between them. There are two use cases for this model. The first one is around SOA. If you are including a SOA integration architecture the Enterprise Data Model is usually implemented there as a Canonical model. The Enterprise Service Bus that implemented & manages your SOA architecture uses the canonical model to maps messages between systems to a common format. The second use case for an enterprise data model is in the reporting & analytics space. A data warehouse usually also implements the enterprise data model but more in a dimensional and denormalized format. If your organization has a need for SOA strategy and/or a need for Reporting & Analytics the enterprise data model would be helpful. (Read about how TOGAF and SOA connects)

Second we will share some tips & hints on modeling techniques.

- Make sure your visual models are business friendly. So avoid technical details and formats (e.g. UML is BAD, an ERD is BAD). Keep it logical using labels and diagraming techniques that your business stakeholders can understand

- Make sure you can re-use your models. Creating good visual models take time. So once you have a good model that you like and resonates with your business stakeholders make sure you can easily re-use it.

- Apply a consistent flow in your models. Most common the flow is either top-down or left-to-right.

- Setup standards for the symbols to be used across your models. E.g. an application shape should always look visually the same so it is easy for people to read your models.

- Include legends. Remember most other people reading your models won’t have the same background & knowledge so simply include a legend explaining symbols and shapes.

As you see from the above there are several functional requirements for an EA tool embedded. The tool should make it easier for you across all those items e.g. manage visual standards for models, create logical data models, re-use models.

keywords: enterprise architecture modeling, ea modeling, ea tools

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!