Change impact analysis of enterprise architectures

A taxonomy for software change impact analysis

“…A single change can affect many different domains of enterprise architectures, since these combined structures are very change prone. Therefore, de Boer et al [139] analyze and assess impacts on the enterprise-level of an architecture. The proposed analytic process is based on an enterprise architecture modeling language called ArchiMate, which is a combination of Testbed (a business modeling language) and UML concepts at a very general level.…”

“…However, the majority of established classifications is not based on a review of related studies on change types, such as the work of Baldwin and Clark [181] (pp. [132][133][134][135][136][137][138][139][140][141][142]. We are convinced that more work should be spent on creating a taxonomy of change types for source code, architectural models, requirements, and other artifacts which can be integrated into impact analysis.…”

Business Model Design An Evaluation of Paper-based and Computer-Aided Canvases

“…An iterative application of those rules to a model yields the direct and indirect impacts. (de Boer et al, 2005) present such rules for the most important relationships in ArchiMate models, differentiating between the removal, the extension and the modification of an architectural element. However, the definitions are given in an informal and textual manner and no technical realization is supplied.…”

“…the modification of a CRM system) and to assess risks in the current architecture (e.g. which business operations would be affected if a specific server goes offline) (de Boer et al, 2005). To generate this information, an impact analysis has to evaluate the dependencies between the architecture's constituents.…”

Assessing Impacts of Changes to Business Rules through Data Exploration

“…Although UML does not have a complete formal semantics, it is sufficiently well-defined to allow rules to be developed which describe how a particular type of change (for example, the addition of a new message send to a sequence diagram) can disturb the consistency of other UML elements (such as class methods in class diagrams). de Boer et al adopt a similar approach to the identification of impacts to enterprise architectures [3]. Again, the architectural models are expressed in a formal language that has a sufficiently rich semantics to allow impacts to be calculated with a fair degree of accuracy.…”