Today's software projects face an environment of continuous change and evolution. In order to handle evolution in development environments (e.g., requirements, technology) effectively, over the last decades well-established development processes have been adapted significantly and new process models have been proposed. For example, there is a wide range of agile processes which are risk-driven and which not only handle but embrace frequent change. However, agile and risk-driven processes still suffer from a lack of support for automatic and generic identification of certain risks.

Software developers work concurrently on different kinds of development artifacts such as requirements, architecture, design, or source code. To keep these development artifacts consistent, developers have a wide range of consistency checking approaches available. However, most existing consistency checkers work best in context of single tools and they are not well suited when development artifacts are distributed among different tools and are being modified concurrently by many developers.

In model-driven engineering, design models allow for efficient designing without considering implementation details. Still, it is crucial that design models and source code are in sync. Unfortunately, both artifacts do evolve frequently and concurrently which causes them to drift apart over time. Even though technologies such as model-to-code transformations are commonly employed to keep design models and source code synchronized, those technologies typically still require unguided, manual adaptations. Hence, they do not effectively prevent inconsistencies from being introduced. In this paper, we outline a novel approach for checking consistency between design models and source code. Our approach aims at detecting inconsistencies instantly and informing developers about a project's consistency status live during development.