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.
Connect with SATURN
Join SATURN Network mailing List here:Get UpdatesFor Email Marketing you can trust.
Subscribe to our feed:
Topicsagile release planning architecture evaluation architecture review Architecture Tradeoff Analysis Method ATAM Carnegie Mellon cloud computing documentation enterprise architecture non-functional requirements SATURN 2010 SATURN 2011 SATURN 2012 SATURN 2013 SATURN 2014 SATURN Conference SEI SOA software architecture software architecture evaluation software architecture requirements software architecture review software design software development software engineering Software Engineering Institute system architecture system of systems systems architecture technical debt