Using DYA to work within an architectural structure

Essentially, DYA can be summed up in the following principles:

  • Architecture is not an aim in itself, but rather supports the objectives that the organisation has set for itself. The purpose of architecture is not to merely generate a document, but to ensure that the organisation’s change processes run increasingly smoothly. For this reason, the development of architectural models and principles needs to be firmly tied to these change processes.
  • There’s no reason why architecture cannot be developed bit by bit as need be. Architecture evolves along with the organisation: just-enough, just-in-time architecture.
  • Under certain circumstances, it may be necessary to deviate from the established architecture. It is, however, important to set up a mechanism that can be used to control such deviations from the architectural models and principles. This can be done by distinguishing separate scenarios for the development within and outside of an architectural structure.

DYA model

The DYA model forms the core of DYA.

DYA model

The above model outlines four processes that cover the entire path from strategy formation to realisation.
These processes help you to develop your architectural models and principles. This will allow you to implement an IT structure that provides your business with efficient support at an acceptable cost. In this process, the correlation of business architecture, information architecture and technical architecture is safeguarded.

One advantage of structuring of the architectural processes in accordance with DYA is that you can record the moment of an architecture’s creation and implementation. As a result, you know when an architect is required and what he or she subsequently brings in. This allows you to develop the right architecture for the right moment.

Architectural framework

In order to be able to classify the architectures, DYA has adopted its own architectural framework.

Architectural framework

In a manner of speaking, the framework serves as a filing cabinet, in which each architecture is stored in the correct place. The architectural framework illustrates the fact that an organisation’s architecture should not be seen as a uniform whole, but should be divided into components. In a specific case, some of these components are elaborated in detail, while other components may not be considered at all. This is an entirely legitimate approach, as long as the elaborated components are consistent with each other and with the business objectives, and the components required to direct current changes within the organisation are also realised.