## 3 Results: Method Development, Implementation, and Testing of CADA Framework
### Method Implementation  
The developed method aims to streamline the design process by incorporating AD principles. The following implementation as a workflow follows a hybrid agile-waterfall approach inspired by the manifesto for agile software development. This approach allows for flexibility and structure, as it combines the iterative nature of agile methodologies with the systematic planning of the waterfall method. The workflow begins with thoroughly understanding the project requirements and objectives, using the AD elements to design the procedure. The visual representation fosters clarity and transparency, allowing for the easier identification and resolution of potential design issues. A strong focus on existing knowledge and reusable data ensures that the design meets the functional requirements and creates a positive and intuitive user experience. Stakeholders and end-users are actively involved throughout the design process, providing valuable insights and feedback. Our design method is mainly supported by representing knowledge (CR, FR, DP, and PV) as a node connected to other nodes in the following design stage according to AD. The nodes are connected by arrows that indicate a relationship (coupling) between them. If there are only one-on-one connections, the design is classified as uncoupled (Figure 6a), which is the best possible scenario. If arrows share the same target, the design is decoupled (Figure 6b), which is then fed back to the user by a color code. The design is coupled if connections share a source and target and thus intersect (Figure 6c). This scenario has to be avoided to satisfy the independence axiom. The design assistant can instantly give feedback on such an axiom violation by message or color code within a graphical support tool. From there, the method emphasizes iterative design cycles, with regular feedback and iteration loops to ensure that the design meets the project's evolving needs. The  
Figure 6: AD with visual keys: (**a**) Uncoupled Design; (**b**) Decoupled Design; (**c**) Coupled Design. method incorporates AD principles, focusing on achieving functional requirements while minimizing system complexity. The assistant can guide the user through an iterative process to split nodes into sub-nodes with more specific knowledge. After splitting requirements (Figure 7b), a more in-depth analysis of the possible solution can be carried out to meet the iteratively detailed requirements (Figure 7c). This process can be carried out with the designer and client to gather knowledge in detail. This collaborative approach helps to ensure that the final design solution is user-centered and meets the needs of all stakeholders. As a result, the design framework enables the development team to adapt to changing requirements, and ultimately enhance user and regulation satisfaction. Furthermore, using a visual framework also promotes a more iterative and adaptable design process. By clearly depicting the various design elements, it becomes easier to visualize how changes or updates may impact the overall design. The node tree structure, which is used as a basic knowledge representation in the visual assistant, takes care of this, as it can show how a change in one design step influences all the following decisions. The nodes' left-to-right orientation helps users understand the connections intuitively (Figure 8). The principle of a tree-based visualization of the AD stages is also well aligned with the concept of a knowledge graph regarding the domain knowledge clustered in CR, FR, DP, or PV nodes. To fully implement a structured design process, semantic and logical reasoning between the connections of these elements needs to be added. Following the idea of CBR, a new visual design assistant component complements the AD tree structure. The relation between the CR or FR and DP can be described through the terms used in CBR. An FR is a short paragraph containing information about selecting the DP.