The architecture of a software application or of a family of software applications has a big impact on various important aspects, such as modifiability, maintainability, understandability, etc. In the case of an existing project, the architecture needs to be understood and meaningfully evolved. However, it is often the case that architectures degenerate with the addition of new requirements. Once changes have been made to the code, developers hesitate to promote the documentation of the undergone changes at the architecture description level, because of various reasons: lack of time, lack of understanding the importance of such an activity, lack of understanding the principles that should drive the implementation of changes, fear that the changes are not considered architecture-compliant, or very often, the fact that the architecture description is very old and needs extensive updating until the new changes can be represented.