DYA framework

[2] The DYA framework is built up with the following modules:[3] The concept of the DYA framework was first introduced in the 2001 by Roel Wagter, Marlies van Steenbergen, Martin van den Berg, and Joost Luijpers of Sogeti in the Dutch book, entitled DYA: snelheid en samenhang in business- en ICT-architectuur,[4] revised, translated in English, and published in 2005 as "Dynamic Enterprise Architecture: How to Make It Work".

It brings business agility, architectural effectiveness and manageable and expandable infrastructure landscapes within the grasp of any organization.

DYA infrastructure provides three mutually supportive elements: Various implementation strategies are outlined, how to extend the Project Start Architecture is explained and the importance of a number of products such as Reference Architectures, Product Catalogs and Service Catalogs are also illustrated.

In 1972, Gerrit Blaauw[11] described how one could think about computer design as separable domains: architecture, implementation and realization.

When working with DYA|Infrastructure, one can readily recognize the three domains as put forward by Blaauw: At the implementation level, infrastructure services and functions can still be kept generic.

Business, information and infrastructure architectures share a common goal: to provide optimum support for an organisation's operations.

To act effectively within the architectural process and at the same time be sufficiently responsive, each discipline must follow the dynamics and structures which underline their own respective area of competence.

This set of quality attributes can be seen as a mandate for each discipline to individually work on their own part of the total solution.

Quality attributes ensure the resulting solutions are not developed in isolation, but that they remain consistent within the complete architectural framework.

Apart from the quality attributes, there are two major restrictions that influence the potential direction of a solution, namely cost and time.

Within this harmonization process, "similar" quality attributes are easily traceable to each other, while others are far more likely to underline the uniqueness of a particular discipline.

Participants in the architectural design process are not always sufficiently aware of the importance of the quality attributes of their own fields of expertise, and consequences that their explicit requirements have on other areas.

That means that it is used to dissect infrastructure landscapes into logical dimensions and parts to enable structured and methodological modeling (composition).

The Building Blocks Model dissects the infrastructure landscape from five directions: The decomposition order that is imposed by the model can be described as follows: These facilities (Building Blocks) "live" in an Environment, that means that they are used in a certain business context and that the way of usage that is dictated by this context demands specific quality requirements.