IDEAS home Printed from https://ideas.repec.org/a/ids/ijpmbe/v2y2007i1p59-70.html
   My bibliography  Save this article

Risk management models in software engineering

Author

Listed:
  • Subhas C. Misra
  • Uma Kumar
  • Vinod Kumar
  • Mahmud A. Shareef

Abstract

With the tremendous growth in the complexity of software development in the last 10–15 years, the management of risks in software engineering activities is becoming an important and non-trivial issue from three perspectives: project, process and product. Therefore, researchers and practitioners are continually trying to find effective risk management approaches. In this paper, we briefly discuss the principles of risk management in software engineering, review some of the process models popular in the software engineering community, and finally discuss some of the important works conducted recently in this area in the last five years. While writing the paper, we have focused mostly on project, and process-based risks and not on product risks.

Suggested Citation

  • Subhas C. Misra & Uma Kumar & Vinod Kumar & Mahmud A. Shareef, 2007. "Risk management models in software engineering," International Journal of Process Management and Benchmarking, Inderscience Enterprises Ltd, vol. 2(1), pages 59-70.
    • Handle: RePEc:ids:ijpmbe:v:2:y:2007:i:1:p:59-70
    as

    Download full text from publisher

    File URL: http://www.inderscience.com/link.php?id=13318
    Download Restriction: Access to full text is restricted to subscribers.
    ---><---

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

    Citations

    Citations are extracted by the CitEc Project, subscribe to its RSS feed for this item.
    as


    Cited by:

    1. Aven, Terje & Hiriart, Yolande, 2011. "The use of a basic safety investment model in a practical risk management context," Reliability Engineering and System Safety, Elsevier, vol. 96(11), pages 1421-1425.
    2. Aven, Terje, 2015. "On the allegations that small risks are treated out of proportion to their importance," Reliability Engineering and System Safety, Elsevier, vol. 140(C), pages 116-121.
    3. Basit Shahzad & Fazal-e-Amin & Ahsanullah Abro & Muhammad Imran & Muhammad Shoaib, 2021. "Resource Optimization-Based Software Risk Reduction Model for Large-Scale Application Development," Sustainability, MDPI, vol. 13(5), pages 1-17, March.
    4. Aven, T. & Ylönen, M., 2016. "Safety regulations: Implications of the new risk perspectives," Reliability Engineering and System Safety, Elsevier, vol. 149(C), pages 164-171.

    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:ids:ijpmbe:v:2:y:2007:i:1:p:59-70. 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: Sarah Parker (email available below). General contact details of provider: http://www.inderscience.com/browse/index.php?journalID=95 .

    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.