An executable business architecture is an executable model that can illustrate dynamic structure and behavior. This model can be created and managed by business domain experts, such as business architects and business analysts.

Undoubtedly, an architecture created by business domain experts can be considered more robust than one created by software engineers. Not surprisingly, software engineers tend to focus on technical aspects, while business domain experts have a distinctly business-oriented view. The challenge lies in the approach to enable business domain experts to create an executable business architecture, which is part of the enterprise architecture. A transformation mechanism is required that implements a bridge between business architecture and technical architecture. Ideally, a kind of execution engine exists that can interpret models and generate executable code at execution time. The generated code would integrate with the existing technical architecture, represented by business process management systems, data management systems, mail systems, operating systems, etc.

The intrinsic alignment of business architecture and business capabilities lifecycle management, including business process management (BPM), data management, etc., is a major characteristic of an executable architecture. The issue of missing alignment between business architecture and BPM, between business architecture and data management, etc., that so many organizations experience today, is effectively eliminated.

In more concrete terms, business domain experts can define business processes, business rules, business documents, etc. as domain models, which are part of the all-encompassing business architecture model. As a result, domain models can never get out of sync with the overall business architecture model.

There are many benefits that an executable business architecture offers:

• The dynamic aspects of the business can be fully described and understood.

• The business architecture can be developed iteratively with analysis and validation being performed at each iteration stage.

• Business domain experts can develop the business architecture, concentrating on business aspects.

• The behavior of the business architecture can be visualized and analyzed.

• The business architecture can be experimented with and stressed to be better able to detect deficiencies.

• The simulation of the architecture and its visualization provides a more accurate view for the stakeholders to determine whether it meets their needs.

• Minimize the need for extensive software experience (non IT-experts can develop the enterprise architecture).

• The round-tripping problem, which occurs when different models need to be synchronized and model transformation works only in one direction, is eliminated.