Recently, a formal requirements method called SCR (Software Cost Reduction) was used to specify software requirements of mission-critical components of three NASA systems. The components included a fault protection engine, which determines how a spacecraft should respond to a detected fault; a fault detection, isolation and recovery component, which, in response to an undesirable event, outputs a failure notification and raises one or more alarms; and a display system, which allows a space crew to monitor and control on-orbit scientific experiments. This paper demonstrates how significant and complex requirements of one of the components can be translated into an SCR specification and describes the errors detected when the authors formulated the requirements in SCR. It also discusses lessons learned in using formal methods to document the software requirements of the three components. Based on the authors' experiences, the paper presents several recommendations for improving the quality of requirements specifications of safety-critical aerospace software.


    Zugriff

    Zugriff prüfen

    Verfügbarkeit in meiner Bibliothek prüfen

    Bestellung bei Subito €


    Exportieren, teilen und zitieren



    Titel :

    Applying a Formal Requirements Method to Three NASA Systems: Lessons Learned


    Beteiligte:

    Erschienen in:

    Erscheinungsdatum :

    2007-03-01


    Format / Umfang :

    12936855 byte





    Medientyp :

    Aufsatz (Konferenz)


    Format :

    Elektronische Ressource


    Sprache :

    Englisch



    NASA lessons learned: moving to a more formal process

    Oberhettinger, David J. | NTRS | 2005


    NASA Procurement Lessons Learned

    G. C. Butts | NTIS | 2011


    NASA Materials Related Lessons Learned

    D. Garcia / P. S. Gill / W. W. Vaughan | NTIS | 2002


    NASA Materials Related Lessons Learned

    Garcia, Danny / Gill, Paul S. / Vaughan, William W. | NTRS | 2003


    NASA Procurement Lessons Learned

    Butts, Glenn C. | NTRS | 2011