This paper reports the results of a small study of requirements changes to the onboard software of three spacecraft subsequent to launch. Only those requirement changes that resulted from post-launch anomalies (i.e., during operations) were of interest here, since the goal was to better understand the relationship between critical anomalies during operations and how safety-critical requirements evolve. The results of the study were surprising in that anomaly-driven, post-launch requirements changes were rarely due to previous requirements having been incorrect. Instead, changes involved new requirements: (1) for the software to handle rare events; or (2) for the software to compensate for hardware failures or limitations. The prevalence of new requirements as a result of post-launch anomalies suggests a need for increased requirements-engineering support of maintenance activities in these systems. The results also confirm both the difficulty and the benefits of pursuing requirements completeness, especially in terms of fault tolerance, during development of critical systems.


    Access

    Access via TIB

    Check availability in my library

    Order at Subito €


    Export, share and cite



    Title :

    Evolution of safety-critical requirements post-launch


    Contributors:
    Lutz, R.R. (author) / Mikulski, I.C. (author)


    Publication date :

    2000


    Size :

    6 Seiten, 13 Quellen




    Type of media :

    Conference paper


    Type of material :

    Print


    Language :

    English





    DEVELOPING SAFETY-CRITICAL SOFTWARE REQUIREMENTS FOR COMMERCIAL REUSABLE LAUNCH VEHICLES

    Murray, D. P. / Hardy, T. L. / European Space Agency | British Library Conference Proceedings | 2007


    Empirical analysis of safety - critical software anomalies post-launch

    Sigal, B. / Lutz, R. / Mikulski, C. | NTRS | 2002


    Japanese Safety Requirements for Expendable Launch Vehicle Payload

    Miki, M. / Sekita, R. / Wada, M. et al. | British Library Conference Proceedings | 2010