{"id":5843,"date":"2017-07-12T22:17:39","date_gmt":"2017-07-12T22:17:39","guid":{"rendered":"https:\/\/modeling-languages.com\/?p=5843"},"modified":"2017-07-12T22:19:51","modified_gmt":"2017-07-12T22:19:51","slug":"aadl-practice","status":"publish","type":"post","link":"https:\/\/modeling-languages.com\/aadl-practice\/","title":{"rendered":"AADL in Practice – Book and Interview with Julien Delange"},"content":{"rendered":"
Julien Delange has a new book on AADL (Architecture Analysis and Design Language) in Practice<\/a>. \u00a0Today, we sit down with him to learn more about this language, its origins, why should you care about it and how it compares with other languages. As he puts it, keep reading to become an expert of software architecture modeling and analysis.<\/span><\/p>\n\n My name is Julien Delange<\/a>. I lived in France, got my PhD in Paris, lived in The Netherlands (where I worked at the European Space Agency) and I am now currently living in Seattle, WA and working for Amazon Web Services. I am a software engineer and enjoys playing\/hacking with computers since I am a kid.<\/p>\n When I started my PhD in 2008, I met Peter Feiler<\/a> while he was visiting my lab in Paris<\/a>. He invited me to work at the Software Engineering Institute<\/a> and I started to contribute to the standard quickly. After my PhD defense, I got a position at the European Space Agency to work on their AADL tools and moved to the USA to work with Peter on the OSATE<\/a> tools (OSATE is an Eclipse-based AADL modeling platform). I worked for 8 years on AADL and its related tools. That is the reason I wrote this book – I wanted to share the knowledge I accumulated through all these years.<\/p>\n The Architecture Analysis and Design Language (AADL<\/a>) is a modeling language to capture the architecture of a software system (e.g. a pace-maker, a self-driving car) and the interactions of that software with the physical aspects of a system (e.g. sensors in the body, signals and lights in the street).<\/p>\n The language was initially designed towards avionics systems but it quickly became popular in other domains (medical, aerospace, etc). The language is originally designed by Peter Feiler<\/a> at the Software Engineering Institute, which took some concepts from other languages (Meta-H).<\/p>\n The language semantics is well defined and not ambiguous. There is a single model to capture the system, so, you avoid defining the same thing twice, which is one of the major issues with others languages (like UML).<\/p>\n The standard defines a textual (easy to process by tools) and graphical notations (easy to visualize by humans). For example, the following picture shows a graphical model of two processes (process_producer and process_consumer) communicating a value through a shared network (ethernet_bus) (a similar example is detailed in the book, you can even have the corresponding textual version inside the book :-). You can use such a model to perform latency analysis (how long does it take to transport the data from the sender to the receiver according to network protocols, traffic congestion, scheduling mechanism, etc.), safety analysis (e.g. what is the impact of an error on the ethernet_bus over the consumer process?), etc.<\/p>\nCan you briefly introduce yourself and how did you get involved with AADL?<\/strong><\/h2>\n
Can you briefly describe what is AADL? Who is behind the language?<\/strong><\/h2>\n