diff --git a/2.-Software-Architecture-Specification.md b/2.-Software-Architecture-Specification.md
index 05e2d98..da735c1 100644
--- a/2.-Software-Architecture-Specification.md
+++ b/2.-Software-Architecture-Specification.md
@@ -195,7 +195,7 @@ The advantage of this solution is that the code of the plug-in remains largely i
 The "Program" field in the diagram is supposed to represent an executable file; if you click on it, "Form1" is called. This function then loads the "ModellingWizard", i.e. the plugin. This means that the GUI of the plugin is then displayed in "Form1".  
 
 <p align="center"> 
-<img src="https://user-images.githubusercontent.com/75857685/164975858-5380f170-3a2e-421f-b419-8a6f9790b425.png" alt="System" /><br>
+<img src="https://user-images.githubusercontent.com/75857685/164977846-df95b1ef-a8c2-4a91-b0a5-75ebd9c9b8d9.png" alt="System" /><br>
 <em>Figure 5 - Class design from the ModellingWizard</em>
 </p>