Thanks for the explanation! so architect team now also create an executable file to generate the actually skeleton software from what I understood, I'm I right?
Based on the model created during the architectural phase the application developer gets a skeleton for the executable file (this could also be generated based on the model) and starts to add all the programming logic. Please note that the code of the service interface APIs is generated too and available to the application developer via included header files.
@@vectorinformatik thanks for the answer, does the tools have some kind of export to generate the architecture model in a friendly format that can be used as design documentation? this would help to make the design faster and the documentation being up to date with the actual implementation, I hope this is the case to avoid duplicate effort.
![[UA] Team Vitality проти NAVI | IEM Cologne 2024](http://i.ytimg.com/vi/wttO1zVRTC0/mqdefault.jpg)
Really good series. Vector should keep this up
Thanks for the explanation! so architect team now also create an executable file to generate the actually skeleton software from what I understood, I'm I right?
Based on the model created during the architectural phase the application developer gets a skeleton for the executable file (this could also be generated based on the model) and starts to add all the programming logic. Please note that the code of the service interface APIs is generated too and available to the application developer via included header files.
@@vectorinformatik thanks for the answer, does the tools have some kind of export to generate the architecture model in a friendly format that can be used as design documentation? this would help to make the design faster and the documentation being up to date with the actual implementation, I hope this is the case to avoid duplicate effort.