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.



    Capability vs. Process vs. Service
3 Pages<123
Capability vs. Process vs. Service

The terms Process - Capability - Service are important terms in today's Enterprise Architecture landscape. However a clear definition of how these terms related doesn't exist. Hopefully this post will help you with this.

Process vs. Capability: generally agreed definitions are that process is the how and capability is the what. These seems to be generally accepted by the industry. So let's simply adopt this as a part of our shared definitions.

As stated the harder part is Capability vs. Service. What has been agreed by industry so far is that they are both considered what's. Also both are also defined as having a specific outcome. So what is the difference?

The only distinction between Capability vs. Service is that Service is considered an access a.k.a interface. They are both whats with a specific outcome.

Coming up with clean simple definitions is not easy but can be very powerful when done right. So the terms we landed on are below, hopefully this can help someone else needing to define these terms and/or integrate ITIL & TOGAF.

Capability: is the what we do
Process: is the how we do it (--> how a capability is executed)
Service: is the how we access it (--> how a capability is accessed)

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!