Yes, so during the client communications or the client meetings that are happening with our on-site that is the Japanese clients. So some of the members are non-technical stakeholders. So based on that, they cannot understand the complex technical details. So for that, I have also created an architecture diagram for graphical representations or along with the sequence diagrams to explain the flow of how the communication is happening between the HMI and the framework and along with simple minor explanations to them like what happens. For example, suppose a USB is plugged into the system. So what is happening behind the system that client does not need to know like what is what we are doing at the back end to read that USB mount and unmount intents. So that the client does not need to know. So based on using simple graphical representations such as architecture diagrams and sequence diagrams, we can just make components such as USBs plug and after the USBs plug the package is read and based on that HMI is performing updates from the after fetching the values from the USB. So in such cases, graphical representation helps a lot to explain to the non-technical stakeholders.
