IDEAS home Printed from https://ideas.repec.org/a/eee/reensy/v92y2007i7p902-913.html
   My bibliography  Save this article

Towards a lessons learned system for critical software

Author

Listed:
  • Andrade, J.
  • Ares, J.
  • García, R.
  • Pazos, J.
  • Rodríguez, S.
  • Rodríguez-Patón, A.
  • Silva, A.

Abstract

Failure can be a major driver for the advance of any engineering discipline and Software Engineering is no exception. But failures are useful only if lessons are learned from them. In this article we aim to make a strong defence of, and set the requirements for, lessons learned systems for safety-critical software. We also present a prototype lessons learned system that includes many of the features discussed here. We emphasize that, apart from individual organizations, lessons learned systems should target industrial sectors and even the Software Engineering community. We would like to encourage the Software Engineering community to use this kind of systems as another tool in the toolbox, which complements or enhances other approaches like, for example, standards and checklists.

Suggested Citation

  • Andrade, J. & Ares, J. & García, R. & Pazos, J. & Rodríguez, S. & Rodríguez-Patón, A. & Silva, A., 2007. "Towards a lessons learned system for critical software," Reliability Engineering and System Safety, Elsevier, vol. 92(7), pages 902-913.
    • Handle: RePEc:eee:reensy:v:92:y:2007:i:7:p:902-913
    DOI: 10.1016/j.ress.2006.05.016
    as

    Download full text from publisher

    File URL: http://www.sciencedirect.com/science/article/pii/S0951832006001347
    Download Restriction: Full text for ScienceDirect subscribers only
    File URL: https://libkey.io/10.1016/j.ress.2006.05.016?utm_source=ideas
    LibKey link: if access is restricted and if your library uses this service, LibKey will redirect you to where you can use your library subscription to access this item
    ---><---

    As the access to this document is restricted, you may want to search for a different version of it.

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:eee:reensy:v:92:y:2007:i:7:p:902-913. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Catherine Liu (email available below). General contact details of provider: https://www.journals.elsevier.com/reliability-engineering-and-system-safety .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.