Advertisement

Software Risk Management: Using the Automated Tools

  • Sergey M. AvdoshinEmail author
  • Elena Y. Pesotskaya
Part of the Progress in IS book series (PROIS)

Abstract

Software development process nowadays faces many challenges and risks. In order to manage risks we need to understand the scope and objectives of the software developments and use the appropriate automated risk management tool. The study addresses software risk management in software development area and an approach to analysis, structuring, and evaluating risk with the help of specialized automated tools. The author provides recommendations on how to define a set of selection criteria for automated tools and analyses the growing demand for service hosting solutions and web-applications, stressing that almost any software including risk management tools can be successfully run using this method.

Keywords

Software risks Risk management Risk management software Risk management tools Web-based applications SaaS solution 

References

  1. 1.
    Chapman, C. B., & Ward, S. C. (2003). Project risk management, processes, techniques and insights (2nd ed.). Chichester: Wiley.Google Scholar
  2. 2.
    Kwak, Y. A., & Stoddard, J. (2003). Project risk management: Lessons learned from software development environment. Technovation, 24, 915–920.CrossRefGoogle Scholar
  3. 3.
    Del Cano, A., & De La Cruz, M. P. (2002). Integrated methodology for project risk management. Journal of Construction Engineering and Management, 128(6), 473–485.CrossRefGoogle Scholar
  4. 4.
    Pipattanapiwong, J. (2004). Development of multi-party risk and uncertainty management process for an infrastructure project. PhD thesis, Kochi University of Technology. Kochi, Japan.Google Scholar
  5. 5.
    Haimes, Y. Y., Kaplan, S., & Lambert, J. H. (2002). Risk filtering, ranking and management framework using hierarchical holographic modeling. Risk Analysis, 22(2), 381–395.CrossRefGoogle Scholar
  6. 6.
    PMI (Project Management Institute). (2004). A guide to the project management body of knowledge (PMBoK). Newtown Square. Pennsylvania.Google Scholar
  7. 7.
    Cooper, D. Tutorial notes: The Australian and New Zealand standard on risk management (AS/NZS 460). Retrieved from May, 2004 http://www.broadleaf.com
  8. 8.
    Conrow, E. H. (2003). Effective risk management: Some keys to success (2nd ed.). Reston, VA: American Institute of Aeronautics and Astronautics.CrossRefGoogle Scholar
  9. 9.
    Lian, X. Software project management – Risk management (Abstraction). http://www.docstoc.com/docs/24840578/Software-Project-Management
  10. 10.
    Avdoshin, S., & Pesotskaya, E. (2011). Business informatization. Managing risks. Moscow: DMK Press. 176 p. [in Russian].Google Scholar
  11. 11.
    Garbani, J.-P., Cecere, M. (2011, May 3). IT infrastructure and operations: The next five years. Cambridge: Forrester Research.Google Scholar

Copyright information

© Springer International Publishing Switzerland 2016

Authors and Affiliations

  1. 1.Software Management Department, School of Software EngineeringNational Research University Higher School of EconomicsMoscowRussian Federation

Personalised recommendations