Abstract

The objective of study is to introduce stepwise regression approach modelling to mitigate and manage the software design process issues in software project by using proposed controls. In addition, the software design process issues were controlled and modelled by using stepwise regression approach except risk 3. Furthermore, we illustrated the design process issues were mitigated by control techniques in Table 40. However, we need to combine more techniques and artificial optimal algorithms to mitigate the issues in software design process.

Keywords:

Design process, risk controls, software risk management, software design issues, stepwise approach modelling,

References

1. Addison, T., 2003. E-commerce project development risks: Evidence from a Delphi survey. Int. J. Inform. Manage., 23(1): 25-40.
   CrossRef    
2. Addison, T. and S. Vallabh, 2002. Controlling software project risks: An empirical study of methods used by experienced project managers. Proceeding of the 2002 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists on Enablement through Technology (SAICSIT, 2002), pp: 128-140.
   
3. Ahmed, A., 2011. Software Project Management: A Process-driven Approach. CRC Press, Taylor and Francis Group, Auerbach Publications, pp: 456.
   CrossRef    
4. Aloini, D., R. Dulmin and V. Mininno, 2007. Risk management in ERP project introduction: Review of the literature. Inform. Manage., 44(6): 547-567.
   CrossRef    
5. Aritua, B., N.J. Smith and D. Bower, 2011. What risks are common to or amplified in programmes: Evidence from UK public sector infrastructure schemes. Int. J. Proj. Manag., 29(3): 303-312.
   CrossRef    
6. Bennatan, E.M., 2006. Catastrophe Disentanglement: Getting Software Projects Back on Track. Addison-Wesley, Upper Saddle River, NJ, pp: 288.
   
7. Boehm, B.W., 1991. Software risk management: Principles and practices. IEEE Software, 8(1): 32-41.
   CrossRef    
8. Boehm, B., 2002a. Boehm's Top 10 2002-Software Risks. The USC Center for Systems and Software Engineering. Retrieved form: http://csse.usc.edu/BoehmsTop10/2006/survey.php. (Accessed on: February 28, 2012).
   Direct Link
9. Boehm, B., 2002b. Software Risk Management: Overview and Recent Developments. pp: 90.
   
10. Boehm, B., 2007. USC CSSE workshop overview: Top 3 software-intensive systems risk items. pp: 34.
    
11. Buckley, R. and J. Caple, 2009. The Theory & Practice of Training. 6th Edn., Kogan page London, Philadelphia. pp: 369.
    
12. Chen, H.G., J.J. Jiang, G. Klein and J.V. Chen, 2009. Reducing software requirement perception gaps through coordination mechanisms. J. Syst. Software, 82(4): 650-655.
    CrossRef    
13. Chen, J.C. and S.J. Huang, 2009. An empirical analysis of the impact of software development problem factors on software maintainability. J. Syst. Software, 82(6): 981-992.
    CrossRef    
14. Cliff Mitchell, 2011. Why Don't We Learn from Our Project Failures. Retrieved from: https://tm.mbs.ac.uk/SearchResults/tabid/56/ArticleID/72/Why-don%E2%80%99t-we-learn-from-our-project-failures.aspx. (Accessed on: March 1, 2012).
    Direct Link
15. Dash, R. and R. Dash, 2010. Risk assessment techniques for software development. Eur. J. Sci. Res., 42(4): 629-636.
    
16. Elzamly, A. and B. Hussin, 2011a. Estimating quality-affecting risks in software projects. Int. Manage. Rev., American Scholars Press, 7(2): 66-83.
    
17. Elzamly, A. and B. Hussin, 2011b. Managing software project risks with proposed regression model techniques and effect size technique. Int. Rev. Comput. Software, 6(2): 250-263.
    
18. Elzamly, A. and B. Hussin, 2013a. Managing software project risks (implementation phase) with proposed stepwise regression analysis techniques. Int. J. Inform. Technol. (IREIT), 1(4): 300-312.
    
19. Elzamly, A. and B. Hussin, 2013b. Managing software project risks (design phase) with proposed fuzzy regression analysis techniques with fuzzy concepts. Int. Rev. Comput. Software, 8(11): 2601-2613.
    
20. Elzamly, A. and B. Hussin, 2014a. An enhancement of framework software risk management methodology for successful software development. J. Theor. Appl. Inform. Technol., 62(2): 410-423.
    
21. Elzamly, A. and B. Hussin, 2014b. Identifying and managing software project risks with proposed fuzzy regression analysis techniques: Maintenance phase. Proceeding of Conference on Management and Engineering (CME, 2014), pp: 14.
    
22. Elzamly, A. and B. Hussin, 2014c. Managing software project risks (planning phase) with proposed fuzzy regression analysis techniques with fuzzy concepts. Int. J. Inform. Comput. Sci. (IJICS), 3: 31-40.
    CrossRef    
23. Elzamly, A. and B. Hussin, 2014d. Evaluation of quantitative and mining techniques for reducing software maintenance risks. Appl. Math. Sci., 8(111): 5533-5542.
    CrossRef    
24. Elzamly, A., and B. Hussin, 2014f. Managing software project risks (analysis phase) with proposed fuzzy regression analysis modelling techniques with fuzzy concepts. J. Comput. Inf. Technol., 22(2): 131-144.
    CrossRef    
25. Elzamly, A. and B. Hussin, 2015a. Classification and identification of risk management techniques for mitigating risks with factor analysis technique in software risk management. Rev. Comput. Eng. Res., 2(1): 22-38.
    CrossRef    
26. Elzamly, A. and B. Hussin, 2015b. Modelling and evaluating software project risks with quantitative analysis techniques in planning software development. J. Comput. Inf. Technol., 23(2): 123-139.
    CrossRef    
27. Elzamly, A., B. Hussin, S.S. Abu Naser and M. Doheir, 2015a. Predicting software analysis process risks using linear stepwise discriminant analysis: Statistical methods. Int. J. Adv. Inform. Sci. Technol., 38(38): 108-115.
    
28. Elzamly, A., B. Hussin and N. Salleh, 2015b. Methodologies and techniques in software risk management approach for mitigating risks: A review. Asian J. Math. Comput. Res., 2(4): 184-198.
    
29. Ewusi-Mensah, K., 2003. Software Development Failures: Anatomy of Abandoned Projects. The MIT Press, Cambridge, MA, pp: 276.
    
30. Fairley, R.E., 2009. Managing and Leading Software Projects. Wiley, Hoboken, NJ, pp: 492.
    CrossRef    
31. Han, W.M. and S.J. Huang, 2007. An empirical analysis of risk components and performance on software projects. J. Syst. Software, 80(1): 42-50.
    CrossRef    
32. Hoffer, J., J. George and J. Valacich, 2011. Modern Systems Analysis and Design. 6th Edn., Prentice Hall, New York, pp: 575.
    
33. House of Commons, 2009. The national offender management information system. Fortieth Report of Session 2008–09, House of Commons Public Accounts Committee, Parliament, pp: 41.
    
34. Huang, S.J. and W.M. Han, 2008. Exploring the relationship between software project duration and risk exposure: A cluster analysis. Inform. Manage., 45(3): 175-182.
    CrossRef    
35. Jalote, P., 2008. A Concise Introduction to Software Engineering. Springer-Verlag, London Ltd., pp: 288.
    
36. Kaur, R. and N. Malhotra, 2013. Estimating the effects of developing wrong software functions using fuzzy cognitive map. Int. J. Comput. Appl., 70(18): 38-41.
    CrossRef    
37. Kettunen, P. and M. Laanti, 2005. How to steer an embedded software project: Tactics for selecting the software process model. Inform. Software Tech., 47(9): 587-608.
    CrossRef    
38. Khanfar, K., A. Elzamly, W. Al-Ahmad, E. El-Qawasmeh, K. Alsamara and S. Abuleil, 2008. Managing software project risks with the chi-square technique. Int. Manage. Rev., 4(2): 18-29.
    
39. Laplante, P.A., 2004. Real-Time Systems Design and Analysis. 3rd Edn., J. Wiley, Hoboken, New Jersey, pp: 505.
    CrossRef    
40. Lyons, T. and M. Skitmore, 2004. Project risk management in the Queensland engineering construction industry: A survey. Int. J. Proj. Manag., 22(1): 51-61.
    CrossRef    
41. Nakatsu, R.T. and C.L. Iacovou, 2009. A comparative study of important risk factors involved in offshore and domestic outsourcing of software development projects: A two-panel Delphi study. Inform. Manage., 46(1): 57-68.
    CrossRef    
42. Pandian, C.R., 2007. Applied Software Risk Management: A Guide for Software Project Managers. Risk Management. Auerbach Publications is an Imprint of the Taylor and Francis Group, pp: 246.
    
43. Paré, G., C. Sicotte, M. Jaana and D. Girouard, 2008. Prioritizing clinical information system project risk factors: A delphi study. Proceeding of the 41st Hawaii International Conference on System Sciences, pp: 1-10.
    CrossRef    
44. Rudd, C., 2010. Planning to Implement Service Management (PISM). TSO (The Stationery Office), pp: 305.
    PMid:19841155    
45. Schmidt, R., K. Lyytinen, M. Keil and P. Cule, 2001. Identifying software project risks: An international delphi study. J. Manage. Inform. Syst., 17(4): 5-36.
    CrossRef    
46. Schwalbe, K., 2010. Information Technology Project Management. 6th Edn., Course Technology, Cengage Learning, Boston, MA, pp: 490.
    
47. Selby, R., 2007. Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management, and Research (Practitioners). 1st Edn., Wiley-IEEE Computer Society, pp: 832.
    CrossRef    
48. Sodhi, J. and P. Sodhi, 2001. IT Project Management Handbook. Management Concepts, Vienna, VA, pp: 264.
    
49. Sumner, M., 2000. Risk factors in enterprise-wide/ERP projects. J. Inform. Technol., 15(4): 317-327.
    CrossRef    
50. Surie, D., 2004. Evaluation and integration of risk management in CMMI and ISO / IEC 15504. Proceeding of the 8th Student Conference in Computing Science, Umeå, Sweden, pp: 14.
    
51. Thomas, S. and H. Uwe, 2010. Agile Software Development: Best Practices for Large Software Development Projects. Springer-Verlag, Berlin, Heidelberg, pp: 203.
    
52. Yogesan, K., P. Brett and M. Gibbons, 2009. Handbook of Digital Homecare. Series in Biomedical Engineering. Springer-Verlag, Berlin, Heidelberg, pp: 363.
    CrossRef    

Competing interests

The authors have no competing interests.

Open Access Policy

This article is distributed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided you give appropriate credit to the original author(s) and the source, provide a link to the Creative Commons license, and indicate if changes were made.

Copyright

The authors have no competing interests.