{"references": ["Rita C. Nienaber, Andries Barnard, \"A Generic AgentFramework to\nSupport the Various Software Project Management Processes\",\nInterdisciplinary Journal of Information, Knowledge, and Management, Vol. 2, 2007", "Ronald P. Higuera, Yacov Y. Haimes, \"Software Risk Management\",\nCarnegie Mellon University, Pittsburgh, 1996", "Ray C.Williams, Goerge J.Pandelios, Sandra G.Behrens, \"Software Risk\nEvaluation Method Description\", version 2.0, Software Engineering\nInstitute,Carnegie Mellon University, 1999", "Anatoliy Antonov, Vladimir Nikolov, Yanka Yanakieva, \"Risk Simulation\nin Project Management System\", International Conference on Computer\nSystems and Technologies- Compsystech, 2006", "Barry W. Boehm, \"Software Risk Management Principles and Practices\",\nDefense Advanced Research Projects Agency, IEEE Software, 8(1): 1991,\nPP. 32-41", "Roger S. Pressman, Ph.D., \"Software Engineering a Practitioners\nApproach\", 5th Edition, McGraw-Hill, 2001, pp. 145-159", "Marcio de Oliveira Barros, Claudia Maria Lima Werner, Guilherme Horta\nTravassos,\" Supporting Risks in Software Project Management\", The\nJournal of Systems and Software, Published by Elsevier Inc, 2002", "Ayad Ali Keshlaf, Khairuddin Hashim, \"A Model and Protorype Tool to\nManage Software Risks\", First Asia-Pasific Conferance IEEE, 2000", "Jyrki Kontio, \"The Riskit Method for Software Risk Management\", version\n1.00, Institute for Advanced Computer Studies and Department of\nComputer Science, University Of Maryland ,1999\n[10] Linda. Westfal, \"Software Risk Management\", the Westfal Team, 2001\n[11] Jakub Miller, Janusz Gorski, \"Risk Identification Patterns for Software\nProjects\", Published in Foundations of Computing and Decision Sciences,\nVol. 29, No. 1-2, 2004, PP. 115-131\n[12] Lawrence E. Hyatt, Linda H. Rosenberg, Ph.D., \"A Software Quality\nModel and Metrics for Identifying Project Risks and Assessing Software\nQuality\", 1996\n[13] Yudistira Asnar, Paolo Giorgini, \"Risk Analysis as part of the\nRequirements Engineering Process\" University of Trento, Department of\nInformation and Communication Technology, 2007\n[14] Bryan L. McKinney, David R. Engfer, \"Formulating Risk into Research\nand Engineering Projects\", Crystal Ball User Conference, 2004\n[15] Aagedal J. O., den Braber F., Dimitrakos T., Gran B. A., Raptis D., Stolen\nK., \"Model-based Risk Assessment to Improve Enterprise Security\", 5th\nInternational Enterprise Distributed Object Computing Conference ,\nSwitzerland, IEEE, 2002, PP. 51-62\n[16] Marvin J. Carr, Suresh L. Konda, Ira Monarch, F.Carol Ulrich, Clay\nF.Walker, \"Taxonomy-Based Risk Identification\", Carnegie Mellon\nuniversity, Pittsburgh Pennsylvania, 1993\n[17] Robert Armstrong, Gillian Adens, \"Management Software Project Risk\",\n2004\n[18] Hu Yong, Chen Juhua, Rong Zhenbang, Mei Liu, Xie Kang, \"A Neural\nNetworks Approach for Software Risk Analysis\", 2006\n[19] Daniel D. Galorath, Michael W. Evans, \"Software Sizing Estimation and\nRisk Management\", Auerbach Publications, United States of America, 2006, pp. 339-393\n[20] Philippe Kruchten, \"The Rational Unified Process an Introduction\",\nThird edition, Addison Wesley, 2003, chapter 7\n[21] C.Ravindranath Pandian, \"Applied Software Risk Management a Guide\nfor Software Project Managers\", Auerbach Publications, United States of\nAmerica, 2007, Chapters 2,3,5\n[22] John D. McGregor, David A. Sykes, \"A Practical Guide to Testing\nObject-Oriented Software\", Addison-Wesley, 2001, pp. 87-92\n[23] Yacov Y. Haimes, \"Risk Modeling, assessment, and Management\",\nsecond edition, John Wiley & Sons, INC., Publication, 2004, pp. 525-540\n[24] Nikolaos Limnios, \"Fualt Trees\", Published in Great Britain and United\nstates by ISTE Ltd, 2007, chapters 3 and 5"]}

Despite various methods that exist in software risk management, software projects have a high rate of failure. When complexity and size of the projects are increased, managing software development becomes more difficult. In these projects the need for more analysis and risk assessment is vital. In this paper, a classification for software risks is specified. Then relations between these risks using risk tree structure are presented. Analysis and assessment of these risks are done using probabilistic calculations. This analysis helps qualitative and quantitative assessment of risk of failure. Moreover it can help software risk management process. This classification and risk tree structure can apply to some software tools.