An enhancement of framework software risk management methodology for successful software development

Journal of Theoretical and Applied Information Technology

Volumn 62, Issue 2, 2014, Pages 410-423

  Elzamly, Abdelrafe ^a   Hussin, Burairah ^a  

^a UNIVERSITI TEKNIKAL MALAYSIA MELAKA   (Malaysia)

Author keywords

Risk; Risk management techniques; Software development lifecycle; Software project management; Software risk factors; Software risk management methodology; Statistical and mining techniques

Indexed keywords

EID: 84898799706     PISSN: 19928645     EISSN: 18173195     Source Type: Journal    
DOI: None     Document Type: Article

References (78)

1. D. McNair, "Controlling risk," Magazine Ubiquity, vol. 2001, no. January, ACM New York, NY, USA, 01-Jan-2001.
2. K. Schwalbe, Information Technology Project Management, Sixth. course technology,cengage learning, 2010, p. 490.
3. J. Miler, "A Method of Software Project Risk Identification and Analysis," Gdansk University of Technology, 2005.
4. J. Miler and J. Gorski, "Supporting Team Risk Management in Software Procurement and Development Projects," in 4th National Conference on Software Engineering, 2002.
5. C. R. Pandian, Applied software risk management: a guide for software project managers. Auerbach Publications is an imprint of the Taylor & Francis Group, an informa business, 2007, p. 246.
6. S. Masticola, "A Simple Estimate of the Cost of Software Project Failures and the Breakeven Effectiveness of Project Risk Management," 2007 First Int. Work. Econ. Softw. Comput., May 2007.
7. J. Taylor, Managing Information Technology Projects: Applying Project Management Strategies to Software, Hardware, and Integration Initiatives. AMACOM c 2004, 2004, p. 274.
8. J. Sodhi and P. Sodhi, IT Project Management Handbook. Management Concepts, 2001, p. 264.
9. B. Boehm, "Value-based software engineering," ACM SIGSOFT Softw. Eng. Notes, vol. 28, no. 2, p. 3, Mar. 2003.
10. W. Al-ahmad, K. Al-fagih, K. Khanfar, K. Alsamara, S. Abuleil, and H. ABU-salem, "A Taxonomy of an IT Project Failure: Root Causes," Manage. Rev., vol. 5, no. 1, pp. 93-104, 2009.
11. N. Gorla and S.-C. Lin, "Determinants of software quality: A survey of information systems project managers," Inf. Softw. Technol., vol. 52, no. 6, pp. 602-610, Jun. 2010.
12. J. Gulla, "Seven Reasons Why Information Technology Projects Fail," 2011.
13. C. Jones, Applied Software Measurement Global Analysis of Productivity and Quality, Third Edit., no. Third Edition. McGraw-Hill Companies., 2008, p. 662.
14. A. Taimour, "Why IT Projects Fail," 2005.
15. P. Savolainen, J. Ahonen, and I. Richardson, "Software development project success and failure from the supplier' s perspective: A systematic literature review," Int. J. Proj. Manag., p. 12, 2011.
16. J. Miler and J. Gorski, "Implementing risk management in software projects," in 3rd National Conference on Software Engineering, 2001.
17. R. Dash and R. Dash, "Risk Assessment Techniques for Software Development," Eur. J. Sci. Res., vol. 42, no. 4, pp. 629-636, 2010.
18. M. Keil, P. Cule, K. Lyytinen, and R. Schmidt, "Aframework for Identifying Software Project Risks," Commun. ACM, vol. 41, no. 11, 1998.
19. "Third Quarter Research Report," 2004.
20. "First Quarter Research Report," 2007.
21. J. Dominguez, "The CHAOS Report 2009 on IT Project Failure," 2009.
22. T. Clancy, "The standish group report," 1995.
23. H. Costa, M. Barros, and G. Travassos, "A risk based economical approach for evaluating software project portfolios," ACM SIGSOFT Softw. Eng. Notes, vol. 30, no. 4, p. 1, Jul. 2005.
24. I. S. Magazine, "Why Software Fails," IEEE Spectrum Magazine, 2009.
25. R. Charette, "Why Software Fails," 2006.
26. T. Clancy, "The standish group report c," 1995.
27. N. White, ICT BUSINESS DEVELOPMENT "Market Mapping of the Palestinian ICT Sector the Opportunities for Partnerships in the Region," 2nd Editio. Mercy Corps Knowledge Based Transformation Programs, 2010, p. 86.
28. D. Remenyi and A. Heafield, "Business process re-engineering: some aspects of how to evaluate and manage the risk exposure," Int. J. Proj. Manag., vol. 14, no. 6, pp. 349-357, Dec. 1996.
29. A. Z. B. Kamaruddin, "Development of an Early Software Project Risk Assessment Application Using Case-Based Reasoning," Universiti Teknologi MARA, 2006.
30. J. Dhlamini, I. Nhamu, and A. Kachepa, "Intelligent Risk Management Tools for Software Development," Risk Manag., pp. 33-40, 2009.
31. G. Conroy and H. Soltan, "ConSERV, a project specific risk management concept," Int. J. Proj. Manag., vol. 16, no. 6, pp. 353-366, Dec. 1998.
32. W. Ma, L. Liu, W. Feng, Y. Shan, and F. Peng, "Analyzing project risks within a cultural and organizational setting," in 2009 ICSE Workshop on Leadership and Management in Software Architecture, 2009, pp. 6-14.
33. V. Tummala and B. John, "Applying a Risk Management Process (RMP) to manage cost risk for an EHV transmission line project," Int. J. Proj. Manag., vol. 17, no. 4, pp. 223-235, Aug. 1999.
34. Oracle, "A Standardized Approach to Risk Improves Project Outcomes and Profitability," 2010.
35. L. Sarigiannidis, "Software Development Project Risk Management: A New Conceptual Framework," J. Softw. Eng. Appl., vol. 04, no. 05, pp. 293-305, 2011.
36. T. Merna and F. Al-Thani, Corporate Risk Management and Optimal Hedging Disclosure, Second. John Wiley and Sons, 2008.
37. T. Aven, Risk Analysis: Assessing Uncertainties Beyond Expected Values and Probabilities. John Wiley & Sons, Inc., 2008, p. 204.
38. M. Fan, N.-P. Lin, and C. Sheu, "Choosing a project risk-handling strategy: An analytical model," Int. J. Prod. Econ., vol. 112, no. 2, pp. 700-713, Apr. 2008.
39. P. Bannerman, "Risk and risk management in software projects: A reassessment," J. Syst. Softw., vol. 81, no. 12, pp. 2118-2133, Dec. 2008.
40. O. Mizuno, E. Shigematsu, Y. Takagi, and T. Kikuno, "On Estimating Testing Effort Needed to Assure FieldQuality in Software Development," Proc. 13 th Int. Symp. Softw. Reliab. Eng. (ISSRE'02, p. 139, 2002.
41. A. Dias-Neto and G. Travassos, "Evaluation of {model-based} testing techniques selection approaches: An external replication," in 2009 3rd International Symposium on Empirical Software Engineering and Measurement, 2009, pp. 269-278.
42. Z. Begum, M. S. A. Khan, M. Hafiz, M. S. Islam, and M. Shoyaib, "Sofware Development Standard and Software Engineering Practice: A Case Study of Bangladesh," J. Bangladesh Acad. Sci., vol. 32, no. 2, pp. 131-139, May 2008.
43. K. Padayachee, "An Interpretive Study of Software Risk Management Perspectives," in Annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology, 2002, pp. 118-127.
44. Veracode, "IT Risk Management: Guide to Software Risk Assessments and Audits," 2008.
45. V. Holzmann and I. Spiegler, "Developing risk breakdown structure for information technology organizations," Int. J. Proj. Manag., Jun. 2010.
46. T. Arnuphaptrairong, "Top Ten Lists of Software Project Risks: Evidence from the Literature Survey," in proceedings of the Intrnational multi conference of Engineers and Computer Scientists 2011 (IMECS 2011), 2011, vol. I, p. 6.
47. Oracle white paper, "Successfully Managing Contract Risk by Forming Win- Win Relationships," 2009.
48. P. Jalote, Software Project Management in Practice. Addison Wesley, 2002, p. 288.
49. A. Azari, N. Mousavi, and S. F. Mousavi, "Risk assessment model selection in construction industry," Expert Syst. Appl., no. December, Dec. 2010.
50. B. Boehm, "Software Risk Management: Principles and Practices," Management, no. January, 1991.
51. B. Boehm and R. Ross, "Theory-W Software Project Management: Princioles and Examples," vol. 15, no. 7, pp. 902-916, 1989.
52. S. Islam, "Software Development Risk Management Model - A Goal Driven Approach," Development, pp. 5-8, 2009.
53. J. Miler and J. Gorski, "Risk-driven Software Process Improvement - a Case Study," in 11th European Software Process Improvement Conference EuroSPI'2004, 2004, no. 4, pp. 1-7.
54. X. Lu and Q. Ma, "Risk analysis in software development project with owners and contractors," IEEE Int. Eng. Manag. Conf., vol. 4, pp. 789-793, 2004.
55. T. Wu, J. Blackhurst, and V. Chidambaram, "A model for inbound supply risk analysis," Comput. Ind., vol. 57, pp. 350-365, Jan. 2006.
56. J. Hallows, Information Systems Project Management: How to Deliver Function and Value in Information Technology Projects, Secondi. AMACOM, 2005, p. 304.
57. C. Dawson, Projects in Computing and Information Systems A Student' s Guide, First. England: Pearson Education Limited, 2005.
58. A. Sharif and S. Basri, "A Study on Risk Assessment for Small and Medium Software Development Projects," Int. J. New Comput. Archit. their Appl., pp. 325-335, 2011.
59. J. Bennett, G. Bohoris, E. Aspinwall, and R. Hall, "Risk analysis techniques and their application to software development," Eur. J. Oper. Res., vol. 95, no. 3, pp. 467-475, Dec. 1996.
60. Oracle, "More Realistic Estimating: Separating Risks and Opportunities from Uncertainty," 2009.
61. M. Holcombe, Running an Agile Software Development Project. John Wiley & Sons, Inc., 2008, p. 306.
62. S. Du, M. Keil, L. Mathiassen, Y. Shen, and A Tiwana, "Attention-shaping tools, expertise, and perceived control in IT project risk assessment," Decis. Support Syst., vol. 43, no. 1, pp. 269-283, Feb. 2007.
63. P. Webern, G. Medina-Oliva, C. Simon, and B. Iung, "Overview on Bayesian networks applications for dependability, risk analysis and maintenance areas," Eng. Appl. Artif. Intell., Jul. 2010.
64. B. Berenbach, D. J. Paulish, J. Kazmeier, and A. Rudorfer, Software & Systems Requirements Engineering: In Practice. McGraw-Hill Companies., 2009, p. 321.
65. J. Deng and Y. Bian, "Constructing a Risk Management Mechanism Model of ERP Project Implementation," in 2008 International Conference on Information Management, Innovation Management and Industrial Engineering, 2008, pp. 72-77.
66. A. Zafra-Cabeza, M. Ridao, and E. Camacho, "An algorithm for optimal scheduling and risk assessment of projects," Control Eng. Pract., vol. 12, no. 10, pp. 1329-1338, Oct. 2004.
67. John Horch, Practical Guide to Software Quality Management. ARTECH HOUSE, INC., 2003, p. 286.
68. S. H. Kan, Metrics and Models in Software Quality Engineering, Second. Addison Wesley, 2002, p. 560.
69. J. Walewski, "International Project Risk Assessment: Methods, Procedures, and Critical Factors," 2003.
70. E. Bennatan, Catastrophe Disentanglement: Getting Software Projects Back on Track. Addison Wesley Professional, 2006, p. 288.
71. E. W. T. Ngai and F. K. T. Wat, "Fuzzy decision support system for risk analysis in e-commerce development," Decis. Support Syst., vol. 40, no. 2, pp. 235-255, Aug. 2005.
72. L. Cooper, "A research agenda to reduce risk in new product development through knowledge management: a practitioner perspective," J. Eng. Technol. Manag., vol. 20, no. 1-2, pp. 117-140, Jun. 2003.
73. G. Buyukozkan and D. Ruan, "Choquet integral based aggregation approach to software development risk assessment," Inf. Sci. (Ny)., vol. 180, no. 3, pp. 441-451, Feb. 2010.
74. D. Houston, G. Mackulak, and J. Collofello, "Stochastic simulation of risk factor potential effects for software development risk management," J. Syst. Softw., vol. 59, no. 3, pp. 247-257, Dec. 2001.
75. K. Khanfar, A. Elzamly, W. Al-Ahmad, E. El-Qawasmeh, K. Alsamara, and S. Abuleil, "Managing Software Project Risks with the Chi-Square Technique," Manage. Rev., vol. 4, no. 2, pp. 18-29, 2008.
76. A. Elzamly and B. Hussin, "Managing Software Project Risks with Proposed Regression Model Techniques and Effect Size Technique," Int. Rev. Comput. Softw., vol. 6, no. 2 March, pp. 250-263, 2011.
77. A. Elzamly and B. Hussin, "Managing Software Project Risks (Implementation Phase) with Proposed Stepwise Regression Analysis Techniques," Int. J. Inf. Technol., vol. 1, no. 4, 2013.
78. A. Elzamly and B. Hussin, "Managing Software Project Risks (Design Phase) with Proposed Fuzzy Regression Analysis Techniques with Fuzzy Concepts.pdf," Int. Rev. Comput. Softw., vol. 8, no. 11, 2013.