Software Safety Architecture Analysis
The intent of this paper publication is to address Software (SW) Safety Architecture Analysis and to provide an approach for conducting the architecture analysis Level of Rigor task utilizing software architecture patterns. While there are many architecture analysis techniques commonly used in practice today (e.g., Architecture Tradeoff Analysis Method (ATAM), Software Architecture Analysis Method (SAAM), Scenario based Architecture Level UsabiliTy Analysis (SALUTA), etc.), they seem to concentrate on the architecture of the system rather than the structure of the system’s software. By analyzing software architecture patterns, the safety practitioner can pay close attention to the true architecture of the software. The methodology described within further details the safety concerns associated with each of the patterns. The general safety concerns are stability/robustness, data handling, maintainability, testability, and security. Each of these concerns are broken down to more specificity in the brief. By identifying the software architecture pattern(s) employed in a system and understanding the safety concerns and potential mitigations, system safety practitioners have a basis for an in-depth, repeatable software architecture analysis methodology.