Being a AE and ME doing software and systems engineering, I get what AADL is about. It is really a high level programming language much like pseudo code, which makes it compile-able. It is meant for component level engineering (where a component is a black box like a flight computer or an engine fuel controller), not systems engineering problem like an airplane, car, etc. [granted a system is where the boundary under study is drawn], that is why compiling is possible.
Thank you for sharing. So far I’m finding the content useful, concise and to the point. I’m looking forward to completing the whole series.
Thanks...I hope you find that it's worth making the journey.
Being a AE and ME doing software and systems engineering, I get what AADL is about. It is really a high level programming language much like pseudo code, which makes it compile-able. It is meant for component level engineering (where a component is a black box like a flight computer or an engine fuel controller), not systems engineering problem like an airplane, car, etc. [granted a system is where the boundary under study is drawn], that is why compiling is possible.
OK...which is why I think it's not well-suited for systems architecting.
bpmn?