Page tree

Architectural Thinking Framework

Skip to end of metadata
Go to start of metadata

The Architectural Thinking Framework® provides a small number of solution maps that have proven to be valuable in many companies and have been accepted by business people and executives. The strict separation of business- from IT architecture maps enables business people to participate in architectural work.

The maps that are used at solution level are connected to the enterprise-wide architectural maps. This connection makes it possible to trace each requirement and design decisions to the enterprise-wide level.

Here are some examples:

  • Solution Requirement Map
  • Solution Business Object Model
  • Solution Application Interface Map
  • Software Architecture – Technical Interface Map
  • Software Architecture – Whitebox Component Map
  • Software Architecture – Relational Database Model
  • System Architecture – Deployment View

→ Comparison to State of Practice


  1. Do you think it's useful to include anything from the Customer Experiences or Customer Services in this space?

  2. Heidi Beets : we don't just think, we are absolutely SURE that we need to add Customer Journeys&Touchpoints. Current idea: customer journey is a process (part of our meta-model) that starts at the customer, crosses the boundary to the enterprise via a touchpoint, runs through certain capabilities of the enterprise, leaves the enterprise on a touchpoint back to the customer or to another company.

    We are discussing exactly this topic with Milan and his ED framework.

Write a comment…