Stephen Blanchette

Assurance Cases for Design Analysis of Complex System of Systems Software

This paper discusses the application of assurance cases as a means of building confidence that the software design of a complex system of systems will actually meet the operational objectives set forth in the project’s top-level requirements. The discussion will explain the reasons for selecting the assurance case approach and step through an example of how to apply the method in the described context. The challenges of applying the approach in a real setting will be considered, followed by conclusions. This paper will serve as an anonymous case study. At the close of the paper, readers will have learned how assurance cases have been used in real, non-trivial settings to solve the stated problem. They will have a blueprint for applying similar techniques to their own challenges, with the insight into potential pitfalls that will allow them to succeed.

Giant Slayer: Will You Let Software be David to Your Goliath System?

Modern aerospace systems are marvels of engineering. Their amazing achievements are due in large part to software, yet relatively few project personnel, especially project management staff, understand or appreciate the significance of it. The lack of understanding and attention to software often dooms large aerospace projects to significant delay if not outright failure. As a motivation, several software-related aerospace incidents, from benign to calamitous, are recounted here to demonstrate the extent of the problem. Frequently repeated oversights witnessed on many large aerospace projects are then reviewed, with an eye toward what can (and should) be done to avoid the pitfalls. The intent is to empower the reader with information and ideas to prevent software from slaying the giant systems that it is built to support.