Posted on by Architecture-Centric Practicesin
When a system fails, engineers too often focus on the physical components, but pay scant attention to the software. In software-reliant systems ignoring or deemphasizing the importance of software failures can be a recipe for disaster. This blog post at the SEI Blog�is the first in a series on recent developments with the Architecture Analysis Design Language (AADL) standard. First published in 2004 by SAE International, AADL is a modeling notation that employs both a textual and graphical representation. AADL provides modeling concepts to describe the runtime architecture of application systems in terms of concurrent tasks, their interactions, and their mapping onto an execution platform.
Development organizations use AADL to conduct lightweight, rigorous, yet comparatively inexpensive analyses of critical real-time factors such as performance, dependability, security, and data integrity. Use of AADL helps alleviate mismatched assumptions between the hardware, software, and their interactions that can lead to system failures. This podcast, an interview with Julien Delange and Peter Feiler of the SEI, covers the latest developments in AADL.