A comparison of stepwise and fuzzy multiple regression analysis techniques for managing software project risks: Analysis phase

Journal of Computer Science

Volumn 10, Issue 10, 2014, Pages 1725-1742

  Elzamly, Abdelrafe ^a,b   Hussin, Burairah ^a  

^a UNIVERSITI TEKNIKAL MALAYSIA MELAKA   (Malaysia)

^b AL AQSA UNIVERSITY   (Palestine)

Author keywords

Analysis phase; Fuzzy multiple regression analysis; Risk management technique; Software project management; Software risk factors; Software risk management; Stepwise regression analysis techniques

Indexed keywords

EID: 84900459546     PISSN: 15493636     EISSN: None     Source Type: Journal    
DOI: 10.3844/jcssp.2014.1725.1742     Document Type: Article

References (138)

1. Aagedal, J.O., F. den Braber, T. Dimitrakos, B. Gran and D. Raptis et al., 2002. Model-based risk assessment to improve enterprise security. Proceedings of the 6th International Enterprise Distributed Object Computing Conference, Sept. 20-20, IEEE Xplore Press, pp: 51-62. DOI: 10.1109/EDOC.2002.1137696.
2. Addison, T., 2003. E-commerce project development risks: Evidence from a Delphi survey. Int. J. Inform. Manage., 23: 25-40. DOI: 10.1016/S0268-4012(02)00066-X.
3. Addison, T. and S. Vallabh, 2002. Controlling software project risks: An empirical study of methods used by experienced project managers. Proceedings of the Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists on Enablement through Technology, (TET 02), pp: 128-140.
4. Alhawari, S., F. Thabtah, L. Karadsheh and W. Hadi, 2008. A risk management model for project execution. Proceedings of the 9th IIBIMA Conference on Information Management in Modern Organizations, (MMO' 08), pp: 887-893.
5. Aloini, D., R. Dulmin and V. Mininno, 2007. Risk management in ERP project introduction: Review of the literature. Inform. Manage., 44: 547-567. DOI: 10.1016/j.im.2007.05.004.
6. Alyahya, M., R. Ahmad and S. Lee, 2009. Effect of CMMI-based software process maturity on software schedule estimation. Malaysian J. Comput. Sci., 22: 121-137.
7. Anantatmula, V., 2010. Project planning techniques for academic advising and learning. Int. J. Scholarship Teach. Learn., 6: 1-19.
8. 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. Project Manage., 29: 303-312. DOI: 10.1016/j.ijproman.2010.04.004.
9. Azari, A., N. Mousavi and S. Mousavi, 2011. Risk assessment model selection in construction industry. Expert Syst. Applic., 38: 9105-9111. DOI: 10.1016/j.eswa.2010.12.110.
10. Aziz, M. and H. Salleh, 2011. People critical success factors of IT/IS implementation: Malaysian perspectives. World Acad. Sci. Eng. Technol., 80: 75-82.
11. Basha, S. and D. Ponnurangam, 2010. Analysis of empirical software effort estimation models. Int. J. Comput. Sci. Inform. Security 7: 68-77.
12. Bavani, R., 2010. Global software engineering: Challenges in customer value creation. Proceedings of the 5th IEEE International Conference on Global Software Engineering, Aug. 23-26, IEEE Xplore Press, Princeton, NJ., pp: 119-122. DOI: 10.1109/ICGSE.2010.21.
13. Begum, Z., M. Khan, M. Hafiz, M.S. Islam and M. Shoyaib, 2008. Software development standard and software engineering practice: A case study of Bangladesh. J. Bangladesh Acad. Sci., 32: 131-139. DOI: 10.3329/jbas.v32i2.2432.
14. Bennatan, E., 2006. Catastrophe Disentanglement: Getting Software Projects Back on Track. 1st Edn., ADDISON WESLEY Publishing Company Incorporated, Upper Saddle River, ISBN-10: 0321336623, pp: 270.
15. Bhoola, V., S. Hiremath and D. Mallik, 2014. Identifying and evaluation of risks in software projects in Indian IT industries. Int. J. Res. Bus. Technol., 4: 346-353.
16. Blackmore, K. and K. Nesbitt, 2008. Identifying risks for cross-disciplinary higher degree research students. In Proceedings of the 10th Conference on Australasian Computing Education, Jan. 2-25, Wollongong, Australia, pp: 43-52.
17. Boehm, B., 1991. Software risk management: Principles and practices. IEEE Software, 8: 32-41. DOI: 10.1109/52.62930.
18. Boehm, B., 2001. Project termination doesn't equal project failure. IEEE Comput., 33: 94-96. DOI: 10.1109/2.868706.
19. Boehm, B., 2002a. Boehm's top 10 2002-software risks. The USC Center for Systems and Software Engineering.
20. Boehm, B., 2002b. Software risk management: Overview and recent developments. University of Southern California.
21. Boehm, B., 2003. Value-based software engineering. ACM Software Eng. Notes, 28: 1-12.
22. Boehm, B., 2007. USC CSSE workshop overview: Top 3 software-intensive systems risk items. SlideServe.
23. Boehm, B. and V. Basili, 2001. Software defect reduction top 10 list. Computer, 34: 135-137. DOI: 10.1109/2.962984.
24. Boehm, B., B. Clark, E. Horowitz, C. Westland and R. Madachy et al., 1995. Cost models for future software life cycle processes: COCOMO 2.0. Ann. Software Eng., 1: 57-94. DOI: 10.1007/BF02249046.
25. Boehm, B. and R. Ross, 1989. Theory-W software project management principles and examples. IEEE Trans. Software Eng., 15: 902-916. DOI: 10.1109/32.29489.
26. Brandon, D.M., 2006. Project management for modern information systems. Electronic Library, 25: 379-380.
27. Cahill, V., A. Fox, T. Kindberg and B. Noble, 2004. Guest editors' introduction: Building and evaluating ubiquitous system software. IEEE Pervasive Comput., 3: 20-21. DOI: 10.1109/MPRV.2004.1321023.
28. Cantor, M., 1998. Object-Oriented Project Management with UML. 1st Edn., Wiley, New York, ISBN-10: 0471253030, pp: 343.
29. CHAOS, 1995. The Standish group report. CHAOS.
30. Chapman, R. and D. Thomas, 2007. A Guide to Printed and Electronic Resources for Developing a Cost-Effective Risk Mitigation Plan for New and Existing Constructed Facilities. 1st Edn., National Institute of Standards and Technology Building and Fire Research Laboratory, pp: 162.
31. Chen, J. and S. Huang, 2009. An empirical analysis of the impact of software development problem factors on software maintainability. J. Syst. Software, 82: 981-992. DOI: 10.1016/j.jss.2008.12.036.
32. Dash, R. and R. Dash, 2010. Risk assessment techniques for software development. Eur. J. Sci. Res., 42: 629-636.
33. Dom, R., B. Abidin, S. Kareem, S. Ismail and N. Daud, 2012. Determining the critical success factors of oral cancer susceptibility prediction in Malaysia using fuzzy models. Sains Malaysiana, 41: 633-640.
34. Dufner, D., O. Kwon and A. Doty, 1999. Improving software development project team performance: A web-based expert support system for project control. Proceedings of the 32nd Annual Hawaii International Conference on Systems Sciences, Jan. 5-8, IEEE Xplore Press, Maui, HI, USA, pp: 1-10. DOI: 10.1109/HICSS.1999.772622.
35. Dyba, T. and T. Dingsoyr, 2008. Empirical studies of agile software development: A systematic review. Inform. Software Technol., 50: 833-859. DOI: 10.1016/j.infsof.2008.01.006.
36. Dzung, D. and C. Briod, 2005. Shared authorization in industrial automation systems using threshold cryptography. Proceedings of the 10th IEEE Conference on Emerging Technologies and Factory Automation, Sept. 19-22, IEEE Xplore Press, Catania, pp: 867-876. DOI: 10.1109/ETFA.2005.1612764.
37. Elzamly, A. and B. Hussin, 2011a. Estimating qualityaffecting risks in software projects. Int. Manage. Rev., 7: 66-83.
38. Elzamly, A. and B. Hussin, 2011b. Managing software project risks with proposed regression model techniques and effect size technique. Int. Rev. Comput. Software, 6: 250-263.
39. Elzamly, A. and B. Hussin, 2013a. Managing software project risks (Implementation Phase) with proposed stepwise regression analysis techniques. Int. J. Inform. Technol., 1: 300-312.
40. 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: 2601-2613.
41. Elzamly, A. and B. Hussin, 2014a. An enhancement of framework software risk management methodology for successful software development. J. Theoretical Applied Inform. Technol., 62: 17-17.
42. Elzamly, A. and B. Hussin, 2014b. Managing software project risks (Planning Phase) with proposed fuzzy regression analysis techniques with fuzzy concepts. Int. J. Inform. Comput. Sci., 3: 31-40. DOI: 10.14355/ijics.2014.0302.02.
43. Emam, K., 2005. The ROI from Software Quality. 1st Edn., CRC Press, ISBN-10: 1420031201, pp: 296.
44. Fairley, R., 2009. Managing and Leading Software Projects. 1st Edn., Wiley, Los Alamitos, ISBN-10: 0470294558, pp: 492.
45. Ferraro, J., 2012. Project Management for Non-Project Managers. 1st Edn., AMACOM Div American Mgmt Assn, New York, ISBN-10: 0814417361, pp: 242.
46. Galorath, D., 2006. The 10 step software estimation process for successful software planning, measurement and control.
47. Galorath, D. and M. Evans, 2006. Software Sizing, Estimation and Risk Management: When Performance is Measured Performance Improves. 1st Edn., CRC Press, ISBN-10: 0849335930, pp: 576.
48. Grabski, S., S. Leech and B. Lu, 2001. Risks and controls in the implementation of ERP systems. Int. J. Digital Account. Res., 1: 47-68. DOI: 10.4192/1577-8517-v1_3.
49. Grady, J.O., 2010. System Requirements Analysis. 1st Edn., Academic Press, Amsterdam, ISBN-10: 0080457851, pp: 480.
50. Green, R., 2000. Documentation meets version control: An automated backup system for HTML-based help. Proceedings of the 18th Annual ACM International Conference on Computer Documentation: Technology and Teamwork, Sept. 24-27, Cambridge, MA, USA, pp: 541-548.
51. Greenyer, J., A. Sharifloo, M. Cordy and P. Heymans, 2012. Efficient consistency checking of scenariobased product-line specifications. Proceedings of the 20th IEEE International Requirements Engineering Conference, Sept. 24-28, IEEE Xplore Press, Chicago, IL, pp: 161-170. DOI: 10.1109/RE.2012.6345800.
52. Horine, G., 2009. Absolute Beginner's Guide to Project Management. 2nd Edn., Pearson Education, ISBN-10: 0768687446, pp: 432.
53. Gu, X., G. Song and L. Xiao, 2006. Design of a fuzzy decision-making model and its application to software functional size measurement. Proceedings of the International Conference on Computational Intelligence for Modelling Control and Automation and International Conference on Intelligent Agents, Web Technologies and Internet Commerce, Nov. 28-Dec. 1, IEEE Xplore Press, Sydney, NSW, pp: 199-205. DOI: 10.1109/CIMCA.2006.82.
54. Han, W. and S. Huang, 2007. An empirical analysis of risk components and performance on software projects. J. Syst. Software, 80: 42-50. DOI: 10.1016/j.jss.2006.04.030.
55. Hayat, F., M. Bhatt, N. Ehsan, A. Ishaque and S. Ahmed et al., 2010. A methodology to manage the changing requirements of a software project. Proceedings of the International Conference on Computer Information Systems and Industrial Management Applications, Oct. 8-10, IEEE Xplore Press, Krackow, pp: 319-322. DOI: 10.1109/CISIM.2010.5643642.
56. Hill, P., 2010. Practical Software Project Estimation: A Toolkit for Estimating Software Development Effort and Duration. 1st Edn., McGraw Hill Professional, New York, ISBN-10: 0071717927, pp: 312.
57. Hoffer, J., J. George and J. Valacich, 2011. Modern Systems Analysis and Design. 6th Edn., Pearson Education India, ISBN-10: 8131726258, pp: 575.
58. Holcombe, M., 2008. Running an Agile Software Development Project 1st Edn., John Wiley and Sons, ISBN-10: 0470385871, pp: 350.
59. Huang, S. and W. Han, 2008. Exploring the relationship between software project duration and risk exposure: A cluster analysis. Inform. Manage., 45: 175-182. DOI: 10.1016/j.im.2008.02.001.
60. IEEE, 2011. IEEE Guide-Adoption of the Project Management Institute (PMI ®) Standard A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) 4th Edn., The Institute of Electrical and Electronics Engineers, Inc., pp: 508.
61. Islam, S., 2009. Software development risk management model: A goal driven approach. Proceedings of the Doctoral Symposium for ESEC/FSE on Doctoral Symposium, Aug. 24-28, Amsterdam, Netherlands, pp: 5-8. DOI: 10.1145/1595782.1595785.
62. Jalote, P., 2002. Software Project Management in Practice 1st Edn., Addison-Wesley Professional, Boston, ISBN-10: 0201737213, pp: 262.
63. Jiang, G. and Y. Chen, 2004. Coordinate metrics and process model to manage software project risk. Proceedings of the IEEE International Engineering Management Conference, Oct. 21-21, IEEE Xplore Press, Singapore, pp: 865-869. DOI: 10.1109/IEMC.2004.1407505.
64. Jianga, J., G. Kleinb, H.G. Chenc and L. Lind, 2002. Reducing user-related risks during and prior to system development. Int. J. Project Manage., 20: 507-515. DOI: 10.1016/S0263-7863(01)00049-7.
65. Jin, J. and B. Li, 2009. Cooperative multicast scheduling with random network coding in WiMAX. Proceedings of the 17th International Workshop on Quality of Service, Jul. 13-15, IEEE Xplore Press, Charleston, SC, pp: 1-9. DOI: 10.1109/IWQoS.2009.5201384.
66. Jones, C., 2008. Applied Software Measurement: Global Analysis of Productivity and Quality. 3rd Edn., McGraw Hill Professional, New York, ISBN-10: 0071643869, pp: 662.
67. Jones, C., 2009. Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies, 1st Edn., McGraw Hill Professional, New York, ISBN-10: 0071621628, pp: 688.
68. Kamaruddin, A., 2006. Development of an early software project risk assessment application using case-based reasoning. Universiti Teknologi MARA.
69. Kandt, R.K., 2003. Software Requirements Engineering: Practices and Techniques. JPL.
70. Kanjanasanpetch, P. and B. Igel, 2003. Managing knowledge in Enterprise Resource Planning (ERP) implementation. Proceedings of the Managing Technologically Driven Organizations: The Human Side of Innovation and Change Engineering Management Conference, Nov. 2-4, IEEE Xplore Press, pp: 30-35. DOI: 10.1109/IEMC.2003.1252226.
71. Kasurinen, J., O. Taipale and K. Smolander, 2010. Test case selection and prioritization: Risk-based or design-based? Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering and Measurement Sept. 16-17, Bolzano, Italy, pp: 1-10. DOI: 10.1145/1852786.1852800.
72. Keil, M., P. Cule, K. Lyytinen and R. Schmidt, 1998. A framework for identifying software project risks. Commun. ACM, 41: 76-83. DOI: 10.1145/287831.287843.
73. Keil, M., L. Li, L. Mathiassen and G. Zheng, 2008. The influence of checklists and roles on software practitioner risk perception and decision-making. IEEE Comput. Society, 81: 908-919.
74. Keil, M., A. Tiwana and A. Bush, 2002. Reconciling user and project manager perceptions of IT project risk: A Delphi study. Inform. Syst. J., 12: 103-119.
75. Khanfar, K., A. Elzamly, W. Al-Ahmad, E. El-Qawasmeh and K. Alsamara et al., 2008. Managing software project risks with the chi-square technique. Int. Manage. Rev., 4: 18-29.
76. Kontio, J., 2001. Software engineering risk management: A method, improvement framework and empirical evaluation. Computer. Suomen Laatukeskus/the Center for Excellence Purotie.
77. Kouskouras, K. and A. Georgiou, 2007. A discrete event simulation model in the case of managing a software project. Eur. J. Operat. Res., 181: 374-389. DOI: 10.1016/j.ejor.2006.05.031.
78. Kumar, J., A. Mandala, M. Chaitanya and G. Prasad, 2011. Fuzzy logic for software effort estimation using polynomial regression as firing interval. Int. J. Comput. Technol. Applic., 2: 1843-1847.
79. Kumar, R., 2002. Managing risks in IT projects: An options perspective. Inform. Manage., 40: 63-74. DOI: 10.1016/S0378-7206(01)00133-1.
80. Ewusi-Mensah, K., 2003. Software Development Failures: Anatomy of Abandoned Projects. 1st Edn., MIT Press, Cambridge, ISBN-10: 0262050722, pp: 276.
81. Lan, Y. and S. Guo, 2008. Multiple stepwise regression analysis on knowledge evaluation. Proceedings of the International Conference on Management of ECommerce and E-Government, Oct. 17-19, IEEE Xplore Press, Jiangxi, pp: 297-302. DOI: 10.1109/ICMECG.2008.65.
82. Lee, S., 2011. Probabilistic risk assessment for security requirements: A preliminary study. Proceedings of the 5th International Conference on Secure Software Integration and Reliability Improvement, Jun. 27-29, IEEE Xplore Press, Jeju Island, pp: 11-20. DOI: 10.1109/SSIRI.2011.12.
83. Li, M., S. Yu, N. Cao and W. Lou, 2013. Privacypreserving distributed profile matching in proximitybased mobile social networks. IEEE Trans. Wireless Commun., 12: 2024-2033. DOI: 10.1109/TWC.2013.032513.120149.
84. Lientz, B.P. and L. Larssen, 2006. Risk Management for IT Projects: How to Deal with Over 150 Issues and Risks. 1st Edn., Routledge, ISBN-10: 0750682310, pp: 331.
85. Lin, J., Q. Zhuang and C. Huang, 2012. Fuzzy statistical analysis of multiple regression with crisp and fuzzy covariates and applications in analyzing economic data of china. Comput. Econom., 39: 29-49. DOI: 10.1007/s10614-010-9223-1.
86. Linberg, K.R., 1999. Software developer perceptions about software project failure: A case study. J. Syst. Software, 49: 177-192. DOI: 10.1016/S0164-1212(99)00094-1.
87. Liu, D., Q. Wang and J. Xiao, 2009. The role of software process simulation modeling in software risk management: A systematic review. Proceedings of the 3rd International Symposium on Empirical Software Engineering and Measurement, Oct. 15-16, IEEE Xplore Press, Lake Buena Vista, FL, pp: 302-311. DOI: 10.1109/ESEM.2009.5315982.
88. Lyons, T. and M. Skitmore, 2004. Project risk management in the Queensland engineering construction industry: A survey. Int. J. Project Manage., 22: 51-61. DOI: 10.1016/S0263-7863(03)00005-X.
89. Ma, W., L. Liu, W. Feng, Y. Shan and F. Peng, 2009. Analyzing project risks within a cultural and organizational setting. Proceedings of the ICSE Workshop on Leadership and Management in Software Architecture, IEEE Computer Society Washington, DC, USA, pp: 6-14. DOI: 10.1109/LMSA.2009.5074858.
90. Maglyas, A., 2009. Evaluating the success of software development projects in Russia, Ukraine and Belarus. Lappeenranta University of Technology.
91. Martin, C.L., J.L. Pasquier, C.M. Yanez and A.G. Tornes, 2005. Software development effort estimation using fuzzy logic: A case study. Proceedings of the 6th Mexican International Conference on Computer Science, Sept. 26-30, IEEE Xplore Press, pp: 113-120. DOI: 10.1109/ENC.2005.47.
92. Marza, V. and M. Seyyedi, 2009. Fuzzy multiple regression model for estimating software development time. Int. J. Eng. Bus. Manage., 1: 31-34. DOI: 10.5772/6775.
93. Masticola, S., 2007. A simple estimate of the cost of software project failures and the breakeven effectiveness of project risk management. Proceedings of the 1st International Workshop on the Economics of Software and Computation, May 20-26, IEEE Xplore Press, Minneapolis, MN., pp: 6-6. DOI: 10.1109/ESC.2007.1.
94. McConnell, S., 1996. Rapid Development: Taming Wild Software Schedules. 1st Edn., Microsoft Press, Redmond, ISBN-10: 1556159005, pp: 647.
95. Miler, J., 2005. A method of software project risk identification and analysis. Technology. Gdansk University of Technology.
96. Miller, S., 2004. Best practices for software projects: Requirements scrubbing. TechWell Corp.
97. Miotto, O., T. Tan and V. Brusic, 2005. Supporting the curation of biological databases with reusable text mining. Genome Inform., 16: 32-44. PMID: 16901087.
98. Munch, J. and J. Heidrich, 2004. Software project control centers: Concepts and approaches. J. Syst. Software, 70: 3-19. DOI: 10.1016/S0164-1212(02)00138-3.
99. Na, K., J. Simpson, X. Li, T. Singh and K. Kim, 2007. Software development risk and project performance measurement: Evidence in Korea. J. Syst. Software, 80: 596-605. DOI: 10.1016/j.jss.2006.06.018.
100. Nakatsu, R. and C. 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: 57-68. DOI: 10.1016/j.im.2008.11.005.
101. Oda, M., 2011. The characteristics of the use of twitter by beginners: Study of the applicability to the ehealthcare. Proceedings of the International Conference on Systems, Man and Cybernetics, Oct. 9-12, IEEE Xplore Press, Anchorage, AK., pp: 1268-1273. DOI: 10.1109/ICSMC.2011.6083834.
102. Oracle, 2010. A standardized approach to risk improves project outcomes and profitability. Oracle White Paper.
103. Pandian, C.R., 2006. Applied Software Risk Management: A Guide for Software Project Managers. 1st Edn., CRC Press, ISBN-10: 0849305314, pp: 264.
104. Peppen, A. and M. Ploeg, 2000. Practising what we teach: Quality management of systems-engineering education. IEEE Trans. Syst. Man Cybernet., 30: 189-196. DOI: 10.1109/5326.868440.
105. Persohn, K. and D. Brylow, 2011. Interactive real-time embedded systems education infused with applied internet telephony. Proceedings of the 35th IEEE Annual Computer Software and Applications Conference, Jul. 18-22, IEEE Xplore Press, Munich, pp: 199-204. DOI: 10.1109/COMPSAC.2011.33.
106. Popescu, C. and M. Giuclea, 2007. A model of multiple linear regression. Publish. House Romanian Acad., 8: 1-8.
107. Puntambekar, A.A., 2009. Software Engineering. 1st Edn., Technical Publications, ISBN-10: 8184311834, pp: 202.
108. RM: GBP, 2003. Project Management Committee. Risk Management: Guidelines and Best Practices, pp: 19.
109. Rodriguez-Repisoa, L., R. Setchib and J. Salmeronc, 2007. Modelling IT projects success: Emerging methodologies reviewed. Technovation, 27: 582-594. DOI: 10.1016/j.technovation.2006.12.006.
110. Ropponen, J. and K. Lyytinen, 2000. Components of software development risk: How to address them? A project manager survey. IEEE Trans. Software Eng., 26: 98-112. DOI: 10.1109/32.841112.
111. Rudd, C., 2010. ITIL V3 Planning to Implement Service Management. 1st Edn., The Stationery Office, London, ISBN-10: 0113311095, pp: 320.
112. Sarfraz, F., 2009. Managing for a successful project closure. Proceedings of the Portland International Conference on Management of Engineering and Technology, Aug. 2-6, IEEE Xplore Press, Portland, OR, pp: 1392-1395. DOI: 10.1109/PICMET.2009.5262001.
113. Savolainen, P., J. Ahonen and I. Richardson, 2012. Software development project success and failure from the supplier's perspective: A systematic literature review. Int. J. Project Manage., 30: 458-469. DOI: 0.1016/j.ijproman.2011.07.002.
114. Schmidt, R., K. Lyytinen, M. Keil and P. Cule, 2001. Identifying software project risks: An international Delphi study. J. Manage. Inform. Syst., 17: 5-36.
115. Schulmeyer, G., 2008. Handbook of Software Quality Assurance. 4th., Edn., Artech House, Incorporated, Boston, ISBN-10: 1596931868, pp: 464.
116. Schwalbe, K., 2010. Information Technology Project Management, Revised. 6th., Edn., Cengage Learning, Boston, MA., ISBN-10: 1111221758, pp: 704.
117. Selby, R.W., 2007. Software Engineering: Barry W. Boehm's Lifetime Contributions to Software Development, Management and Research. 1st Edn., John Wiley and Sons, Hoboken, N.J., ISBN-10: 047014873X, pp: 818.
118. Sentas, P., L. Angelis and I. Stamelos, 2003. Multinomial logistic regression applied on software productivity prediction. Proceedings of the 9th Panhellenic Conference in Informatics, (PCI' 03), pp: 1-12.
119. Shand, R.M., 1994. User manuals as project management tools. II. Practical applications. IEEE Trans. Profess. Commun., 31: 123-142. DOI: 10.1109/47.317478.
120. Smith, N., T. Merna and P. Jobling, 2006. Managing Risk in Construction Projects. 2nd Edn., Blackwell Publishing, pp: 244.
121. Sodhi, J. and P. Sodhi, 2001. IT Project Management Handbook. 1st Edn., Management Concepts, ISBN-10: 1567260985, pp: 350.
122. SPM: MT, 2004. SE Project 2003/2004 group E. Software project management: methodologies and techniques.
123. Strawbridge, C., 2005. Project management in large collaborations: SNS lessons learned for ITER. Proceedings of the 21st IEEE/NPS Symposium on Fusion Engineering, (SFE' 05), IEEE Xplore Press, Knoxville, TN., pp: 1-5. DOI: 10.1109/FUSION.2005.252858.
124. Sumner, M., 2000. Risk factors in enterprise-wide/ERP projects. J. Inform. Technol., 15: 317-327. DOI: 10.1080/02683960010009079.
125. Surie, D., 2004. Evaluation and integration of risk management in CMMI and ISO/IEC 15504. Proceedings of the 8th Student Conference in Computing Science, (CCS' 04), Umeå, Sweden, pp: 14-14.
126. Stensrud, E., 2003. A further empirical investigation of the relationship between MRE and project size.
127. Taylor, J., 2004. Managing Information Technology Projects: Applying Project Management Strategies to Software, Hardware and Integration Initiatives, 1st Edn., American Management Association, New York, ISBN-10: 0814408117, pp: 274.
128. Tayntor, C.B., 2006. Successful Packaged Software Implementation. 1st Edn., CRC Press, ISBN-10: 0849334101, pp: 336.
129. Tomczyk, C., 2005. Project Manager's Spotlight on Planning. 1st Edn., Wiley, San Francisco, ISBN-10: 0782144136, pp: 208.
130. Tsui, F.F., 2004. Managing Software Projects. 1st Edn., Jones and Bartlett Learning, Sudbury, ISBN-10: 0763725463, pp: 337.
131. Veracode, 2008. IT risk management guide to software risk assessments and audits. Information Systems Veracode.
132. Verner, J., K. Cox and S.J. Bleistein, 2006. Predicting good requirements for in-house development projects. Proceedings of the ACM/IEEE International Symposium on Empirical Software Engineering, Sept. 21-22, Rio de Janeiro, Brazil, pp: 154-163. DOI: 10.1145/1159733.1159758.
133. Wallace, L. and M. Keil, 2004. Software project risks and their effect on outcomes. Commun. ACM, 47: 68-73. DOI: 10.1145/975817.975819.
134. Webern, P., G. Medina-Oliva, C. Simon and B. Iung, 2010. Overview on Bayesian networks applications for dependability, risk analysis and maintenance areas. Eng. Applic. Artificial Intell., 42: 115-125. DOI: 10.1016/j.engappai.2010.06.002.
135. Westfall, L., 2001. Software Risk Management. 1st Edn., Westfall Team, pp: 8.
136. Westfall, L., 2006. Software Requirements Engineering: What, Why, Who, When and How. 1st Edn., pp: 14.
137. Yassin, A., 2010. Organizational Information Markets: Conceptual Foundation and an Approach for Software Project Risk Management. University of South Florida.
138. Zhou, N., J. Pierre and D. Trudnowski, 2012. A stepwise regression method for estimating dominant electromechanical modes. IEEE Trans. Power Syst., 27: 1051-1059. DOI: 10.1109/TPWRS.2011.2172004.