Coding with AADL
One of the challenges in product line deployment and maintenance is managing the variation and making sure you understand whether you have deployed the correct configuration to each individual instance. So, AADL can be the home of the performance parameters, the different configuration settings that are related to each of the different environmental instances. Oh, that is very cool.
Given that up to 70 percent of system errors are introduced during the design phase, stakeholders need a modeling language that will ensure both requirements enforcement during the development process and the correct implementation of these requirements. Previous work demonstrates that using the Architecture Analysis and Design Language (AADL) early in the development process not only helps detect design errors before implementation but also supports implementation efforts and produces high-quality code. Previous research has demonstrated how AADL can identify potential design errors and avoid propagating them through the development process. Verified specifications, however, are still implemented manually. This manual process is labor intensive and error prone, and it introduces errors that might break previously verified assumptions and requirements. For these reasons, code production should be automated to preserve system specifications throughout the development process. In this podcast, Julien Delange summarizes different perspectives on research related to code generation from software architecture models.
About the Speaker
Julien Delange has been at the SEI since November of 2012. His research focuses on the Architecture Analysis and Design Language, also called AADL. Before joining the SEI, he worked as a software engineer at the European Space Agency where he led and contributed to several research projects related to software and system architectures. He also has a Ph.D. from Telecom ParisTech in France and developed the real-time operating system called POK for building safe and secure systems.