have already been concerned about the changes necessary to allow for solid and reliable software engineering processes for (self-)adaptive systems. Central challenges were collected in [@salehie2009self], where issues of quality assurance are already mentioned but the focus is more on bringing about complex adaptive behavior in the first place. The later research roadmap of [@de2013software] puts a strong focus on interaction patterns of already adaptive systems (both between each other and with human developers) and already dedicates a section to verification and validation issues, being close in mind to the perspective of this work. We fall in line with the roadmap further specified in [@bures2015software; @belzner2016software; @bures2017software].

While this work largely builds upon [@holzl2011towards], there have been other approaches to formalize the notion of adaptivity: [@oreizy1999architecture] discusses high-level architectural patterns that form multiple inter-connected adaptation loops. In [@arcaini2015modeling] such feedback loops are based on the MAPE-K model [@kephart2003vision]. While these approaches largely focus on the formal construction of adaptive systems, there have also been approaches that assume a (more human-centric or at least tool-centric) software engineering perspective [@elkhodary2010fusion; @andersson2013software; @gabor2016simulation; @weyns2017software]. We want to discuss two of those on greater detail:

In the results of the *ASCENS* (Autonomous Service Component 