《Automation for System Safety Analysis》.pptVIP

SAS 07 Automation for System Safety Analysis Malin Automation for System Safety Analysis Jane T. Malin, Principal Investigator Project: Automated Tool and Method for System Safety Analysis Software Assurance Symposium September, 2007 Problem Need early evaluation of software requirements and design Assess test and validation plans Assess system failures and anomalous conditions that may challenge software in system integration testing Identify software-system interaction risks Identify requirements gaps Perform virtual system integration tests prior to software-hardware integration Benefits Reduce software-system integration risks early Reduce requirements-induced errors and rework in later development phases Improve efficiency and repeatability of analyzing system and software risks Reduce time spent reanalyzing when specifications and designs change Reduce contention for software-hardware integration laboratory resources Technical Approach Systematic semi-automated analysis for early evaluation and rapid update Capture model of the controlled system architecture Abstract physical architecture models with subsystems, functions, interfaces, connections Extracted directly from requirements and design text and data Capture risks and hazards in model Constraints, hazards, risks from requirements and design Risk and failure libraries Analyze model and risk data to identify relevant risks and constraints Analyze and simulate risk propagation in the system Use operational and off-nominal scenarios and configurations Identify possible test scenarios for virtual system integration testing Relevance to NASA This work leverages component tools that have been used in NASA applications Goal: Integrate and enhance these tools for software assurance during requirements and design phases Project test case is NASA Constellation Launch Abort System (LAS) Extend and Integrate Existing Technology Extraction Tool and Nomenclature Reconciler Extractor Extract model parts f